What lives on your device
Jott is local-first. Everything you write is stored on your own device and is fully usable with no network connection. Your encryption password never leaves your device, and we cannot recover it for you — that is a direct consequence of not being able to read your jotts.
So that a new device can unlock your account, the sync server keeps a copy of your account's private key locked with a key derived from your password, together with the random salt used to derive it. The server cannot open it. It does mean that someone who obtained that copy could try to guess a weak password offline, so choose a strong one. Signing in with a password directly to a sync server also sends a value derived from your password (never the password itself) to prove it is you.
What the sync server can and cannot see
If you turn on sync, your jotts are encrypted on your device and then sent to our sync server, which stores them and passes them between your devices and anyone you share with. It holds them sealed: the server has no key and cannot read a single word of a jott, and nor can we.
Encryption hides content, not the existence of content. Being honest about the difference, the server can see:
- Your account — the email address you signed in with, and an identifier from Google if you used Google sign-in.
- Activity metadata — how many jotts you have, roughly how large each one is, and when each was created or changed.
- Image fingerprints — each image is identified by a fingerprint (a SHA-512 hash) of its contents. The server cannot see the image, but anyone holding a copy of the same file could confirm that an account has it.
- Your sharing graph — which accounts you have shared a jott with, though not what the jott says. When you share, the invitation the server passes on names the jott (by its random identifier), its owner, and the images involved by their fingerprints.
- Your contacts — which accounts you are connected with or have blocked, and your pending invite links. The names you give people stay encrypted.
- Your profile — the display name you choose, and your public key, can be read by any signed-in Jott account, so that people can find and share with you.
- Live presence — while you have a jott open, your display name, cursor colour and cursor position, tagged with that jott's identifier, pass through the server unencrypted on their way to anyone else the jott is shared with. The server holds this in memory only and does not store it, but it could see who has which jott open, and roughly where.
- Your devices — each device's name (the one you gave it, or what its operating system calls it), its operating system, the Jott app version, and when it last synced. These are stored readable, so that you can see your list of devices.
- Push tokens — if you use the mobile app, a token from Apple or Google so your phone can be told that something changed. A notification carries no jott content: at most the random identifiers of the jott and of the account that changed it.
- Your sync plan — whether your account currently has sync (a free trial, a subscription, or neither) and when that period ends, so the server knows whether to sync for you. It never sees any payment details.
We use this only to make sync work. We do not profile you with it, and we do not sell or share it.
Signing in
Jott is invite-only. We store the email address of each invited person, and a session cookie once you sign in so that you stay signed in.
If you sign in with Google, we ask Google only for your email address and a stable account identifier — nothing else, no access to your Gmail, Drive, contacts or anything of the kind. Google will know that you signed in to Jott. Signing out revokes the token we hold.
Our account site keeps a record of sign-in events — when you signed in or downloaded the app, how, whether it worked, and the general kind of browser used — so that we can help when sign-in goes wrong. These records are deleted after about 90 days.
We occasionally email account holders about new releases. Whether you receive these is recorded on your account; every one has an unsubscribe link, and unsubscribing does not affect sign-in or account email.
Paying for sync
The Jott apps are free. Sync is a paid subscription, bought on our website, never inside an app. Payments are handled by Stripe, a payment processor.
The free trial
The free trial needs no card, and Stripe is not involved in it at all. We record when your trial started and when it ends.
What Stripe receives
When you start a subscription, Stripe's checkout page collects your payment card and your billing address directly. We also give Stripe your email address, so that receipts reach you, and your Jott account's random identifier, so that the subscription is linked to the right account. A Stripe customer record is only created for you if you go to checkout. Cancelling, changing plan, updating your card and viewing past invoices all happen on Stripe's own pages. Stripe may use your billing address to work out sales tax where it applies, and sends you receipts and payment-failure notices itself.
What Stripe does with this information is governed by Stripe's privacy policy, not this one.
What we keep
- Stripe's identifiers for your customer record and your subscription.
- Your subscription's state — its status (for example active, cancelling or past due), whether it is monthly or annual, its price and currency, and the date the current period ends.
- Your trial dates — when your free trial started and ends.
We never see or store your card number. We do not keep your billing address or your country either. Paid subscriptions are US-only during the beta, so at purchase we check the billing country Stripe collected; if a purchase is refused for that reason, we record only that it was refused and whether it was refunded, not the country.
Feedback you send us
The app has a feedback form. It is entirely voluntary, and nothing is sent unless you submit it. When you do, it includes your message, the app version, the platform you are on, your device's identifier, your account's identifier if you are signed in, and any screenshots or images you attach.
Two more attachments are worth understanding, because one is on by default:
- Diagnostic logs are attached by default. They help us reproduce what went wrong and may include fragments of what you were doing at the time. You can untick this before sending.
- Your database is never attached unless you tick it. It is off by default. If you do tick it, you are sending us a copy of your jotts in readable form — only do that when we have asked and you are comfortable with it.
Feedback is not encrypted the way your jotts are, and today we keep it, attachments included, until you ask us to delete it or delete your account. We plan to expire attachments automatically, and will update this page when we do.
Downloads and updates
App downloads and update checks are served through our own portal, which fetches the files on your behalf. Our release host does not see who is downloading. On iPhone, the app is distributed through Apple's TestFlight, and on Android through Google Play; those are governed by Apple's and Google's privacy policies rather than this one.
Optional downloads from Hugging Face
Semantic search (finding jotts by meaning) runs entirely on your device, but needs a language model the first time you switch it on. The app downloads it directly from Hugging Face, which sees your IP address and which model file was requested. Nothing is downloaded unless you switch the feature on, and none of your jotts are sent.
Server logs
Our servers keep operational logs — the ordinary record of requests a server makes to stay debuggable — which include IP addresses and are also used to rate-limit abuse. They are kept for a short period and used only to run and repair the service.
What we deliberately do not do
- No analytics or product telemetry. There is no Google Analytics, no Mixpanel, Amplitude, PostHog or similar. The app ships with no analytics library of any kind.
- No crash-reporting service. No Sentry, no Crashlytics. If something crashes, we only learn about it if you tell us.
- No advertising, and no ad identifiers.
- No selling or sharing of personal information with data brokers, advertisers or anyone else.
- No training AI models on your jotts. We cannot read them, and we would not do this if we could.
Other companies involved
We keep this list short on purpose, and it is complete:
- Google — for Google sign-in, if you choose it; to deliver push notifications to Android through Firebase Cloud Messaging, whose library also creates its own installation identifier on your phone; to distribute the Android app through Google Play; and to host our support email, so anything you email us is stored by Google. App versions before 0.3.6 also loaded fonts from Google Fonts, which saw your IP address.
- Apple — to deliver push notifications to iPhones, and to distribute the iPhone beta through TestFlight.
- Stripe — to take payment for a sync subscription, only if you subscribe.
- DigitalOcean — which runs our servers and databases.
- Cloudflare — whose R2 storage holds the encrypted copies of your jotts and images, which it cannot read.
- Postmark — which delivers our email, such as sign-in links, to your address.
- Hugging Face — only if you switch on semantic search, as described above.
Keeping and deleting your data
We keep your account and your encrypted jotts for as long as your account exists. You can delete individual jotts in the app at any time.
If your subscription ends, nothing is deleted. Your jotts stay on your devices and, encrypted, on our server. Syncing pauses until you subscribe again.
For now, you delete your account by emailing support@jott.ink. If your account shares jotts with other people, deletion may take longer while we finish the support for it. You can also ask us for a copy of what we hold about you. Deleting your account:
- Removes what our servers hold for you — your account, your encrypted jotts and images, your devices, your feedback submissions, and your billing record.
- Cancels any subscription immediately, and deletes your customer record at Stripe. Stripe keeps records of past payments and invoices, as payment processors must for tax and accounting.
- Leaves your devices alone. Your jotts stay on each device, usable without an account, unless you also choose to erase that device.
- Reaches backups too. Any backup copies expire within 30 days.
We keep a minimal record that an account was deleted, made of random identifiers only and no email address, so that the deletion can be applied again if we ever have to restore from a backup.
Children
Jott is not intended for children under 13, and we do not knowingly collect their information.
Changes to this policy
If this policy changes in a way that affects what we collect or who we share it with, we will update the date at the top and tell users directly. Jott is early software under active development, and we would rather over-communicate.
Contact
Questions, deletion requests, or anything else about privacy: support@jott.ink.