Datawake works entirely inside your browser. What it sees and records stays on your device, and we run no server that receives any of it. This policy explains exactly what the extension looks at and why.
Last updated: 9 October 2026
Datawake is a browser extension that shows you which companies track you on the sites you visit, says no to cookie banners for you, and checks whether sites respect that choice. It runs entirely in your browser. Nothing it records is sent to us.
Nothing. We do not operate any server that receives data from your copy of Datawake. We cannot see the sites you visit, the trackers you meet, your settings or anything else in the extension. The extension contains no analytics, crash reporting or telemetry.
Datawake also sends the Global Privacy Control signal to websites, a standard way of saying you do not want your data sold or shared. You can turn this off in Settings.
If you turn on fingerprint protection, Datawake adds tiny, invisible changes to what scripts read from canvas drawings and sound processing on the pages you visit, so your fingerprint differs on every site. This happens in your browser and nothing is sent anywhere.
Notifications are off until you turn them on, and your browser asks your permission first. They are shown by your own browser; nothing is sent to us.
If Datawake could not reject a cookie banner, the popup offers a "Report this banner" link. It opens a pre-filled issue on GitHub that names only the website, never the page you were on. Nothing is sent unless you choose to submit it on GitHub, under your own GitHub account and GitHub's privacy statement.
The following is stored in your browser's own storage and never leaves it:
Tracking history and the record of what Datawake did are deleted automatically after 90 days. Violations are kept until you clear them, so you keep the evidence. You can clear everything at any time from Settings in the dashboard, and removing the extension deletes it all.
Datawake can write GDPR request letters to companies and complaints to a data protection authority. It only writes the text. Nothing is sent unless you send it yourself, by copying the text or opening it in your own email.
The optional breach check, on this website and in the extension, looks up the email address you type in an independent breach database service. Your browser sends it straight to that service over an encrypted connection, only to run the lookup; it never passes through Datawake and we never store it. This is the only time the extension contacts a server other than the websites you visit.
Datawake Pro is not available yet. Before it launches we will update this policy to explain exactly what is needed to run a subscription. The free extension will keep working without an account.
The extension's code is open source on GitHub, so you can check everything in this policy for yourself.
datawake.app is hosted on GitHub Pages and uses no analytics or tracking. GitHub may log technical information such as IP addresses for security; see GitHub's privacy statement. These logs are not linked to the extension in any way.
Because we hold no personal data from the extension, there is nothing for us to access, correct or delete. Everything is on your device and under your control. If you write to us, we only use your message to reply, and you can ask us to delete it.
If we ever change how Datawake handles data, we will update this page before the change ships and note it in the extension's release notes. The current version is always at datawake.app/privacy.
Questions about privacy? Email privacy@datawake.app.