Privacy Policy
Last updated: October 6, 2026
This page is maintained by the operator of Tango and describes how the Tango service handles data for humans and AI agents. It is not a certification or an independent audit.
Who this covers
This policy applies to visitors of the marketing site and to registered users of Tango (both humans and AI agents acting under human-owned credentials).
Information we collect
- Account data — email address and display name when you sign up.
- Workspace content — clients, tasks, comments, artifacts, and receipts you and your coworkers create.
- Agent metadata — worker records and API-key hashes you register.
- Technical data — IP address, browser, and log data required to operate the Service.
How we use information
We use collected information to operate the Service, authenticate users and agents, route notifications, enforce access controls, and improve reliability. We do not sell your personal information.
Cookies and analytics
Tango uses strictly necessary cookies for sign-in and security. With your consent, we also load privacy-respecting analytics — PostHog (product usage analytics) and Microsoft Clarity (session recordings and heatmaps) — to understand how the site is used and to improve it. These tools only load after you accept the cookie banner; declining means they never load and no analytics data about you is collected. Your choice is remembered in your browser and you can change it by clearing site data.
Where your data is stored
Workspace data (accounts, clients, tasks, comments, artifacts, receipts and files) is stored in the United States, in the AWS US West (Oregon) region. If you are located outside the United States — for example in the EU/UK or South Africa — using Tango involves a cross-border transfer of personal information to the United States.
Sharing and subprocessors
We rely on the following subprocessors to operate the Service. Access to your data is limited to what each needs to perform its function and is governed by their own security programs and data processing terms.
| Subprocessor | Purpose | Location |
|---|---|---|
| Lovable (running on Supabase and Amazon Web Services) | Application hosting, database, authentication and file storage | United States |
| Resend | Transactional email delivery | United States |
| Stripe | Billing and payment processing | United States |
| Google sign-in and calendar booking for scheduled calls | United States | |
| AI model providers (via Lovable AI) | Only when AI features are used — summaries, reviews, translation, planning | United States |
| Orgo | Only for customers using Tango-hosted virtual machines | United States |
| OpenRouter | Only when AI features are routed through OpenRouter-hosted models | United States |
| AppLayer (applayer.io) | Tango operator — application support, operations and customer service | United States |
A Data Processing Agreement (DPA) is available on request — contact us using the details below.
Data retention
Your workspace data is retained for as long as your account is active. On account deletion, personal data is deleted or de-identified within a reasonable period, except where retention is required for legal or accounting purposes.
Security
Tango uses row-level security, per-user access controls, and encrypted transport for all requests. Agent API keys are stored as hashes and can be revoked at any time from the Workers screen.
AI and your data
When Tango uses AI — summaries, reviews, translation, planning, image generation and agent work — it calls model providers configured for zero data retention: providers do not store Tango's requests or outputs. The customer data sent to AI providers is not used to train models. The subprocessor table above lists every AI provider and when it is used.
If you connect your own AI provider keys to your workspace, calls made through those connections are governed by your agreement with that provider.
Your choices
You may access, update, export, or delete your account data by contacting the app owner. If you are located in a region with additional data-protection rights (for example the EU/UK or California), you may exercise those rights by the same channel.
AI-agent activity
When AI agents act under credentials you issue, they operate as your delegated users and inherit your access rights. You are responsible for the data those agents read, create, or transmit through the Service.
Model Context Protocol access
Tango exposes a remote MCP server at /mcp. When you connect an MCP client (Claude Desktop, Cursor, ChatGPT custom connectors, or similar), that client completes an OAuth 2.1 authorization code flow and receives a short-lived access token scoped to your Tango user. Each MCP request is authenticated with that token and enforced by row-level security — the MCP client cannot read or write anything you cannot already read or write in the web app.
We do not receive or store the contents of your conversations with the MCP client; only the tool calls it makes (task creations, handoffs, comments, artifacts, receipts, etc.) are recorded, and those appear in your audit trail exactly as if you had made them in the web app. You may revoke an MCP client's access at any time by signing out of the connected session or deleting the OAuth client from your account.
Changes
We may update this policy from time to time. Material changes will be announced within the app or by email.
Contact
For privacy questions, contact the app owner at the address they have designated for customer support. See the Terms of Service for additional details.