Security model

Yogfile minimizes the identity needed to operate a drive. That makes credential handling simple, but it also makes the account number sensitive.

Account credential

The complete 16-digit account number is a bearer-style root credential while MFA is disabled. The service stores a keyed blind index and the last four digits, not the recoverable complete number.

Never place the complete number in:

• source code or environment files committed to version control;
• prompts, agent memory, logs, analytics, or screenshots;
• URLs, issue trackers, Discord, or support email;
• shell arguments visible to other local processes.

Optional MFA

MFA is off by default. Enabling TOTP returns a secret and ten recovery codes once. Store the recovery codes before confirming setup. Future sessions require either a current authenticator code or one unused recovery code.

Yogfile has no email-based recovery. Losing the authenticator and every recovery code can make the account permanently inaccessible.

Device sessions

Access tokens last 24 hours. A trusted client can receive a revocable device token and rotate it for a new session. Revoking a device does not delete files.

Signed links

A download link is a short-lived capability. Its expiry limits the link, not the file. Moving a file to Trash prevents new links and closes its stable public page, but a capability already issued remains valid until its signed expiry.

Trash and deletion

Deleted files, folders, and drives remain recoverable in Yogfile Trash for 30 days. Purge is permanent. Lifecycle rules are optional and separate from manual deletion.

Reporting a problem

For security issues, contact security@yogfile.com. For privacy requests, contact privacy@yogfile.com. Never include the complete account number.