Privacy policy
What we collect, why we hold it, and what happens to it.
Last updated 2026-09-12
What we collect
Account details: your name, email address and a hashed password. Passwords are stored as salted hashes and cannot be read back.
Vault content: the message you write, the recipient name and email address you choose, and the check in interval you set.
Files: whatever you upload, encrypted with AES-256-GCM before it is written to storage, along with its name, size and type.
Technical records: the IP address behind each significant action, kept in your audit log and in the security event log so unusual activity can be investigated.
Billing records: if you buy a plan, a customer and subscription identifier from Stripe. Card numbers never reach this site.
Why we hold it
To run the service you asked for: storing your files, tracking your check in deadlines, sending reminders, and delivering a vault to the person you named if its deadline passes. To keep the account secure through rate limiting, lockouts and the audit log. To take payment where you have chosen a paid plan. To answer support requests you send us.
Who it is shared with
The recipient you name receives the contents of a vault when and only when that vault delivers. That is the purpose of the service and it is entirely under your control until the moment it happens.
We use a small number of processors to operate: an email provider to send messages, a storage provider to hold encrypted files, and a payment processor to take payment. Each receives only what it needs to perform that function. We do not sell personal information and we do not share it for advertising.
How long it is kept
Account data, vaults and files are kept while your account exists. Deleting a file removes it from storage. Deleting a vault removes its message. Audit log entries are kept for one year and security events for ninety days, then deleted automatically.
Encryption
Files are encrypted at rest with AES-256-GCM. Each file has its own key, which is itself encrypted with the account master key. Decryption happens on the server at the moment you download or a vault delivers, which means this is encryption at rest rather than end to end encryption. If your needs require that no server operator can ever read a file, encrypt it yourself before uploading it.
Your choices
You can read your full activity history at any time, download or delete any file, delete any vault, change or turn off email notifications, and close your account. To request a copy of your data or its deletion, write to us through the contact form.
Cookies
The site uses a session token stored in your browser to keep you signed in, and standard WordPress cookies where you sign in through the administration area. There are no advertising or tracking cookies.
Contact
Questions about this policy, or a request about your data, can be sent through the contact form.