Terms of Service

Effective Date: June 1, 2026
Version dated June 1, 2026

0. Preamble and Document Structure

These Terms of Service ("ToS") govern the use of the Revenipe platform services provided by localoyal GmbH ("Provider", "we", "our", "us", or "Revenipe"). By accessing or using the Service, creating an account, executing an order form, or otherwise agreeing to these ToS, the Customer agrees to be bound by these ToS.

The Service is offered exclusively to entrepreneurs and businesses within the meaning of Section 15 of the German Civil Code (BGB). Consumers are not permitted to use the Service.

• Provider: localoyal GmbH, Mercatorstrasse 62, 49080 Osnabrück, Germany, registered with the Local Court of Osnabrück under HRB 218235
• Contact: hello@revenipe.com
• Support Contact: support@revenipe.com
• Sub-processors: see the DPA and the current sub-processor list made available by Provider
• Technical Parameters: plans, limits, pricing, retention periods and technical specifications are set out on www.revenipe.com, in the ordering process, or in the documentation

These ToS are supplemented by the API Terms, Billing Terms, Data Processing Agreement (DPA), and any order form or plan description agreed with the Customer. In case of conflict, the order of precedence in Section 22 applies.

1. Definitions

1.1 "Service" means the cloud-based software-as-a-service platform operated by Provider, including the dashboard, APIs, SDKs, webhooks, automation, documentation and related functionality for configuring and managing monetization logics, subscription products, one-time purchases, trials, entitlements, usage tracking, credits, customer access management, and integrations with Customer-controlled accounts at Third-Party Services.

1.2 "Customer" means the legal entity or natural person acting as an entrepreneur that uses the Service, including its authorized representatives.

1.3 "Connected Application" means the Customer application, such as a mobile app or web app, that is connected to the Service.

1.4 "End User" means a user of the Connected Application or of the Customer's products or services.

1.5 "Authorized User" means an employee, contractor, representative, or other person authorized by Customer to access the Service on Customer's behalf.

1.6 "Third-Party Services" means services provided by third parties, including payment service providers and app-store or subscription platforms such as Stripe, RevenueCat if and when supported by the Service, Apple App Store, Google Play, hosting providers, analytics providers, e-mail providers, or other external services to which the Service connects or on which the Service depends.

1.7 "Stripe Configuration Data" means configuration data, metadata, product data, price data, entitlement data, subscription-related metadata, identifiers, statuses, timestamps and similar technical data that Customer authorizes Provider to create, read, update, map, synchronize or display in Customer's connected Stripe account or other Third-Party Service account.

1.8 "Customer Data" means data submitted to, generated by, or processed through the Service by or on behalf of Customer, including Stripe Configuration Data, account data, End User identifiers, customer identifiers, product identifiers, subscription identifiers, entitlement states, usage keys, consumption events, usage events, purchase or checkout-session metadata, trial status, plan status, webhook payload metadata, technical metadata, billing-related metadata, logs and support communications.

1.9 "Usage Limits" means contractual, plan-specific or technical limits, including limits on API calls, webhook events, connected apps, accounts, users, subscriptions, storage, retention periods or other usage metrics.

1.10 "Entitlements" means access rights, usage rights, feature flags, renewable values, consumable balances, metered usage rights or similar rights configured by Customer through the Service and associated with End Users, products, subscriptions, purchases, plans, trials or manual grants.

1.11 "Usage Keys" means identifiers configured by Customer that allow multiple entitlement sources, including subscriptions, one-time purchases, credit packs, manual grants or other allocations, to contribute to a single balance or usage value made available through the Service or SDK.

2. Subject Matter and Scope of the Service

2.1 Provider makes the Service available to Customer as a developer-focused monetization configuration backend and entitlement configuration platform for connecting the Connected Application and Customer-controlled Third-Party Service accounts, including Stripe and other supported providers, configuring monetization logic, subscription products, one-time purchases, trials, plan changes, customer management, entitlements, usage tracking, credits, webhook processing and access-control rules, and processing related technical metadata.

