Privacy Policy
Last updated: May 30, 2026
Summary #
Takt does not collect, transmit, or store your personal data on any external server. All extension data stays in your browser's local storage. The only network communication is license validation for paid features, handled by a third-party payment processor.
What data Takt stores #
All data is stored locally using Chrome's built-in storage APIs (chrome.storage.sync, chrome.storage.local, chrome.storage.session):
| Data | Storage | Purpose |
|---|---|---|
| Tab grouping rules | sync | Your rules for organizing tabs |
| Extension settings | sync | Preferences (theme, automation mode, etc.) |
| Profiles | sync | Named rule sets for different workflows |
| Rule match statistics | local | Counts of how many tabs each rule matched |
| Dismissed suggestions | local | Domains you dismissed from suggestions |
| License cache | local | Cached payment status to avoid repeated checks |
| Group registry | session | Maps group names to Chrome tab group IDs (cleared on browser close) |
| Resource snapshots | session | Tab memory/network data for the resource dashboard (cleared on browser close) |
chrome.storage.sync data may be synced across your Chrome instances via your Google account if Chrome Sync is enabled. This is a Chrome platform feature, not controlled by Takt.
Interaction tracking #
The staleness reporter content script listens for click, scroll, and keydown events on each active tab. When any of those events occurs, the script records a single Unix-millisecond timestamp (Date.now()) and transmits it to the extension's service worker at most once every 30 seconds — and only if a new interaction has occurred since the last report. Tabs with no user interaction generate zero reports.
The transmitted payload contains exactly one data field: the integer timestamp. No other information is included. Specifically, the staleness reporter does not read page text, form values, keystroke characters, the tab URL, the page title, or any DOM node content. The keydown listener only records that a key was pressed, not which key.
This data stays within the extension: it is used solely to determine whether a tab is stale and is never sent to any external server.
What data Takt does NOT collect #
- Browsing history or URLs you visit
- Page content or form data
- Personal information (name, email, etc.)
- Analytics or telemetry of any kind
- Cookies or authentication tokens
Network communication #
Takt makes exactly one type of network request:
- License validation via ExtensionPay — checks whether you have an active paid subscription. This happens on extension startup and when you open the upgrade page. ExtensionPay receives a pseudonymous extension user ID (generated by Chrome), not your browsing data or personal information.
Free users with no payment interaction generate zero network requests from Takt.
Permissions explained #
| Permission | Why |
|---|---|
tabs | Read tab URLs and titles to match against your rules |
tabGroups | Create and manage Chrome tab groups |
storage | Save your rules, settings, and profiles |
contextMenus | Right-click "Create rule from this tab" menu item |
scripting | Inject the duplicate-prevention toast notification |
notifications | Alert you when tab groups exceed memory budgets |
alarms | Periodic budget checks and scheduled profile switching |
Optional permissions #
These are requested at runtime only when you enable the features that need them:
| Permission | Why | When requested |
|---|---|---|
webRequest + <all_urls> | Monitor network requests for the resource dashboard | When you open the resource dashboard |
webNavigation | Detect navigation for duplicate tab prevention | When you enable duplicate prevention |
system.memory | Show total system memory in the resource dashboard | When you open the resource dashboard |
You can revoke any optional permission at any time from the extension's settings page.
Third-party services #
ExtensionPay (their privacy policy) processes payments for the Premium plan. Takt does not handle payment information directly. ExtensionPay uses Stripe for payment processing.
Data deletion #
Uninstalling Takt from Chrome automatically deletes all locally stored data. To delete synced data, disable Chrome Sync or clear extension data from your Google account settings before uninstalling.
Children's privacy #
Takt is not directed at children under 13 and does not knowingly collect information from children.
Changes to this policy #
If this policy changes, the updated version will be posted at this URL with a new "Last updated" date. Material changes will be noted in the extension's changelog.
Contact #
Questions about this privacy policy can be directed to: takt.extension@gmail.com