Privacy Policy

Effective October 10, 2026. Last updated October 10, 2026.

Effective date: October 10, 2026

Last updated: October 10, 2026

This Privacy Policy explains how Legion Code Inc. ("Legion Code", "we", "us", "our") collects, uses, stores, shares and deletes personal information when you use WHIPT, our cloud software service at https://app.whipt.ai, our website at https://www.whipt.ai, and our checkout pages at https://pay.whipt.ai (together, the "Service").

If you have questions, contact us at privacy@whipt.ai.

1. Who we are

The Service is operated by Legion Code Inc., a Delaware corporation. Our mailing address is in Section 15.

For personal information about our own users (for example, the account details you use to sign in), we are the controller: we decide why and how that information is processed.

For content that our customers put into their WHIPT workspaces (for example, records about their own customers, emails received in a customer inbox, or form submissions on pages a customer publishes), we act as a processor (also called a "service provider") on behalf of that customer. In that case the customer's own privacy notice applies, and requests about that information should go to the customer. We will help our customers respond.

2. Information we collect

2.1 Account and sign-in information

You can sign in to WHIPT with Google, with GitHub, or with a one-time code we email to you. Sign-in is handled by our authentication provider, WorkOS. When you sign in we receive and store:

  • your name, as provided by your sign-in method (if none is provided, we use your email address as your display name);
  • your email address and whether it has been verified;
  • a unique account identifier issued by WorkOS;
  • the organization (workspace) memberships and roles that link your account to a WHIPT workspace.

During sign-in, your IP address and browser user agent are passed to WorkOS for security, fraud prevention and rate limiting. We also keep short-lived records of sign-in attempts (keyed to your email address and IP address) to block repeated failed attempts.

2.2 Google user data (Sign in with Google)

This section describes exactly what we do with data we receive from Google when you choose Sign in with Google.

What we access. We request only the openid, email and profile scopes. From these we receive your Google account identifier, your email address, whether Google has verified that email address, and your basic profile information (your name and, if set, your profile picture URL). We do not request access to your Gmail, Google Drive, Google Calendar, contacts or any other Google data when you sign in.

How we use it. We use this data only to create and sign you in to your WHIPT account, to show your name and email address inside the product (for example, to your teammates in the same workspace), to send you service messages about your account, and to keep your account secure. We do not use it for advertising.

How we store it. Your name, email address, verification status and account identifier are stored in our production database hosted by DigitalOcean in the United States, and in your sign-in record at our authentication provider, WorkOS. Our database does not store your Google profile picture (WorkOS may keep the picture URL as part of your sign-in record). Your session is kept in an encrypted, secure browser cookie. We never receive or store your Google password.

How we share it. We share Google user data only with the service providers that help us run the sign-in and hosting of the Service (WorkOS for authentication, DigitalOcean for hosting and database, Cloudflare for network delivery), as described in Section 5. Our email delivery, hosted AI and error monitoring providers (Section 5.1) do not receive your Google user data for sign-in or account management; they may see your name or email address only where it appears in Workspace Content, such as a task or message that mentions you. We do not sell Google user data, we do not transfer it to data brokers or advertising platforms, and we do not use it to train generalized artificial intelligence or machine learning models.

How to delete it. You can ask us to delete your account and the Google user data associated with it at any time by emailing privacy@whipt.ai from the email address on your account. See Section 10. You can also remove WHIPT's access to your Google account at any time at https://myaccount.google.com/permissions.

Limited Use. WHIPT's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google Workspace connectors. Separately from sign-in, a workspace administrator may choose to connect Google Workspace apps (such as Gmail, Google Drive or Google Calendar) so that WHIPT agents can work with that data. You see and approve the specific Google permissions at the time you connect. Data we receive through those connections is used only to perform the tasks you or your workspace direct, is subject to the same Limited Use commitments above, is not used for advertising, is not sold, is not used to train generalized AI or machine learning models, and is not read by our staff except with your permission, where needed for security, or where required by law. You can disconnect a connected app inside WHIPT or at https://myaccount.google.com/permissions at any time.

