Privacy.

Your notes live on your disk as plain files. If you turn on sync, we store ciphertext we cannot read.

Last updated 2026-10-10

If you never sign in

Jotura works without an account. Your notes are ordinary Markdown files in a folder you choose, and they never leave your machine unless you turn on sync, or unless you choose OpenAI embeddings for semantic search, in which case note text and search queries go to OpenAI under your own API key and nothing goes to us. The app contains no analytics or telemetry. Its only routine network request is an update check against our release server, which carries no account identifier and only fetches a version manifest.

What we collect, if you use sync

An account only exists to run cloud sync and its billing. For that we store:

  • Your email address: to sign you in (we email you a code; there are no passwords) and to send receipts.
  • Device names and public keys: the name each of your devices reports, and its public key, so sync knows who's who.
  • Subscription state: whether you're subscribed, via Stripe. Your card details never touch our servers.
  • Timestamps: when your account and devices were created and last seen.
  • Your encrypted vault: ciphertext blobs, encrypted manifests, and HMAC-derived path identifiers. The next section explains why that tells us so little.

IP addresses are used transiently for rate limiting (to stop abuse of sign-in and sync endpoints) and expire automatically. We don't build access logs tied to your account.

What we can't see

Sync is end-to-end encrypted. Your notes are encrypted on your device before upload, with keys derived from a sync password we never receive. The server stores opaque ciphertext, and the identifier it uses to route each file is an HMAC: deterministic, but meaningless without a key that only your devices hold. Concretely, we cannot read:

  • The content of any note
  • Note titles, filenames, or folder structure
  • Your sync password, master key, or any per-file key

The encryption itself enforces these limits, whatever any policy says. The full design, including the exact primitives, is on the security page.

Issue reports

The app sends an issue report only when you send one, from Report an issue or from a crash notice. A report contains:

  • Your message: what you typed.
  • A reply email: only if you add one.
  • Your setup: the app version, your operating system, and your device's memory and processor cores.
  • A recent log excerpt: with note names, vault paths and email addresses removed.

Reports are stored on Jotura's server and deleted after 90 days. Adam, who runs Jotura, is the only person who reads them, and he uses them for support. Amazon SES delivers him email copies of new reports.

Third parties

  • Stripe processes subscription payments. Card numbers go directly to Stripe and never touch Jotura's servers. Stripe knows your email and your payment details.
  • Amazon Web Services (Amazon SES) delivers the sign-in code emails, so it processes your email address when you sign in. It also carries the email copies of issue reports.
  • Cloudflare is our infrastructure provider: the sync API, storage, and this website all run on it. Like any host, it processes request metadata (such as IP addresses) to serve traffic.

We use no other third parties. We don't sell data, share it with advertisers, or use it for anything beyond running sync and billing.

Retention and deletion

We keep your account data for as long as you have an account. You can delete your account yourself at any time from the account page. The process is documented step by step at jotura.io/account/delete. Deletion deactivates your account immediately, and the encrypted data we held for sync is permanently purged from our servers after a 30-day grace period. Records of past payments are retained by Stripe as financial record-keeping requires. The notes on your devices are yours and are never touched by any of this.

This website

We use Google Analytics to count page views and downloads. In the UK, the EU, and Switzerland, its cookies stay off until you accept them in the banner; if you decline, Google receives cookieless counts with no identifier. Elsewhere the cookies are on by default. There are no ad pixels and no advertising cookies anywhere.

When the one-line installer finishes, it sends one event to jotura.io with your platform, CPU architecture, package type, and the version installed, so we can count installs. We pass that on to Google Analytics along with your country, never your IP address. SetDO_NOT_TRACK=1 before running the script to skip it.

If you sign in on the account page, your session tokens are stored in your browser's local storage, on your machine, and sent only to our API.

Contact

Questions about any of this: [email protected].

If we ever change what we collect, this page changes first, and the date at the top with it.