Privacy Policy
What TabSail processes, why it is needed, and how to request access or deletion.
Effective date: October 24, 2026.
Who is responsible
Individual operator 朱城磊, based in China, operates TabSail at https://tabsail.com. Send privacy questions and requests to support@tabsail.com.
Data we process and why
| Category | Examples and purpose |
|---|---|
| Account and authentication | Email, display name, provider user identifiers, and revocable session records, to sign you in and control access. WorkOS handles hosted authentication. TabSail does not store an account password. |
| Resource and usage records | Project ownership, API-key verification records, session identifiers, configuration and metadata you submit, timestamps, connection authorization, usage and credit ledger, to run browsers, enforce limits, and bill accurately. |
| Payment records | Checkout, customer and transaction references, purchase amount, tax, refunds and dispute status, to grant credits and reconcile payments. Creem handles payment details; TabSail does not store your full card number or card security code. |
| Browser data | Websites, inputs, cookies, files, and live browser traffic you or your application send through the runtime, to perform your workflow. Website providers receive the requests you make. |
| Saved Profiles | Encrypted snapshots of supported cookies and localStorage, only when you choose to save reusable login state. These can contain sensitive access credentials. |
| Operational and support information | IP addresses, request and error identifiers, technical logs, and messages you send support, to protect the service, diagnose failures, and answer requests. |
Where applicable law requires a legal basis, processing is based on providing the service you request, legitimate interests in security and reliable operation, legal obligations, or consent where required. Do not put sensitive personal information into session metadata or send secrets in support requests.
Cookies and local browser storage
TabSail uses necessary authentication cookies and browser preferences such as the selected theme. WorkOS's hosted sign-in and Creem's checkout have their own necessary storage and privacy practices. Websites you open in a cloud browser may set their own cookies. A cloud browser does not automatically inherit your local browser's login state.
Service providers and locations
We use WorkOS for authentication, Creem for payments, Cloudflare for public documentation, DNS and support email routing, Contabo for the current hosted browser/control-plane infrastructure, and Gmail for the support inbox. These providers process data needed for their service under their own terms and privacy notices. Data may be processed outside your country. A requested browser region does not guarantee residency for account, support, payment, or control-plane records.
TabSail does not sell personal data or provide browser content to advertising networks. Your own agent, model provider, browser client, and websites receive information according to how you configure and use them; review their practices separately.
Retention and deletion
Temporary browser files and memory are tied to the running session and become unavailable through TabSail after release. Saved Profile state remains until you delete the Profile; deletion clears its saved snapshot, while ownership and deletion metadata may remain. The platform retains account, session, usage, security, and payment records for operation, reconciliation, dispute handling, and legal obligations. It does not currently promise a fixed retention period for every record category.
Request account closure, access, correction, export, or deletion through support. We verify ownership before releasing or removing account data. We will explain any records that must remain for a legal obligation, an unresolved payment, security, or the establishment or defense of a claim. Recovery copies, where present, are restricted to recovery and may retain information until replaced or removed. Closing a browser is not an account-data deletion request.
Security and your choices
Public service connections use HTTPS. Saved Profile snapshots are encrypted at rest; authorization limits access to the owning project. No system can guarantee absolute security. Protect your API keys and saved website credentials, revoke compromised access, and keep independent copies of important outputs. You can use browsers without saving a Profile and can delete saved Profiles when they are no longer needed.
Requests and changes
Depending on applicable law, you may have rights to access, correct, delete, restrict or object to processing, request portability, withdraw consent, or complain to a competent authority. Contact support to exercise a right or ask about a concern. Material changes to this policy will be communicated with an updated effective date.