Privacy policy

Effective October 21, 2026

Monton (https://monton.dev) is a place where people and their AI agents write docs together, with full version history. Enrique Carlos Enríquez Minjárez runs Monton as an individual, not a company. In this policy, "we" means Monton and the person who runs it. If you have a question, write to enrique.c.enriquez.m@gmail.com.

In short: we collect what we need to run Monton. We don't sell your data, we show no ads, and we don't train AI models on your content. We send your docs to no AI provider. An agent you connect reads only what you can read, and its provider handles that under your agreement with them.

What we collect

Your account. You sign in with Google, or with a one-time code that WorkOS, our sign-in provider, emails you. You can also set a password. WorkOS gives us your email address, whether you verified it, your first and last name if you gave them, and your WorkOS account's ID.

What you write. Your docs and folders, every version of every doc (like GitHub, we keep a doc's full history), your comments and replies, and the passage each comment quotes. We also keep a search index of each doc's current text. When you import an archive, we keep it for up to 15 minutes while you look at the preview, then delete it, and keep only the text files that become docs.

Who you work with. Your workspaces and their members, with each member's role and who added them; what you share and with whom; invites, including the email address of the person you invite, who may not have an account yet; and your inbox of mentions, replies, adds and shares.

Your agents. When you connect an agent such as Claude or ChatGPT, we create an agent under your name ("Ana's Claude") and record the app it connects from and when it last used Monton. Agents sign in through WorkOS, or with a personal access token: we show you a token once and keep only a hash of it, so we can't read it. Every change and comment an agent makes carries its name.

Email settings. Whether you want notification emails, and the addresses that unsubscribed from all our emails. So we don't email you about something you already saw, we record when you last opened each doc in the web app (once per visit, never for agents).

Cookies and browser storage. We use cookies only for signing in. We set monton_session to keep you signed in for up to a week after your last visit, short-lived cookies to hold a sign-in in progress, and, after we refuse a sign-in, monton_choose_account for 30 days, so you can pick another account next time. In your browser's storage, we keep the workspace you opened last, the folders you expanded, the agent you picked on the Connect page, and comment drafts you haven't sent. We use no analytics, no advertising cookies and no third-party trackers, and we serve our own fonts. We load an image from another website in a doc only when you click it; that website's owner then sees your request.

Network addresses and logs. We use your IP address to limit how often one address can sign in or try a token. We keep those counts in the server's memory and forget them within minutes. To stop anyone from creating accounts in bulk, we also count new accounts per address in our database: we store a keyed hash of the address, not the address itself, and delete it after 7 days. In our server logs, we record errors and unusual events, naming workspaces and docs by ID, never by their text. We may log the IP address of a client we slowed down, or the email address of a sign-in we refused.

Error reports. When something goes wrong, we send a report to Sentry from the server or the web app. First we remove doc text, request bodies, cookies, email addresses, tokens, and the parts of web addresses that name your workspaces or docs. We identify you in a report only by an internal ID, and include your browser's name and version. We send no performance traces, screen recordings or session replays.

How we use it

We use this information to run Monton: to sign you in, save and merge your edits, keep history, search, show comments and your inbox, send the emails you asked for, and let your agents work. We also use it to keep Monton secure, stop abuse, and fix bugs, and we may email you about your account or about changes to Monton. We use it for nothing else, and we build no profile of you.

We don't read your docs unless you ask us for help with them, we need to look into abuse or a security problem, or the law requires it. We have built no tool for browsing people's docs, and only Enrique Carlos Enríquez Minjárez can reach Monton's production systems.

Who sees your content

People you work with. Members of a workspace see its docs, history, comments and members, as their role allows, including each member's name and email address. When you share a folder or a doc with someone, they see it, its history and comments, and the names and emails of others who can see it. In history, anyone with access sees who changed what, and when. People who have the same doc open see your name and your cursor.

Agents. An agent you connect can read and change what you can, up to an editor's access. What it reads goes to the company behind it, such as Anthropic or OpenAI, under your agreement with them, not this policy. Other members' agents can read what those members can read. We call no AI models ourselves.

Our service providers. These companies handle data for us, only to provide their service:

• Fly.io hosts the server in Ashburn, Virginia, in the United States, and keeps its logs.

• Neon hosts the database on Amazon Web Services in Northern Virginia, encrypted on disk.

• WorkOS signs in people and agents, and holds your email, name and sign-in records.

• Google, only if you sign in with Google, under Google's own privacy policy.

• Resend sends our emails from mail.monton.dev. It sees your address and each email's content, which can include workspace and doc names and up to 300 characters of a comment.

• Sentry receives the error reports above.

If you install the Monton command-line tool, npm delivers it to you; we learn nothing about you from npm. We share your data with nobody else, unless the law requires it; then we tell you, unless the law forbids us to.

Our server and database run in the United States. If you use Monton from another country, your data travels there.

How long we keep it

We keep your account and content for as long as your account exists.

We keep old versions in history. When you edit a doc, we keep its earlier versions. When you delete a doc, we move it to Recently deleted, where people in the workspace can still see it and editors can restore it, and we keep its history. When you delete a comment, we remove its text and keep a record that it existed and who deleted it. When you edit a comment, we keep only the new text.

Neon keeps 7 days of database backups, so something we delete can stay in a backup for up to 7 days. After we send an email, we delete its content from our database and keep only who we sent it to, what kind it was and when; Resend keeps its own copy for a limited time. We keep invites after they expire, with the address they went to. Fly.io keeps server logs, and Sentry keeps error reports, for a limited time that their own policies set.

Deleting your account. We haven't built a button for this yet. Email us from your account's address. Within 30 days of your request, we delete your account and the workspaces where you're the only member, with their history, and remove your name and email from everything that stays. If you unsubscribed from our emails, we keep your address on our do-not-email list so we never email you again, unless you ask us to remove it too. In workspaces you share with others, your docs, edits and comments stay in that workspace's history, credited to a deleted account.

Your choices

• See and export. You can see everything we hold about your work in the web app, and copy a workspace's docs to your computer with monton clone in the command-line tool. For anything else, email us.

• Correct. Email us to change your name or email address.

• Stop emails. Turn off notification emails under "Email notifications" in the person menu, or with the link in any notification email. To stop all our emails, use the unsubscribe link in any of them.

• Disconnect an agent. Revoke it on the Agents page, or disconnect Monton in the agent's app.

• Delete. Delete docs and comments yourself, and ask us to delete your account.

Depending on where you live, you may have more rights under the law, such as to object to how we use your data, or to complain to your data protection authority. Email us and we will help. If you live in the EU or the UK: we use your data to provide the service you signed up for, and, for security and error reports, because we have a legitimate interest in keeping Monton safe and working.

Children

You must be at least 13 to use Monton, or 16 where local law requires it. If you believe someone younger has an account, email us and we will delete it.

Security

We use HTTPS for every connection, Neon encrypts the database on disk, we keep only hashes of tokens, and we seal the session cookie so nobody can read or change it. We don't encrypt docs end to end, because we need to read them on the server to merge edits, search, keep history and serve your agents. No service is perfectly secure; if someone gets into data about you, we will tell you promptly.

Changes to this policy

When we change this policy, we post the new version here with a new date. For changes that matter, we tell you by email or in Monton at least 14 days before they take effect.

Contact

Enrique Carlos Enríquez Minjárez, enrique.c.enriquez.m@gmail.com