2.2 Provider's role is limited to providing software, automation and technical integration functionality. Customer remains responsible for its Connected Application, its products and services, its End Users, its Third-Party Service accounts, and the legal, commercial, tax and technical correctness of all configurations. Customer retains ownership and control over its Connected Application, End User relationships, Customer Data, Third-Party Service accounts, products, pricing, business logic and customer-facing monetization model. Provider does not acquire ownership of Customer Data or Customer's business logic.

2.3 The Service is provided as SaaS. No software is supplied for local installation except where SDKs, sample code or libraries are made available for integration purposes.

2.4 Provider may improve, change, discontinue or replace non-material features, user interfaces, APIs, SDKs and documentation, provided that Provider reasonably considers Customer's legitimate interests. Material changes will be handled in accordance with these ToS and any applicable deprecation policy.

2.5 Documentation, plan descriptions and technical parameters may be updated from time to time. Customer is responsible for reviewing the documentation and implementing the Service accordingly.

2.6 Details on support, availability, maintenance, incidents, service credits, backups and third-party service dependencies are set out in Section 3.

3. Support, Availability, Maintenance and Incidents

3.1 Commercially Reasonable Efforts. Provider provides the Service on a commercially reasonable efforts basis. Unless expressly agreed in a separate service level agreement, order form, plan description or written agreement, Provider does not guarantee any minimum availability, uptime, response time, recovery time, resolution time, real-time synchronization or error-free operation.

3.2 Scheduled Maintenance. Provider may perform scheduled maintenance, updates, upgrades, security patches and infrastructure changes. Provider will use commercially reasonable efforts to announce material planned maintenance in advance where practicable. Scheduled maintenance may temporarily affect the availability or performance of the Service.

3.3 Emergency Maintenance and Security Measures. Provider may perform emergency maintenance or take immediate technical or organizational measures without prior notice where reasonably necessary to protect the security, integrity, availability or compliance of the Service, Customer Data, Provider's systems or other customers. Such measures may include temporary suspension, traffic limitation, API key rotation, blocking of requests, disabling of integrations or rollback of deployments.

3.4 Support Channels and Support Hours. Support is provided through the support channels specified on Provider's website, in the dashboard, in the documentation, in the applicable plan description or in a separate support agreement. Support hours, target response times, support priorities and escalation procedures apply only if expressly stated in the applicable plan description, order form, service level agreement or support agreement.

3.5 Incident Communication. Provider may communicate material service incidents, maintenance notices or security-relevant information by e-mail, dashboard notice, status page, documentation update or other appropriate means. Incident updates are provided on a commercially reasonable basis and do not constitute a guarantee of resolution within a specific period.

3.6 Backups and Recovery. Provider may maintain backups and recovery procedures appropriate for the Service. Unless expressly agreed otherwise in a separate service level agreement, order form or plan description, Provider does not guarantee any specific recovery time objective, recovery point objective, backup frequency, retention period or ability to restore particular Customer Data. Customer remains responsible for exporting, retaining and backing up Customer Data where export functionality is available and for maintaining its own business continuity measures.

3.7 Third-Party Service Dependencies. The Service may depend on Third-Party Services, including Stripe, app stores, hosting providers, e-mail providers, analytics providers or other infrastructure and integration providers. Provider is not responsible for outages, API changes, degraded performance, account restrictions, rate limits, security measures, data unavailability or other failures of Third-Party Services. Such events do not constitute unavailability or defective performance of the Service unless expressly agreed otherwise.

3.8 No Service Credits Unless Expressly Agreed. Service credits, refunds, fee reductions or other remedies for unavailability, incidents, delays or performance issues are not granted unless expressly provided in an applicable service level agreement, order form, plan description or mandatory law.

4. No Payment Services, No Financial Services, No Merchant-of-Record Role

4.1 Provider does not provide payment services, financial services, banking services, e-money services, acquiring services, payment initiation services, account information services, payment facilitation, money transmission or similar regulated services.

4.2 Provider does not hold, receive, transfer, settle, acquire, process or transmit funds of Customer or End Users. Provider does not provide payment accounts and does not control Customer's or End Users' funds.

4.3 Provider does not initiate, authorize, execute, accept, reject, refund, settle or reverse payments. Payment processing, payouts, refunds, chargebacks, disputes, KYC/AML checks, tax calculations, receipts and payment-related compliance are handled exclusively by Customer and/or the applicable Third-Party Services.

