Terms of Service
Version 2026-04-26
Last updated 2026-04-26
These Terms of Service govern the access to and use of RetentBase by business customers. They are drafted for B2B use and are intended to define the contractual allocation of responsibilities, risks, and liabilities between Hexonis (Daniel Piringer) and its customers.
RetentBase helps customers collect cancellation signals, analyze churn patterns, and run retention workflows. It does not automatically change customer billing systems or replace legal, tax, accounting, or regulatory advice.
The customer must independently verify legal deadlines, contract status, billing effects, and customer communications before taking action on any output, workflow, or recommendation generated through RetentBase.
Parties, scope, and order of precedence
These Terms apply to the RetentBase website, application, APIs, hosted cancellation flows, and related services supplied by Hexonis (Daniel Piringer).
If a checkout screen, order form, statement of work, or other written agreement contains different commercial terms, that document prevails over these Terms to the extent of the conflict. For data protection matters, the Data Processing Agreement prevails over these Terms to the extent of any conflict.
B2B only
RetentBase is offered exclusively to entrepreneurs, businesses, and persons acting in the exercise of their trade, business, or profession. Consumers are not permitted to use the service for private purposes.
By registering, ordering, or using the service on behalf of an organization, the user represents that they are duly authorized to bind that organization.
We may reject, suspend, or terminate registrations that reasonably appear to involve consumer use, unauthorized access, or a lack of authority to bind the relevant organization.
Service scope and provider role
RetentBase provides software for cancellation capture, custom event ingestion, churn review workflows, issue detection, reporting, and related operational features.
Hexonis (Daniel Piringer) is not the customer's merchant of record, payment processor, subscription manager, or end-customer contracting party. Unless expressly agreed in writing, Hexonis (Daniel Piringer) does not send statutory notices on the customer's behalf, terminate the customer's end-customer contracts, or apply refunds, pauses, discounts, or billing changes in external systems.
Unless expressly agreed in writing, RetentBase is not the customer's system of record for end-customer contracts, payment status, tax treatment, or statutory communication history, and no agency, partnership, fiduciary, or representation relationship is created.
The customer remains solely responsible for commercial decisions, legal notices, customer-facing disclosures, and downstream actions taken in its own billing, support, CRM, or contract systems.
Customer verification and downstream actions
- The customer must independently verify contract status, notice periods, refund entitlement, tax treatment, customer identity, pricing effects, and any other legally or commercially relevant prerequisite before acting on service output.
- The customer remains solely responsible for outbound emails, notices, webhooks, refunds, pauses, discounts, terminations, and other downstream operational decisions or automations based on information from the service.
- Templates, reason labels, offer text, suggested workflows, and analytics views are starting points only and must be reviewed and adapted by the customer for legal, commercial, and brand suitability.
- Analytics, issue indicators, suggested workflows, and other service output are informational and operational only. They are not determinations of legal rights, contract status, billing entitlement, consumer rights, or compliance outcomes.
No regulated, high-risk, or prohibited use
RetentBase must not be used as a system for making legally binding decisions about consumers, employees, credit, insurance, healthcare, housing, eligibility, regulated financial services, or other high-risk determinations unless Hexonis (Daniel Piringer) has expressly agreed to that use in writing.
The service must not be used where failure, delay, or inaccurate output could reasonably be expected to cause death, personal injury, severe property damage, or other safety-critical consequences. RetentBase is not designed for regulated professional advice, emergency use, or safety-critical operations.
Sanctions, export controls, and restricted parties
The customer may not access or use the service in violation of applicable sanctions, export-control, embargo, anti-corruption, anti-money-laundering, or similar trade compliance laws.
The customer represents that it is not located in, organized under the laws of, or ordinarily resident in a jurisdiction subject to comprehensive sanctions, and that it is not a denied, blocked, or restricted party under applicable sanctions or export-control rules.
We may suspend or terminate access where reasonably necessary to comply with sanctions, export-control, law-enforcement, or similar legal obligations.
Accounts, admins, and workspace ownership
Customer admins are responsible for user access, role assignment, invite handling, and the accuracy of workspace settings. The customer is responsible for all acts and omissions by its authorized users, agents, contractors, and affiliates using the service under its workspace.
Credentials, API keys, webhook secrets, and other access mechanisms must be protected with appropriate care. The customer shall notify us without undue delay if it becomes aware of unauthorized access or a suspected compromise.
Customer data and legal responsibility
- The customer is solely responsible for the lawfulness, accuracy, quality, and integrity of the data it submits to the service.
- The customer must have a valid legal basis and any required notices, permissions, or consents for personal data submitted to the service.
- The customer must not upload unlawful content, malware, payment card data, or special categories of personal data unless strictly necessary, legally permitted, and expressly supported by the customer's own compliance framework.
- The customer is responsible for configuring return URLs, webhooks, reason labels, offer messages, and customer-facing workflows in a lawful and non-misleading manner.
- The customer is responsible for determining whether its use of the service complies with consumer, employment, subscription, privacy, competition, and other sector-specific rules applicable to its own business and markets.
Acceptable use restrictions
- No unlawful, fraudulent, defamatory, abusive, or rights-infringing use.
- No attempts to gain unauthorized access, defeat security controls, overload the service, scrape protected areas, or probe vulnerabilities without prior written authorization.
- No use of the service to store or transmit malicious code, spam, or content unrelated to the intended purpose of the platform.
- No resale, sublicensing, or white-label redistribution of the service except where expressly agreed in writing.
- No use that would require us to become subject to sector-specific licensing, filing, escrow, or compliance obligations unless we have expressly agreed to that in writing.
Subscription, fees, taxes, and payment
Prices, plan scope, billing intervals, trial periods, included usage, and other commercial terms are displayed in the applicable checkout flow, pricing page, billing surface, or written order.
Recurring subscriptions renew automatically for successive billing periods unless canceled before the next renewal date through the designated billing workflow or as otherwise agreed in writing.
Fees are exclusive of taxes unless expressly stated otherwise. The customer is responsible for applicable taxes, duties, levies, and similar charges other than taxes on our net income.
Payment processing is handled through Stripe or another designated payment provider. Except to the extent required by mandatory law, fees are non-cancelable and non-refundable once the relevant billing period has started.
Suspension and termination
We may suspend, restrict, or terminate access immediately if reasonably necessary for security, legal compliance, protection against abuse, non-payment, material breach, or a risk to the service, other customers, or third parties.
The customer may stop using the service at any time and may terminate paid subscriptions through the applicable billing workflow subject to the agreed billing period and any non-cancelable committed term.
Upon termination, access rights end. We may retain and delete data in accordance with the Privacy Policy, the Data Processing Agreement, legal retention duties, backup cycles, and legitimate needs to establish, exercise, or defend legal claims.
Third-party services and integrations
Some functionality depends on third-party providers or customer-controlled systems, such as payment services, email delivery, DNS, browsers, networks, hosting, or customer-configured integrations and webhooks.
Subject to mandatory law, Hexonis (Daniel Piringer) is not responsible for outages, API changes, message deliverability issues, data returned by third-party systems, or acts and omissions of systems outside Hexonis (Daniel Piringer)'s reasonable control.
The customer is responsible for configuring, testing, monitoring, and legally approving its own integrations, return URLs, webhooks, outbound messages, and downstream automations.
Customer integration resilience and missed captures
RetentBase must not be implemented as a single point of failure for the customer's application, checkout, cancellation path, billing system, account management, login, or other customer-critical workflow. The customer is responsible for designing fail-open, fallback, retry, queueing, timeout, and error-handling behavior appropriate to its own application and business risk.
Unless expressly agreed in writing, Hexonis (Daniel Piringer) is not responsible for crashes, downtime, blocked user journeys, lost events, missed cancellation captures, incomplete analytics, delayed webhooks, failed API calls, or downstream data gaps caused by the customer's integration design, unavailable third-party systems, network issues, customer-side code, or temporary unavailability of RetentBase.
The customer must not assume that every cancellation attempt, webhook, event, API request, or analytics signal will be captured, delivered, or processed in real time. The customer remains responsible for maintaining its own authoritative records, fallback cancellation channels, reconciliation processes, and customer-support procedures.
Data backup and business continuity
The customer shall maintain backups, exports, fallback processes, independent records, and business continuity procedures appropriate to the significance of the customer's data and workflows.
The customer shall promptly review reports, logs, alerts, and workflow results and take reasonable measures to mitigate avoidable damage.
Intellectual property
Hexonis (Daniel Piringer) and its licensors retain all rights, title, and interest in and to RetentBase, its software, documentation, branding, know-how, and all related intellectual property rights.
The customer retains its rights in customer data. The customer grants us the limited rights necessary to host, process, transmit, analyze, display, and otherwise use customer data solely to provide, secure, support, and improve the service and to comply with law.
Feedback, suggestions, or ideas provided to us may be used without restriction and without any obligation to the customer.
Confidentiality
Each party shall protect the other party's confidential information with reasonable care and shall use it only for the purpose of performing or receiving the service, complying with law, or exercising legal rights under the contract.
Confidential information does not include information that is public without breach, already lawfully known, independently developed, or lawfully received from a third party without confidentiality restriction.
Security and data processing
Hexonis (Daniel Piringer) implements technical and organizational measures appropriate to the service and the risks involved. However, no internet-based service, software environment, or transmission channel can be guaranteed to be completely uninterrupted, error-free, or invulnerable.
Where we process personal data on behalf of the customer, the Data Processing Agreement applies. The customer is responsible for determining whether the service and the documented measures are suitable for its legal and operational requirements.
Availability, support, and changes
We may modify, replace, improve, or discontinue features from time to time for legal, security, operational, or product reasons. Where practicable, we will seek to avoid materially degrading the core contracted functionality without reasonable notice.
Unless explicitly agreed in writing, no specific uptime commitment, service level, response time, feature freeze, or support tier applies.
Maintenance, security patches, abuse-prevention measures, and emergency actions may be deployed without prior notice where reasonably necessary.
Disclaimers
Subject to mandatory law, RetentBase is provided on an "as available" basis. Hexonis (Daniel Piringer) does not warrant uninterrupted availability, complete accuracy, or the achievement of any specific business, retention, recovery, compliance, or revenue outcome.
RetentBase is an operational software tool and does not constitute legal advice, tax advice, accounting advice, regulatory advice, investment advice, or professional consulting. The customer remains solely responsible for the decisions it makes using the service output.
Subject to mandatory law, Hexonis (Daniel Piringer) does not warrant that templates, reason taxonomies, workflow suggestions, customer-facing text, or integrations satisfy customer-specific legal or regulatory requirements or remain continuously available through third-party providers.
Customer indemnification
The customer shall indemnify and hold harmless Hexonis from third-party claims, losses, damages, fines, costs, and expenses arising out of or related to customer data, customer instructions, the customer's unlawful or contract-breaching use of the service, or the customer's relationship with its own end users, except to the extent caused by Hexonis's own breach of contract or applicable law.
The customer shall reasonably cooperate in the defense of indemnified matters. Hexonis may control the defense and settlement of an indemnified claim, provided it acts reasonably and does not impose non-monetary obligations on the customer without the customer's consent.
Limitation of liability
Nothing in these Terms excludes or limits liability that cannot be excluded under mandatory law, including liability for intent, gross negligence, fraud, injury to life, body, or health, the assumption of an express guarantee, or liability under applicable product liability law.
In cases of slight negligence, Hexonis is liable only for the breach of essential contractual obligations whose fulfillment is necessary for the proper performance of the contract and on whose observance the customer may regularly rely. In such cases, liability is limited to the foreseeable damage typical for this type of contract.
Subject to mandatory law, Hexonis is not liable for indirect or consequential damages, lost profits, lost savings, loss of goodwill, loss of opportunity, lost or missed data capture, missed cancellation signals, delayed or failed webhook delivery, customer application crashes, or damages resulting from the customer's own business decisions, downstream billing actions, end-customer disputes, third-party service failures, telecommunications or internet failures, force majeure events, malicious third-party activity despite appropriate safeguards, customer misconfiguration, integration design, missing fallback processes, or avoidable data loss where the loss could have been prevented by appropriate customer backup and recovery measures.
Subject to the unlimited-liability carve-outs above, Hexonis's aggregate liability arising out of or in connection with the contract, whether in contract, tort, or otherwise, shall not exceed the fees actually paid by the customer for the affected workspace subscription during the twelve months preceding the first event giving rise to the claim.
Force majeure
Neither party is liable for delays or failures caused by events beyond its reasonable control, including widespread internet or infrastructure outages, labor disputes, governmental action, war, terrorism, civil unrest, epidemics, natural disasters, or broad attacks on infrastructure, except for payment obligations that became due before the event.
Governing law and venue
These Terms and all non-contractual disputes arising out of or in connection with them are governed by the laws of Germany, excluding its conflict-of-laws rules and excluding the United Nations Convention on Contracts for the International Sale of Goods (CISG).
If the customer is a merchant, a legal person under public law, or a special fund under public law, the exclusive place of jurisdiction for all disputes arising out of or in connection with the contract shall be Munich, Germany, where legally permissible.
Updates to these Terms
We may update these Terms for legal, regulatory, security, commercial, or product reasons. Updated versions apply to new contracts upon publication and to existing customers when accepted in the product, agreed in writing, or otherwise validly incorporated under applicable law.