The short version. We use information to run the website, respond to enquiries and operate the private email pilot. This website has no advertising pixels or analytics scripts. Invite-code submissions never create an account and their values are not saved by the application.
Who operates PrivyMailbox
PrivyMailbox is an independent project operating this website and a limited private preview. The operator can be contacted at [email protected]. This notice describes the current stage; before public paid signup, the contracting operator and applicable commercial details will be identified.
When you visit or contact us
Hosting and network providers process connection data such as your IP address, request time, requested path and browser information to deliver and protect the website. The origin web access log is disabled; infrastructure and security systems may still produce technical logs. We do not add third-party analytics, advertising trackers or remote font services.
The invite form uses a necessary security cookie to prevent cross-site request forgery. Owner sign-in uses a necessary session cookie. The website does not set advertising cookies. Public invite submissions are deliberately rejected; the application does not read, retain or echo the code value. Network infrastructure necessarily handles the request in transit, so do not enter passwords or other secrets.
When you email us, we receive your address, message and any details you choose to include. We use them to respond, provide support, handle security reports and address privacy requests. Do not send credentials or private message contents. Contact correspondence is kept while needed to resolve the enquiry and maintain necessary support, security or legal records; request deletion when it is no longer needed.
Data in the private email preview
For the authorized pilot, we process owner access credentials in protected form, domain configuration, alias addresses and labels, forwarding verification details, hashed app passwords, email headers, message bodies and attachments, delivery state, reply routes and operational status.
We use this data to receive mail for created aliases, store and display messages, provide per-alias IMAP access, forward mail to a verified destination, route replies to existing correspondents, enforce retention and deletion, recover from failures and investigate abuse. Tools you connect and inbox providers you choose may process separate copies under their own terms.
PrivyMailbox does not sell email contents or use them for advertising. Where data protection law requires a lawful basis, service operation relies on the arrangements for authorized preview access; website delivery, security and responding to enquiries rely on legitimate operational interests, subject to applicable law. Legal obligations may also require limited processing. Contact us to discuss the basis for a particular use.
Infrastructure providers & locations
The current service uses Hetzner for server hosting in Germany, Cloudflare for DNS, website protection and encrypted offsite recovery storage, SMTP2GO for outbound forwarding and replies, and UptimeRobot for availability monitoring. Monitoring checks public service health and ports; it is not given inbox contents or app passwords.
Providers process only the information involved in their role, under their applicable service terms. Outgoing email providers handle message content needed for delivery. Offsite backups are encrypted before upload; this does not mean live mail is end-to-end encrypted. Provider processing and recipient mail systems may involve countries outside your location. We do not claim that every copy stays in one country. Ask us about a specific data-location requirement before requesting access.
We may disclose information where required by applicable law or where reasonably necessary to investigate abuse, protect accounts or address a security incident. We do not publish private inbox data in marketing demonstrations.
Retention & deletion
- Live hosted email: retained for 30 days, or deleted earlier through the dashboard. Automated maintenance applies the policy.
- Encrypted recovery copies: retained for up to seven days after a live deletion, until the relevant backup expires.
- Alias and message retirement records: minimal identifiers, retired addresses and deletion timestamps remain permanently to prevent address reuse or deleted email returning through recovery.
- Active account configuration: kept as needed to operate the pilot, maintain access controls and resolve outstanding delivery or recovery work.
- Technical provider records: retained according to each provider’s operational and legal requirements. We do not claim a single retention period for all infrastructure logs.
Alias deletion rejects new receipt and logins immediately. Existing session disconnection, mail cleanup and protection against restoration complete in the background; the dashboard shows pending work until confirmed. Forwarded copies, sender-held messages and emails downloaded by your tools are controlled separately.
Security & access
The website and IMAP service use TLS. Per-alias credentials limit tool access to the corresponding inbox. App passwords are stored as hashes; encrypted recovery backups use a separately held recovery key. Formatted email is sanitized and remote images are blocked by default.
This is a hosted mail service. Authorized operator access to live message data may be necessary for operation, troubleshooting, recovery or legal obligations. It is not a zero-access or end-to-end encrypted service, and no system can promise absolute security.
Your choices, requests & changes
You can archive aliases, revoke tool access, delete messages and permanently retire aliases through the owner dashboard. Email [email protected] for questions or requests concerning access, correction, deletion, export, restriction or objection. Availability of a particular right depends on applicable law and may be limited by security, legal obligations or the minimal retirement records described above. We may verify a request before disclosing or changing data.
If applicable law gives you the right to complain, you may contact the relevant data protection authority in your jurisdiction. We encourage you to contact us first so we can address the concern.
We will update this notice when material processing changes and revise its effective date. Existing pilot participants will be informed of material changes through the contact route available to us where practicable.