4.4 Provider is not Customer's merchant of record, payment service provider, payment facilitator, agent, fiduciary, trustee, financial institution, tax advisor or legal advisor. Customer is solely responsible for its contractual relationship with its End Users and Third-Party Services.

4.5 Any payment-related information displayed in the Service is provided solely as technical metadata received from, or synchronized with, Third-Party Services. Provider does not verify the accuracy, legality or completeness of such information except to the extent expressly stated in the documentation.

4.6 Customer remains, where applicable, the merchant, seller, contracting party and account holder in relation to its End Users and Third-Party Services, including Stripe. Stripe or the applicable Third-Party Service remains solely responsible for regulated payment services, payment processing, acquiring, settlement, payouts, refunds, chargebacks, KYC/AML checks and related payment-service functions.

4.7 For the avoidance of doubt, technical functionality that creates, redirects to, opens or manages checkout sessions, purchase flows, billing-provider flows or subscription-management flows through Third-Party Services does not constitute payment initiation, payment execution, acquiring, settlement, money transmission or payment processing by Provider. Such flows are performed by the applicable Third-Party Service and/or Customer under Customer's account and responsibility.

5. Stripe and Third-Party Service Configuration

5.1 Customer may authorize Provider to access Customer's Third-Party Service accounts, including Stripe, through OAuth, API keys, restricted keys, webhooks or other access methods supported by the relevant Third-Party Service.

5.2 Customer authorizes Provider to create, read, update, map, synchronize and display technical configuration data in Customer's connected accounts only to the extent required to provide the Service and as configured by Customer.

5.3 Customer remains solely responsible for reviewing, testing and approving all products, plans, prices, tax settings, billing settings, trial periods, subscription terms, entitlements, refund settings, checkout settings, customer communications, invoice settings and any other configuration created, proposed or synchronized through the Service.

5.4 Customer is solely responsible for compliance with the terms of Third-Party Services, applicable app-store rules, consumer-facing disclosures, tax obligations, accounting obligations, refund and cancellation rules, chargeback handling, dispute handling and any sector-specific legal requirements applicable to Customer's business.

5.5 Provider is not responsible for Third-Party Service outages, API changes, account restrictions, app-store decisions, payment failures, payout delays, fraud decisions, risk decisions, compliance reviews, fees, tax calculations or disputes handled by Third-Party Services.

5.6 Customer is solely responsible for setting up, maintaining, securing and lawfully operating its Stripe account and any other Third-Party Service account, including the accuracy of account information, permissions, API access, business information, tax information, payout settings, compliance information and any required approvals by the relevant Third-Party Service.

6. Monetization Configuration, Entitlements, Usage Keys and Access Rules

6.1 Monetization Configuration. Customer may use the Service to configure and manage subscription products, one-time purchases, free trials, plan upgrades and downgrades, customer management, customer access rules, entitlements, credits, usage tracking, webhook processing and related monetization logic, as supported by the applicable plan, documentation and Third-Party Services.

6.2 Entitlements and Usage Keys. The Service may support flag entitlements, value entitlements, limited value or consumable entitlements, metered entitlements, Usage Keys, and similar entitlement models. Usage Keys may allow multiple entitlement sources, including subscriptions, one-time purchases, credit packs and manual grants, to contribute to a single balance or usage value.

6.3 Customer Responsibility. Customer is solely responsible for configuring and reviewing all products, plans, subscriptions, one-time purchases, trials, entitlements, Usage Keys, access rules, usage-tracking rules, metered-billing rules, all other configurations and customer-access logic before using them in production.

6.4 No Guarantee of Commercial Outcome. Provider does not guarantee that Customer's monetization setup will achieve any specific revenue, conversion, tax, accounting, billing, legal, regulatory or customer-access outcome.

6.5 Usage and Consumption Logic. Customer is responsible for determining which events, API calls, usage records, consumption events or metered quantities are submitted to, generated through or relied upon by the Service. Customer must verify that usage-tracking, credit-consumption and metered-billing configurations are accurate before using them in production. Provider does not guarantee that usage data is suitable for Customer's billing, accounting, tax, regulatory or customer-facing purposes unless expressly agreed otherwise.

