Privacy Policy

How Quad Chat handles your data. Never used to train AI, never sold, never shared with advertisers. Encrypted, with export and deletion you control.

Effective date

October 8, 2026 · Contact: privacy@quad.chat

1. Scope

Quad is an AI workspace that lets you create accounts, submit prompts, upload files, connect integrations, buy subscriptions, and use AI models and tools. This Privacy Policy explains how Quad Labs Technologies LLC collects, uses, discloses, and protects personal information when you use quad.chat, our web and mobile apps, and related services.

If you use the service through a team, the team's owner and billing managers control seats, roles, usage caps, and billing for that team. Your conversations and files remain in your own account and are not exposed to team administrators through team administration features.

2. Information We Collect

Account and profile data: name, email address, profile image, login/session details, account identifiers, and a versioned confirmation that you are at least 18. We do not require identity-document uploads through the standard eligibility screen.

Workspace content: prompts, conversation history, uploaded files, generated outputs, saved preferences, custom instructions, tasks, memories, API keys you choose to store, and integration settings.

Published content: published sites and experiences expose the artifact, title and public address. Separately, sharing a conversation exposes the conversation and messages available through that link, including prompts, outputs and any attachments or filenames included in the shared view. Anyone with a shared link may access or copy that content until you revoke it; revocation does not remove copies already made.

Billing and subscription data: plan, subscription status, billing customer identifiers, invoices, and transaction metadata from our payment provider. We do not store full payment card numbers.

Team and organization data: when you create or join a team, we process the team name, member names and email addresses, roles, seat and invitation status, per-member usage totals (such as credits and searches consumed), billing settings, and an audit log of team administration actions.

Device and usage data: IP-derived location at a coarse level, browser/device information, app diagnostics, crash data, request metadata, product analytics when you consent to analytics, and ad conversion measurement data when you consent in the mobile app or enable marketing cookies on the web.

Integration data: information necessary to connect third-party services such as GitHub, Google Drive, OneDrive, MCP servers, and other tools you choose to enable.

Support and communications data: messages you send us, feedback, and account-deletion or data-rights requests.

Information from other sources: authentication and integration providers, payment and app-store providers, team owners who invite you, connected services you authorize, and security or fraud-prevention providers.

Your prompts and files may contain sensitive information that you choose to provide. Please do not submit health, biometric, government-identifier, financial-account, precise-location, children's, or other sensitive data unless it is necessary and you are authorized to do so.

3. How We Use Information

To provide, operate, secure, and maintain the service, including authenticating users, storing conversations and files, routing requests to AI or search providers you select, and processing billing.

To improve reliability, performance, product quality, abuse prevention, moderation, fraud detection, debugging, and customer support.

To communicate with you about transactional matters such as account notices, receipts, verification, service updates, legal requests, and support.

To comply with law, enforce our Terms, protect users and the public, and investigate misuse.

We do not sell personal information for money or use customer content to train our own general-purpose AI models. Optional advertising measurement may qualify as sharing or targeted advertising under some laws. It is controlled separately from service processing.

4. Legal Bases For Processing

Contract: we process account data, workspace content, selected model or tool requests, integration data, and subscription information to create your account and provide the features you request.

Legitimate interests: we process limited device, request, security, fraud-prevention, service-health, and support data to protect the service, diagnose failures, prevent abuse, and improve reliability. Our interests are operating a secure and dependable service; we assess necessity and privacy impact before relying on this basis.

Consent: optional analytics, replay, advertising measurement and non-essential device storage require an affirmative choice. We separately ask for third-party AI permission on web and mobile. Withdrawing AI permission in Settings pauses new AI requests and scheduled AI work across your account. It does not delete prior transmissions. Cookie settings control optional web analytics and marketing. Sensitive memory has a separate, optional permission; it is off by default.

Legal obligations and legal claims: we process billing, tax, compliance, safety, and request records where law requires it or where necessary to establish, exercise, or defend legal claims.

5. How We Share Information

Service providers and subprocessors that help us run the service, such as authentication, infrastructure, payment, monitoring, analytics, email, and support vendors.

AI processing: before enabling AI requests, we explain third-party processing and ask for permission. Requested features can include prompts, relevant history, selected files, audio, project instructions, saved memory and preferences, and a limited plan or usage summary. Content you choose to submit may itself contain names, email addresses or other personal information.