2.3 Workspace content you provide

When you use WHIPT you and your teammates create and upload content, including company and project information, agent configurations and instructions, issues, comments, approvals, decisions, files and attachments, published pages and funnels, automations, and the outputs that AI agents produce ("Workspace Content"). Workspace Content is stored in our database and in private object storage (Cloudflare R2) and is used to provide the Service to your workspace.

Company memory. WHIPT agents can save and recall memories for your workspace (for example facts, decisions and summaries of past work). The text of each memory is stored in our database. Search by meaning is not yet turned on for customer workspaces (Section 5.2). When it is, to let agents find memories by meaning, we may also send memory text to an AI model provider through OpenRouter to create an embedding (a list of numbers that represents the meaning of the text), and store that embedding in Qdrant Cloud, our vector search provider. Qdrant stores only the embedding and identifiers such as the workspace, memory record and agent identifiers; it does not store the memory text. When a memory is deleted or corrected, or a workspace is deleted, see Section 7 for how the embeddings are removed.

2.4 Connected apps and integrations

If your workspace connects third-party apps (for example GitHub, Slack, Google Workspace or other tools in the WHIPT app directory), we store the credentials or access tokens needed for that connection in encrypted form, and we exchange data with that app as your workspace directs. Some connectors call third-party services that process the text your agents send them; where we know of this, WHIPT shows a notice before you connect.

2.5 Customer inbox and published pages

If your workspace enables a customer inbox, we process the emails sent to and from that inbox, including the names and email addresses of senders and recipients, subject lines, message bodies, email headers (such as message identifiers, reply references and sender authentication results) and attachments. We send and receive that email through an email delivery provider, AgentMail or Resend, depending on how the inbox is set up (see Section 5.1). If your workspace publishes pages or funnels with forms, we process what visitors submit through those forms. We do this as a processor for the workspace that owns the inbox or page. Published pages may also record cookieless visitor statistics (see Section 6).

2.6 Usage, log and device information

Our servers record technical information when you use the Service, such as the pages and API endpoints requested, timestamps, error details, browser type, and IP address. In our web server access logs, IP addresses are truncated before they are written: we keep only the first 24 bits of an IPv4 address (/24) and the first 48 bits of an IPv6 address (/48). Where we keep an IP address in a security or audit record (for example a request to join a workspace), we store it truncated in the same way. We use this information to operate, secure and troubleshoot the Service. On our checkout pages, Stripe and Cloudflare Turnstile also collect device and browser signals to prevent fraud and automated abuse (Section 2.11).

We send error reports to Sentry (see Section 5.1) so we can find and fix problems. Error reports contain the type of error, its message and the program locations where it happened (a stack trace), and, for errors on our servers, the request method, the API path requested and non-sensitive request headers (such as the browser user agent). Our software configures Sentry not to collect default personal information, and it does not attach your name, email address or account identifier to error reports. When your browser delivers an app error report, Sentry necessarily sees your browser's network connection, but our configuration does not ask Sentry to record your IP address. Browser error reporting runs only while you are signed in and stops when you sign out. Browser reports leave out the page address, query string, referrer and click, console and network histories. Server reports leave out query strings, request bodies, cookies, authentication and signature headers, and IP addresses, and replace database and network error text with a fixed message. Session replay (screen recording) is not used. An error message can occasionally contain a fragment of the content that caused it.

We use PostHog product analytics in the app (see Section 5.1) to understand how the Service is used, so we can improve it. App analytics runs only while you are signed in, and it stops and clears its identifier when you sign out. It records the pages you view and the type of each control you use, with page addresses reduced to their route (identifiers in the address are replaced with a placeholder, and the query string and fragment are removed). It also records the page you came from (reduced to its website address, or to its route if it is part of the app), any campaign tags in the link that brought you to the app (such as utm parameters and ad click identifiers), the search engine you came from and any search terms it passes along, your browser, device and screen information, and the approximate location (such as city, region, postal code and country) that PostHog derives from your IP address. PostHog receives and stores your IP address. It identifies you by your internal account identifier and your workspace by its internal identifier, never by your name or email address. Page titles are not sent, the text and attributes of the elements you click are masked, and session replay (screen recording) and surveys are not used. Our servers also send a small number of account events to PostHog (signing up, creating a workspace, inviting a member and joining a workspace). They contain internal identifiers and a few event details, such as the sign-up method, the member's role and the kind of workspace, never names, email addresses or content, and PostHog does not derive a location for them.

