Privacy Policy

Compliance Colleague

Last Updated: November 10, 2026

How Your Data Is Handled: Summary

In plain terms, here is what happens to your questions and documents. This summary is for convenience; the numbered sections below give the full detail and govern.

1. Overview

This Privacy Policy explains how Compliance Colleague Limited Liability Company, an Arizona limited liability company doing business as “Compliance Colleague” (“Company,” “we,” “us,” or “our”), collects, uses, discloses, and protects personal data in connection with the Compliance Colleague website, application, and related services (collectively, the “Service”). This Policy is incorporated by reference into, and should be read together with, our Terms of Service.

This Policy describes our practices as a business. If your organization has its own Data Processing Agreement with us covering personal data your organization submits through the Service, that agreement governs our processing of that data as your processor, and this Policy supplements it by describing our practices as a business generally.

2. Scope

This Policy applies to personal data we collect through the Service, our website, related communications (such as support emails), and the forms we use to collect feedback and requests for content we publish (Section 3.8). It does not apply to third-party websites, applications, or services that we do not control, even if you access them through the Service or a link we provide — including the separate services described in Section 6 below, each of which has its own privacy practices.

The Service is intended for business and professional use and is not directed to consumers or to individuals under 18. See Section 13 (Children's Privacy).

3. Information We Collect

3.1 Account information

When you create an account, we collect your email address (used for magic-link sign-in through our authentication provider, Supabase, which sends sign-in emails through our email delivery provider, Resend) and the subscription tier and compliance standards you select.

3.2 Content you submit

We collect the questions you ask, the compliance standards you select for a query or comparison, and any documents you upload for AI-assisted review against a standard. Documents and questions may contain personal data at your discretion — for example, if an uploaded policy document names individual employees. We do not control what you choose to include in content you submit, and you should avoid submitting personal data that isn't necessary for your query.

3.3 Usage and billing data

We collect records of your usage of the Service (which standards you queried, token/compute usage, and computed cost) to enforce your plan's allowance and calculate any opted-in overage. Payment card and billing details are collected and processed directly by our payment processor and merchant of record, Paddle — see Section 6.3. We receive only your subscription and payment status from Paddle, not your full payment card number. When you sign up, we also record how you reached us: a campaign tag in the link you followed (for example, ?ref=linkedin), or, if there is none, the domain of the website that sent you. This is read from the link itself, not from cookies or third-party tools, is stored with your account, and is used only to understand which channels bring people to the Service.

3.4 Device and session data

To enforce the single-user license described in Terms of Service Section 5 (account-sharing prohibition), we collect a device identifier (stored in a first-party cookie), multi-factor authentication enrollment status, and records of concurrent active sessions across devices. This is used only for the anti-sharing and account-security purposes described in Section 4 below.

3.5 Communications

If you contact us (for example, by email), we collect the content of that communication and any information you choose to provide in it. Our business email is hosted by Google Workspace (Section 6.1). If you start a free trial, we send you up to three emails during it, through our email delivery provider, Resend (Section 6.1): a welcome with suggestions for using the trial, a follow-up a few days in, and a reminder shortly before the trial ends that describes our paid plans. We record which of these emails we have sent to your account. You can opt out when you sign up, by unticking the box on the trial sign-up page, and every one of these emails includes a link to unsubscribe that does not require signing in. Opting out or unsubscribing stops these emails; it does not stop messages about your account, such as sign-in links and billing or legal notices.

3.6 Information we do not intentionally collect

We do not use advertising trackers or cross-site tracking, and we do not sell personal data. We use cookieless, aggregate website analytics, described in Section 3.7. See Section 12 (Cookies) for the specific cookies the Service uses.

3.7 Website analytics

We use Vercel Web Analytics to count visits to our website in aggregate. For each page view it records the time, the page visited, the referring website, the campaign tag in the link you followed (for example, ?ref=linkedin), your approximate location (country, region and city), and your device type, operating system and browser. It sets no cookies and stores nothing on your device. Vercel tells visitors apart using a hash derived from the incoming request, which it discards after 24 hours, and the statistics we see are aggregated and not tied to any individual or IP address. Before anything is sent, we remove everything in the page address except the page itself and the campaign tag, so codes such as trial invitations or sign-in links are never included, and we do not record sign-in pages at all. We also keep our own count of visits that arrive through a link carrying a campaign tag, or from a search engine or AI assistant (recorded only as the name of the service, for example google.com, never the search terms), stored only as daily totals for each source and page, with no IP address, device data or identifier. We use these statistics only to understand which pages and channels are useful.

3.8 Feedback forms, content requests and updates

We use Google Forms for short surveys and requests, such as feedback on a trial or a request for a guide or table we publish. We collect what you enter: your answers and, where the form asks for it or you choose to give it, your email address. We use your answers to improve the Service. We use your email address only for the purpose the form states, such as sending you the content you asked for once or following up on your feedback. We send occasional updates about new guides and tools only if you tick the separate opt-in box, which is never ticked for you. Every update includes a way to unsubscribe, and you can also withdraw your consent at any time by contacting us (Section 16). We do not add your email address to any other list, and we do not sell it or share it for others' marketing. The form pages are served by Google on its own website, where Google may use its own cookies as described in Google's privacy policy.

3.9 Free question on our homepage

Visitors may ask one question on our homepage without creating an account. We send the question and the standard you pick to our AI model provider to generate the answer, as described in Section 5, and we do not store the question or the answer ourselves. To limit each visitor to one question a day and protect the Service from abuse, we keep a keyed one-way hash of your IP address (never the address itself) together with the standard you picked, the outcome and its cost. We delete the hash after 25 hours, and the rest of the record, which no longer identifies anyone, after 30 days.

4. How We Use Information

We do not use your account information, questions, or uploaded documents to train AI models. Section 5 below explains how content you submit is handled by our AI model provider specifically.

5. AI Processing and Our Model Provider

The Service uses Anthropic's Claude models, accessed through Anthropic's commercial API, to generate responses to your questions and to review documents you upload. This section describes how that processing works and is intended to mirror Terms of Service Section 11 (Confidentiality of Your Data) so the two documents stay consistent — if you notice any inconsistency between them, this Policy and Section 11 should be read together, and please let us know.

5.1 What we send to Anthropic

Your question, the text of the compliance standard(s) you selected (via Anthropic's Agent Skills feature), and, if you upload one, the content of your file (a PDF is sent as the file itself or as text extracted from it; an image is sent as the image itself; a Word, Excel, CSV, Visio or draw.io file is sent as text extracted from it) are sent to Anthropic's API to generate a response. We do not send your account email address, payment information, or device/session data to Anthropic — only the content needed to answer your question.

5.2 Anthropic does not train on this data by default

By Anthropic's own published policy for commercial/API customers (which governs our use of Claude): “By default, we will not use your inputs or outputs from our commercial products (e.g. Claude for Work, Anthropic API, Claude Gov, etc.) to train our models.” We have not opted in to any Anthropic program (such as its Development Partner Program) that would change this, and the Service does not expose any “thumbs up/down” feedback mechanism to Anthropic. Source: Anthropic Privacy Center, “Is my data used for model training?”, privacy.claude.com.

5.3 How long Anthropic retains this data

Anthropic's stated default policy for its commercial API is to “automatically delete inputs and outputs on our backend within 30 days of receipt or generation,” subject to limited exceptions (for example, active investigations of a Usage Policy violation, or a separate zero data retention agreement; the Company does not have one). Where Anthropic's automated trust and safety systems flag a request as a potential Usage Policy violation, Anthropic may retain the related inputs and outputs for up to 2 years. The Service sends documents inline as part of each API request rather than through Anthropic's separate Files API, so the longer, user-controlled retention available through that product does not apply here — the standard 30-day (or shorter) deletion window governs. Source: Anthropic Privacy Center, “How long do you store my organization's data?”, privacy.claude.com.

5.4 Anthropic's own data processing terms

Anthropic's Data Processing Addendum, including Standard Contractual Clauses for international transfers, is automatically incorporated when a business accepts Anthropic's Commercial Terms of Service — which we have done as an Anthropic API customer. This means Anthropic's processing of the content described in Section 5.1 is already governed by a data processing agreement with SCCs in place, one link in the transfer chain described in Section 8 below. Source: Anthropic Privacy Center, “How do I view and sign your Data Processing Addendum (DPA)?”, privacy.claude.com.

6. Other Service Providers

6.1 Sub-processors acting on our instructions

We use the following service providers to operate the Service. Each processes personal data only on our instructions, for the purposes described below, and is bound by a data processing agreement with us.

Provider

Role & Data

Location & Safeguards

Anthropic, PBC

AI model provider. Processes your questions, selected standards, and uploaded document content to generate responses. See Section 5.

United States. Anthropic's Commercial DPA with Standard Contractual Clauses applies automatically (Section 5.4). Anthropic's current sub-processor list is published at trust.anthropic.com.

Supabase, Inc.

Database, authentication, and (if used) file storage. Hosts your account record, usage logs, and device/session records.

United States (East US, Ohio). Supabase offers a Data Processing Addendum; see supabase.com/legal/customer-resources/data-processing-addendum.

Vercel Inc.

Website and application hosting, and cookieless website analytics. Processes the requests your browser sends to the Service, including your IP address and the content of your requests and uploads, to deliver the Service; and records aggregated page-view statistics (Section 3.7).

United States (primary processing facilities). Vercel's Data Processing Addendum forms part of its terms for Pro customers; see vercel.com/legal/dpa.

Google LLC

Business email and forms (Google Workspace). Hosts our email, including messages you send us and emails we send you, and stores responses to our Google Forms (Section 3.8).

United States and other countries where Google operates data centers. Google's Cloud Data Processing Addendum, including Standard Contractual Clauses, forms part of our Google Workspace agreement; see cloud.google.com/terms/data-processing-addendum.

Plus Five Five, Inc. (Resend)

Email delivery. Sends the emails the Service generates, such as sign-in links, and processes your email address and the content of those emails.

United States. Resend's Data Processing Addendum, including Standard Contractual Clauses, applies automatically under its terms; see resend.com/legal/dpa.

6.2 Sub-processor changes

We may add or replace sub-processors as our business needs evolve. Any new sub-processor will be held to data protection obligations materially equivalent to those described in this Policy and in our Data Processing Agreement.

6.3 Paddle — not our sub-processor

Payment processing works differently. We use Paddle.com Market Limited (“Paddle”) as our merchant of record for billing, consistent with Terms of Service Section 6. Because Paddle is the merchant of record, Paddle itself — not us — is the party you transact with for payment, and Paddle acts as an independent data controller (not our sub-processor) for the billing and payment data it collects directly from you at checkout. Paddle's handling of that data is governed by Paddle's own privacy policy, available at paddle.com/legal/privacy, not by this Policy. We receive from Paddle only your subscription status and the identifiers needed to link your subscription to your account — we do not receive or store your full payment card number.

7. Legal Bases for Processing (EEA/UK Users)

If you are located in the European Economic Area, the United Kingdom, or another jurisdiction that requires a stated legal basis for processing, we process personal data on the following bases:

8. International Data Transfers

Compliance Colleague is based in the United States, and our service providers described in Section 6 process data primarily in the United States. If you are located outside the United States, your information will be transferred to, and processed in, the United States and potentially other countries.

Where required by applicable data protection law (including the GDPR and UK GDPR), we rely on Standard Contractual Clauses or another valid transfer mechanism for these transfers. As described in Section 5.4, Anthropic's own Commercial DPA with Standard Contractual Clauses applies automatically to our use of its API. Google's Cloud Data Processing Addendum and Resend's Data Processing Addendum each include Standard Contractual Clauses for transfers of the data they process for us. We are evaluating the equivalent transfer mechanism available through Supabase's Data Processing Addendum for account and usage data.

9. Data Retention

9.1 Account and usage data

We retain your account information (email, tier, allowed standards) and usage records for as long as your account is active, and for 24 months after cancellation or termination — to allow reactivation, resolve billing disputes, and comply with our legal and accounting obligations — after which we delete or anonymize it, except where a longer period is required by law (for example, tax recordkeeping).

9.2 Questions and uploaded documents

We do not separately store the content of your questions or uploaded documents once a response has been generated and returned to you, beyond what is transiently necessary to process the request. As described in Section 5.3, Anthropic separately retains the inputs and outputs it processes for up to 30 days by default under its own policy, independent of our own systems.

9.3 Device and session records

Device and concurrent-session records described in Section 3.4 are retained on a rolling basis (see Terms of Service Section 5.4) to support account-sharing detection, and are not kept longer than necessary for that purpose.

9.4 Form responses and update subscriptions

Feedback answers, including any email address you leave for follow-up, are kept for as long as they help us improve the Service, and for no more than 24 months. If you request a guide or table without opting in to updates, we delete your email address within 90 days after we send it. If you opt in to updates, we keep your email address until you unsubscribe; after that, we keep only a record that you unsubscribed, so that we do not email you again. If you opt out of or unsubscribe from our trial emails, we keep only a one-way hash of your email address, not linked to your account, so that we do not email you again, including if you delete your account and later sign up again.

10. Data Security

We use technical and organizational measures designed to protect personal data, including:

No method of transmission or storage is completely secure, and we cannot guarantee absolute security. If we become aware of a breach affecting your personal data, we will notify you and any required regulator as described in Section 14.

11. Your Privacy Rights

11.1 EEA, UK, and similar jurisdictions

If applicable data protection law gives you these rights, you may have the right to: access the personal data we hold about you; correct inaccurate data; request deletion; restrict or object to certain processing; receive a portable copy of data you provided; withdraw consent at any time where we rely on it; and lodge a complaint with your local data protection authority. To exercise any of these rights, contact us using the details in Section 16.

11.2 India

If you are located in India, India's Digital Personal Data Protection Act 2023 (DPDP Act) may give you rights over your personal data, including the right to access, correction, and erasure, and the right to grievance redressal. We will honor applicable DPDP Act rights requests.

11.3 Australia

If you are located in Australia, the Privacy Act 1988 (Cth) and the Australian Privacy Principles may apply to our handling of your personal data. We will honor applicable access and correction requests consistent with that Act.

11.4 United States

Depending on your state of residence, you may have rights under a state privacy law (such as the right to know, delete, or correct your personal information). Because the Service is a business/professional tool and we do not sell personal data or use it for cross-context behavioral advertising, several state-law obligations that apply to consumer-facing, ad-supported services may not apply to our processing — we will still honor a verifiable rights request consistent with applicable law.

11.5 How to exercise your rights

Contact us at the email address in Section 16. We may need to verify your identity before acting on a request, and we will respond within the time required by applicable law.

12. Cookies and Similar Technologies

We use a small number of first-party cookies necessary for the Service to function: an authentication session cookie (so you stay signed in) and a device identifier cookie used for the account-sharing detection described in Section 3.4. Our website analytics (Section 3.7) sets no cookies and stores nothing on your device. Our forms are served by Google on its own website (Section 3.8), where Google's own cookies may apply. We do not use third-party advertising or cross-site tracking cookies. Because the cookies we use are strictly necessary for the Service to operate, we do not currently display a cookie consent banner. If we add any cookie or similar technology that is not strictly necessary, we will update this Policy and add appropriate consent controls before using it.

13. Children's Privacy

The Service is intended for business and professional use by individuals at least 18 years old, consistent with Terms of Service Section 1, and is not directed to children. We do not knowingly collect personal data from anyone under 18. If you believe a child has provided us personal data, contact us using the details in Section 16 and we will delete it.

14. Data Breach Notification

If we become aware of a security incident that compromises the confidentiality, integrity, or availability of your personal data, we will notify affected users and, where required by applicable law, the relevant regulator(s), without undue delay and consistent with the timelines applicable law requires.

15. Changes to This Policy

We may update this Policy from time to time. If we make material changes, we will provide notice (such as by email or an in-product notice) before the changes take effect. The “Last Updated” date at the top of this Policy reflects the most recent revision.

16. Contact Us

Questions about this Privacy Policy, or requests to exercise a privacy right described in Section 11, can be sent to support@compliancecolleague.ai or 7090 N Oracle Rd, Ste 178 #3297, Tucson, Arizona 85704.