Privacy policy
Common Ink keeps what it needs to run your notebook, and shows your notes only to the people and agents you let in. This page says what Common Ink stores, why, who else handles it, how long it is kept, and how you get a copy or have it deleted.
Effective 9 November 2026.
Who runs Common Ink
Common Ink, at commonink.app, is run by Audrow Nash LLC ("we", "us"). Write to support@commonink.app about anything on this page.
What Common Ink stores
Your account
When you sign in with Google, Google tells Common Ink your email address and your name. Common Ink keeps those two things, the time you first signed in, and a count of the times you signed out everywhere. It does not keep your profile picture or a copy of your Google password.
A signed-in browser holds a session cookie. The session itself lives in that cookie, and the database keeps nothing per session.
Before you connect a bank, or sign in to one again, Common Ink asks for a passkey of yours. For each passkey you add, it keeps the passkey's public key and id, the name you gave it, when you added it and when you last used it, a count your device keeps of the times it was used, and how your browser said it reaches the device, such as USB or built in. Your fingerprint, face or screen lock never leaves your device, and Common Ink never sees the passkey's private key.
What you put in a workspace
- Workspaces, folders and the role of each member (admin, editor or viewer).
- Notes: their text, title, folder, whether they are private to you, and whether they are archived or in Trash.
- Every change to a note: what changed, when, and who made it (a member, an agent or a plugin). This is the note's history, which lets anyone who can see the note see and revert its changes.
- What Common Ink works out from a note's text so it can search and list it: its todos, tags, links, mentions of people, which uploads it refers to, and a search index of its words.
- Uploads: the file's name, type, size, a fingerprint of its contents (SHA-256), who uploaded it, and its bytes. The bytes are kept in Cloudflare R2. The rest is in the database.
- What each member keeps for themselves: their settings, favorites, daily notes, completed recurring todos, and the time they last read the workspace.
Sharing
- Invites: the email address invited, the role offered, and who invited them.
- Grants: who shared a note, folder or upload with whom, by email address, and with what access. A grant can name an email address that has not signed in yet.
- Share links: the link's secret, what it opens, and who made it.
Agents and connected apps
- An agent is a program you connect to act for you, such as Claude or ChatGPT, or a script with a token. Common Ink keeps its name, the limits you set (which workspace, which folders, read only, when it expires), when it was made and last used, and when it was disconnected. It keeps only a hash of the agent's token, never the token itself.
- An app that connects through a sign-in (OAuth) also has the name and return addresses it registered with, and a hash of the network address it registered from, which is used only to count registrations. Its access codes and tokens are kept only as hashes.
The web clipper
The Common Ink Clipper for Chrome sends what you choose to clip: the page's text, its address, and its images and files, which your browser downloads from the sites they are on. They become a note and uploads like any other. Common Ink keeps a hash of the clipper's token, the extension's ID, and when it was allowed and last used.
Plugins
For each plugin installed in a workspace, Common Ink keeps its code and description, who installed it, and what admins allowed it to do. A plugin you are writing in the store is kept as your unpublished changes, seen by you alone, until you publish it. While you try them, what goes wrong as they run in your browser is kept with them, for you and your agent, until they are saved again. The same is kept of a plugin you installed for yourself, until other code is installed in its place. A plugin can keep its own settings in your browser.
Your calendar and contacts
If you connect Google Calendar or Google Contacts, Common Ink keeps the access tokens Google gives it, the account's email address, and which permissions you agreed to. The tokens are encrypted (AES-256-GCM) before they reach the database, and the key is not in the database.
Common Ink does not keep your events, and it keeps your contacts only as this section says. It reads them from Google each time you or your agent ask, and shows them to you alone.
If you merge two contacts, Common Ink keeps both names, so a mention of the merged contact still finds the one you kept, and a full copy of the merged contact for 30 days, so you can restore it. It also keeps which pairs of contacts you said are not the same person. A note that refers to an event or a contact holds only a reference to it, with the label you wrote. Nobody else in a workspace can see that you connected a calendar or contacts, or anything in them.
Email you send to Common Ink
If you connect Email, mail you send, copy or forward to notes@in.commonink.app from an address of yours is kept in Common Ink, because there is nowhere else to read it from later:
- Each message: who sent it and who received it, its subject, when it was sent and received, its text, its HTML with anything that runs, loads or tracks taken out, and the ids that place it in a thread.
- Each attachment's name, type and size. Never the attachment itself.
- The addresses you added, and the rules you set for mail not to keep.
Mail that doesn't come from an address of yours is dropped. What is kept is yours alone: nobody else in a workspace sees it or that you connected Email, whatever their role. An agent you connect can read it, unless it is limited to folders. A note that refers to a message holds only a reference to it.
Recordings you transcribe
When you or your agent ask Common Ink to transcribe a recording, the Worker sends its audio, with the workspace's vocabulary, to Whisper, a speech model run by Cloudflare on Workers AI. The text comes back to be written where you asked. Nothing is sent until you ask, and a recording you don't transcribe goes to no model.
Your banks and cards
If you connect a bank or card, you sign in to it at a page of Plaid's, and Common Ink never sees your bank login. Plaid gives Common Ink an access token, which is encrypted (AES-256-GCM) before it reaches the database, as Google's tokens are.
Unlike your calendar, what comes from your bank is kept in Common Ink, so a year of history is there without asking your bank each time:
- Each account you shared: its name, its last four digits, its type, its currency and its balances. Never its full number.
- Each account's balances for each day, from the day you connect it.
- Each transaction, starting from the past 12 months: its date, amount, currency, vendor, Plaid's category for it, whose account it is if your bank says, and whether it is pending.
Common Ink brings these up to date when you look at them and once a day. They are yours alone: nobody else in a workspace sees them or that you connected a bank, whatever their role. Your agents see them only if you turn on Let agents use accounts, Let agents use transactions or Let agents use envelopes, each for what its page shows. A note that refers to a transaction holds only a reference to it.
Connecting a bank also asks you to agree to investments and liabilities, so you won't be asked again if Common Ink comes to use them. Common Ink reads neither today.
If you turn on any of those three, an agent you connected can also add a bank's accounts and transactions itself, from wherever it reads them, in place of Plaid. Common Ink keeps what it adds as it keeps a bank's: each account's name, last four digits, type, currency and balances, and each transaction's date, amount, currency, vendor, category, whose it is if the agent says, and whether it is pending. These show as added by that agent, are yours alone as your banks are, and nothing of them goes to Plaid. Disconnecting or deleting the agent leaves them. You remove them in Settings, under Banks and cards, and deleting your account deletes them.
If you add something by hand on the Accounts page, such as what your house is worth or what you owe on it, Common Ink keeps its name, its type, each value you or your agent gave it with the day it was set, and whether an agent set it. It takes your number as you wrote it: nothing looks up or estimates a value, and nothing is sent to Plaid or anyone else. These are yours alone as your banks are, your agents see and change them only if you turn on Let agents use transactions, and disconnecting a bank leaves them. Deleting one deletes its values, and deleting your account deletes them all.
The email list
If you join the email list on the site, Common Ink keeps the email address you gave and when you joined. It is not an account, and nothing else is kept with it. It is used only to write to you about Common Ink, such as when it opens.
Google user data
What Common Ink asks Google for, and when
Signing in asks for openid, email and profile, to learn who you are. Common Ink keeps only your email address and name from them.
Signing in also asks, in the same Google screen, for your calendar and your contacts, so they work without a separate step. Google lets you untick each one. You can connect or reconnect them later from Common Ink.
| Scope | What Common Ink does with it |
|---|---|
https://www.googleapis.com/auth/calendar.calendarlist.readonly |
Lists your calendars, and whether you may change each one. |
https://www.googleapis.com/auth/calendar.events |
Shows your events, and creates and changes events when you or your agent ask. |
https://www.googleapis.com/auth/contacts.readonly |
Shows your contacts. |
https://www.googleapis.com/auth/contacts |
Asked for only when you first choose to edit a contact. Creates and changes contacts, and their photos, when you or your agent ask. |
A change is sent to Google with your own access, so Google records it as yours. It is not part of a note's history and can't be reverted in Common Ink.
If Google answers for an account that can't use Common Ink, or Common Ink can't keep what Google sent, it asks Google at once to end the calendar and contacts access it was given.
Limited Use
Common Ink's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In plain words, for what Common Ink does:
- Your Google data is used only for features you can see in Common Ink: signing you in, and showing and changing your calendar and contacts.
- It is passed on only to provide those features at your request: to you, and to an agent you connected when that agent asks for your events or contacts. It is also passed on where the law requires it, for security, or in a merger or sale, with your consent first.
- It is never sold, never used for advertising, and never used to decide creditworthiness.
- No person at Common Ink reads it unless you ask, it is needed for security, or the law requires it.
You can disconnect your calendar and contacts in Common Ink. That deletes the tokens and asks Google to end the access. You can also remove Common Ink's access in your Google Account.
How Common Ink uses what it stores
- To sign you in and show you the workspaces you belong to.
- To store, search, show and sync your notes and files, for you and for the people and agents you share them with.
- To read and change your calendar and contacts when you or your agent ask.
- To keep and show your email, your banks and your cards, if you connect them.
- To transcribe a recording when you or your agent ask.
- To write to the people on the email list about Common Ink.
- To keep Common Ink secure and fix problems.
What Common Ink counts
Common Ink counts how it is used, so we know what to build and fix. It does this in two ways, and neither counts anything a note says.
The site's public pages (the home page, the docs, this policy and the terms) use Cloudflare Web Analytics. It counts visits, the page visited, the site that linked to it, and the visitor's country, browser and device type, and how fast the page loaded. It sets no cookie, keeps nothing in your browser, and does not follow you to other sites. Those pages load its script from static.cloudflareinsights.com. The app's pages, a page a share link opens, and the frames embeds and plugins run in never load it.
The app counts on the server, as things happen, and loads no script for it. Each count says what happened (such as signing up, opening the app, making or editing a note, adding or completing a todo, recording, transcribing, clipping a page, inserting a timer, deleting a tag, which tool an agent called, or which hint the app gave you and whether you took it up), in which workspace, whether a person, an agent or a plugin did it, and when. It names who did it only by a code made from their account with a key kept on the server: a pseudonym, the same for one person each time, which nobody without that key can turn back into a person. A count never holds what a note, a title, a tag, a file name, a folder name or an email says, and never an email address or a name. The counts are kept in Cloudflare Workers Analytics Engine and read only in aggregate, on a page only Common Ink's operators can open: how many people were active each week, how many signed up, how much people and agents each wrote, and which features are used.
Common Ink sends your notes, files, calendar, contacts, email, banks and cards to no AI model of its own. A recording you ask it to transcribe is the one exception, and is covered above. An agent you connect is different, and is covered below. We don't sell or rent your information, use it for advertising, or let anyone train AI models on it. That includes everything that comes from your bank.
Who can see your content
- You. A private note or upload is seen by you alone, even in a shared workspace.
- The members of a workspace, according to their role. A guest sees only the notes, folders and uploads shared with them.
- Anyone with a share link you made for a note or a folder, until you turn the link off. A link can be for anyone, or for anyone signed in to Common Ink.
- Agents you connect. An agent reads and writes with the access you gave it, never more than your own. What it reads goes to the company that runs it, such as Anthropic or OpenAI, under that company's terms.
- Plugins an admin approved. A plugin reads and changes only what its permissions allow. A plugin allowed to reach the network can send what it reads to the sites it names. A plugin given full trust runs in your session and can do anything you can.
- Our service providers, below.
- The law. We may disclose information when we believe the law requires it.
Service providers
- Cloudflare runs Common Ink: the Worker that answers every request, the D1 database, the R2 bucket that holds uploads, the Worker's logs, the counts of how the app is used (Workers Analytics Engine), and Web Analytics on the site's public pages. It also receives mail sent to notes@in.commonink.app (Email Routing) and runs the model that transcribes recordings (Workers AI). Its data centers may be outside your country.
- Google signs you in, and holds your calendar and contacts if you connect them.
- Plaid connects your banks and cards if you connect them. You sign in to your bank at Plaid's page, and Plaid reads your accounts and transactions from it for Common Ink. Plaid's own End User Privacy Policy covers what it does with them.
- Stripe will take payment when paid plans start and you subscribe. Common Ink is free during the closed beta, so nothing goes to Stripe yet. It holds your card and billing details, and Common Ink keeps only your Stripe customer and subscription ids, your plan, and when it renews. Stripe's own privacy policy covers what it holds.
The Worker sends requests to no other service but Plaid, to connect a bank and read it. When paid plans start, it will also send requests to Stripe, to start a payment, open your billing page, or cancel your subscription when you delete your account. Some features make your browser talk to other sites directly:
The site's public pages load Cloudflare Web Analytics from
static.cloudflareinsights.comand send it the visit.Embeds of YouTube videos, posts on X, and Bluesky posts load from those services (YouTube's from
youtube-nocookie.com).The Weather plugin, when you add it to your Dashboard, sends your browser's location or a place you type to Open-Meteo and BigDataCloud.
Night shift, when it follows sunset, sends the place you type to Open-Meteo to find its position.
Editing a contact sends what you type in its Address field to Photon (
photon.komoot.io, run by komoot on OpenStreetMap's data) to suggest addresses.The clipper downloads a clipped page's images and files from their sites, and asks YouTube and X to describe a clipped video or post.
Logs
The Worker writes a log line when something fails. Before a line is kept, src/core/logs.ts removes tokens, cookies, email addresses, share link secrets, sign-in codes, and anything an error quotes, which is where note text would be. Cloudflare's own record of each request, which would include its address, is turned off, because an address can hold a share link's secret. Cloudflare keeps the Worker's logs for 7 days on the Workers Paid plan. Cloudflare may also keep records such as IP addresses for its own security, under its own policy.
Cookies and browser storage
Common Ink sets three cookies, all needed to sign in:
__Host-ink_sessionkeeps you signed in, for 30 days.__Host-ink_googleprotects the step where Google signs you in, for 10 minutes, or where you connect a bank at Plaid, for 30 minutes.__Host-ink_passkeysays you used your passkey in this browser, for 10 minutes.
Your browser's local storage keeps preferences such as the workspace you last opened and the panels you had open, and what plugins store for you. Common Ink uses no analytics, advertising or tracking cookies. The app's pages load no scripts from other sites, and an embed runs in a frame of its own. The site's public pages load one, Cloudflare Web Analytics, which sets no cookie (see What Common Ink counts).
How long Common Ink keeps it
- Your account and workspaces: until you delete them.
- Notes and uploads in Trash: 30 days, then the hourly job removes them for good, a note with its history. Removing one from Trash yourself removes it at once.
- An upload that never finishes: removed by the hourly job after a day with nothing sent to it.
- A note's history: as long as the note.
- Sessions: 30 days, or until you sign out everywhere.
- Passkeys: until you remove them, or delete your account.
- An app connected by sign-in: its access token lasts an hour and its refresh token 30 days. A new refresh token replaces the old one each time it is used. The hourly job deletes codes and tokens a day after they expire.
- The clipper: 90 days, then you allow it again.
- Google tokens: until you disconnect, or until Google stops accepting them, when they are deleted.
- Email: until you disconnect Email, when every message kept and every address you added are deleted, and mail sent after that is dropped.
- A contact you merged: the copy of it for 30 days. Both names, until you delete your account.
- Your banks and cards: their token, accounts, balances and transactions until you disconnect that bank, when they are deleted and Common Ink tells Plaid to end the connection. A bank that has wanted you to sign in to it again for 90 days is disconnected the same way, and Common Ink says on the bank, from the day it starts wanting it, when that will be. Until Plaid says it ended a connection, Common Ink keeps its token, encrypted and with nothing that says whose it was, to ask again. What you said of a vendor and your categories stay until you delete your account.
- What an agent added as a bank: its accounts, balances and transactions until you remove them in Settings, under Banks and cards, which also deletes what was filed in your envelopes of them. Disconnecting the agent leaves them.
- The email list: until you ask to leave it, by writing to support@commonink.app, until you delete an account with that email, or until the list is no longer needed.
- Logs: 7 days.
- Counts of how the app is used: three months, which is as long as Workers Analytics Engine keeps them. Web Analytics on the public pages is kept by Cloudflare under its own policy, with no cookie and nothing that names you.
- Backups: the database's history (Cloudflare D1 Time Travel) goes back 30 days. Anything deleted from the database stays in that history until it is 30 days old, and then it is gone. Uploads' bytes have no backup. When Common Ink deletes them from R2, they are gone at once.
Deleting your data
Your account. You delete your account in Settings, under Account. It removes your name and email, your settings, your private notes and private uploads, your banks and cards, with what was kept of them (once your account is gone, Common Ink tells Plaid to end each one), your calendar and contacts connection (once your account is gone, Common Ink asks Google to end its access), what you merged or dismissed of your contacts, your email, with the addresses and rules you added, your clipper, the invites you sent and those sent to you, the grants waiting for your email, your email on the email list, and every workspace you are the only member of. Your agents stop at once. Your changes in workspaces shared with others stay, attributed to "A former member", with no name or email, and so do the agents that made changes there, as "A former member's agent". Where someone else mentioned you in their notes, the mention keeps your name as they wrote it: that text is theirs. If you own a workspace that others are in, you first hand it to another member, by making them an admin and then its owner, or delete the workspace. Once paid plans start, if you subscribe, deleting your account first cancels your subscription at Stripe, at once and with no refund, and deletes Common Ink's record of your plan. A workspace you hand to someone else is paid for by them from then on.
A workspace. An admin deletes a workspace in Settings. From that moment nobody reaches it: its members, invites, grants, share links and the agents limited to it go at once. Its notes, their history, its uploads and their bytes, and its folders are then erased, most often in the same request, and otherwise by the hourly job.
What a deletion removes from the database stays in the backup history until it is 30 days old. Counts of how the app was used are not deleted with an account or a workspace: they stay, under the same pseudonym and workspace id and with nothing that names you, until they are three months old.
Getting a copy of your data
In any workspace, you can download a zip of every note and file you can read there. The notes come as Markdown and the files as they were uploaded, in their folders. What is in Trash is left out: restore it first to include it. Your email and what was kept of your banks and cards are not in it.
Your rights
You can ask us to see, correct, export or delete your information by writing to support@commonink.app. We answer within 30 days. Depending on where you live, you may have more rights, such as to object to how we use your information, and to complain to your data protection authority.
Security
All traffic to Common Ink is encrypted. Google and Plaid tokens are encrypted before they are stored, and agent, clipper and app tokens are stored only as hashes. Every request is checked against what its person or agent may reach. The security page says more. To report a security problem, email security@commonink.app. If we learn of a breach that affects your data, we will tell you within 72 hours of confirming it, and tell Plaid where it affects what came from your bank.
Children
Common Ink is not for anyone under 18, and we don't knowingly collect information from anyone under 18.
Changes to this policy
If we make a material change, we will tell you in Common Ink or by email before it takes effect. Before Common Ink uses Google user data in a new way, it will ask for your agreement to the new policy.