Privacy, in plain language

Last updated 2026-06-12 · applies to CheapAgent v0.2.9 beta

Your documents stay in your browser

When you paste or upload a document, the conversion runs locally in your browser using the open-source doc2toon engine. The text of your document is never uploaded, never stored, and never sent to a server or an LLM API. This is true whether you are signed in or not.

What we store if you sign in

Signing in raises your daily allowance from 1,000 characters per run to 15,000 characters per day. To enforce that limit we keep a minimal account record:

• Your user id and email address (managed by Netlify Identity).
• How many characters and conversions you have used today.
• Timestamps for when the account was created and last used.

That is the whole account record. No document bodies, no document titles, no conversion history. When your browser checks your remaining allowance, it sends only a character count — a number — not the text itself. Counters from previous days are discarded from your account record; we keep only today's totals there. The only thing kept day over day is the site-wide aggregate described next.

Site-wide daily totals

To understand whether CheapAgent is being used at all, we keep one aggregate counter record per day for the whole site: how many allowance checks, conversions, first-time-today accounts, and debited characters happened that day, as plain totals. Since 2026-06-12 the same daily record also counts, as plain totals: copy and download clicks by signed-in users (which button, never what was copied), useful/not-useful feedback votes, and clicks on the two interest links on the API early-access page. These totals contain no user ids, no emails, and nothing that links a number to an account. Daily totals older than about 400 days are deleted.

Every number in that record comes from an explicit action — running a check while signed in, clicking a button that says what it does. Nothing is counted from merely visiting or reading. Quota counters and copy/download counts cover signed-in activity only; feedback votes and interest-link clicks count the click itself and carry no identity either way.

One honest caveat: on a very low-traffic day, a daily total could in practice reflect a single account's activity. See deletion requests below for how we handle that.

What we never store

• The contents of anything you paste or upload.
• Your converted TOON output.
• Passwords — credentials are handled entirely by Netlify Identity, not by CheapAgent code.

Anonymous use

You can use CheapAgent without an account. Anonymous use makes no network requests with your content or its size; the 1,000-character limit is applied in your browser. The only network requests anonymous use can make are ones you explicitly trigger by pressing something that says it submits: the useful/not-useful buttons (one anonymous bit), the waitlist form on the API early-access page (the fields you typed), or a /go interest link (one anonymous click count). Nothing about your document travels with any of them, and nothing is ever sent passively.

The API early-access page

The hosted API early-access page has three things that talk to a server, all opt-in:

• The waitlist form. Submitting it stores what you typed — your email, and optionally why hosted matters to you — with Netlify Forms, so we can email you about hosted API early access. That is the only use. It is the one place on this site that stores an email address outside of account sign-up. Deletion on request, same as accounts.
• The two interest links (/go/pro, /go/enterprise). Clicking one increments a server-side daily total — a number, with no cookie, no identity, and no request body — and forwards you to the waitlist. We use the totals to decide whether to launch the hosted API.
• The labeled email address, if you choose to write to us directly.

Cookies and local storage

CheapAgent sets no advertising or analytics cookies. The only cookies it sets are essential first-party sign-in cookies (nf_jwt and nf_refresh), set by Netlify Identity to keep you signed in — only if you sign in, and cleared when you sign out. Browser local storage is used for at most three things:

• Sign-in session (essential) — your Netlify Identity token, held in local storage and the sign-in cookies above, only if you sign in.
• Theme preference (optional) — remembers light or dark mode, only if you choose “Allow all” in the consent banner.
• Your consent choice itself (essential) — so we do not ask again on every visit.

You can change your storage choice at any time; the same link is in the footer of the main page as “Cookie preferences”.

Third parties

CheapAgent is hosted on Netlify, and sign-in is provided by Netlify Identity. Waitlist form submissions are stored by Netlify Forms — the same provider, same policy. Netlify processes requests as our hosting provider; see Netlify's privacy policy for how they handle infrastructure-level data such as IP addresses and user-agent strings in server logs.

Our Netlify setup also runs Netlify's Prerender extension (active since 2026-06-02, disclosed here 2026-06-12): it checks each request's user-agent header to recognize web crawlers and AI agents, and serves those agents a cached, pre-rendered copy of the requested page from Netlify's storage. The cached copies are of our own pages — they contain nothing you typed, and the extension collects and stores no visitor data. Human visitors receive the site directly and are unaffected. No other analytics or measurement extension is active: one called Baseline is installed at the Netlify team level but has never been enabled for this site, and we verified it captures nothing in that state; if that ever changes, this page changes first, in the same release.

No billing in v0.2

The v0.2 beta has no paid tier and collects no payment information.

Questions or deletion requests

To ask a question or have your account record deleted, open an issue at github.com/Profusion-AI/cheapagent-ai or contact the maintainer listed there. Because we store so little, deletion means removing your Identity account and the usage counter keyed to it. On request we will also zero any site-wide daily total from a day where fewer than three accounts were counted, since on such days the total could otherwise describe your activity. (Daily totals are not linked to accounts, so beyond that there is no per-account history to delete — none exists.)

Changes

If this page changes in a way that affects what is stored, the change will be noted in the project changelog with the date.