Infrastructure and data retention
Last updated: November 13, 2026 • Luxembourg, EU
This page explains how PrivateNote protects notes, which providers handle requests, how long data is kept, and what deletion leaves behind. The decryption key stays in the URL fragment (#…). Browsers do not send that fragment to PrivateNote. It supplements the Privacy Policy.
Privacy at a glance
- Encrypted before upload. Notes and attachments are encrypted in your browser.
- Keys stay client-side. PrivateNote does not store plaintext decryption keys on its servers.
- Limited retention. Encrypted notes are removed from active storage after expiry, their read limit, or deletion.
- Cloudflare storage. Encrypted notes, encrypted attachments, and account records are stored separately. Requests can be processed globally.
- No advertising trackers. No advertising pixels, session replay, or third-party product-analytics SDKs.
How PrivateNote protects your data
- Note content is encrypted in your browser with AES-256-GCM before upload. Attachments are encrypted in your browser with libsodium secretstream (XChaCha20-Poly1305). The encrypted file is what gets stored.
- PrivateNote does not store the plaintext decryption key on its servers. The key is carried in the URL fragment, which is not sent in normal HTTP requests. For password-protected notes, the stored ciphertext includes an encrypted (wrapped) key, but not the password or the plaintext key.
- Expiry, the read limit, and the read count are stored with the encrypted note. They are not the note contents.
- Account email, sessions, passkeys, billing state, and audit events are stored apart from note contents.
Infrastructure and providers
- Cloudflare delivers the site, the API, and file uploads, and protects the service against abuse. Bot checks use Cloudflare Turnstile when a challenge is required. Requests are handled at Cloudflare's edge, which is not limited to the EU.
- Encrypted notes are stored under a Cloudflare EU jurisdiction restriction. Account information and sign-in records are stored in a separate Cloudflare database.
- Encrypted attachments are stored in Cloudflare R2 object storage. Request processing can occur globally.
- Those storage restrictions do not cover every request. Cloudflare can process connection data and logs at the edge. Email, payments, Cloud Assist, and optional integrations can involve processing outside the EU.
- Resend delivers account, notification, and feedback email. Stripe hosts checkout and subscription management. PrivateNote does not load a Stripe script on note pages.
- PrivateNote offers optional AI assistance. On-device AI processes text locally in your browser after downloading the necessary model files from Hugging Face or jsDelivr. Cloud Assist sends the draft text you explicitly submit to Cloudflare Workers AI for processing before encryption. Cloud Assist is not end-to-end encrypted processing. According to Cloudflare's published Workers AI data-use terms for standard inference, prompts and outputs are not retained after the response is delivered, and Customer Content is not used to train AI models. PrivateNote does not enable AI Gateway logging or other stateful Workers AI storage for Cloud Assist. Do not use Cloud Assist for information you do not wish to share with the AI provider.
- These run only if you use them: Google's identity script loads when you connect Gmail to send a note from your browser; Have I Been Pwned, for a password check that does not send the full password.
- Cloudflare Web Analytics loads only on privatenote.ai and www.privatenote.ai.
Data retention
| Data | Retention |
|---|---|
| Encrypted notes | Until expiry, read limit, or deletion |
| Deleted-note identifiers | Up to 90 days |
| Attachment records | 30 days after release |
| Signed-in sessions | Up to 7 days of inactivity, maximum 30 days |
| Account audit events | 90 days |
| Abuse-prevention records | A few minutes to approximately 1 hour |
| First-party analytics | Daily aggregates: 730 days. All-time note creation totals: retained without identifiers. |
| pn_client_id cookie | Approximately 30 days |
| Support and legal correspondence | Up to 24 months after closure, subject to legal requirements |
| Provider logs and recovery copies | Subject to provider retention policies |
- When a note is deleted, its encrypted content is removed from active storage. PrivateNote retains a minimal deletion marker containing only the note identifier for up to 90 days, so the service can distinguish deleted notes from invalid links. The marker contains no note content, decryption key, recipient identity, or access history. If that identifier can be linked to a URL or other activity elsewhere, it may still be personal data.
- A country or network restriction is stored separately. It is deleted with the note, unless an attachment can still be downloaded. Then it stays until that download window, plus a short grace period, has closed.
- After a session expires, scheduled cleanup deletes that record, including the IP address. It is not kept until the session is used again. If you revoke it sooner, the record is deleted within 30 days. Abuse-prevention records are deleted by the same scheduled cleanup after their short limit.
- The pn_client_id cookie is set by the API for signed-in and anonymous requests. It is HttpOnly, lasts about 30 days, and separates rate-limit buckets for abuse prevention. It is not used for analytics.
IP addresses and analytics
IP addresses are recorded in a few specific places. They are not stored as a history of who opened an anonymous note.
- Cloudflare sees the connecting IP on every request, for routing and abuse protection.
- Signed-in sessions and account audit events store the IP, for the periods in the retention table. Sessions also store city and country.
- Abuse-prevention records can include the IP for that short limit.
- If you restrict a note to particular addresses or networks, those values are stored with the note.
- There are no advertising pixels, session replays, or third-party product-analytics SDKs such as Google Analytics.
- The app sends coarse first-party counts to its own API: page, engaged time, referrer category, and funnel steps. Those requests omit cookies and do not send the page referrer. Raw events, note ids, and visitor ids are not stored. Daily aggregates expire after 730 days. All-time note creation totals are retained without identifiers.
- On privatenote.ai and www.privatenote.ai, the page loads Cloudflare Web Analytics after the page has loaded. Other hosts do not load it. First-party analytics do not store IP addresses or a persistent visitor id.
Deletion and backups
Deletion from active storage is not deletion from backups, logs, or caches.
- PrivateNote deletes encrypted notes from active storage and subsequently removes associated encrypted attachments. PrivateNote does not maintain a separate application-managed backup of note content. Provider-managed replicas and recovery systems may retain deleted data temporarily.
- The account database has provider recovery history. A deleted account, session, audit, or file record can remain in that history until the provider's recovery period ends.
- Encrypted-note storage is replicated by Cloudflare. Removing a note from the live store does not let PrivateNote decide how long a deleted copy remains in Cloudflare's replicas or recovery systems.
- Note responses include cache-prevention directives and are configured not to be cached by browsers or Cloudflare's cache. Client behavior and any copy that was already stored elsewhere cannot be guaranteed.
- Deleting a note does not delete provider logs. Cloudflare keeps its own request and security logs, and PrivateNote does not set how long Cloudflare retains them. Application logs used to diagnose errors can include a technical request identifier. Those logs are separate from the note store.
What happens when a note is opened
- When a note expires, its encrypted content becomes unavailable and is deleted from active storage through the expiry process. Expired notes cannot be opened again.
- Each successful retrieval counts toward the note's read limit. Once the limit is reached, including a one-time note, the encrypted note is removed from active storage and subsequent retrieval attempts are rejected.
- A note allowed more than one read keeps the encrypted note until the read limit or the expiry, whichever comes first.
- The sender can delete an unopened note. If that note has already been read, an unread-only delete is refused.
- An attachment can stay available for a short download window after the note is opened. It is deleted after the note is gone and that window, plus a short grace period, has passed.
- The link can still contain the key. Deleting the server copy does not remove that key from a browser, chat, or inbox that already has the full URL.