2.7 Feedback on AI outputs

If you rate an AI output (thumbs up or down), your vote is saved in your workspace. If you choose "Always allow" to share voted outputs, we may review the shared outputs and votes to improve the quality of WHIPT. You can change this choice at any time in Settings.

2.8 Communications

If you email us or contact support, we keep your message, your contact details and our reply so we can help you.

2.9 Payment information

Payments are processed by Stripe (see Section 5.1). When you buy credits, you enter your card details into fields or pages that Stripe hosts, either on our checkout pages at https://pay.whipt.ai or on a Stripe payment page. Your full card number and security code go directly to Stripe; we never receive or store them.

When you check out, we collect the name and email address you enter, and we create a Stripe customer record for your organization. From Stripe we receive and store, for each card on file: Stripe's identifiers for the customer and the card, the card brand, the last four digits, the expiry month and year, and the card fingerprint (a value Stripe derives from the card number that lets us recognize the same card again without knowing its number). We also store Stripe's identifiers for each payment, refund and dispute. Card fingerprints are used only for fraud prevention (Section 2.11); we keep them out of API responses, logs and error reports, and our staff do not see them.

2.10 Credits, usage and billing records

WHIPT bills usage from prepaid credits held in a wallet for each company (workspace). Today we record and price usage but do not yet deduct it from wallets (see Section 9 of our Terms of Service). To run your wallet we keep:

  • a record of each billable unit of usage, such as a hosted AI model request, an embedding, or an email sent, with the time, the type and quantity of usage, the provider's cost where one applies, the credits charged, and the workspace and agent it was for;
  • a ledger of every change to the wallet balance (purchases, usage, refunds, disputes and adjustments), with the amount, the resulting balance, the reason, who or what made the change, and the related Stripe identifier;
  • each payment attempt, including the credits being paid for, the price at the time, and which card it was charged to; and
  • for card disputes, the dispute's status, reason, amount, currency and response deadline.

2.11 Fraud prevention and account security

To protect the Service and our customers from payment fraud and abuse, we use the following signals:

  • Bot protection. Our checkout pages use Cloudflare Turnstile, which evaluates your browser and network signals, including your IP address, to tell people from automated traffic. Our servers check the result with Cloudflare on each checkout attempt.
  • Stripe fraud screening. Stripe uses your IP address and device and browser information collected by its script on the checkout pages to screen payments for fraud.
  • Card fingerprints. We compare card fingerprints across accounts to detect a card that is reused by another organization or that belongs to a banned account.
  • Email checks. We refuse disposable email domains at checkout, and if an account already exists for the email address you enter, we send a sign-in code to that address instead of continuing the purchase.
  • Account bans. If our staff ban an account for fraud or abuse, we record that it was banned, when, and the reason. We do not complete purchases made with any card that a banned account has used.
  • Rate limits. We limit repeated checkout attempts by IP address, and by each combination of email address and IP address. Limits based on your IP address are evaluated in memory (for IPv6, using its first 64 bits) and are not written to a database. We also limit how many unpaid purchases can be open for each combination of email address and IP address; that count is kept in memory and checked against the purchase records, which do not store your IP address.

3. How we use personal information

We use personal information to:

  • create and manage accounts, sign you in, and keep sessions secure;
  • provide, operate and maintain the Service, including running the AI agents and automations your workspace configures;
  • send service messages such as sign-in codes, invitations, security notices and changes to our terms;
  • process payments, keep your credit wallet and its history accurate, and handle refunds and card disputes;
  • respond to support requests;
  • monitor, debug and improve the reliability, performance and security of the Service;
  • understand how the Service is used, through product analytics, so we can improve it;
  • prevent fraud, abuse and unauthorized access, including payment fraud and the return of banned accounts;
  • keep financial records required for tax, accounting and audit purposes;
  • comply with legal obligations and enforce our Terms of Service.

