Privacy Policy

CheckRun is a Chrome browser extension. This Privacy Policy explains what data is collected, how it is used, and what choices you have. We've written it to be straightforward, not to bury important details in legal language.

1. Data stored locally

CheckRun stores all user data exclusively in chrome.storage.local — a browser-level storage that lives on your device. This includes:

• Checklist templates you create (names, sections, items)
• Run history (URL, date, item statuses, comments, notes)
• Extension settings and preferences

This data never leaves your browser. CheckRun has no backend servers, no database, and no user accounts. We cannot access, read, or recover your local data.

2. Google integration (optional)

CheckRun includes an optional feature to export run results to Google Sheets. This integration is entirely opt-in and only activates when you explicitly click the export button.

When you use Google integration:

• CheckRun requests the drive.file OAuth scope — the narrowest scope available. This allows the extension to create and edit only the files it creates itself. It cannot read or modify any other files in your Google Drive.
• Authentication is handled entirely by Google's OAuth 2.0 flow. CheckRun never sees or stores your Google credentials or password.
• Exported data (run results) is written to your own Google account, not to any CheckRun-controlled storage.
• You can revoke this access at any time via your Google Account permissions page.

3. Template sharing

CheckRun lets you share templates with other users via a token, a JSON file, or a share link. All sharing happens entirely within the browser:

• Share links open directly in the extension (chrome-extension://) — no CheckRun server is involved at any point.
• Template data is encoded client-side before sharing. CheckRun never transmits, receives, or stores shared templates on its servers (CheckRun operates no servers).
• JSON exports are downloaded to your device. What you do with that file is up to you.

You are responsible for the content of templates you choose to share.

4. Website analytics

The CheckRun website (checkrun.co) does not currently use third-party analytics tools. If analytics are added in the future, we will update this section before enabling them, including what data is collected, how long it is retained, and how to opt out. Any analytics we add will be privacy-respecting: no personally identifiable information, no cross-site tracking cookies.

5. Cookies

The CheckRun website uses only technically necessary cookies (e.g. session state if applicable). We do not use advertising cookies or third-party tracking pixels. See our Cookie Policy for details.

6. Data we do not collect

We do not collect, store, or process:

• Your name, email, or any account information (no sign-up required)
• Your browsing history or visited URLs beyond what you actively open in a Run
• The content of pages you visit
• Any telemetry or usage analytics from inside the extension
• Payment information (the extension is free)

7. Data deletion

Uninstalling the CheckRun extension permanently removes all locally stored data — templates, run history, settings, and drafts. This data cannot be recovered after uninstall.

If you used the Google Drive backup feature, your backup files remain in your own Google Drive inside the "CheckRun" folder. You can delete them at any time directly in Google Drive — CheckRun has no access to them after you uninstall or revoke access.

8. Children's privacy

CheckRun is not directed at children under 13. We do not knowingly collect data from children.

9. Changes to this policy

If we make material changes to this Privacy Policy, we will update the "Last updated" date at the top and, where appropriate, provide a more prominent notice. Continued use of CheckRun after changes constitutes acceptance of the updated policy.

10. Contact

Questions about this Privacy Policy or requests related to your data: [email protected]