Security

Effective November 16, 2026 · Last updated November 16, 2026

We build Loft so that your files stay yours and stay safe. This page describes how we protect data and how to report a problem.

How Loft is built to be safe

Encryption in transit. All connections between the app, our backend, the sync server, and storage use TLS.

Encryption at rest. Files are stored in Cloudflare R2, which encrypts objects at rest, and Loft also seals each drive's files with keys its servers hold. This is not end-to-end encryption: Loft's servers can decrypt your files to serve them to you.

Content addressing. Files are split into chunks named by the hash of their contents. Bytes are verified against their hash on the way into and out of every cache tier, so a corrupted or tampered chunk is detected and never served.

Short-lived, scoped credentials. The app never holds a long-lived storage key. To read or write, a device exchanges its token for storage credentials that are scoped to a single drive's bucket and expire within an hour. The parent storage key never leaves our backend.

Isolation. Each drive is a separate storage bucket, and access is checked per organization, so one customer's credentials cannot reach another's data.

Revocable devices. Each Mac you connect has its own token. You can revoke a lost or stolen device from your account without affecting your others; revoking it also ends that device's sessions.

Least privilege and rate limiting. Authentication is handled by a dedicated identity provider (WorkOS); our backend issues its own scoped tokens. Sensitive endpoints are rate-limited to resist abuse and credential-stuffing.

Our practices

  • Access to production systems is limited to the people who run Loft.
  • Every change is checked automatically for known-vulnerable dependencies, leaked credentials, and common security mistakes before it ships.
  • Our servers keep audit records and are monitored around the clock, with alerts on errors and downtime.
  • The database is backed up every night to a separate provider, under a lock that stops the backups being changed or deleted for 30 days, and we have practiced restoring it.

Subprocessors

We rely on the vetted providers listed in the Privacy Policy, each under a data-processing agreement.

Data location

Files are stored in Cloudflare R2. Our backend, database, and backups run in the United States.

Reporting a vulnerability

We welcome reports from security researchers. Email security@loftfs.com with enough detail to reproduce the issue. Please give us reasonable time to fix it before public disclosure, and do not access or modify other users' data while testing. We will acknowledge your report and keep you updated. We will not take legal action against research done in good faith under these rules.

Incident response

If we become aware of a breach affecting your data, we will notify affected users and regulators as required by law and without undue delay, and describe what happened and what we are doing about it.

Contact

security@loftfs.com