TABCREW
Effective 31 August 2026 / TabCrew for Chrome
This policy describes the TabCrew private beta and its capability gateway. TabCrew proposes groups for open Chrome tabs. It does not move a tab until the user approves the plan.
Grouping and installation statistics
Plan request
TabCrew sends the browser locale, Chrome tab title, and URL scheme, host, and path for each open HTTP(S) tab. The gateway adds a fixed instruction for the AI provider.
Boundary filter
Query strings and URL fragments are removed. Titles and URL paths are length-limited. Non-HTTP(S) tabs remain outside the provider request.
After activation
The data-supported build records navigation to HTTP(S) pages using the Chrome tab title and URL scheme, host, and path. It also records plan creation, edit, and Apply events so TabCrew can produce installation statistics and usage studies.
Outside the boundary
TabCrew does not send page contents, DOM data, HTML metadata, cookies, local files, data URLs, or Chrome pages.
Device state and service records
Chrome extension storage holds the installation session, a non-extractable signing key, and recent plans and reports. A plan can include tab titles and sanitized URLs. This data remains in the browser profile until it is replaced, cleared, or the extension is removed.
After the activation disclosure is accepted, the gateway stores minimized tab titles, URL scheme, host, and path; validated plan inputs and model answers; and navigation, plan-edit, and Apply events. These records power My stats, aggregate TabCrew usage studies, and training or evaluation of TabCrew's own grouping models. They are not sold, used for advertising, or reused for unrelated products.
Raw plan and navigation records are retained for up to 90 days. Login, authorization, password, checkout, payment, billing, and account paths are excluded from content retention. Additional hostname and text exclusions can be configured. An excluded record keeps only a safety count and reason; its title, URL, host, and path are not stored.
The database also stores the installation public key, consent version, last-seen time, short-lived security records, current-day quota counters, and short-lived concurrency leases. Application logs record route, status, duration, tab count, request identifier, and a keyed installation pseudonym. Logs do not include tab text, URL paths, prompts, tokens, signatures, model answers, or provider keys. Hosting and security services may keep standard access and abuse-prevention logs under their own retention rules.
Other systems involved in one plan
The gateway currently sends the fixed instruction and sanitized tab fields through OpenRouter to the configured model provider. OpenRouter and the downstream provider must read that input while the plan runs. Their logging, retention, and training rules depend on the account settings and selected endpoint.
The current TabCrew request does not require OpenRouter's per-request zero-data- retention filter. Review OpenRouter's data collection documentation, provider policy documentation, and privacy policy for the current rules.
Background navigation events and customer statistics are sent to the TabCrew gateway, not to the model provider. A provider sees tab fields only when TabCrew requests a grouping plan.
Turnstile checks the one-time installation activation. Cloudflare receives the browser and network data needed to perform that check under its own terms and privacy policy.
Review, clear, remove, or ask
Before Chrome changes
TabCrew shows the proposed groups before it changes Chrome. You can inspect, edit, or reject the plan.
From My stats
My stats shows this installation's 7, 30, or 90-day report and can delete its retained plans and navigation history. Deletion does not disable future collection; the data-supported beta records new eligible events while it remains active.
To stop collection
Offline grouping skips model inference for that plan, but it is not a privacy toggle. Removing the extension stops future extension collection.
Privacy support
Ask about gateway records or request deletion of an installation record at contact@th3nolo.com. Include the TabCrew installation identifier if available. Do not send browser history, API keys, authentication tokens, or other secrets by email.
Email privacy support