We do not sell personal information, we do not use it for targeted advertising, and we do not use Workspace Content to train generalized AI models. We send only service and transactional email (such as sign-in codes, invitations, security notices and notices of changes to our terms). We do not send marketing email.

4. Legal bases (EEA, UK and Switzerland)

Where the GDPR or UK GDPR applies, we rely on:

  • Contract: to provide the Service you signed up for, including sign-in, account management, payments and your credit wallet.
  • Legitimate interests: to secure the Service, prevent abuse and payment fraud, troubleshoot errors, understand how our website and app are used, and improve the product, balanced against your rights.
  • Consent: where we ask for it, such as sharing voted AI outputs. You can withdraw consent at any time.
  • Legal obligation: where the law requires us to keep or disclose information, such as tax and accounting records.

5. How we share personal information

We share personal information only as described here.

5.1 Service providers (sub-processors)

We use the following service providers to run the Service. They may process personal information only on our instructions and to provide their services to us.

Each of these providers processes personal information only to deliver the part of the Service it supports. Stripe also processes some payment information as an independent controller, for its own fraud prevention and legal compliance, under the Stripe Privacy Policy. Customer inbox email belongs to the workspace that owns the inbox, so for that email we act as a processor for that workspace and the email provider acts as our sub-processor (see Section 1). Transfers to providers outside your country are covered by Section 9.

These three tables are our complete list of sub-processors; we do not keep a separate list elsewhere. Before any provider not listed here processes personal information, we will add it to this list and update the "Last updated" date above. We may also let you know by email or in the Service.

5.2 AI model providers

WHIPT agents send prompts and relevant Workspace Content to AI model providers to produce their outputs. A prompt can include the agent's name and instructions, the task or issue it is working on (including titles, descriptions and comments), the workspace skills assigned to it, and, for automations, the data the automation step is given. Any personal information in that content goes to the model provider with it.

Hosted models. Workspaces that are entitled to models WHIPT provides ("hosted models") can run agents and automations on them. When your workspace does, we send the prompt to OpenRouter, which forwards it to Anthropic to produce the response. We configure each request so that OpenRouter sends it only to Anthropic, with no fallback to other providers, and only to endpoints that OpenRouter's routing rules mark as not collecting request data (OpenRouter's "data collection: deny" setting). Requests to hosted models may pass through an AI gateway that we run on our own servers at DigitalOcean; it is part of our infrastructure, not a separate provider. The gateway does not store the content of prompts or responses. It keeps request metadata, such as the time, the model, token counts, cost, status and the workspace the request was for, for 90 days, so we can bill and reconcile usage. We do not add your name, email address or account identifier to the request, although they can appear in the prompt content described above. OpenRouter and Anthropic may keep request data for a limited period under their own terms, for example to detect abuse.

Embeddings for company memory. To make company memory searchable by meaning (Section 2.3), we send memory text through OpenRouter to an embedding model and store only the resulting embedding in Qdrant Cloud. Search by meaning is not yet turned on for customer workspaces. Until it is, no memory text is sent for embedding and nothing is stored in Qdrant Cloud. Before we turn it on, we will name the embedding model provider, and the data settings we use with it, in Section 5.1.

Your own model provider. If your workspace connects its own model provider account or API key, that data goes to the provider you chose, under your agreement with that provider, and that provider is not our sub-processor.

5.3 Apps your workspace connects

When your workspace connects a third-party app, we send data to and receive data from that app as your workspace directs. Those apps are operated by their own providers under their own terms and privacy policies, and they are not our sub-processors.

5.4 Within your workspace

Your name, email address and activity are visible to other members of the workspaces you belong to, according to their roles.

5.5 Legal and safety

We may disclose information if we believe in good faith that it is required by law, legal process or a government request, or that it is needed to protect the rights, property or safety of Legion Code, our users or others.

5.6 Business transfers

