What we store, and where#
Your account (your email address, or Apple's relay address if you use Hide My Email), your notes, folders, files and earlier versions of each note as encrypted copies, your profile name and photo if you set them, your devices, and the AI apps you've connected. It's all stored at Supabase, our host, in Frankfurt, Germany.
The website and shared note pages run on Vercel, and are built in Frankfurt too. Vercel passes requests on to our server, including the requests AI apps make, and sees a shared note while it shows the page, but it doesn't store your notes. Our server does its work in Frankfurt: a request from anywhere enters Supabase's network at the nearest location and is passed to Frankfurt before it's handled.
What's encrypted#
- On your devices: your notes, their titles, folder names, file names and files, and every earlier version are encrypted on your device before they're uploaded, with a key made on your first device, or in your browser if you sign up on our website. We store the encrypted copies.
- Your key, and our copy of it: your devices hold the key, and iCloud Keychain carries it between your iPhone and Mac. We keep a locked copy of your key so that signing in opens your notes on a new device, with no other device and no recovery key. That means we could open your notes if we had to, for example under a court order, and so could someone who gets into your account. The copy is sealed with a secret kept outside the database, so the sealed copy can't be opened with a copy or a backup of the database alone. We hold both the secret and the database.
- Advanced protection: we're retiring it, and newer versions of the apps don't offer it. If you turned it on, it stays on until you turn it off in Settings, Security, and turning it off stores a copy again. While Advanced protection is on, your notes are end-to-end encrypted: we can't open them and can't help you back in. Then only your devices, and AI connections you approve, can unlock your notes. A new device gets your key from iCloud Keychain, is added from a device that has your notes, or is opened with your recovery key. If you lose every device and the recovery key, your notes are lost.
- Accounts made before we kept copies: the app asks once, with a sheet titled "Signing in now opens your notes", before anything is copied. Continue stores the copy. Older versions of the apps also offer Keep my key on my devices only, which turns on Advanced protection. Until you answer, nothing is copied and your key stays on your devices, as before.
- Your recovery key: a key you can save yourself. Signing in already opens your notes, so newer versions of the apps show it in Settings, Security only while Advanced protection is on. It opens your notes without us. We keep your notes' key locked with it. Our copy of your key, while we keep one, holds the recovery key too.
- Notes shared with people: encrypted like your other notes, with a key of their own. Each person in the note keeps that key with their notes' key, so whoever can open a person's notes can open the notes shared with them. Where we keep a copy of someone's key, we could too. When someone in the note asks their AI about it, our server reads it for that request, as it does for your own notes.
- Locked notes: encrypted a second time, with a key made from your notes password. That key never leaves your devices, so not even an AI you connect can read a locked note's text. If you forget the password, nobody can recover it.
- On the way and on disk: everything travels over HTTPS, and Supabase encrypts its disks as well (AES-256).
- Passwords and access tokens are stored only as one-way hashes.
Signing in, with Apple, Google or a password, tells us who you are. Unless Advanced protection is on, it is also what lets a new device get your key, and there is no waiting period, also after a password reset. A device that has been signed in for more than an hour without your notes asks you to sign in again first. Each time a device gets your key by signing in, every device of yours shows the notice "A new device opened your notes", and we send an email to your account's address.
What stays readable to us#
To sync your notes and run your account, some details aren't encrypted:
- Your email address and your sign-in records.
- Your profile name and photo.
- Your notes-password hint.
- The size and dates of each note, file and version.
- Which folder each note is in, and which notes are sub-notes of which.
- Which notes are pinned, and which are locked.
- The names of the AI apps that edited a note.
- Your list of devices.
- Your AI connections: their names, access, and when they were made and last used.
- The usage counts listed below.
- A note you share as a web page, while it's shared, since anyone with the link can read it.
- Who is in each note shared with people, their roles, and when each of them changes it.
When you connect an AI#
- You approve it on your device. Your iPhone or Mac asks you, and you type the number the page you started on shows there. With no device nearby, you can approve in the browser with your recovery key, if you saved one.
- Our server opens your notes for it. Approving gives that AI connection a copy of your notes' key, locked with a key derived from that connection's access token. We store only a hash of the token; the token itself arrives with each of the AI's requests. During each request our server unlocks your whole notes' key in memory, reads the notes the AI asks for, and forgets the key when the request ends.
- Our hosts carry that text. For AI requests, the text of the notes the AI reads or writes, and its access tokens, pass through Vercel and Supabase in readable form on their way. Neither stores your notes.
- Locked notes stay locked. An AI sees only their titles, never their text.
- Every change an AI makes keeps the previous version, so you can see what changed and restore it.
- Disconnect any AI app in Settings → Connect an AI. It loses access at once.
- What an AI app reads becomes part of your conversation with it, and the company behind it handles that under its own privacy policy.
- In a note shared with other people, each of them can connect their own AI. When one of them asks their AI about the note, our server reads the shared note for that request, as it does for your own notes, and keeps nothing of it.
Limits#
- Our copy of your key. Unless Advanced protection is on, we hold a copy of your notes' key, sealed with a secret kept outside the database. We hold both, so we could open your notes, and so could someone who took over our hosting account. The sealed copy can't be opened with a copy of the database alone. A recent copy of the database also holds sign-in sessions, though, and a session from a sign-in in the last hour can get your key as a device of yours would.
- Signing in. Unless Advanced protection is on, anyone who can sign in as you can open your notes: with your password, by resetting it from your mailbox, or through the Apple or Google account you sign in with. The notice on your devices and the email tell you it happened. They don't stop it.
- AI requests. While an AI you connected works, our server handles the text it asks for. A changed server could copy it. Disconnecting ends this at once.
- The recovery key in the browser. Approving on pintonotes.com with your recovery key runs our code in your browser. It never stores or sends the key, but a changed page could read it. When you can, approve from your iPhone or Mac instead.
- No key rotation yet. Your notes' key stays the same for the life of your account. Disconnecting an AI deletes its copy of the key, but you can't change the key itself yet.
- The database. Someone with only an old copy of the database can't read your notes. With a recent one they might, where we keep a copy of your key: it holds sign-in sessions, and one from a sign-in in the last hour can get the key. Someone running the live database could roll a note back to an earlier encrypted version, or hide notes from your devices. Where we keep a copy of your key, they could also sign in as you and get it, as a new device of yours would.
Who can see what#
- You, on every iPhone and Mac you sign in on. With Advanced protection on, a new device first needs your key: from iCloud Keychain, from one of your devices, or from your recovery key.
- Us. As the people running Pinto Notes (that's Emil, who makes it), we see the encrypted copies and the details listed under what stays readable. We keep a locked copy of your key, so we could open your notes if we had to, for example under a court order. With Advanced protection on, we can't open them.
- Anyone who can sign in as you, unless Advanced protection is on. Signing in opens your notes on a new device.
- AI apps you approve, for the notes they ask for, until you disconnect them. They never see the text of locked notes.
- Anyone with the link to a note you share, until you stop sharing it. Your device publishes a readable copy for the link, and it's deleted when you stop. Shared pages are hidden from search engines.
No ads, no tracking in the app#
There are no ads, and there never will be. The apps have no tracking and link no analytics or crash-reporting SDK. The App Store version 1.2 and the Mac download 1.2.3 and later send error and crash reports and a few usage counts to PostHog in the EU: never your notes, titles or anything you write. Settings, General, Share diagnostics and usage turns it off. We never sell or share your data.
This website counts page views and where visitors came from with Vercel Web Analytics, and which links and buttons are clicked, where on a page people click and how far pages are scrolled with PostHog, in the EU. These are counted across all visitors. Neither keeps a profile of you, and neither runs on shared notes or the connect pages. PostHog uses a cookie only if you choose Accept on the cookie banner, to recognise your return visits for up to a year, and then also records your visits to the public pages as session replays, with everything you type masked, kept for 30 days. Without Accept, no visit is recorded. Cookie settings at the bottom of the page changes your answer. It also counts Mac downloads as daily totals. None of this touches your notes or your computer.
The apps count a few things on our own server, so we can tell whether Pinto Notes works for people. Kept for 12 months, never shared:
- How many notes an AI connection changed on each day.
- Which days you used the app, to ask once, after a week, whether you'd like to share it.
- Which tips were shown and whether the feature was then used.
- Which first-run setup steps you've done.
- How you heard about Pinto Notes, if you answer that one question after sign-up.
- A random id for each installation and whether it's an iPhone or a Mac, to count devices.
Your data, your choice#
- Export: Settings → Account → Export Your Notes makes a zip on your device with every note as Markdown in its folder, with its files. Your notes are encrypted on your devices, so the export is made there. For everything else we keep about you, write to us.
- Delete: Settings → Delete Account deletes your account and everything in it from our server at once: notes, files, versions, AI connections, share links and usage counts.
- Deleted notes stay in Recently Deleted for 30 days, then they're gone for good.
- You can also ask us to correct, restrict or stop using your data, or object to the usage counts. Write to hello@pintonotes.com; we answer within a month. You can complain to the Swedish Authority for Privacy Protection (IMY).
Open source, so you can check#
Everything above is in the code, and the code is on GitHub: the apps, the server and this website. Found a security problem? Write to hello@pintonotes.com, not a public issue.
The legal details are in the privacy policy.
Every log, and how long it's kept
We don't write the text of your notes, email addresses, access tokens or IP addresses into any log of our own. Our hosts log the requests that reach them; we can't turn that off, but they keep it briefly.
| Log | What's in it | Kept |
|---|---|---|
| Supabase request logs | Each request to our server: the time, the address it asked for, the IP address and device type, and a rough location from the IP address. | 1 day |
| Supabase sign-in logs | Each sign-in and sign-out: the time, the email address and the IP address. | 1 day |
| Supabase function and database logs | When each server function ran and what it was asked for, and errors, with names, addresses and ids blanked out. | 1 day |
| Sign-in records in our database | Each sign-in: the time, the email address and the IP address, to keep your account secure. | 30 days |
| Vercel request logs | Each request to this website: the time, the page, the IP address and device type, and whether it worked. | 1 hour |
| Rate limits | A one-way hash of the IP address, made with a key that changes every day, to stop floods of sign-in attempts. | 2 hours |
| The log of our copy of your key | Each time the copy was stored, fetched by a device or removed, and each time a request for it was refused: the time and the kind of device. | 12 months |
Our hosting plan keeps no backups of the database, so what you delete is gone. If that changes, a backup would hold only the encrypted copies and the locked copies of your key, for as long as this page and the privacy policy say.