6.6 Customer must design its Connected Application to handle delayed updates, duplicate events, retries, failed consumption attempts, insufficient-balance responses, concurrent consumption attempts and other consistency issues related to credits, Usage Keys and entitlements. Unless expressly agreed otherwise, entitlement states, and usage values are provided on a commercially reasonable, best-efforts basis and may depend on Customer configuration and Third-Party Service events.

6.7 End User Access. Customer remains solely responsible for its relationship with End Users, for granting or denying access to Customer's products or services, and for handling End User complaints, refunds, cancellations, account issues and support requests, even where the Service provides technical entitlement or access-control information.

6.8 Production Use and Testing. Customer must test and verify that its product, entitlement, access-control, credit-consumption, usage-tracking, metered-billing and all other configurations and are accurate and suitable for Customer's intended use before using them with real End Users or in production. Provider is not responsible for commercial, legal, tax or customer-facing consequences resulting from Customer's configuration of such rules or from Customer's failure to test them appropriately.

7. Registration, Accounts and Authorized Users

7.1 Use of the Service requires a Revenipe account. Customer must provide accurate and current registration, billing and contact information.

7.2 Customer is responsible for all activity under its account and for the acts and omissions of its Authorized Users. Customer must ensure that Authorized Users comply with the Agreement.

7.3 Credentials, API keys, tokens and secrets must be kept confidential and protected against unauthorized access. Customer must notify Provider without undue delay of suspected misuse, compromise or security incidents.

7.4 Provider may require reasonable security measures, including multi-factor authentication, IP restrictions, rotation of keys, restricted API permissions, or suspension of compromised credentials.

8. Customer Obligations and Acceptable Use

8.1 Customer may use the Service only in accordance with the Agreement, the documentation and applicable law. Customer is responsible for Customer Data, instructions, account configurations and use of the Service by its Authorized Users.

8.2 Customer shall not:

• reverse engineer, decompile, disassemble or attempt to derive the source code, structure, algorithms or underlying ideas of the Service, except where mandatory law permits this;
• circumvent authentication, authorization, security controls, rate limits or Usage Limits;
• perform penetration tests, load tests, scraping or vulnerability scans without Provider's prior written consent;
• use the Service to develop, support or operate a competing product or service;
• make the Service available to third parties as a service bureau, reseller or managed service unless expressly agreed;
• process unlawful content, fraud, spam, malware, adult content, gambling content or other content prohibited by the documentation or applicable Third-Party Service rules;
• interfere with the integrity, availability or security of the Service or Third-Party Services;
• use the Service in violation of export control, sanctions, anti-corruption, anti-money-laundering or data-protection laws.

8.3 Customer shall obtain all rights, permissions, consents and authorizations required for Customer, Authorized Users and End Users to use the Service and for Provider to process Customer Data as described in the Agreement.

8.4 Customer shall promptly provide technical information reasonably required by Provider to provide support, investigate incidents or prevent misuse.

9. Prices, Plans and Usage-Based Billing

9.1 The Service may be offered under free and paid plans. Plan scope, Usage Limits and prices are set out in the order form, pricing page, plan description or ordering process.

9.2 Usage may be measured by system-based metrics, such as connected apps, API calls, webhooks, active users, subscribers, customers, products, prices, subscriptions, one-off payments or other metrics specified in the plan description.

9.3 If a Usage Limit is exceeded, the plan description may provide for warnings, restrictions, overage fees, automatic upgrades, or other consequences. Provider will make commercially reasonable efforts to provide transparent usage information, but Customer is responsible for monitoring its own usage.

9.4 Customer must not manipulate usage metrics, identifiers, events or account structures to avoid fees or limits.

10. Payments, Taxes and Invoicing

10.1 Customer shall pay all fees due under the applicable plan, order form or pricing page. Payments are due in advance for subscriptions and, where applicable, in arrears for usage-based components.

10.2 Payments are collected through a third-party payment provider. Provider does not store full payment card or bank account data.

10.3 Fees are non-refundable except where mandatory law requires otherwise or Provider expressly agrees otherwise.

10.4 Customer is responsible for providing accurate billing and tax information. Unless otherwise stated, prices include statutory VAT where applicable. Customer is responsible for taxes, duties and levies resulting from Customer's use of the Service, except for taxes on Provider's income.

