SilentPost
How it works Use cases Pricing Trust FAQ
Request Access
How it works Use cases Pricing Trust FAQ Request Access
Legal

Privacy Policy

Last updated: April 23, 2026

SilentPost is built to hold sensitive content until you decide it should be delivered. This policy explains, in plain terms, what we collect, why we need it, who else touches it, and how long it stays.

1. What we collect

Your account

We collect the email address you sign in with. We use it to deliver one-time login codes, check-in reminders, and notifications when a message has been delivered. If you register our mobile app, we also store a push notification token for your device.

Your content

We store the messages and attachments you choose to place in the Service. Plaintext is received by our servers only during the brief moment of creation; it is then encrypted with a unique per-message key and the plaintext is discarded. Only the encrypted ciphertext is retained.

Your recipients and trusted contact

We store the email addresses of the recipients you designate, because we need them to deliver your messages. If you configure a trusted contact, we also store the phone number, verification question, and verification passphrase you provide.

Your schedule

We store your check-in interval, grace period, last check-in time, and the schedule of reminder and delivery events that follow from them.

Billing

If you pay with a card, Stripe processes the transaction; we store only a Stripe customer reference and the plan you're on. We do not see or store your card number. If you pay in USDC on Solana, we store the on-chain transaction signature for verification purposes. Blockchain transactions are, by their nature, public and permanent; we do not control what the network records.

Operational data

We record standard server logs and IP addresses to operate the Service, enforce rate limits, and diagnose abuse. These are kept for a limited period and are not linked to the content of your messages.

2. What we don't collect

We do not run analytics trackers, advertising pixels, or third-party behavioral cookies. We do not build a profile of you. We do not sell, rent, or share your data with marketers.

3. How we store and protect your content

Every message and attachment is encrypted at rest using AES-256-GCM. The per-message data key is wrapped by AWS Key Management Service (KMS), and only the automated delivery process is authorized to unwrap it — and only once your delivery trigger has fired. Our application servers do not have standing permission to decrypt your content.

All stored data lives on AWS infrastructure, protected by AWS-managed encryption in addition to our application-layer encryption.

4. How long we keep it

  • Your account: until you delete it. Account deletion is available from the settings page and is immediate and irreversible.
  • Messages before delivery: as long as your account is active and the message has not been delivered.
  • Messages after delivery: the recipient's delivery link is valid for 24 hours. At the end of that window, the encrypted content, any attachments, and the key material used to decrypt them are permanently purged from our systems. A minimal record that a message existed remains associated with your account so your own history is not blanked.
  • Push notification tokens: until your mobile app is uninstalled, the token rotates, or you delete your account.
  • Billing records: retained as required for financial and tax compliance.
  • Server logs: retained for a limited operational window, then rotated out.

5. Who else touches your data

We use a small number of service providers to operate the Service. Each receives only the data they need to do their specific job.

  • Amazon Web Services (AWS): hosts our application, databases, object storage, and encryption keys.
  • Amazon SES: delivers transactional email — login codes, reminders, and the delivery emails that carry your message links. The subject lines and email bodies are plain (they never include recipient names, message content, or other sensitive detail).
  • Expo Push: if you use the mobile app, Expo relays push notifications to Apple's and Google's delivery networks. Push bodies are generic and never include message content.
  • Stripe: if you pay by card, Stripe handles the payment and stores your card details on its own systems.
  • Solana blockchain: if you pay in crypto, your payment transaction is recorded on a public blockchain that we do not control.

We do not sell your data, and we do not share it with advertisers.

6. Legal process

We may disclose information when legally required — for example, in response to a valid court order or similar legal process. Because your message content is encrypted and the delivery process is the only automated authority able to decrypt it, we generally cannot produce plaintext of undelivered messages even when compelled.

7. Your rights

You can review the account data we hold about you within the Service. You can delete your account, and with it every message, attachment, device registration, and piece of account metadata, from the settings page.

If you need help with any of these, or have a question this policy doesn't answer, write to hello@silentpost.io.

8. Children

SilentPost is not intended for anyone under the age of 18. We do not knowingly collect information from children. If you believe a child has created an account, contact us and we will remove it.

9. International users

Our infrastructure is hosted on AWS. Depending on your location, your data may be processed in a country different from the one you live in. By using the Service, you consent to this transfer.

10. Changes to this policy

If we change this policy in a material way, we will update the “Last updated” date above and, where appropriate, notify you by email or in the app. Continued use of the Service after a change takes effect means you accept the updated policy.

11. Contact

Questions about this policy or your data? Reach us at hello@silentpost.io.