1. What this policy covers
This policy describes how Alloy Tabs (“we,” “us,” or “our”) handles information in the Alloy Tabs website and Chrome extension, including support requests, product updates, analytics, and optional Google Drive backups. Contact us at hello@alloytabs.com with privacy questions.
The current app is a Chrome development build that manages native tabs and groups, saves workspace and recovery records locally, and offers optional Drive backups. The website also includes a demonstration using sample links. Planned mobile apps, agent integrations, and broader cloud services are not part of the current app.
2. Tabs, groups, and local storage
The extension accesses tab URLs and titles, favicons from Chrome’s local cache, group names and colors, window placement, pinned-tab order, and the folders and workspace names you create. It uses these to display, organize, save, close, and reopen your tabs and groups.
Session records, recovery snapshots, operation status, and backup preferences are stored on your device using Chrome extension storage. The ordinary website prototype stores its demo state in browser local storage. The current extension does not automatically send your browsing library or tab URLs to Alloy Tabs servers or PostHog.
The extension does not collect full page contents, website passwords, cookies, unsaved forms, or Chrome browsing history. It does not inject scripts into websites. Incognito windows are excluded. Saved URLs can themselves contain personal information, identifiers, or sensitive query parameters, so treat session exports and backups as private files.
3. Optional Google Drive backups
When you connect Google Drive, Chrome’s authorization flow grants access to the drive.appdata scope. Alloy Tabs reads and writes its own backup files in Google Drive’s hidden app-data area; this scope does not grant access to your other Drive documents.
Backups contain saved workspace/session data such as URLs, titles, group and folder structure, tab layout, and backup metadata including device and revision identifiers, timestamps, and checksums. These files travel directly between the extension and Google’s API, rather than through an Alloy Tabs backup server. Google authorization tokens are used for these requests and are not sent to our analytics service.
Automatic Drive backups are off by default and require you to enable them. Manual backups and importing a selected backup are available through the app. Disconnecting Drive stops the app’s connection and automatic backups; it does not delete existing Drive files or local sessions. To revoke access or remove stored app data, use your Google Account and Google Drive connected-app controls.
Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Google data is used to provide the backup and recovery features you authorize, not for advertising, profiling for advertising, or training general-purpose AI models. Staff do not access your Drive backups through a central Alloy Tabs account; if you explicitly share a backup for support, it is handled as support information.
4. Support information we collect
We collect support data when you contact us or provide troubleshooting information. This can include your name, email address, message, correspondence, app/browser version, operating system, error details, and logs, screenshots, diagnostic reports, or backup files you choose to share.
We use this information to respond, troubleshoot, investigate reliability or security issues, and improve Alloy Tabs. We do not automatically receive your entire local library when you request support. Share only what is needed; remove private URLs, access tokens, passwords, and unrelated personal information from attachments where possible. Support files may contain tab titles and URLs if you include them.
5. Analytics and operational information we collect
We collect analytics and operational data to understand usage, improve the product, detect failures, and protect the service. On the current marketing website, selected pageviews, demonstration interactions, updates-link clicks, and successful-signup events are sent through our Cloudflare Worker to PostHog.
The website uses a random identifier held in page memory rather than an analytics cookie or persistent browser identifier. Our analytics event payloads do not include form values, your browser’s tab library, or URL query strings. We do not enable session replay, page-content capture, or form autocapture in this website implementation. The current extension does not contain an automatic PostHog analytics or crash-reporting integration; support diagnostics are collected when you provide them.
Hosting and security providers process network information such as IP addresses, request URLs, timestamps, and request/error metadata to deliver the website, limit abuse, and operate infrastructure. Our Worker uses the incoming IP address for rate limiting. Provider request logs may include information that is not part of our selected analytics event payloads.
The website’s analytics code honors the browser’s Do Not Track setting. This does not stop essential hosting/security processing or a signup you explicitly submit. If we introduce additional app telemetry or materially change what is collected, we will update this policy and provide any notice or choice required by law before that processing begins.
6. Product updates and email
When you sign up for updates, we collect your name, email address, signup time, and record of your request to receive updates. We store these in PostHog to manage the mailing list and send confirmation and product-update emails. A hash of your normalized email is used as a subscriber identifier; the email itself is also stored so we can send messages.
You can unsubscribe using the link in an update email or contact us. We may keep a suppression record so your opt-out is respected. Unsubscribing from product updates does not prevent a response to a support request you initiate.
8. Storage, retention, and security
Local sessions and recovery snapshots remain in extension storage until you remove them, clear extension data, or uninstall the extension. Recovery snapshots are not automatically pruned in the current build. Downloaded exports remain wherever you save them. Drive backups remain until removed separately; disconnecting is not deletion.
We retain support correspondence, signup records, analytics, and operational logs for as long as reasonably necessary for the purposes described above, including resolving issues, respecting opt-outs, securing the service, and meeting legal obligations. Retention varies by record type and provider; we do not promise a fixed automatic deletion period that the current system does not implement.
We use HTTPS for website and Google API connections and restrict access to service accounts and records. Device and downloaded-file security also depends on your environment. No system can guarantee absolute security or data recovery.
The current PostHog project uses its US service. Other providers may process information in the United States or other countries where they operate, whose privacy laws may differ from those where you live.
9. Your choices and requests
You can manage local records and backups in the app, export your data, disconnect optional Drive access, revoke Google authorization, unsubscribe from updates, and use Do Not Track for website analytics.
To request access, correction, deletion, or to raise a privacy concern about information we hold, email hello@alloytabs.com. Depending on your location, you may also have rights to portability, restriction, objection, withdrawal of consent, appeal, or a complaint to your local privacy regulator. We will handle requests under applicable law and may ask for information needed to verify the request. We cannot remotely delete local files or data in your Google account. Some records may be retained where legally required or needed to honor an opt-out.
10. Children and policy changes
Alloy Tabs is not directed to children under 13, and we do not knowingly collect their personal information. If you believe a child has provided information, contact us so we can address it.
We will post policy changes here and update the date. For material changes, we will provide additional notice and obtain consent where required. This policy describes current handling; it is not blanket permission for undisclosed future collection.
Questions?
Contact hello@alloytabs.com.