Managed model requests use Vercel AI Gateway. Music generation sends prompts and lyrics directly to Google under its paid API terms when the feature is enabled. Search, URL retrieval, YouTube transcription, code execution, support and connected tools use their own providers and policies. We do not automatically add your account email, payment card details, authentication secrets or unselected photo-library content to model inference prompts. Opaque account identifiers may be used for service attribution or abuse prevention; information you include in content is transmitted with that content.

Private Lane requests require Zero Data Retention routing through Vercel AI Gateway; this restriction applies to model routing and does not delete content stored in your Quad workspace. Standard Lane models require an additional choice and may retain requests under provider terms; Gateway requests also require no-training routing. Studio uses separate provider confirmation and no-training routing, with provider retention terms. Direct Google music, search, transcription services, connected tools and support have their own retention policies and are not covered simply because your chat model uses Private Lane. Our provider and recipient register describes these differences.

You may decline AI processing and still access privacy and account settings, deletion, support and subscription help. You can withdraw AI permission in web or mobile Settings. New chat, media, speech, AI memory updates and scheduled AI work are paused until you explicitly grant permission again.

Your team administrators when you join a team workspace: the team owner and billing managers can see your name, email address, role, seat status, usage totals, and team audit records for seat management and billing. Team administration features do not give administrators access to the content of your conversations or files.

Advertising and measurement partners: with optional purpose permission, Google receives conversion events and ad-click or account identifiers. If Meta server purchase measurement is enabled, current marketing permission is required before sending hashed email and purchase metadata. Hashing does not make identifiers anonymous. Browser GPC is treated as refusal of optional analytics and marketing and is propagated to account consent when you are signed in. Workspace content is excluded from these conversion events.

Corporate transactions, legal disclosures, and safety-related disclosures when required to complete a merger, financing, reorganization, respond to lawful requests, enforce our rights, or protect people and systems.

Public sharing: publishing an artifact and sharing its source conversation are separate actions. An artifact page does not automatically publish its source chat. A shared conversation does expose its shared messages. External destinations such as Telegram receive content you authorize us to send under their own terms; Telegram bot messages are not end-to-end encrypted.

Our current subprocessor list, including what each provider receives and why, is available on our /subprocessors page.

6. Cookies And Similar Technologies

We use cookies, SDKs, local storage, and similar technologies for authentication, security, remembering preferences, measuring usage, improving performance, and measuring advertising.

Essential technologies are used to keep the service working. Analytics technologies are used only when you consent. We present a cookie banner, record your choices, and let you reject non-essential cookies as easily as accepting them.

Simple Analytics measures pageviews without analytics cookies. We still enable it only after you opt in to analytics. We redact private page identifiers and disable referrer, URL parameter, page-load identifier, scroll and time-on-page collection. We do not send chat titles, prompts or files through this integration. Withdrawing analytics consent stops new pageviews. Browser Do Not Track and Global Privacy Control signals also disable this integration.

Google Consent Mode starts with denied defaults. The Google tag container is fetched only when an optional purpose is allowed. Enabling GPC overrides a stored grant before initialization. Withdrawing a purpose updates the tag permission; remotely configured tags must also respect that decision. Cookie settings remain available to review or change your choice.

Where required by applicable law, we honor browser-based Global Privacy Control signals as a request to reject non-essential tracking related to sale or sharing.

7. Retention

Account, workspace, conversation, project, integration, and stored-content data are kept while your account or the relevant feature remains active, and are deleted when you delete the item or account, subject to the limited exceptions below.

Unpublishing a site or experience disables its public address. Deleting its source conversation or your account removes the hosted artifact from active service, subject to the backup timing described below.

If a plan downgrade or ended subscription leaves an account above its new private-storage allowance, new uploads are paused and the account receives a 30-day grace period. Unless the user deletes files or restores sufficient storage before the deadline, the oldest stored files are deleted until usage fits the active allowance.

Operational usage events are normally kept for up to 395 days; billing webhook payloads, app command logs, and generated weekly suggestions for up to 90 days; privacy and security audit events for up to 400 days; and stale live-activity tokens for up to 7 days. These are default service windows; legally required retention and configured deployment windows may differ. Closed privacy requests are normally removed after their applicable due date plus the audit-retention window.

