Privacy
Last updated: June 7, 2026
AppTab and AppTab Companion are built around local, explicit control. Session import is powerful, so the rule is simple: data stays on your Mac unless you choose to put it somewhere else.
AppTab for macOS
AppTab stores generated-app configuration locally on your Mac. Generated apps use WebKit storage on your Mac for cookies, localStorage, sessionStorage, IndexedDB, cache, and related site data.
AppTab does not include analytics, telemetry, advertising identifiers, or a remote account system.
AppTab Companion for Chrome
AppTab Companion can read browser session data for the active Chrome tab only after you grant Chrome site access and click an export/import button.
The extension can handle:
- The active tab URL and page title.
- Cookies for the active site.
- localStorage, sessionStorage, and readable IndexedDB records for the active site.
How Session Import Works
The extension copies an AppTab-compatible session payload to your local clipboard. AppTab then opens the matching generated app's import sheet and imports that payload locally.
Session data is not uploaded to AppTab servers. There are no AppTab servers involved in this flow.
What Is Not Collected
- No analytics events.
- No background browsing history collection.
- No sale or transfer of personal data.
- No remote storage of cookies, tokens, or browser session data.
- No access to unrelated sites unless Chrome grants site access for that active site.
Clipboard
Session import currently uses the clipboard as an explicit local handoff between Chrome and AppTab. Because browser sessions can contain sensitive tokens, you should treat the copied payload like a password and avoid pasting it anywhere except AppTab.
Support
Questions or security concerns: support@apptab.app.