10.5 In case of payment default, Provider may, after reasonable notice, restrict features, suspend access, downgrade the account, terminate the Agreement for cause and claim outstanding amounts, statutory interest and collection costs.

11. API, SDKs, Webhooks and Documentation

11.1 API, SDK and webhook use is governed by the API Terms and documentation. Provider may set rate limits, quotas and technical restrictions.

11.2 Webhook delivery, event synchronization and third-party API calls are provided on a commercially reasonable, best-efforts basis. Customer must design its systems to handle delays, duplicate events, missed events, retries, ordering differences and idempotency.

11.3 Customer must not expose secrets or private API keys in client-side applications and must follow secure key management practices.

11.4 SDK functions that allow Customer to start purchases, retrieve products, check entitlements, consume credits, track usage or manage subscriptions are technical integration functions only. Customer remains responsible for the customer-facing purchase flow, product presentation, pricing, tax information, refund and cancellation information, and compliance with Third-Party Service terms and applicable law.

12. Data Protection

12.1 The parties acknowledge that, for Customer Data processed on behalf of Customer, Customer is generally the controller and Provider is generally the processor within the meaning of the GDPR. Details are governed by the DPA.

12.2 Provider may act as an independent controller for its own account administration, billing, security, website, marketing and support processing. Details are provided in the Privacy Policy.

12.3 Customer is responsible for legal bases, transparency notices, consents, data minimization, retention instructions and the lawfulness of all Customer Data and instructions.

13. Security

13.1 Provider implements appropriate technical and organizational measures designed to protect the Service and Customer Data, as further described in the DPA and documentation.

13.2 Customer is responsible for secure configuration of its Connected Application, endpoints, credentials, Third-Party Service accounts, user permissions and access controls.

13.3 Provider may take emergency measures, including suspension of access, key rotation or blocking of traffic, where reasonably necessary to protect the Service, Customer, other customers, End Users or Third-Party Services.

14. Confidentiality

14.1 Each party may receive non-public business, technical, security, financial or other confidential information of the other party. Confidential Information includes non-public information about the Service, pricing outside public pricing pages, security details, Customer Data and connected account data.

14.2 The receiving party may use Confidential Information only to perform the Agreement and must protect it using at least reasonable care.

14.3 Confidentiality obligations do not apply to information that is public, lawfully known without confidentiality obligation, lawfully received from a third party, independently developed without use of Confidential Information, or required to be disclosed by law or governmental order, provided that prior notice is given where legally permitted.

15. Intellectual Property and Feedback

15.1 Provider and its licensors retain all rights, title and interest in the Service, software, APIs, SDKs, documentation, trademarks, know-how and related intellectual property.

15.2 Customer receives only the limited rights expressly granted in the Agreement. No rights are granted by implication.

15.3 Customer grants Provider the limited rights necessary to process Customer Data, access connected accounts and perform the Service in accordance with the Agreement and Customer's configuration.

15.4 Provider may use feedback, suggestions and ideas provided by Customer without restriction or compensation, provided that Provider does not disclose Customer's Confidential Information.

15.5 Provider may use Customer's name or logo for marketing only with Customer's prior permission.

16. Warranty

16.1 The Service is provided as standard SaaS. Statutory warranty rights apply subject to the limitations in this Agreement.

16.2 Provider does not warrant that the Service will meet all of Customer's requirements, operate without interruption or errors, be compatible with all Customer systems or all changes of Third-Party Services, or achieve a specific commercial, tax, legal or payment outcome.

16.3 Customer must notify Provider of defects without undue delay and reasonably cooperate in error analysis and remediation.

17. Liability

17.1 Provider is liable without limitation for intent, gross negligence, injury to life, body or health, and under mandatory statutory liability, including product liability where applicable.

17.2 In case of slightly negligent breach of material contractual obligations, Provider's liability is limited to damages typical for the contract and reasonably foreseeable at the time of conclusion of the Agreement.

17.3 To the extent permitted by law, Provider's aggregate liability for all claims arising from or in connection with the Agreement is limited to the fees paid by Customer to Provider under the relevant paid plan during the twelve months preceding the event giving rise to liability. For free plans, Provider's aggregate liability is limited to EUR 100, except where Section 17.1 applies.