Data-export downloads require an expiring token, normally valid for one day. Expired links are rejected even before the physical archive is removed by the cleanup job. Billing, tax, transaction, suppression, policy-acceptance, fraud, security, dispute, and legal-request records may be retained for the period required by applicable law or reasonably needed to document compliance and resolve claims.

Backups and provider logs may persist for a limited rolling period before deletion or overwrite. When immediate deletion from a backup is not technically possible, the data is isolated from ordinary use and removed on the provider's normal backup cycle.

8. Security

We use administrative, technical, and organizational safeguards designed to protect information, including encryption in transit, access controls, segmentation of systems, monitoring, and vendor controls. No system is perfectly secure, and we cannot guarantee absolute security.

9. International Transfers

We and our vendors may process information in countries outside your own, including the United States and Kosovo, where authorized personnel work remotely. Where personal information is transferred out of the European Economic Area, the United Kingdom, or Switzerland, a legally recognized transfer mechanism is required. Available mechanisms include applicable European Commission Standard Contractual Clauses and, for covered certified recipients and transfers, the EU-U.S. Data Privacy Framework and its extensions. Contact privacy@quad.chat for information about the safeguards applicable to a particular transfer.

You can request a copy of the relevant safeguards, or ask which mechanism applies to a specific vendor, by contacting privacy@quad.chat. Our current vendors are listed on the Subprocessors page.

We assess transfer safeguards and supplementary measures for restricted transfers. A vendor's Data Privacy Framework participation is used only while that vendor and the relevant data recipient are covered; other restricted transfers require applicable standard contractual clauses or another lawful mechanism before processing.

10. Your Rights And Choices

Depending on where you live, you may have rights to access, correct, delete, export, restrict, object to, or appeal certain processing of your personal information.

California residents may have rights to know, delete, correct, opt out of sale or sharing, limit sensitive personal information where applicable, and receive non-discriminatory treatment for exercising privacy rights.

EEA, UK, and similar-law residents may have rights to access, rectification, erasure, restriction, portability, and objection. You may withdraw consent at any time and lodge a complaint with the supervisory authority where you live or work, or where you believe an infringement occurred.

To exercise rights, use the privacy and data settings in the product or email privacy@quad.chat. We may need to verify your identity and authority. We respond within the time required by applicable law, generally one month under GDPR and 45 days under many U.S. state laws, subject to lawful extensions. If we deny a request, we will explain why and provide an appeal route where required.

We do not currently use personal information to make solely automated decisions that produce legal or similarly significant effects about users. AI outputs are generated in response to user requests and must not be used as the sole basis for high-impact decisions.

11. United States State Disclosures

During the preceding 12 months, we may have collected the categories described in Section 2: identifiers; customer and commercial records; internet or electronic activity; approximate geolocation; professional or organization information supplied for teams; inferences such as saved preferences or memories; and content that may qualify as sensitive personal information when you choose to submit it.

We collect these categories from you, your device, team administrators, and the providers described in Sections 2 and 5. We use and disclose them for the business purposes in Sections 3 and 5. We do not sell personal information for money. Optional advertising measurement may be considered 'sharing' or targeted advertising under some state laws, so it remains off unless you consent and can be disabled through Cookie settings or a supported Global Privacy Control signal.

We do not use sensitive personal information for advertising or intentionally infer protected traits for saved memory. If you enable sensitive memory, we instruct the service to store a sensitive detail only when you explicitly ask it to remember that exact information. You can review and delete memory; disabling future extraction does not erase previously saved memory. We do not knowingly sell or share personal information of consumers under 16.

Where a state law applies to us, residents may use privacy@quad.chat or the in-product privacy controls to submit a request. Authorized agents may submit requests with proof of authority. We will not discriminate against you for exercising a privacy right.

12. Children

Quad is an adults-only service. You must be at least 18 to use it, including guest AI chat. Parental permission does not make a person under 18 eligible. We ask for a versioned adult confirmation and pause AI processing for accounts known to be ineligible. Contact privacy@quad.chat if a minor has used Quad or an eligibility decision needs correction.

13. Third-Party Links And Services

The service may link to third-party sites, documentation, integrations, and providers. We are not responsible for their privacy practices or content.

14. Changes To This Policy

We may update this Privacy Policy from time to time. If we make material changes, we may update the effective date, post the revised version, and provide additional notice where required.

15. Contact Us