If Legion Code is involved in a merger, acquisition, financing or sale of assets, personal information may be transferred as part of that transaction, subject to this policy.

Infrastructure providers
ProviderPurposeData involvedLocation
WorkOS, Inc.Authentication (Google, GitHub and emailed sign-in codes), organization membership, invitationsName, email, account identifiers, IP address and user agent at sign-inUnited States
DigitalOcean, LLCApplication hosting, managed PostgreSQL database, backups, container registryAll account data and Workspace ContentUnited States (New York)
Cloudflare, Inc.DNS, network edge, TLS, load balancing, private object storage (R2), bot protection on our checkout pages (Turnstile), and, where enabled, cookieless visitor statistics (Cloudflare Web Analytics) on pages and funnels that workspaces publishNetwork traffic, IP addresses, stored files and attachments; on the checkout pages, the browser and network signals Turnstile evaluates; on published pages, the page address, referrer, browser information and page load timingsGlobal edge network; R2 storage in Eastern North America
Vercel, Inc.Hosting of our marketing website www.whipt.ai and our checkout pages pay.whipt.aiWebsite request data, IP addressesUnited States and global edge
Qdrant Solutions GmbH (Qdrant Cloud)Vector search for company memory (not yet in use; see Section 5.2)Embeddings of memory text, and workspace, memory record and agent identifiers; no memory textUnited States
Email, AI and error monitoring providers
ProviderPurposeData involvedLocationWhose data
AgentMailSending and receiving email for customer inboxesInbox address and an internal workspace identifier; for each email, sender and recipient names and addresses, subject, message body, headers and attachmentsUnited States, or the European Union where we use AgentMail's EU regionWorkspaces whose customer inbox uses AgentMail
ResendSending and receiving email for customer inboxesSending and receiving addresses; for each email, sender and recipient names and addresses, subject, message body, headers (including sender authentication results) and attachmentsUnited StatesWorkspaces whose customer inbox uses Resend
OpenRouter, Inc.Routing requests to AI models that WHIPT provides ("hosted models"), and creating embeddings of company memory textPrompts and the Workspace Content included in them (see Section 5.2), memory text sent for embedding, the model's response, and usage and cost figuresUnited StatesWorkspaces that run agents or automations on hosted models, or use company memory search
Anthropic, PBCAI model that produces hosted model outputs, reached through OpenRouterThe same prompts and responses that pass through OpenRouterUnited StatesWorkspaces that run agents or automations on hosted models
Sentry (Functional Software, Inc.)Error monitoring for the app and our serversError reports as described in Section 2.6United StatesAll signed-in users of the app (browser errors) and all users (server errors)
PostHog, Inc.Product analytics on our marketing website www.whipt.ai and in the appPages viewed, referring page, browser and device information, IP address and the approximate location derived from it, and a random visitor identifier (see Section 6); in the app, also the controls used, campaign tags and search details from the link that brought you there, internal account and workspace identifiers, and account events (see Section 2.6)United StatesVisitors to www.whipt.ai and signed-in users of the app
Payment providers
ProviderPurposeData involvedLocationWhose data
Stripe, Inc.Payment processing for credit purchases, saved cards, refunds and disputes, and payment fraud screeningName, email address, card details you enter in Stripe's fields (which we never receive), billing details, IP address, and device and browser information collected by Stripe's script on the checkout pages; payment, refund and dispute recordsUnited States, and other countries where Stripe operatesOrganizations and companies that buy credits, and the people who enter card details

6. Cookies and similar technologies

The WHIPT app uses these cookies that are strictly necessary for it to work:

  • a secure session cookie that keeps you signed in (it holds an encrypted session, not your password);
  • short-lived cookies used only during the sign-in flow (for example, to complete email verification or choose a workspace);
  • security cookies used for staff administrative access;
  • a secure purchase cookie set during checkout, which links your browser to the status of the purchase you just made and lasts up to 30 days.

