Privacy

What stays in your browser

The extension reads the posts X shows you so it can sort and fold them. Your settings, your rules, the list of accounts flagged as ads or adult spam, recent judgments, and the executors you asked for are kept in your browser's extension storage. So is a two-day reading log — for each post PolishX judged, its id, the author's name, handle and picture address, the first line of the post, the scores, and what was done with it — which is what the side panel shows you. None of it is sent to us. Uninstalling the extension deletes it all.

What is sent to judge posts

To judge a post, the extension sends its text and your rule sentences to our server at polishx.ai, which forwards them to Jev, a model run by TypeSafe (typesafe.ai), and returns the answer. We do not store the post or the answer.

When PolishX drafts your rules — on first run, or when you ask it to redraft — the extension reads your bio, recent bookmarks, likes, and the accounts you follow on your own X pages, in your browser, and sends a summary of them once to our server, which passes it through Vercel AI Gateway to GLM, a language model from Z.ai, with training on your data disallowed. We do not store what was sent or the draft; the draft comes back to your browser.

Your account and credits

You sign in with Google on polishx.ai. We receive your name, email address and profile picture from Google, and keep them with your account so you can sign in and we can tell you apart. We do not receive your Google password or any other Google data. The site sets one sign-in cookie; the extension uses it to get a short-lived token and keeps no password. PolishX does not need to know which X account you use and does not record it.

PolishX runs on credits. For your account we keep a ledger of them: each grant (the daily free credits, a plan's monthly credits, a pack you bought) and each charge, with its time, its kind (judging or drafting rules) and its amount, plus how many posts you had judged each day. Never the posts themselves. The account page shows you this ledger.

Payments

Plans and credit packs are paid on Stripe's checkout, and invoices, cards and cancelling live in Stripe's billing portal. Stripe collects your payment details under its own privacy policy; we never see your card number. We keep your Stripe customer id, the status and dates of your plan, and a record of each payment Stripe tells us about, so your credits match what you paid. Nothing in the extension takes a payment.

Automations

Light, collect and fold happen in your browser. Rules that send posts out of the page (a webhook, Slack, Discord) are not running yet; asking for one is kept in your browser. Before any automation runs, this page will say what it sends, where, and what we keep.

Error reports

When something breaks in the extension or on the site, an error report goes to our own error system, stored on Cloudflare: the error message, where in our code it happened, the extension version, and your browser and operating system. Reports from the extension never include the address of the page you were on or any post. We use them only to fix PolishX.

Usage counts

PolishX counts how it is used, so we can find what breaks and what people need. An event is a count or a choice: that the side panel opened, that the first reading finished or failed and why, that you kept or discarded a draft, how many posts were judged, folded, removed or lit in a day, how many posts and replies each judging request carried and how much model input it used, that credits ran out, and which page or button you used on the website. Events never include a post, text you wrote, an X account you use or follow, or the address of a page you read on X. On the website, a page view records the polishx.ai address you opened, the site that linked you here and any campaign tags in the link, so we can see how people find PolishX.

Each browser gets a random identifier. Once you sign in it is linked to your PolishX account and its organization, so one person's day of use counts once. Events go to Celados's own analytics service at stat.celados.com, which runs on Cloudflare, and are not sold or given to an advertiser. The website keeps its identifier in your browser's local storage and cookies, and honors Do Not Track and Global Privacy Control. If you visit from the European Economic Area, the United Kingdom or Switzerland, a cookie card asks first, and the website measures nothing until you accept; “Essential only” keeps it off. In the extension, Settings has a switch, “Share anonymous usage”, that turns it off; until you turn it off, usage counts are on.

Right after you install the extension, it opens a page on polishx.ai that links its random identifier to the website's, so a visit to polishx.ai and the install that followed count as one person even before you sign in. It does this only while usage sharing is on.

When you remove the extension, Chrome opens a page on polishx.ai. It counts the removal with the extension's version and, unless you had turned usage sharing off, its random identifier, and asks you, if you like, why you removed it.

What we do not do

We do not sell your data, show ads, or use your data to train models. We do not share it except with the services named on this page, which process it to run PolishX: Cloudflare (hosting), Convex (our database), TypeSafe (Jev), Vercel (AI Gateway), Z.ai (GLM, for drafting rules), Google (sign-in) and Stripe (payments).

Deleting your data

Email hello@celados.com from the address on your account and we will delete your account, your credit ledger and your usage records. Stripe keeps billing records it is required to keep by law.

Changes

If this policy changes, the date above changes with it. We will email account holders before any change that uses data in a new way.