1. Overview

This Privacy Policy explains what information veilsend ("we", "our", "the Service") collects when you use our secure file sharing service at veilsend.app, how we use it, and the choices you have. veilsend is built around a zero-knowledge architecture: the design of the Service itself limits what we are capable of knowing about you and your files.

2. Information We Collect

2.1 Account information

When you create an account, we store:

• Email address — used for login, email verification codes, and account-related notices.
• Password hash (email sign-up only) — we store a PBKDF2-HMAC-SHA256 hash, never your plain-text password.
• Google account identifiers (Google sign-in only) — your Google user ID, email, display name, and avatar URL, provided to us by Google with your consent.

2.2 File data

• Encrypted file content (ciphertext) — files are encrypted in your browser before upload. We store only the encrypted container.
• File metadata — original file name, file size, upload time, the expiry option you selected, and the optional note you attach.

We never receive or store your passphrase or encryption keys. Decryption happens only in the recipient's browser.

2.3 Payment information

Paid subscriptions are processed by Creem, our Merchant of Record. When you purchase a Pro subscription, you provide payment details (such as card number) directly to Creem. We never see or store your full card number. We receive from Creem only what is needed to manage your subscription: your plan status, subscription ID, transaction amounts, and billing period dates.

2.4 Technical data

• IP address and request logs — used transiently for rate limiting, abuse prevention, and security monitoring.
• Basic device/browser information — contained in standard HTTP headers, used only to operate and debug the Service.

3. What We Cannot Access

By design, we have no ability to access:

• The contents of your files (we store only AES-256-GCM ciphertext)
• Your file passphrases (they never leave your browser)
• Your derived encryption keys

Because of this, we cannot recover a lost passphrase, and we cannot decrypt your files even if legally compelled to do so. If you lose the passphrase, the file is unrecoverable — this is a deliberate security property, not a limitation we can work around.

4. How We Use Information

We use the information we collect only to:

• Provide, operate, and maintain the Service (accounts, file storage, expiry and deletion)
• Process subscriptions and payments through our Merchant of Record
• Send transactional emails (verification codes, essential account notices)
• Prevent abuse, enforce rate limits, and secure the Service
• Comply with legal obligations

We do not use your information for advertising, profiling, or sale to third parties.

5. Third-Party Service Providers

We share limited data with the following processors, only as needed to run the Service:

Provider	Purpose	Data shared
Creem	Payment processing (Merchant of Record)	Email, purchase details; card data goes directly to Creem
Resend	Transactional email delivery	Email address, message content (e.g. verification codes)
Cloudflare Turnstile	Bot / abuse protection	Browser signals analyzed by Cloudflare
Cloudflare R2	Encrypted file storage	Ciphertext only (never keys or passphrases)
Google	OAuth sign-in; font delivery	Sign-in consent data; standard web requests for fonts

6. Cookies

We use a single strictly-necessary cookie: a session cookie that keeps you signed in (HTTP-only, SameSite=Lax). We do not use analytics, advertising, or third-party tracking cookies. Cloudflare Turnstile may set its own cookie for bot detection when you use sign-up or login forms.

7. Data Retention

• Files — stored until the expiry time you choose (1 day, 7 days, or permanent for Pro), then automatically and permanently deleted.
• Account data — kept while your account is active. You may request deletion at any time (see Section 9).
• Payment records — retained as required by tax and accounting law, held by Creem as Merchant of Record.
• Logs — security and access logs are kept for a limited period and rotated automatically.

8. Data Security

Files are protected with end-to-end encryption (AES-256-GCM with keys derived via PBKDF2-HMAC-SHA256, 600,000 iterations). Access to our systems is restricted, and data in transit is protected with HTTPS. That said, no method of transmission or storage is 100% secure; the zero-knowledge design is our primary safeguard — even a breach of our storage exposes only ciphertext.

9. Your Rights

You may at any time:

• Access the personal data we hold about you
• Correct inaccurate account information
• Delete your account and associated data
• Export your account information
• Object to or restrict certain processing

To exercise any of these rights, contact us at [email protected]. Deleting your account removes your files and account data; payment records may be retained as legally required.

10. Children's Privacy

The Service is not directed at children under 13 (or the minimum age in your jurisdiction), and we do not knowingly collect personal information from children. If you believe a child has provided us personal data, contact us and we will delete it.

11. International Data Transfers

Our service providers (listed in Section 5) may process data in jurisdictions other than your own. By using the Service, you consent to such transfers. We rely on these providers' own compliance frameworks (e.g. Cloudflare, Google) for appropriate safeguards.

12. Changes to This Policy

We may update this Privacy Policy from time to time. We will post the new version on this page and update the "Last updated" date. Material changes will be announced on the site or by email where appropriate. Continued use of the Service after changes take effect constitutes acceptance.

13. Contact Us

Questions about this policy or your data: [email protected]
To report abuse of the Service: [email protected]