On this page
1. About these terms
These Terms and Conditions (“Terms”) govern access to the Churnor website, dashboard, APIs, imports, and related customer-monitoring services (“Service”). “Churnor,” “we,” “us,” and “our” refer to the operator of the Service. “You” means the person or business that creates an account or uses the Service. If you act for a business, you confirm that you have authority to bind it.
By creating an account or using the Service, you agree to these Terms. If you do not agree, do not create an account or connect data. The Privacy Policy describes information handling; it does not replace your own privacy notices or responsibilities toward your customers.
A separate agreement signed or expressly accepted by both parties may supplement these Terms. Where that agreement expressly changes a provision, the agreed change applies to that relationship. Feature descriptions and examples do not create a custom service-level agreement.
2. Eligibility and EU availability
The Service is intended for lawful business use by adults aged 18 or older. You must provide accurate account information and have authority over the application and data you connect.
Churnor is not offered to individuals located in the European Union or businesses established in EU member states. Do not create an account or purchase a plan for those users or businesses. This condition concerns location and establishment, not a person’s nationality.
Businesses outside the EU must not use Churnor to monitor people located in the EU or send their personal information to the Service. If you serve customers in the EU, you must exclude their records before connecting a source, sending an API request, or uploading a file. If you cannot reliably exclude those records, do not connect that source.
A public page being reachable, a checkout being available, or an API accepting a request does not override these restrictions. Notify us if your eligibility changes or you discover restricted data in a project. We may stop an affected integration, suspend access, or require deletion while resolving the issue.
This restriction does not exempt either party from applicable law or waive a person’s mandatory rights. Other countries may have their own requirements. You must assess whether the Service is appropriate for your business and contact us before use if you require additional privacy, hosting, or regulatory commitments.
3. What Churnor provides
Churnor receives customer profiles, product activity, and supported billing events and uses available records to show risk scores, explanations, suggested actions, and saved history. Scores range from 0 to 100; higher scores indicate higher risk under Churnor’s current rules. Results are decision support, not a guarantee that a customer will churn or stay.
Your app sends updates when customers use it. Churnor does not scan your database. APIs, CSV imports, and supported provider connections deliver the data you choose to submit. New records can update scores; scores may also be refreshed while you use the dashboard. The standard API setup does not require a cron job.
Features and capacity depend on your selected plan and current configuration. We may improve or change features and processing rules. Saved explanations describe the check recorded at that time; they are not a reconstruction of records that were never saved.
4. Accounts, workspaces, and security
You are responsible for activity performed through your account and the permissions you grant. Keep your sign-in credentials and API keys secure, use authorized access only, and notify us promptly of suspected compromise. Remove access that is no longer needed.
A workspace may contain multiple project environments. Select the intended environment before changing integrations, uploading records, or deleting data. Team permissions govern who can access the workspace and perform administrative actions. You are responsible for confirming that each person has a legitimate business need to access Customer Data.
API keys are project-scoped secrets. Save them only in trusted server settings; do not place them in browser code, public repositories, screenshots, or public environment variables. A newly created key is shown in full once. Replacing or revoking a key requires updating applications that use it and can interrupt delivery.
We may request information needed to verify account authority, investigate suspicious activity, or resolve conflicting ownership claims. We do not promise to restore access when ownership cannot be established safely.
5. API delivery, retries, and connection checks
Send customer updates after signup or profile changes have been saved, and activity after a successful product action. Use the identifiers from your own saved records. Each distinct action needs its own event ID. Keep its original timestamp and payload unchanged when retrying; reusing an event ID for different data may be rejected.
The copyable Node/TypeScript helper checks HTTP results and retries supported temporary failures within its documented limits. A successful storage response can still report score_saved: false. Retrying the same saved event lets Churnor try to finish the score update. Do not assume every accepted request has already produced a score.
A connection is verified only after real activity arrives through the current authorized key and its score is saved. Key creation, customer-only requests, and dashboard-generated tests do not establish full verification. Verification confirms received data at that time; it is not a guarantee that every future source action will be delivered.
You are responsible for retaining source records, monitoring failures, and arranging replay of missed updates. A queue in your application can provide automatic redelivery, but it has its own retention period, usage limits, and provider conditions. A failed publish or expired queue message may require replay from your source. Do not let a background send end before your hosting platform finishes it.
6. Customer Data and privacy responsibilities
You retain your rights in the records you submit (“Customer Data”). You grant Churnor permission to host, process, display, and transmit that data as reasonably needed to provide and secure the Service, follow your instructions, and satisfy applicable legal duties.
You confirm that you have the authority and permissions needed to submit the data and use the results. You must provide required notices, obtain consent where necessary, honor privacy requests, and avoid submitting records whose processing would violate a law, contract, or another person’s rights.
Submit only information needed for customer monitoring. Do not include passwords, secret keys, payment-card numbers, government identification documents, medical or biometric records, children’s information, or prohibited EU-related records. Review custom properties, CSV columns, and provider permissions before enabling delivery.
Churnor does not sell Customer Data or use submitted customer activity to train public general-purpose AI models. Operational processing and provider disclosures are described in the Privacy Policy. Contact us before submitting data if your organization requires a separate data-processing agreement, regional storage, or another specific contractual safeguard.
7. Limits of scores and recommended actions
Scores and recommendations depend on the completeness, accuracy, timing, and mapping of the information received. A missing event, delayed webhook, changed customer ID, or limited activity history may affect the result. A risk score is not a probability or a professionally certified conclusion.
Past scores show what Churnor recorded at the time. A chart does not imply that a check occurred on a day without saved data. The latest saved score may not include activity received later. A lower score by itself is not evidence that a customer has recovered.
Review the evidence and your own business context before taking action. You decide whether and how to contact a customer. Use of Churnor does not create permission to send marketing messages or override communication preferences.
Do not use the Service as the sole basis for employment, credit, insurance, education, healthcare, legal, or other decisions with significant consequences for individuals. Churnor does not provide legal, financial, medical, or other regulated professional advice.
8. Plans, billing, and usage limits
The price, currency, billing interval, included capacity, and any tax information shown at checkout govern the plan you select. Review those details before purchasing. Churnor plan payments are handled through Dodo Payments; payment-provider terms also apply where relevant. Connecting your Stripe account as a data source is a separate feature.
Recurring subscriptions renew under the terms shown at checkout until canceled through the available payment-provider controls or an agreed support process. You authorize the recurring charges disclosed at purchase and must keep payment information current. A free account or a project deletion does not by itself cancel an existing subscription.
Customer, event, and environment limits apply at the workspace level as described by your plan. Multiple environments may share the same allowance. Rate limits and database limits may reject requests when an allowance is reached; do not assume excess usage will be accepted or automatically billed.
Plan changes, failed payments, or provider delays can affect access and ingestion capacity. We may restrict paid features when payment is overdue or the applicable plan no longer permits them. We do not guarantee provider-specific retry windows, payment outcomes, or collection schedules.
Any future price change applies only as disclosed before the affected purchase or renewal, subject to mandatory notice requirements. Contact us promptly if you believe a charge or plan assignment is incorrect.
9. Cancellation and refund requests
To cancel, use the cancellation controls provided by the payment provider where available, or contact raman8ransubhe@gmail.com for help before the next renewal. The cancellation’s effective date and any remaining access depend on the subscription’s confirmed status and checkout terms.
Refund eligibility is governed by the terms disclosed at purchase and any mandatory rights under applicable law. These Terms do not promise an automatic refund, a trial period, or a particular refund-processing date. Ask support or the payment provider about the applicable purchase if those details are unclear.
Cancellation, project deletion, and account closure are separate actions. Export or keep the source records you need before requesting deletion. Do not assume that canceling removes data or that deleting a project stops billing.
10. Acceptable use
You must not use the Service to:
- Break applicable law, infringe another person’s rights, or submit data without authority.
- Bypass account permissions, project isolation, usage limits, payment requirements, or security controls.
- Access another customer’s records, probe systems without permission, distribute malware, or disrupt service availability.
- Submit fabricated activity to misrepresent a real customer, impersonate another business, or use results for unlawful discrimination or harassment.
- Collect prohibited sensitive information, monitor children, or evade the EU availability restrictions.
- Resell the Service or represent yourself as Churnor without written permission.
Responsible reporting of a suspected vulnerability is welcome. Contact us privately, avoid accessing other users’ information, and do not perform disruptive testing on production without written authorization.
11. Third-party services and your integrations
The Service relies on hosting, database, authentication, and payment providers. Your application and connected providers are separate systems with their own terms, policies, service limits, and outages. You are responsible for the accounts and permissions you use to connect them.
We cannot guarantee that a provider will deliver every webhook, retain every queue message, or maintain an unchanged API. You should monitor source and destination records and retain original data for reconciliation. Never send your SaaS database service key to Churnor for the standard API integration.
Changes in an integration or provider may require you to update code, credentials, or settings. Sample code is a starting point for your own server implementation; review it for your application’s environment, data handling, and failure recovery.
12. Service ownership and feedback
Churnor and its licensors retain rights in the Service’s software, design, branding, documentation, and scoring implementation. Subject to these Terms and your plan, you may use the Service for your business’s internal customer-monitoring needs. This permission ends when access is terminated.
You retain ownership of Customer Data and may use the results generated for your project for lawful business purposes. You must not copy or redistribute Churnor’s protected software or branding except where authorized or permitted by law.
If you voluntarily send feedback, you allow us to use it to improve the Service without an obligation to compensate you. Do not include another person’s confidential information or Customer Data in public feedback.
13. Availability, changes, and suspension
We work to keep the Service useful and available, but do not promise uninterrupted access, instant delivery, a fixed processing time, or a particular uptime percentage unless separately agreed in writing. Maintenance, infrastructure incidents, configuration problems, and third-party outages can interrupt access or processing.
We may limit or suspend access where reasonably needed to address abuse, a security incident, unauthorized data, non-payment, legal requirements, or a material breach of these Terms. Where practical and lawful, we will explain the reason and provide a way to address it. Immediate action may be necessary to protect people or systems.
We may change or discontinue features. We will provide notice where required by law or a separate agreement. Continue to keep your own source records; Churnor should not be the only copy of information your business needs.
14. Ending access and handling remaining data
You may stop using Churnor and request account closure. You remain responsible for canceling recurring billing and disabling your source integrations. We may end access for a serious or unresolved breach or where necessary to comply with law.
When access ends, stop using the affected APIs and remove or revoke relevant credentials. Data removal and any remaining retention are governed by the Privacy Policy, applicable obligations, and separately agreed terms. We do not guarantee indefinite dashboard access after closure or immediate erasure from every infrastructure backup.
Provisions that reasonably need to survive account closure continue to apply, including ownership, unpaid charges, confidentiality and data responsibilities, limits of liability, and dispute provisions. Ending access does not cancel rights or obligations that already arose.
15. Warranties and limits of liability
To the extent permitted by applicable law, the Service is provided on an “as available” and “as is” basis. We do not guarantee that it will identify every at-risk customer, prevent churn, increase revenue, or be free from errors. No information in a sample, support response, or dashboard creates a guarantee unless expressly agreed in writing.
To the extent permitted by law, neither party is liable under these Terms for indirect or consequential losses, including lost profits, lost opportunities, or business interruption. Churnor’s total liability arising from the Service is limited to the fees you paid for the Service in the 12 months before the event giving rise to the claim, or US$100 for use without paid fees.
These limits do not exclude liability that cannot lawfully be excluded or limited, including applicable mandatory rights or liability for fraud or deliberate misconduct. They do not reduce a payment obligation you already incurred. A separately agreed contract may provide different limits.
You are responsible for claims arising from data you submit without authority or your unlawful misuse of the Service. Any request that you cover a third-party claim must remain subject to applicable law and a fair opportunity to understand and respond to the claim; these Terms do not grant us an unrestricted right to settle a claim at your expense.
16. Disputes and applicable law
If a dispute arises, first contact raman8ransubhe@gmail.com with a description of the issue and the resolution you seek. Both parties should make a reasonable effort to resolve it through direct communication before starting proceedings, unless urgent relief or a legal deadline requires immediate action.
Mandatory laws and rights that apply to the parties and the transaction continue to apply. Disputes may be brought before a court that has jurisdiction under applicable law or a separately agreed contract. These Terms do not impose Delaware law, compulsory arbitration, or a class-action waiver.
The EU availability restriction does not determine by itself which law or court has jurisdiction. A governing-law or forum commitment must be expressly agreed rather than inferred from the website’s hosting location.
17. Changes, general provisions, and contact
We may revise these Terms as the Service develops. The date at the top identifies the current revision. We will provide additional notice when required for a material change. Changes do not retroactively eliminate accrued rights or replace a consent or agreement required by law.
If a provision is unenforceable, the remaining provisions continue to apply to the extent permitted by law. A failure to enforce a provision once is not a permanent waiver. Neither party is responsible for a delay caused by circumstances beyond its reasonable control, subject to applicable law and obligations already incurred.
You must not transfer an account or these Terms in a way that bypasses eligibility or security requirements. A transfer of Churnor’s business may include its service obligations and relevant records, subject to applicable protections and notice requirements.
For account, billing, eligibility, or legal questions, contact Churnor support at raman8ransubhe@gmail.com. Formal notices should identify the relevant account, issue, and sender’s authority. Do not include passwords or API secrets.