Privacy Policy

Semantic Checker operates this service and is responsible for the data described here. This policy covers the Semantic Checker web application and its marketing pages. Questions and deletion requests go to thirdweb30@gmail.com.

• —Your Google account details. Signing in with Google is the only way in. Google returns your name, email address, profile picture URL, and an account identifier, and we store those along with the OAuth tokens needed to keep you signed in. We never receive or store a password — there is no password on this service to steal.
• —The content you analyze. Your target query, the optional title, and the full article text are stored with your account so reports stay available at their own URLs. Text you bring in through Import URL is stored the same way as text you paste.
• —Reports. Each analysis result — scores, section verdicts, evidence, and priority fixes — is stored alongside the content it describes.
• —Your credit ledger. An append-only record of every credit granted, spent, and refunded. It is never edited or deleted in place, because it is what makes your balance auditable.
• —Billing pointers. A customer identifier and subscription state from Stripe. Card numbers never reach our servers — Stripe collects and holds them.
• —Session and operational records. Session tokens with the IP address and user agent that created them, plus ordinary server logs used to keep the service running and to enforce rate limits.
• —Page-view analytics. Google Analytics records which pages are opened, which site referred you, and standard device, browser, and language details. It is described in full below, and it never receives your content.

• —We do not sell or rent your data, and we do not share it for advertising.
• —No ad tech. No advertising or ad-targeting scripts are bundled in this application, and the advertising side of Google Analytics — Google signals, ads personalization, and the third-party advertising cookies that come with them — is left switched off.
• —The complete cookie list: the cookie that keeps you signed in, your light/dark theme preference stored in your own browser, and the first-party _ga cookies Google Analytics uses to tell a returning visit from a new one. Nothing else, and nobody else.
• —We do not use your articles to train machine-learning models.

We run Google Analytics 4 on the marketing pages and inside the signed-in app, so we can see which pages people arrive on and which ones actually get used. Each page view reports the address of the page, the site that referred you, and ordinary device, browser, and language details. Google infers an approximate location — roughly city level — from your IP address; the address itself is not stored in the reports we see.

Analytics never sees your content. Your target query, your article text, and your report contents are sent to our own server in requests the analytics tag cannot read, and a report address contains nothing but a random identifier. We also do not attach your account or email to analytics events, so what we get back is traffic, not a profile of you.

To opt out, use your browser's cookie controls, any content blocker, or Google's official opt-out browser add-on. Everything on this site works exactly the same with analytics blocked.

Import URL makes our server request the page you name and extract its text. That request comes from our infrastructure, not your browser, so the destination site sees us rather than you. We only follow public HTTP and HTTPS addresses, refuse private and internal network destinations, and stop after a few redirects. We store the extracted text, not a copy of the page. Importing is free and does not spend a credit — only running the analysis does.

We rely on a small set of processors, each doing one job: Google for sign-in and for the traffic measurement described above, our database and hosting providers for running the service, Stripe for payments, and Resend for the handful of transactional emails we send. Where a self-hosted deployment substitutes different providers, this list changes with it.

If a deployment is configured to use an external AI provider for analysis, the content being analyzed is sent to that provider to produce the report. The default analyzer runs locally and sends your content nowhere.

Account data, stored articles, and reports are kept until you delete them or delete your account. Deleting your account from Settings removes your profile, your Google connection, every stored analysis and report, and your ledger history, and cancels any active subscription first. Records Stripe is required to retain for tax and accounting purposes stay with Stripe. Backups roll off on their own schedule.

Analytics events are the exception, and we would rather say so than leave it implied: they live in Google Analytics, expire on that property's own retention schedule, and are not removed when you delete your account — there is no link between the two to follow, which is the same reason they cannot identify you.

You can view and edit your name and email in Settings, delete individual reports, or delete the whole account at any time. Depending on where you live you may also have the right to request a copy of your data, ask for corrections, or object to particular processing — write to thirdweb30@gmail.com and we will respond.

Account deletion is confirmed by an emailed link, because with Google-only sign-in there is no password to re-enter.

Semantic Checker is a tool for people publishing content professionally and is not directed at children. We do not knowingly collect data from anyone under 16.

When this policy changes we update the date at the top of this page. Material changes to what we collect or who processes it will be announced by email before they take effect.