Security

    What protects your files, stated precisely

    This page follows a file from upload to expiry: what is encrypted, with what, who holds the key, and what we can still see. It is written from the code that runs in production, and it lists what we have not done yet.

    Updated November 13, 2026

    TLS 1.3 in transit
    AES-256 at rest
    AES-256-GCM end to end, optional
    Stored in Ireland (EU)

    Every transfer

    On by default, on every plan

    In transit
    TLS 1.3, with TLS 1.2 as the minimum. Older protocol versions are refused, and HSTS is enforced for two years.
    At rest
    Files are stored encrypted with AES-256 by our storage provider, in the European Union (Ireland).
    Storage
    The files you send or keep in your Vault sit in private storage. Nothing is served from a public folder.
    Link
    Each transfer link carries a random 256-bit token.
    Download
    The server checks the token, the expiry, the status and the password, then issues a signed URL valid for 24 hours.
    Database
    Row Level Security is enabled on the tables that hold transfers, files, recipients and Vault documents.

    In this default mode the storage keys are held on the server side, as with most file services: your files are protected from outsiders, and technically readable by us. We do not open, scan or analyse them. When that is not enough for a document, switch on end-to-end encryption.

    End-to-end encryption

    Switch it on and the key is created in your browser

    Your browser generates a 256-bit key with the Web Crypto API and encrypts each file with AES-256-GCM before upload, in 5 MB chunks, each with its own random nonce and authentication tag. One key per transfer.

    The key is placed after the # in the link. Browsers do not send that part of a URL to servers, and we strip it from anything our monitoring tools record. Sandra stores the ciphertext and never stores the key.

    Your recipient's browser downloads the ciphertext and decrypts it locally.

    Available on every plan, including Free.

    The limits

    What end-to-end encryption does not cover

    So you can decide with the full picture.

    Delivery
    Sandra does not email end-to-end encrypted transfers. You copy the link and send it yourself. That is what keeps the key away from our servers and from our email provider.
    Metadata
    File names, sizes and types, the transfer title and message, and recipient email addresses are not end-to-end encrypted. We need them to deliver the transfer.
    Scope
    End-to-end encryption applies to transfers. Vault documents and file requests are protected by TLS and encryption at rest.
    Lost link
    We keep no copy of the key. If the link is lost, we cannot decrypt the files for you.

    Access

    Passwords, expiry and limits

    Password (Pro)
    Stored as a bcrypt hash and checked on the server before any download, with 10 attempts allowed per 15 minutes per IP address. A second copy is kept encrypted so that you can look the password up again in your dashboard.
    Two-factor authentication
    Optional on every plan, with an authenticator app. Once it is on, sign-in asks for a 6-digit code, and the database, file storage and server functions refuse any session that has not entered it. Ten single-use recovery codes are issued at setup for a lost phone.
    Expiry
    Free links expire after 7 days. On paid plans you choose how long a link lasts. Once a link has expired, the server refuses the download.
    Deletion
    Once a free or anonymous transfer has expired, a daily job deletes its files from storage. Paid accounts keep their files until they delete them.
    Sending without an account
    Rate limited per IP address and per email address: 5 transfers an hour, and 5 GB a day per email address.
    Account deletion
    Deleting your account cancels any subscription and removes your transfer files, Vault files and logo from storage.

    Privacy

    We store your files and deliver them. Nothing else.

    AI
    Your files are never used to train AI models, ours or anyone else's, and no AI system reads them. The same commitment is written in our Privacy Policy and our Terms.
    Scanning
    No content scanning, no OCR, no indexing of what is inside your files. That also means no malware scan: open files only from senders you trust.
    Advertising
    No ads, no advertising pixels, no cross-site trackers.
    Monitoring
    Page analytics by Vercel and error monitoring by Sentry. Download tokens and encryption keys are removed from URLs before anything is sent to either.

    Infrastructure

    Who processes what

    Supabase
    Database, file storage and authentication, hosted in Ireland (AWS eu-west-1).
    Vercel
    Website hosting and page analytics.
    Stripe
    Payments. Card numbers go to Stripe and never reach Sandra.
    Resend
    Delivery of transfer and account emails.
    Sentry
    Error monitoring, stored in the EU (Germany).
    Google, Microsoft
    Only if you sign in with Google, or import files from Google Drive or OneDrive.

    Not yet

    What Sandra does not have today

    Independent audit
    No third-party penetration test has been published. Internal security reviews were carried out in May and June 2026.
    Certifications
    Sandra itself holds no SOC 2 or ISO 27001 certification.
    Security keys and passkeys
    Not supported. Two-factor authentication works with authenticator apps only, and a team owner cannot yet require it for every member.

    Found a vulnerability? Write to us through the contact form with the subject Security. Every report is read.

    Common questions

    Security questions

    Can Sandra read my files?

    By default, files are encrypted in transit and at rest with keys held on the server side, so they are technically readable by us, as with most file services. We do not open, scan or analyse them. With end-to-end encryption on, we store only ciphertext, and the key never reaches our servers.

    Is the encryption key stored anywhere on Sandra's side?

    No. The key is generated in your browser and carried in the part of the link after the #. Browsers do not send that part to servers, and Sandra never emails an end-to-end encrypted link: you share it yourself, so the key does not reach us.

    Where are files stored?

    In the European Union, in Ireland, in the AWS eu-west-1 region through Supabase.

    What happens when a link expires?

    The server refuses every download request for that link. For free and anonymous transfers, the files are then deleted from storage within a day. Paid accounts keep their files until they delete them.

    Does Sandra scan files for viruses?

    No. Sandra does not open file contents, so it does not scan them. Treat a file received through Sandra like any attachment and open it only if you trust the sender.

    Does Sandra support two-factor authentication?

    Yes, on every plan. Turn it on in Settings with an authenticator app such as Google Authenticator, Microsoft Authenticator or 1Password. Sign-in then asks for a 6-digit code, and ten single-use recovery codes cover a lost phone. Security keys and passkeys are not supported yet.

    How do I report a security issue?

    Through the contact form, with the subject Security. Describe what you found and how to reproduce it. Every report is read.

    Send a file and check for yourself

    No account needed. End-to-end encryption is one switch away.

    Send a file