Privacy Policy

1. Scope and our role

ChurnAI (“we,” “us,” or “our”) provides customer intelligence software for business customers through the Model Context Protocol (MCP). This policy explains how we handle personal information when you visit our website, use the service, or contact us.

We determine how we use account information, website enquiries, and business communications. For personal information processed on a customer’s behalf through connected systems, the customer directs the processing. Where applicable, the customer is the controller and ChurnAI is its processor, subject to the customer agreement and applicable data-processing terms.

The service is intended for business users and is not directed to children. Do not connect children’s data or sensitive personal information unless the use has been expressly agreed and is lawful.

2. Information we handle

• Account information: your login email address, basic profile information, and identifiers needed to recognise your account and authorised access.
• Pilot requests and communications: information you submit when requesting Pilot access, including your name, work email, company name, company website, role, team size, and information you send in emails, demo bookings, support requests, or feedback.
• Connected customer data: information your business authorises us to read through its integrations. Depending on the source and permissions, this can include account and contact identifiers, product activity, subscription and billing status, support information, and CRM records.
• MCP request information: information needed to fulfil an authorised request and return relevant customer context to your chosen AI workspace.
• Website and operational information: usage measurements and technical request information, such as browser, device, network, and error information, depending on the service configuration.

3. Where connected data is stored

Pilot customers

During a Pilot, ChurnAI stores imported connected data in its cloud database using Neon. Neon also stores login and basic account information.

Paid customers

Connected data syncs to the customer’s own cloud storage. ChurnAI retains basic account information to administer the service. Authorised MCP requests can still involve processing context through Cloudflare and transmitting it to your chosen AI workspace.

Our integration access is read-only: it allows us to read and sync approved information, but not change records in the source system.

4. Why we use information

• Identify authorised users and administer their accounts.
• Connect approved sources, sync data, and fulfil customer-intelligence requests.
• Provide Pilot onboarding, respond to enquiries, and support customers.
• Understand website usage and maintain the website and service.
• Investigate errors or misuse and meet applicable legal obligations.

Where applicable, our legal bases are performing a contract with you or taking steps you request before a contract; legitimate interests in business administration, website operation, and security; compliance with legal obligations; and consent where required. We consider individuals’ rights when relying on legitimate interests. Your business is responsible for the lawful basis and notices for connected personal information it asks us to process.

5. AI workspaces and model training

When you connect ChurnAI to an AI workspace such as ChatGPT or Claude, ChurnAI returns relevant customer context through MCP in response to authorised requests.

ChurnAI does not use customer data to train AI models.

Your AI provider’s terms, privacy policy, and account settings govern its use of that context, including retention and model training. Review those settings before connecting customer information.

6. Providers, sharing, and locations

We do not sell customer data. We use the following providers to operate the product; they process information relevant to their role:

• Cloudflare: infrastructure for the MCP service and associated request processing.
• Neon: database storage for login/account information and Pilot customer data.
• Resend: delivery of Pilot-request notifications to ChurnAI and confirmation emails to applicants.

We also use website hosting and analytics providers to deliver this website and measure its usage. If you submit a Pilot request, Resend processes the form information to notify ChurnAI and confirm receipt to you. If you choose to book a meeting through our Cal.com link, Cal.com processes the booking information under its own privacy policy. Your selected AI workspace and connected integrations also process information according to their roles and your authorisations.

We may disclose information where required by law, in response to a valid legal request, or where necessary and legally permitted to protect rights or investigate misuse. A transfer of the business may involve transferring relevant information, subject to applicable legal requirements.

Providers may process information outside your country. Processing locations and any required transfer safeguards must be addressed for your deployment before you connect data with location restrictions. Your own storage location does not determine where your AI workspace or MCP requests are processed.

7. Website analytics and cookies

Optional website analytics loads only after you select “Accept all.” Selecting “Decline” keeps it disabled. Hosting providers still process technical request information needed to deliver the website.

We store your choice in your browser’s local storage until you change it or clear that storage. This preference does not require you to accept analytics. If browser storage is unavailable, your choice applies for the current page session.

You can change your choice through “Cookie settings” in the footer. Withdrawing permission stops future optional analytics and reloads the page to unload the analytics script; it does not undo earlier processing.

These settings apply to this website’s optional analytics. External services, including your AI workspace and the booking service, have their own privacy and storage controls.

8. Retention and deletion

If you do not continue, ChurnAI deletes connected customer data under its control within 30 days after cancellation or Pilot expiry, including backups. Specific legal retention requirements may require us to keep affected records for the required purpose and period.

Cancellation does not erase your source systems or your own cloud storage. Your AI workspace and other services control their separate copies under their terms and settings.

We retain basic account information and communications as needed to administer the relationship, resolve outstanding requests, and meet recordkeeping obligations. The connected-data deadline does not apply to these records. You can request account deletion using the contact below.

9. Your rights and requests

Depending on applicable law and the circumstances, you may have rights to access or correct your information, request deletion, receive a portable copy, restrict or object to processing, withdraw consent where processing relies on it, and raise a complaint with an appropriate authority.

Send requests to shajeed@trychurnai.com. We may request information needed to verify your identity and authority. We will handle requests within the time required by applicable law; some rights are subject to legal exceptions.

If we process the information on behalf of a business customer, that customer controls the response. Contact the business directly, or ask us to help direct your request.

10. Changes and contact

We will update this policy when our practices change and revise the date above. Where required by law, we will provide additional notice or obtain consent before a material change takes effect.

For privacy questions, security concerns, or requests, email shajeed@trychurnai.com. You can also read our Terms of Service.