Privacy Policy for the CheckFox Accessibility Auditor
Last updated: 19 June 2026
This policy explains what data the CheckFox Accessibility Auditor browser extension processes, where it is stored, and when it leaves your device.
What data we process
- CheckFox API key: the personal access token you paste in Settings.
- Page URL of the tab you audit: used to match it to a CheckFox audit or sample.
- Accessibility findings: rule IDs, impact, CSS selectors and HTML snippets produced by scanning a page you choose to audit.
How it is stored
Your API key and preferences are stored locally on your device using the browser's extension storage (chrome.storage.local). We do not use chrome.storage.sync, so this data is never sent to browser-vendor servers.
How it is used and transmitted
Data leaves your device only to your own CheckFox account at https://checkfox.eu, over HTTPS, and only when you explicitly connect, push findings, pull findings, or mark a topic Not Applicable.
The page URL and findings are sent so they can be saved to the corresponding audit. The API key is sent as an authentication token.
Third parties
We do not use analytics or third-party trackers. We do not sell or share your data. The only external service contacted is the CheckFox API you authenticate to.
Retention and control
The cached audit context is short-lived. Use the Disconnect button in Settings to delete your stored API key and cached audits at any time. Removing the extension clears all local extension data.
Changes
We will update this policy and its date if our practices change.
Contact
Questions about this policy? Reach us at:
[email protected]