The app also stores interface preferences (such as layout and theme choices) in your browser's local storage. The app loads Sentry's error reporting script only while you are signed in; it is configured without session replay and is used only to report errors, not for analytics or advertising (see Section 2.6). While you are signed in, the app also uses PostHog product analytics (see Section 2.6): PostHog sets a first-party cookie on the app's own address and uses your browser's local storage to hold its identifier, and the data is sent through our own analytics address (t.lgpxl.com) to PostHog's servers in the United States. We use it only to measure and improve the Service, not for advertising. Signing out clears the analytics identifier. You can block or delete these cookies in your browser settings, and the app keeps working. The WHIPT app does not use advertising cookies or cross-site tracking cookies.

Our marketing website. www.whipt.ai uses PostHog product analytics to understand how visitors use the site, for example which pages are viewed and where visitors came from. PostHog sets a first-party cookie and uses your browser's local storage to hold a random visitor identifier, and the data is sent through our own analytics address (t.lgpxl.com) to PostHog's servers in the United States. We use it only to measure and improve our website, not for advertising, and we do not use advertising or cross-site tracking cookies. You can block or delete these cookies in your browser settings without affecting the website. If we offer a consent choice for analytics cookies, the website will honor your choice.

Our checkout pages. https://pay.whipt.ai loads no analytics. While you are on the checkout pages, Stripe's script collects device and browser information and sets its own cookies, which Stripe uses to process your payment and to detect fraud, and Cloudflare Turnstile evaluates browser signals to tell people from automated traffic (see Section 2.11). These are needed to take payments safely.

Pages that workspaces publish. Pages and funnels that workspaces publish with WHIPT may load Cloudflare Web Analytics, which sets no cookies and records the page address, referrer, browser information and page load timings so we can measure how published pages perform (see Section 5.1).

We honor Global Privacy Control signals as a request to opt out of any sale or sharing of personal information, although we do not sell or share personal information for cross-context behavioral advertising.

