Privacy Policy
Last updated: 10 November 2026
1. Introduction
Welcome to BiasChecker.ai ("we", "us", or "our"). We respect your privacy and are committed to being transparent about our data practices.
This privacy policy explains how we collect, use, and protect your information when you use our website, Chrome extension, and related services, in compliance with the General Data Protection Regulation (GDPR), the UK GDPR, and other applicable data protection laws.
Data controller. The controller responsible for your personal data is Tautech B.V. (KvK no. 83747311), Salland 1, 1948 RE Beverwijk, the Netherlands. For any privacy question or to exercise your rights, contact us at contact@biaschecker.ai.
BiasChecker.ai is an AI-powered media analysis utility. How we handle the content you analyse depends on how you submit it (see Section 2.2). In summary: to produce an analysis, the text you submit is sent to third-party AI providers and passes through our servers; for web page analyses we retain numerical metrics and positional anchors rather than the article text, whereas text you paste or type directly is stored, together with its analysis, in your private account area so you can revisit, manage, and delete it.
2. Information We Collect
2.1 Account Information
When you sign in to BiasChecker.ai using Google, we collect the following information from your Google account:
- Email address - Used to identify your account and communicate with you
- Name - Used to personalise your experience
- Profile picture - Displayed in the user interface
This information is provided by Google through their OAuth authentication service. We only access information you authorise through Google's consent screen.
2.2 Analysis Data
When you use our bias analysis tools:
- Processing by AI providers - To generate an analysis, the text you submit is transmitted to and processed by third-party AI providers (see Section 6) and passes through our servers for that purpose
- Web page analyses - When you analyse a web page in the browser extension, we store the analysis as numerical metrics, category classifications, and positional anchors. We do not store the article's full text or verbatim quotations on our servers; quotations are re-resolved from the live page in your browser. These analyses are stored in a shared cache keyed to the public content and are not linked to your account
- YouTube videos - When you analyse a YouTube video in the browser extension, the extension reads the captions of the video on screen, in your browser, and sends that text for analysis instead of the page around the player. What we keep follows the web page rules above: the analysis, stored against the video's address, not the transcript
- TikTok videos - When you analyse a TikTok video in the browser extension, the extension reads the captions of the video on screen, in your browser: it takes the caption file from the video's page (fetching that page again from TikTok when you reached the video from elsewhere on TikTok) and sends that text for analysis instead of the caption, hashtags and comments around the video. What we keep follows the web page rules above: the analysis, stored against the video's address, not the transcript
- Text you submit directly - When you paste or type text to analyse (for example on our website), we store the text you submit together with the resulting analysis (including verbatim quotations) in your private account area, so you can revisit, manage, export, and delete them. These are visible only to you and are linked to your account
- Questions about an analysis - When you ask a question about an analysis, your question, the analysis, the text it was made from and your earlier questions and answers on it are sent to the provider of the model that answers. We hold the answer for at most 3 days so it can be delivered to you and store nothing else; your browser keeps the questions and answers for the current session only
- Operational records - Separate account, billing, security, and abuse-prevention systems store non-content operational records such as account status, subscription status, credits, token usage totals, authentication records, request status, error information, and technical metadata
- Token usage - We track the number of tokens used per account for billing purposes
Account linkage: Analyses of web pages and other public content are stored in a shared cache and are not linked to the user who requested them. Analyses of text you submit directly are stored in your private account area and are linked to your account, so you can find, manage, and export them.
Please do not submit confidential, proprietary, highly sensitive, legally restricted, or special-category personal data unless you have the legal right and all required permissions to do so.
2.3 Analytics Information
Website. We use Google Analytics to understand how visitors interact with our website. Google Analytics collects standard internet log information and details of visitor behaviour patterns, including online identifiers such as cookie IDs and IP-derived approximate location, which we use in aggregate to improve our services. Where required by law, analytics cookies are used only with your consent (see Section 7).
Browser extension. The extension can send usage analytics to Google Analytics, but only if you turn this on: it is off by default, the side panel asks you once, and you can change your answer at any time under "Share usage analytics" in the extension's settings. When it is on, the extension sends events such as an analysis completing or failing, with the analysis type, whether the result came from the cache, how long it took, the length of the text, and error codes. It never sends the page address, the article text, the results, your email address, or your sign-in tokens. Events carry a random identifier stored in the extension so that they can be grouped; it is not linked to your account, and it is removed when you uninstall the extension. Turning analytics off stops all further events; events already sent cannot be recalled.
2.4 Bug Reports
If you choose to send a bug report from the browser extension ("Report a bug"), we receive only what you send when you press Send:
- Your description of the problem
- A screenshot of the extension panel (or of the extension's Compare or Discover page) you reported from, if you leave it ticked. It shows the extension's own window, never the web page you are reading, although it can show analysis results and short article quotations displayed there
- The address of the page you were on, in full
- Technical details - the extension version, browser and operating system version, language, time zone, window size and scroll position, your extension settings, your plan and remaining allowance, what the extension was showing (for example which analyses were loaded and with which model), and recent extension error messages and request records (address path, status, timing, and request identifier; never request contents, passwords, or sign-in tokens)
- Your account identifier and email address, taken from your signed-in session, so we can follow up on the report
The dialog shows what will be sent before you send it. We use bug reports only to investigate and fix the problem you reported. They are stored in our cloud infrastructure (see Section 6), are visible only to the BiasChecker.ai team, and are deleted automatically after 30 days (see Section 9). When a report arrives, a short notification (your email address, the page address, and the start of your description) is emailed to the team's internal inbox.
2.5 Referral Programme
Every account has an invite code. When you sign up with a friend's code or link, we record on your account which account invited you and, once you buy, when and with which purchase you earned your reward. On the inviting account we record how many invited friends earned it a reward and, if we stop its invitations for abuse, when; both accounts hold the reward credits. We use these records to grant and withdraw rewards under the Terms of Service and to detect abuse of the programme. The inviting account sees how many friends earned it a reward and when its rewards still to come are added, never who the friends are. The records are part of each account and are deleted with it.
3. How We Use Your Information
We use the information we collect to:
- Provide and maintain your account
- Authenticate you when you sign in
- Personalise your experience on our website
- Generate AI-powered analyses, scores, and related outputs you request
- Reconstruct or retrieve previous analysis outputs for the same or substantially similar public content from stored numerical metrics and positional anchors
- Track token usage, credits, subscriptions, billing, fraud prevention, and abuse prevention
- Investigate and fix problems you report from the extension
- Improve our services and develop new features
- Communicate with you about service updates
- Analyse usage patterns to improve user experience
We do not sell your personal information to third parties.
4. Legal Bases for Processing
Where the GDPR applies, we process personal data on the following legal bases:
- Contract - To create and manage your account, provide the Service, process payments, deliver analyses, and manage subscriptions or credits
- Legitimate interests - To analyse and provide critical commentary on published media content (an information and expression activity), secure the Service, prevent abuse, debug errors, investigate bug reports you send us, improve performance, reuse stored metrics and anchors for public content, understand aggregate usage, and protect our legal rights
- Consent - For optional analytics, cookies, marketing communications, or other features where consent is required
- Legal obligation - To comply with tax, accounting, consumer protection, law-enforcement, or regulatory obligations
Analysis of published media and special-category data. Our core function is the analysis of, and commentary on, published media content that our users choose and submit. That content may name or discuss identifiable individuals and may incidentally reveal special-category information about them (such as political opinions). We carry out this processing for journalistic, academic, artistic, and literary expression and for the provision of information, and we rely on the freedom-of-expression and "special purposes" provisions implemented under Article 85 of the GDPR (and the equivalent "special purposes" exemption in Schedule 2 of the UK Data Protection Act 2018), together with our legitimate interests, as the basis for it. We do not use this content to build profiles of individuals or to make decisions about them.
Content you submit. Where you paste or submit your own text, you choose what to send and are responsible for ensuring you have a lawful basis to do so. In respect of that submitted content you determine the purpose of the processing and we act on your instructions to produce the analysis you request, as further described in our Terms of Service.
5. Data Storage and Security
Your account information, saved analyses, usage records, stored numerical metrics, positional anchors, and technical metadata are secured using industry-standard cloud infrastructure that provides:
- Encryption for data at rest and in transit
- Secure token-based authentication
- Compliance with major security standards
We implement appropriate technical and organisational measures to protect your personal information against unauthorised access, alteration, disclosure, or destruction.
No internet-based service can guarantee absolute security. You are responsible for not submitting content you are not authorised to process and for keeping your account credentials secure.
6. Third-Party Services
We use the following third-party services that may process your data:
- Google Sign-In — For authentication. Subject to Google's Privacy Policy
- Google Analytics — For website analytics and, only if you turn it on, extension usage analytics (Section 2.3). On the website you can also opt out using the Google Analytics Opt-out Browser Add-on
- YouTube — The product videos on our home page and extension page are hosted on YouTube. Nothing is loaded from YouTube until you press play. When you do, your browser connects to Google, which receives your IP address and standard browser information under Google's Privacy Policy. We use the youtube-nocookie.com player, which does not set tracking cookies before you play.
- Stripe / Link — Purchases are made through Link, the merchant-of-record service operated by Stripe (including its affiliates Stripe Payments Company and Stripe Technology Europe, Limited). For the personal data processed to complete your purchase (such as your name, email address, billing address, payment details, and transaction history), Stripe acts as an independent data controller under Stripe's Privacy Policy and the Link Privacy Policy. We receive transaction and subscription metadata (plan, status, amounts); BiasChecker.ai never receives or stores your payment card details. You can also ask Stripe directly, through your Link account, to delete the data associated with your purchases.
- AI / LLM Providers — To generate analyses, the text you submit is transmitted to and processed by the large language model provider behind the model you select (or the default). At present these are: Amazon Web Services (Bedrock), which serves the Moonshot Kimi and Z.ai GLM 4.7 models; OpenAI (GPT models); Google (Gemini models); xAI (Grok models); Anthropic, PBC (Claude Haiku, Sonnet and Opus models); and OpenRouter, Inc., a United States model-routing service through which the DeepSeek, Z.ai GLM 5.2 and Alibaba Qwen models are served (we instruct OpenRouter to route only to hosting providers that do not retain or train on submitted content; the Qwen model is hosted by Alibaba Cloud International). The line-up changes as models are added and retired; the current list is on our models page. We use the business or API tiers of these providers where available; under those terms your content is used to generate your analysis and is not, to the extent within our control, used by the provider to train its models. Please review the respective privacy policies: AWS, OpenAI, xAI, Google, Anthropic, OpenRouter.
- Cloud Infrastructure — Your account data, saved analyses (including any text you submitted), bug reports you send, usage records, numerical metrics, positional anchors, and non-content operational metadata may be stored or processed on servers located in the United States or other countries where our providers operate. Where required, international transfers are protected by appropriate safeguards such as the European Commission's Standard Contractual Clauses (and, for transfers from the United Kingdom, the UK International Data Transfer Addendum), data processing agreements, or other lawful transfer mechanisms.
7. Cookies
We use cookies and similar technologies for:
- Essential / authentication - To keep you signed in and maintain your session. These are necessary for the Service to function
- Analytics - To understand how you use our website (Google Analytics). These are non-essential. Where the law requires prior consent (the EU and EEA, the United Kingdom, Switzerland, and Quebec), we show a consent banner and set them only if you accept; elsewhere they are set on the basis of our legitimate interest in understanding aggregate usage, and you can opt out with the Google Analytics opt-out described in Section 6
Where the banner is shown, you can change your choice at any time with the "Cookie settings" link in the page footer. You can also manage cookies through your browser settings. Declining analytics cookies will not affect essential functionality. Most browsers let you refuse or delete cookies; refusing essential cookies may affect your ability to sign in.
8. Your Rights
Under the GDPR and applicable data protection laws, you have the following rights:
- Right of access — Request a copy of the personal information we hold about you. This includes your account profile (name, email, plan), aggregate token usage, any analyses you have saved to your private account (including text you submitted), and any bug reports you sent in the last 30 days.
- Right to rectification — Your name, email address, and profile picture are sourced directly from your Google account. To correct them, update your Google profile. If any other information we hold is inaccurate, please contact us and we will correct it.
- Right to erasure — Delete your account and all associated data, including your saved analyses, any stored text, and your bug reports, directly from the dashboard (Account section). If you have an active subscription, cancel it first; the account can be deleted as soon as the subscription has ended.
- Right to data portability — Download an export of your data directly from the dashboard (Account section). The export is a ZIP archive containing your account profile, usage statistics, your saved analyses (including any text you submitted), and any bug reports you sent in the last 30 days, with their screenshots.
- Right to restrict or object to processing — You may ask us to restrict processing of your personal data, or object to processing we carry out on the basis of our legitimate interests (including analytics), as described in Section 4.
- Right to withdraw consent — Where we rely on your consent (for example optional analytics or cookies), you may withdraw it at any time, without affecting processing already carried out: use the "Cookie settings" link in the page footer for website cookies, or the extension's settings for its usage analytics.
Account deletion, data export, and access to your personal data are all available directly from the dashboard without needing to contact us. Most personal data we hold (name, email, profile picture) comes from your Google account — to correct it, update your Google profile; your saved analyses and any stored text can be managed or deleted from the dashboard. For any other questions about your rights, please contact us using the information below.
You can also revoke BiasChecker.ai's access to your Google account at any time through your Google Account settings. If you believe your data protection rights have been violated, you have the right to lodge a complaint with your national data protection authority. In the Netherlands this is the Autoriteit Persoonsgegevens; if you are elsewhere in the EU or in the UK, you may contact your local supervisory authority.
8.1 California Privacy Rights
If you are a California resident, you have the right to know what personal information we collect (described in Section 2), to request access to or deletion of that information, to correct inaccurate information, and not to be discriminated against for exercising these rights. You can exercise these rights from your dashboard or by contacting us.
We do not sell your personal information, and we do not share it for cross-context behavioural advertising. We do use analytics cookies (Section 7); some privacy laws may treat certain analytics as a "sale" or "sharing", and you can opt out by using the Google Analytics opt-out described in Section 6 or by contacting us.
8.2 If you are mentioned in analysed content
BiasChecker.ai analyses published media that our users choose to submit, and an analysis may refer to individuals who are named or discussed in that content. We do not maintain a database organised by individual identity: analyses are keyed to the underlying content (for example a web page URL), not to the people mentioned in it, and we are not able to search our analyses by a person's name. For web page analyses we store numerical metrics and positional anchors rather than the article text. These results stay in the shared cache until they are removed at the request of a publisher or an affected person, or hidden by our takedown process (see Section 9.1).
Because of this, if you are an individual mentioned in analysed content and you wish to exercise your data protection rights, we may be unable to identify or act on your request unless you provide the specific content concerned — normally the exact URL of the analysed page, or the text in question. With that information we will locate any stored analysis of that content and review your request, and we can remove or disable access to a specific result where appropriate. As explained in Section 4, we process this content for expression and information purposes, which may qualify or limit some of the rights described above, but we will always consider credible requests in good faith. You can reach us at contact@biaschecker.ai.
9. Data Retention
We retain your account information and saved analyses for as long as your account is active. You can delete your account and all associated data at any time from the dashboard (after cancelling any active subscription). We may also delete inactive accounts: after 180 days without signing in, your account and all associated data may be permanently deleted. Before any such deletion we send reminder emails to the address on your account approximately 30 days, 7 days, and 1 day beforehand, and signing in at any time resets this period. When you delete your account (or it is deleted for inactivity), we remove your personal information, saved analyses, and any stored text from our systems within a reasonable timeframe, except where we are required to retain certain records by law. Your payment card and billing details are handled by Stripe (through its Link merchant-of-record service) acting as an independent data controller, and are not stored by us; limited transaction records that form part of our business accounting are retained for the period required by applicable tax and accounting law.
Bug reports you send from the extension, including their screenshots, are deleted automatically 30 days after you send them, or earlier when you delete your account.
Each request the extension or the website sends to our servers is logged with its time, your IP address, the path requested, the response status, your browser's user agent and, when you are signed in, your account identifier; we keep these logs for 30 days for security and abuse prevention.
9.1 Performance Caching
To maintain performance and reduce duplicate processing, analyses of public web pages are stored as numerical scores, category classifications, and positional anchors in a shared cache, allowing identical public URLs to be served quickly to other users. For these web page analyses we do not store the article's full text or verbatim quotations on our servers; quotations are re-resolved from the live page in your browser. Cached analyses are kept for as long as they remain useful to the community and are not deleted on a fixed schedule; a specific analysis is removed or hidden when a publisher or an affected person asks us to, when enough readers flag it as inaccurate, or when the analysis type it belongs to is retired.
Text you submit directly (for example by pasting it on our website) is stored, together with its analysis, in your private account area so that you can revisit and manage it. It is deleted when you delete the analysis or your account, or if your account is deleted after 180 days of inactivity (see above).
We may retain account data, usage records, billing records, non-content operational metadata, numerical metrics, and positional anchors to provide the Service, reduce duplicate processing, control costs, improve quality, investigate abuse, and document how the Service performed.
Billing, tax, accounting, fraud-prevention, and security records may be retained for longer where required or permitted by law.
10. Children and Sensitive Data
The Service is not intended for children under 18 or the age of majority in their jurisdiction. Do not submit personal data about children unless you have a lawful basis and all required permissions.
Do not submit special-category personal data, health records, financial account data, government identifiers, confidential business information, trade secrets, or other highly sensitive content unless you are authorised to do so and accept the processing described in this policy.
11. Changes to This Privacy Policy
We may update our Privacy Policy from time to time. We will notify you of any material changes by posting the new Privacy Policy on this page and updating the "Last updated" date. You are advised to review this Privacy Policy periodically for any changes.
12. Contact Us
If you have any questions about this privacy policy, our privacy practices, or wish to exercise your data rights, please Contact Us