SourceMate – Privacy Policy
SourceMate is a Chrome extension that cross-checks the claims on the page you are reading, and shows each source's bias and reliability. This policy explains, plainly and completely, what data leaves your browser, who receives it, and what is kept. If anything here stops being true, this page will be updated before the change ships.
The short version
- Nothing is read or sent until you click a check button.
- When you do, the text you asked us to check is sent to our server and on to Google's Gemini AI. That is how the check works – it cannot work without it.
- We have no accounts, no analytics, no advertising, no tracking, and we do not sell or share your data for any other purpose.
- Our server does not save what you check. It keeps counts – how many checks have run, and what they cost us – with nothing in them that identifies you or the page.
- Google and our hosting provider, Vercel, do keep some data for limited periods, described below.
- SourceMate is in beta and free to use, so checks are capped. You may be told to come back tomorrow; nothing extra is collected when that happens.
- Don't run a check on a page containing private information (an email inbox, a medical record, a bank page). Its text would be sent to Google like any other page.
What is sent, and when
| When you… | What leaves your browser | Where it goes |
|---|---|---|
| Click Check this page | The readable text of the page (up to about 3,000 characters, or up to about 50,000 for recognised news sites), plus the site's name or domain (for example “BBC” or “example.com”). The full page address is not included in what is sent. | Our server, which passes it straight to Google Gemini. |
| Click Check this video on YouTube | The video's title and caption transcript. To get these, the extension first requests the video page and its captions from YouTube directly, using your browser's normal YouTube session – so YouTube sees that request as coming from you, just as when you watch the video. | Title and transcript go to our server, then Google Gemini. |
| Check a post on X or Reddit | The text of the post as it appears on the page, and which of the two platforms it came from. Not your account, not your handle, and nothing else from the page. | Our server, then Google Gemini. |
| Paste a claim and check it | The text you pasted. | Our server, then Google Gemini. |
| Any check that returns sources | The web addresses of the sources the AI cited, and (when a link is missing) the outlet names and the claim text, so a real link can be looked up. | Our server. It visits those addresses, and the outlets' public sitemaps, to confirm the links are real. The outlets see our server, not you. |
| Carry on searching | The same content again, with the searches made so far. | Our server, then Google Gemini. |
In Live mode, Gemini also runs Google searches built from that content. Fast mode uses no searches.
Every request from your browser to our server – like any website visit – also reveals your IP address and browser type to the server's host.
Who receives it and what they keep
Our server (hosted by Vercel). Our code does not save the content you check, and does not write it to any log or database. It only passes it to Google and returns the answer. Vercel, which runs the server, automatically records basic details of each request – such as the time, the address requested, the response status, your IP-derived region and your browser's user agent – in its request logs.
Vercel keeps these logs for about one hour.
Google (Gemini API). Google processes the content to produce the check. Because Live checks use Grounding with Google Search, Google's terms say it stores the prompt, context and output of those requests for 30 days to generate search results and to debug and test that feature.
We use Google's paid API service. Google's terms say it does not use this content to improve its products, and keeps it only temporarily to detect abuse and keep the service secure – in addition to the 30-day search grounding storage above.
Google's own terms apply to its handling: Gemini API Additional Terms and the Google Privacy Policy.
Upstash. The counters described in the next section live in a Redis database run by Upstash, in London. It holds numbers only: no page text, no claims, no links, and no IP address.
News outlets and YouTube. Outlets whose links we confirm receive ordinary web requests from our server. YouTube receives the request your browser makes for a video's page and captions, as described above.
No one else receives your data. We do not sell it, use it for advertising, or give it to data brokers.
Your install, and the counters that keep it running
SourceMate is free, and it pays Google for every check, so it has to be able to tell one install from another – otherwise one person could spend the whole budget. There are no accounts, so this is how that works instead.
An install token. The first time the extension needs one, our server generates sixteen random bytes, signs them, and hands the result back as a token. The extension keeps it in its own storage and sends it with every later request. It is not derived from you, your browser or your machine, it contains no personal data, and it is not linked to anything else we hold – it identifies the installation and nothing more. Removing the extension discards it, and a fresh install gets a different one.
What the counters hold. Against that token we count how many checks it has run today. We also count how many have come from your internet connection in the last hour, keyed to a one-way cryptographic hash of your IP address rather than the address itself: we need to tell callers apart for an hour, not to know who they are. And we count the total across everyone for the day. The hourly count is discarded after an hour, the daily ones after a day.
What the cost log holds. So that we can see what SourceMate costs to run, each check adds one line recording what kind of content it was (article, video, post, pasted claim), which mode it used, which model answered, how many tokens and searches it took, how long it took, and whether it worked. There is no install token in it, no IP address, no page address, and nothing you checked. Those lines are discarded after 30 days.
What that means for the limits. While SourceMate is in beta there is a cap on checks per install per day, per connection per hour, and across everyone per day. If you reach one, the panel tells you which and when to try again. We are still learning what ordinary use looks like, so those numbers will change.
What is stored on your computer
These are saved in your browser's extension storage. Apart from the install token, which is sent with each request, none of them is sent anywhere:
- Your install token – described above.
- Your last check – the page address, the result, and when it ran – so reopening the panel on the same page doesn't cost another check. Only one is kept; the next check replaces it.
- How many checks you've run this month – a number, reset each month, shown in the panel.
- Your settings – light or dark theme, and whether disputed claims are prioritised.
- Which tips you have already been shown, so the panel doesn't repeat itself.
Removing the extension deletes all of these.
To match the panel to the site's colours, the extension also reads the colours of the page you're checking. That happens on your computer and nothing is sent.
Permissions, and why
- Read pages on all sites (asked for the first time you check a page, not at install). Needed to read the text of whatever page you choose to check. Once granted, Chrome allows access to any site, but SourceMate only reads a page when you click a check button.
- YouTube – to fetch video captions for video checks.
- Our own server – to send it the check and receive the answer.
- Scripting – to run the text reader on the page you're checking.
- Storage – for the on-device items listed above.
- Side panel – to show results beside the page.
Things we can't do
- Because our server keeps no copy of what you checked, we can't show you, correct or delete it – there's nothing on our side to retrieve. Copies held by Google or Vercel are governed by their retention periods above and their own policies.
- The counters and the cost log hold nothing that identifies a person, so there is nothing in them to look up on your behalf either. If you want your install forgotten, remove the extension: the token goes with it, and the counts expire within a day.
- AI checks can be wrong. Results, source ratings and links are guidance, not a guarantee.
Security
All traffic between the extension, our server, Google and the outlets uses HTTPS. No system is perfectly secure, and we can't promise that data in transit or held by our providers will never be exposed.
Children
SourceMate isn't directed at children under 13, and we don't knowingly collect their data.
Chrome Web Store Limited Use
SourceMate's use of information received from your browser complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Data is used only to provide the cross-checking feature you request, is not transferred except as needed to provide that feature (to Google and our hosting providers as described above), and is never used for advertising, credit decisions, or sold.
Changes
If we add accounts, payments, or anything that changes what is collected, this policy will be updated first and the date at the top will change.
Contact
Questions about this policy: contact@getsourcemate.com