7. How long we keep information

  • Account information: for as long as your account is active, then deleted as described in Section 10.
  • Workspace Content: for as long as the workspace is active, or until a workspace owner or administrator deletes it. When a workspace is closed we delete its content within 30 days, unless the law requires us to keep it.
  • Server and application logs (other than the AI gateway's): about 14 days, after which they are automatically removed. IP addresses in access logs are truncated to /24 (IPv4) or /48 (IPv6).
  • AI gateway request metadata and gateway server logs: 90 days. The gateway does not store prompt or response content (Section 5.2).
  • Billing and transaction records (usage records, the credit wallet ledger, payment attempts, refunds and disputes, and the card details listed in Section 2.9 other than card fingerprints): for seven years after the transaction, as needed for tax, accounting, audit and dispute purposes. We keep these records even if the workspace or account is closed, and they are not covered by the 30-day workspace deletion above.
  • Fraud prevention records (account bans and their reasons, and the card fingerprints on related purchases): for as long as needed to keep a banned account or card from returning, and no longer than seven years after the account's last activity.
  • Company memory embeddings: when a memory is deleted or corrected, or a workspace is deleted, the memory stops being returned to agents immediately, and we start deleting its embeddings from Qdrant Cloud at once and confirm that they are gone, normally within one hour. Deleted data may remain in Qdrant's storage until its own cleanup process runs. We have not enabled Qdrant Cloud's snapshot or backup features for company memory. The memory text itself is deleted from our database as described for Workspace Content.
  • Copies held by our providers: error reports held by Sentry, emails held by our email delivery providers, requests held by our hosted AI providers, analytics data held by PostHog, and payment records held by Stripe are kept under each provider's retention settings for our account and its own terms. Stripe keeps payment records for as long as the law requires it to.
  • Backups: encrypted backups are kept on a rolling basis and overwritten within 30 days. Deleted data may remain in backups for up to 30 days after it is deleted, until those backups roll off.
  • Support communications: for as long as needed to resolve the request and for our records, up to 3 years.

8. Security

We protect personal information with measures that include encryption in transit (TLS), encryption of stored secrets and connection credentials, a private network for our database, firewalls that accept traffic only through our network edge, role-based access within workspaces, and restricted staff access to production systems. Card numbers and security codes are handled only by Stripe and never reach our systems, and card fingerprints are kept out of API responses, logs and error reports. No system is perfectly secure, and we cannot guarantee absolute security. If we learn of a breach that affects your personal information, we will notify you as required by law.

9. International transfers

We are based in the United States, and the Service is hosted in the United States. If you use the Service from outside the United States, your information will be transferred to, stored and processed in the United States and in other countries where our service providers operate. Our sub-processors listed in Section 5.1, including Cloudflare, AgentMail, Resend, OpenRouter, Anthropic, Sentry, PostHog, Qdrant and Stripe, process personal information in the locations shown in that section, which are mainly in the United States. Where the law requires a transfer safeguard, including for transfers to these sub-processors, we use the European Commission's Standard Contractual Clauses (with the UK and Swiss addenda where they apply).

10. Your rights and choices

Depending on where you live, you may have the right to:

  • access the personal information we hold about you and receive a copy of it;
  • correct inaccurate information;
  • delete your information;
  • export your information in a portable format;
  • object to or restrict certain processing;
  • withdraw consent where we rely on consent;
  • complain to your local data protection authority.

How to make a request. Email privacy@whipt.ai from the email address on your account and tell us what you would like us to do. We may need to verify your identity. We will respond within 30 days, or sooner where the law requires.

Deleting your account. When you ask us to delete your account, we delete your account record (including your name, email address and Google or GitHub sign-in link) from our database and from our authentication provider, delete the analytics record PostHog holds about you (your PostHog person and its events), and remove you from your workspaces, within 30 days of your request. If you are the only owner of a workspace, we will ask whether to delete the workspace or transfer it first. Content you created inside a workspace that belongs to an organization may remain in that workspace under the organization's control. We keep billing and fraud prevention records for the periods in Section 7 even after your account is deleted, because the law requires them or they protect the Service from fraud; where a billing record names you (for example as the person who made a purchase), we keep that reference only as part of the record.

If your workspace is managed by an organization, that organization may control your account and its content. For requests about information an organization put into WHIPT, contact that organization, and we will support them.

Revoking Google access. You can remove WHIPT's access to your Google account at https://myaccount.google.com/permissions. This stops future sign-ins with Google but does not by itself delete your WHIPT account; email us to delete it.

11. United States state privacy rights

If you are a resident of California or another U.S. state with a comprehensive privacy law, you have the rights described in Section 10, plus the right not to be discriminated against for exercising them. In the last 12 months we have collected the categories of information described in Section 2 (identifiers such as name, email address, IP address, device and browser information, and card fingerprints; commercial information such as credit purchases and payment records; limited payment card information such as card brand, last four digits and expiry; internet or network activity, including website and app analytics; approximate location derived from IP address; and the content you provide) from you, from your workspace, and from our service providers (for example sign-in details from WorkOS, payment and fraud screening results from Stripe, and bot protection results from Cloudflare), for the business purposes described in Section 3, and disclosed them to the service providers listed in Section 5. We do not sell personal information, and we do not share it for cross-context behavioral advertising. We do not receive full card numbers or security codes; Stripe collects them as our service provider to process your payment. We do not collect or use sensitive personal information for the purpose of inferring characteristics about you. You may use an authorized agent to make a request, and we may ask for proof of the agent's authority.

12. Other regions

If you are in Quebec, Brazil or another region with its own privacy law, you have the rights that law provides, and you can exercise them using the contact details in Section 15. Residents of Quebec, Brazil, the European Union and the United Kingdom can contact us about their privacy rights at privacy@whipt.ai.

13. Children

The Service is intended for business use by people who are at least 18 years old. We do not knowingly collect personal information from children under 16. If you believe a child has given us personal information, contact us and we will delete it.

14. Changes to this policy

We may update this policy from time to time. Changes take effect when we post the updated policy on this page, and we will update the "Last updated" date above. We may also let you know about material changes by email or through the Service. Please check this page from time to time.

15. Contact us

Legion Code Inc., c/o its registered agent in Delaware

Privacy questions and requests: privacy@whipt.ai

General support: support@whipt.ai