Tabfleet Privacy Notice
How Tabfleet handles account information, browser sessions, access credentials, and support requests.
Scope and operator
Effective September 12, 2026. This notice describes the Tabfleet alpha operated by Dalton Solutions, LLC. in Burleson, Texas, United States. Contact jordan@daltonsolutions.com with privacy questions or account-data requests. Websites you visit through a Tabfleet browser have their own privacy practices, and your agent or MCP client is operated separately from Tabfleet.
Information used to provide the service
Google sign-in supplies a verified account identifier, email address, and display name. Tabfleet stores workspace records, API-key hashes and labels, approved agent connections, permissions, and authentication state. Account session cookies maintain sign-in. We use these records to authenticate users, isolate workspaces, authorize browser actions, and manage the trial allowance. IP-derived request buckets and temporary authentication records help prevent abuse.
Browser operations transmit the URLs, actions, and page data needed to run your task. Browser pages may contain personal or confidential information that you or your agent enters or accesses. Requested snapshots, screenshots, and live views return browser content to the authorized client or viewer. Session records include identifiers, status, timestamps, termination reasons, and usage estimates. Signed viewer and CDP links grant temporary access and should be shared only with intended recipients.
Service providers and sharing
Cloudflare provides the browser infrastructure, API hosting, and storage used by Tabfleet. Google processes sign-in. The website and dashboard use the Sites hosting platform. Infrastructure services process connection and operational data to deliver and secure the service; Cloudflare traffic and security metrics may also be collected. An agent client receives the results it requests, and a recipient of a signed viewer link can access the browser within that link’s permissions and lifetime. Visiting another website sends requests to that website.
Retention and controls
Browser sessions are temporary and subject to hard and idle timeouts. Closing a session initiates browser cleanup; failed cleanup is retried. The application retains a bounded recent session history and cumulative usage records. Account, workspace, credential, and authorization records may outlive individual browser sessions. Temporary authentication records expire, while revocation prevents continued use of the affected credentials. We do not promise that all infrastructure logs or account records are deleted immediately when a browser closes.
You can close active browsers, revoke API keys and connected apps, and revoke signed viewer links through supported controls. Contact jordan@daltonsolutions.com to request access to, correction of, or deletion of account information. We may verify ownership and explain any records that must be retained for operational or legal reasons. This alpha has no published automatic account-deletion schedule. Avoid sending sensitive browser data or credentials in support messages.
Updates
We will update this page when the service’s data-handling practices change and identify the effective date. Review this notice before using Tabfleet for a new category of data. Questions about a particular workflow or provider can be sent to the support contact above.