On this page
1. About this policy
This Privacy Policy describes how Churnor handles personal information through its website, dashboard, APIs, imports, and connected services. It covers information about the people who use Churnor and information that business customers send about their own customers.
Churnor helps SaaS businesses understand customer activity and churn risk. References to “we,” “us,” or “our” mean the operator of Churnor. “Customer Data” means customer profiles, activity records, billing information, and related content submitted to a Churnor project.
This policy describes our practices; it is not a request for blanket consent to every use of information. Where applicable law requires a specific notice, permission, or consent, that requirement continues to apply. Our Terms and Conditions explain the rules for using the service.
2. Regional availability and EU restrictions
Churnor is not currently offered for use by people located in EU member states or by businesses established in the EU. We do not intend to market the service to those users or provide it for monitoring the behavior of people located in the EU. This is a restriction based on location and business establishment, not citizenship.
A business outside the EU must also keep out customer profiles, activity events, and other personal information concerning people located in the EU. If your application serves those people, filter their records before an API request, CSV upload, or provider integration sends data to Churnor. Do not connect an unfiltered source that includes such records.
Access to a public page or acceptance of an API request does not establish eligibility. If you discover that restricted data was submitted, stop sending it and contact us to arrange removal. We may suspend an affected connection or account while the issue is addressed.
This policy does not claim that EU law can be waived by agreement or that all countries outside the EU have identical requirements. Laws that apply because of the actual parties, processing activities, or location still apply. Contact us before using Churnor if you need a specific privacy agreement, regional hosting, or regulatory commitment.
3. Our role and your responsibilities
We determine how account, billing, support, and service-security information is handled to operate Churnor. For Customer Data sent by a business, we provide the service on that business’s behalf. The business chooses which people and events to include, what notices to provide, and how to use the results.
Businesses are responsible for having permission or another valid legal basis to collect and send Customer Data. They must provide appropriate privacy notices, honor customer requests, restrict access to authorized team members, and use integrations within the permissions granted by the source service.
If your personal information was submitted by a business that uses Churnor, contact that business first. It normally controls your relationship and can identify the relevant records. We can help it respond and will also consider requests addressed directly to us where applicable law requires us to do so.
4. Information we receive
Churnor account information
We receive information used to create and manage your account, such as your email address, name or sign-in profile, authentication identifiers, organization and project details, account permissions, and communications you send to us. Our authentication provider processes the credentials needed for your chosen sign-in method.
Customer profiles and activity
Your business may send customer identifiers, names, email addresses, signup dates, plans, account status, recurring revenue where relevant, and custom properties. Activity records may include an event name, a saved record ID, an original timestamp, and properties describing the action. Information received depends on your implementation and the fields you submit.
Connected billing sources may provide customer and subscription identifiers, subscription states, plan changes, payment outcomes, amounts, and other supported billing details. A one-time purchase is not automatically treated as recurring revenue. Uploaded CSV files provide the fields you select and map during import.
Derived information and operational records
Churnor generates risk scores, risk levels, recorded reasons, recommended actions, and saved score history from available inputs. It also keeps integration status and ingestion records, such as saved record IDs, authenticated key IDs, request outcomes, error details, and processing times. Hosting and infrastructure providers may process IP addresses, device or browser information, request paths, and security logs when operating the service.
Information you should keep out
Do not send passwords, API secrets, full payment-card details, government identification numbers, medical records, biometric information, private image files, or other sensitive information that is unnecessary for customer activity monitoring. Do not place personal contact information in event names or error messages. Custom properties can contain personal information, so review them before sending.
5. How integrations collect information
Your application sends updates when customers use it. Churnor does not scan your database. A server integration sends customer updates and activity to our authenticated APIs after actions in your application. Provider webhooks send supported changes when the provider delivers them. CSV imports submit records that you choose to upload.
A helper or queue installed in your application operates within your application and hosting account. Its source database access is controlled by you. Churnor does not need your source database service key for the standard API connection. Keep your Churnor API key on the server and rotate it if it is exposed.
Retrying a saved event with the same ID and unchanged data lets Churnor recognize a duplicate and retry an unfinished score update. Different data must not reuse the same event ID. Queues and source systems may retain their own copies under their separate settings and policies.
6. Why we use information
- Provide sign-in, account access, project management, and customer dashboards.
- Store received records, calculate and explain risk, show saved history, and provide recommendations based on the available evidence.
- Check integration delivery, repair failed processing, prevent duplicate records, and apply plan limits.
- Process Churnor subscriptions, reconcile payment status, and maintain necessary transaction records.
- Respond to support and privacy requests, investigate abuse or security issues, and comply with applicable legal requirements.
- Understand service reliability and improve the product using operational information and feedback.
We do not sell Customer Data or use it for third-party advertising. Churnor uses structured inputs for automatic rule-based scoring and manually requested AI assessments; a score is not a guaranteed prediction about a person’s future behavior. Provider handling of evidence sent for AI inference is governed by its applicable policies.
7. Optional Cherry AI assessments powered by Groq
When an authorized workspace member asks Cherry to analyze a customer, Churnor sends minimized customer evidence and any optional question they submit to Groq to generate a risk assessment, answer, and suggested actions. Evidence includes recorded activity summaries, subscription and payment signals, categorized support summaries, and project integration delivery status. Names, email addresses, integration credentials, and unrestricted event properties are excluded from the evidence. Do not include personal details or secrets in your question.
Churnor stores the evidence snapshot, assessment, model and prompt version, generation time, and token usage. AI output may be inaccurate and requires human review; the score is not a churn probability. Generating an assessment does not contact customers or perform actions in connected services. Groq processes the supplied evidence under its applicable service terms and policies.
8. Risk scores, recommendations, and saved history
Risk scores reflect the records available to Churnor at the time of a saved check. Missing events, delayed delivery, incorrect customer mapping, or limited activity history can affect the result. A lower score alone does not prove that a customer has recovered or will remain subscribed.
Saved history contains the score and explanation recorded at that time. It is distinct from the customer’s current information. Recommended actions support a business’s own review; they do not authorize contacting a person, changing their account, or making a consequential decision without that review.
Do not use these results as the sole basis for decisions about employment, credit, insurance, education, healthcare, legal rights, or similar matters with significant effects on individuals.
10. Retention, deletion, and backups
Customer profiles, events, and saved risk history are kept while needed to provide your project’s service, subject to available deletion controls, applicable obligations, and any separately agreed retention terms. Churnor does not promise a universal fixed retention period for every type of record.
Deleting a project through the supported settings removes its related records from the active application database according to the database’s deletion relationships. Project deletion is different from canceling a paid subscription or deleting your entire account. Contact us for account-level requests or removal that is not available through the dashboard.
Operational logs, transaction records, and information needed for a legal dispute or security investigation may need to be kept separately. Infrastructure backups may retain a residual copy until their normal replacement or expiry. We do not promise immediate erasure from every backup or a fixed backup-purge schedule.
Deleting Churnor records does not delete copies in your SaaS database, payment provider, delivery queue, or exports. Stop the source integration before deletion if you do not want it to recreate records. Avoid including secrets or unnecessary personal information in a deletion request.
11. Security and international processing
Churnor uses HTTPS endpoints, authenticated access, project-scoped API credentials, and database access controls. API keys are stored as hashes rather than retrievable plaintext. Integration request metadata records key and record identifiers without including the raw secret or customer contact fields.
These safeguards reduce risk but cannot guarantee that a network, account, or service will never be compromised. Your business must secure its own application, use least-necessary permissions, protect credentials, and report suspected misuse promptly. Customer contact information intentionally submitted as a customer profile remains part of that profile.
Hosting, database, authentication, and payment providers may process information in countries other than your own. Do not assume Churnor guarantees a particular country for storage or an executed international-transfer agreement. Ask before submitting data if your organization requires those commitments. Any mandatory legal requirements continue to apply.
13. Privacy choices and requests
You may contact us to ask about information we hold about your Churnor account, request a correction or deletion, or exercise another right available under the law that applies to you. We will assess the request under those requirements rather than promising rights or deadlines that apply identically everywhere.
Send your request to raman8ransubhe@gmail.com. Tell us whether you are a Churnor account holder or a customer of a business using Churnor, and identify the relevant account or project where possible. Do not send passwords or sensitive identity documents in an initial email.
We may need to verify your identity and authority before changing or releasing records. We may refer a request concerning Customer Data to the business that supplied it. Legal retention duties, security concerns, and other applicable exceptions may limit a request; where appropriate we will explain the reason and available next steps.
14. Children and restricted uses
Churnor is a business service for adults and is not directed at children. People under 18 must not create an account. Businesses must not use Churnor to monitor children or submit information they know concerns a child.
If you believe such information or otherwise prohibited data was submitted, contact us so we can investigate and arrange appropriate removal. Do not submit additional sensitive records to prove the issue.
15. Policy changes and contact
We may update this policy when the product, providers, or information-handling practices change. The date at the top identifies the latest revision. Where applicable law requires additional notice of a material change, we will provide it; publication does not replace a required consent.
For privacy questions, suspected data exposure, or requests about this policy, contact Churnor support and privacy contact at raman8ransubhe@gmail.com. This contact is not represented as a designated Data Protection Officer or an EU representative.