Legal · Privacy

Privacy Policy

memrynote is built on a simple promise: your notes belong to you, and we cannot read them.

Last updated · July 23, 2026

Summary in 30 seconds

  • Your notes, tasks, and journal stay on your device. We never see their content.
  • If you connect Google Calendar, its data also stays on your device — and is never shared with AI models or used to train them.
  • Sync uploads only ciphertext. Every byte is encrypted on your device with XChaCha20-Poly1305 before it leaves.
  • Encryption keys live in your password manager and never touch our servers.
  • Anonymous usage metrics are optional, on by default, and switchable from Settings → Privacy. They never include note content, search queries, file paths, emails, or raw IDs.
  • We collect the minimum metadata needed to bill, deliver, and secure the service.
  • We never sell your data. We have nothing to sell.

1. What this policy covers

This policy describes how memrynote handles personal data in the desktop app, the marketing website, and the optional Sync service. It applies to everyone who uses memrynote, regardless of country.

2. The local app keeps your content on your device

The memrynote desktop application runs entirely on your computer. Your notes, tasks, journal, and files are stored as plain Markdown files in a vault folder you choose. None of that content is sent to us, period.

Optional update checks contact our update server, which sees only your IP address and app version.

3. Optional Google Calendar connection

If you connect Google Calendar, memrynote requests the Google Calendar scope to sync events both ways. Event data travels directly between Google and the app on your device and is stored locally in your vault; your OAuth tokens are kept in your operating system's keychain. Nothing from your Google Calendar is sold, used for advertising, or uploaded to our servers in plaintext. You can disconnect at any time in Settings → Calendar, or revoke memrynote's access at myaccount.google.com/permissions.

memrynote's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Google Workspace APIs adheres to the Google User Data Policy, including the Limited Use requirements.

AI features and Google user data. memrynote's AI features never receive Google Calendar data, and we never use Google user data to create, train, or improve AI or machine-learning models. AI in memrynote runs locally on your device by default — bundled on-device models power semantic search and voice transcription, and the optional assistant can run against a self-hosted model (such as Ollama) that you operate yourself. In that self-hosted or offline mode, data is processed locally and never transmitted to any model provider. If you choose to connect your own AI account or API key (Anthropic or OpenAI), events synced from Google Calendar are architecturally excluded from what those integrations can access.

4. Optional anonymous usage metrics

memrynote includes an optional, anonymous telemetry stream so we can understand which features get used, where the app crashes, and where it slows down. You can turn it off at any time in Settings → Privacy → Share Anonymous Usage Metrics. It is on by default in production builds and off in development builds.

Each event is one row from a fixed list — for example app_started, note_created, search_performed, sync_run_completed, app_error_seen. Event dimensions are not free-form: the schema rejects any dimension that looks like an email address, URL, file path, or raw identifier before the event ever leaves your device. Crash events (app_error_seen) may also carry a short error message and stack frames; both are redacted on your device — emails, tokens, UUIDs, and file paths replaced with placeholders — before upload, and the server re-checks that redaction before storing anything.

Each event ships with:

  • The event name and a short action label (both from a fixed enum).
  • An anonymous install ID and session ID. The install ID is a random UUID generated on your device — it is not derived from your hardware, account, or any personal data.
  • App version, release channel, OS platform, CPU architecture, locale, and your timezone offset.
  • Whether you are signed in to Sync (yes/no/unknown) and whether Sync is enabled.
  • Optional numeric metrics for the action — duration, item count, byte count, retry count.

Events are batched in memory and uploaded to sync.memrynote.com/telemetry/batch at most every 30 seconds. We never log your IP address against your telemetry stream beyond the standard edge access logs that every web server keeps for a short window.

Crash reporting is part of the same stream. We see that an error happened, on which surface, and an error code from a fixed list, plus the redacted stack frames and error message described above.

5. What Sync sends to our servers

If you opt into the paid Sync service, the following is uploaded:

  • Encrypted blobs. Notes, tasks, journals, attachments, and metadata, all encrypted on your device before upload. We hold ciphertext only.
  • Routing metadata. Vault IDs, blob keys, content hashes, byte counts, and timestamps. These are needed to route updates to your other devices and to count usage against your plan.
  • Account identifiers. Your email address, a hashed password, and verification tokens.