17.4 To the extent permitted by law and except where Section 17.1 applies, Provider is not liable for indirect damages, consequential damages, lost profits, lost revenue, loss of goodwill, business interruption, failed payments, payment disputes, payout delays, third-party fees, app-store decisions, tax consequences, or loss of data where Customer failed to maintain appropriate backups or export options.

17.5 Provider is not liable for Third-Party Services, their outages, API changes, compliance decisions, payment decisions, fraud decisions, account restrictions, fees, disputes, chargebacks, refunds or tax calculations.

17.6 The exclusions and limitations in this Section apply regardless of legal basis and also in favor of Provider's directors, employees, agents, subcontractors and affiliates.

18. Indemnification

18.1 Customer shall indemnify and hold Provider harmless from third-party claims, damages, losses and reasonable legal-defense costs arising from: (a) Customer Data; (b) Customer's Connected Application, products, prices, tax settings, End User terms or disclosures; (c) Customer's use of Third-Party Services; (d) Customer's violation of applicable law, third-party rights or Third-Party Service terms; (e) unlawful or improper use of the Service by Customer, Authorized Users or End Users.

18.2 Provider will notify Customer of the claim, reasonably cooperate in the defense, and allow Customer to control the defense and settlement where reasonable. Provider may participate at its own expense. Customer may not settle a claim in a manner that imposes obligations on Provider without Provider's prior consent.

19. Term, Termination and Suspension

19.1 The Agreement runs for the agreed subscription period or, if no fixed period is agreed, for an indefinite term.

19.2 Customer may terminate at the end of the then-current billing period in accordance with the cancellation process in the dashboard, order form or plan description.

19.3 Either party may terminate for cause. Cause includes material breach, payment default, misuse, security risk, insolvency, legal prohibition or material violation of Third-Party Service terms relevant to the Service.

19.4 Provider may suspend or restrict access where reasonably necessary to prevent security risks, misuse, legal violations, excessive load, payment default or harm to Provider, other customers, End Users or Third-Party Services. Provider will use commercially reasonable efforts to provide prior notice where practicable.

19.5 Upon termination, Customer's right to use the Service ends. Customer should export required data before termination where export functionality is available. Provider deletes or returns Customer Data in accordance with the DPA and statutory retention obligations.

20. Changes to the Agreement

20.1 Provider may amend these ToS where reasonably necessary due to changes in law, regulation, security requirements, Third-Party Services, technical developments, business model, features or documentation.

20.2 Provider will notify Customer of material changes at least 30 days before they take effect, unless shorter notice is required for legal, security or technical reasons.

20.3 If Customer objects to material changes, Provider may terminate the Agreement as of the effective date of the changes. Continued use after the effective date constitutes acceptance to the extent permitted by law.

21. Export Control and Sanctions

21.1 Customer warrants that it is not subject to sanctions and will not use the Service in violation of export control or sanctions laws.

21.2 Provider may suspend or terminate access if Provider reasonably suspects a violation of export control or sanctions obligations.

22. Governing Law, Jurisdiction and Order of Precedence

22.1 German law applies, excluding the United Nations Convention on Contracts for the International Sale of Goods (CISG).

22.2 The exclusive place of jurisdiction for all disputes is Osnabrück, Germany, to the extent legally permitted.

22.3 For customers outside the EU, disputes may, to the extent legally permitted and if separately agreed or validly incorporated, be resolved by binding arbitration and class actions may be excluded. Mandatory law remains unaffected.

22.4 In the event of conflict, the following order of precedence applies: (1) individually negotiated order form or written agreement; (2) the DPA for data-protection matters; (3) plan-specific or product-specific terms; (4) API Terms; (5) Billing Terms; (6) these ToS; (7) documentation and website information expressly incorporated by reference. The Privacy Policy is an information document and does not override contractual terms.

23. Final Provisions

23.1 Customer may not assign rights or obligations under the Agreement without Provider's prior consent, except where mandatory law provides otherwise.

23.2 Provider may assign the Agreement to an affiliate or successor in connection with a merger, reorganization, sale of substantially all assets or similar transaction, provided that Customer's legitimate interests are reasonably protected.

23.3 If any provision is invalid, the remaining provisions remain effective. The parties will replace the invalid provision with a valid provision that comes closest to the economic purpose.