We do not receive plaintext titles, plaintext tags, or any contents of your vault. The server's view of your notes is a stream of opaque encrypted bytes.

6. What the website collects

memrynote.com does not run third-party advertising trackers and does not sell visitor data. It does run product analytics and session replay, provided by PostHog, so we can see how the site is used and diagnose problems. Every form field value is masked in the replay by default, and pages that can show your email address (sign-in, account settings) mask that text specifically as well, so it is never captured. PostHog sets cookies to keep track of your session.

If you contact us or sign up for an account, we store the email address you submit so we can reply or send the messages you opted into. We may track delivery, opens, clicks, and unsubscribes for those emails so we can understand whether the campaign is working.

7. How we use the data we have

We use the data described above only to:

  • Operate, sync, and secure your account.
  • Bill you, through Paddle, for the plan you chose.
  • Send transactional email (sign-up confirmation, payment receipts, security notices).
  • Understand which features get used and where the app crashes (if you have left anonymous usage metrics on).
  • Investigate abuse and comply with legal obligations.

We do not use your data to train models, build advertising profiles, or sell anything to anyone.

8. Encryption details

memrynote uses end-to-end encryption based on the libsodium primitives: XChaCha20-Poly1305 for content, Ed25519 for signatures, and Argon2id for password-based key derivation. Your master key is derived from your password on your device and is never sent to us.

Because we never hold your keys, we cannot decrypt your data. We cannot reset it for you, and we cannot disclose its contents in response to a subpoena — we have no way to read it ourselves.

9. Sub-processors

We use a small set of third-party services to operate memrynote. Each is contractually bound to handle your data only for the purpose listed:

  • Cloudflare — hosts the Sync API, stores encrypted blobs in R2, and runs the marketing website's edge.
  • PostHog — receives anonymous desktop product usage metrics and crash reports (if you leave usage metrics on), and provides product analytics and session replay for memrynote.com.
  • Paddle — merchant of record for payments. Receives billing details (name, billing address, payment method).
  • Resend or a similar transactional email provider — delivers sign-up, billing, and security emails.

We do not share data with advertising networks, data brokers, or social media platforms.

10. International transfers

memrynote is a small indie operation. Our infrastructure is global by default — encrypted blobs may be served from data centers near you for performance. Where personal data crosses borders, we rely on standard contractual clauses with our sub-processors.

11. How long we keep things

  • Encrypted blobs: kept while your Sync account exists. Deleted-item history follows your plan window: 30 days on Plus, 365 days on Pro and Believer.
  • Account record: kept while your account exists. If you delete your account, the record and any remaining blobs are removed within 30 days.
  • Billing records: retained as required by tax law in your country (typically 7 years).
  • Anonymous usage metrics: aggregated and retained for up to 24 months, then deleted. There is no way to tie an event back to a person.
  • Server logs: retained for up to 30 days for security and debugging.

12. Your rights

Depending on where you live (GDPR, UK GDPR, CCPA, and similar laws), you have the right to:

  • Access the personal data we hold about you.
  • Correct inaccurate data.
  • Delete your account and associated data.
  • Export the metadata we hold about your account.
  • Object to processing or restrict it in specific cases.

To exercise any of these rights, email privacy@memrynote.com from the address tied to your account. We respond within 30 days.

You can also lodge a complaint with your local data protection authority. We would rather hear from you first, but you do not have to.

13. Children

memrynote is not designed for children under 13 (or under 16 in jurisdictions that require it). We do not knowingly collect data from children. If you believe a child has signed up, email privacy@memrynote.com and we will delete the account.

14. Security incidents

If we discover an incident that affects your data, we will notify you within 72 hours of confirming the impact. Because content is end-to-end encrypted, the most likely incident types are metadata exposure, billing data exposure, or account-takeover attempts — we will tell you exactly what was affected.

15. Changes to this policy

We will update this page when our practices change. Material changes will be announced in the app and via email at least 14 days before they take effect.

16. Contact

Privacy questions: privacy@memrynote.com. Anything else: hi@memrynote.com.