Voidhash Terms of Service

Version 1.0 · Effective from 14 October 2026

Czech version: Podmínky poskytování služby Voidhash (obchodní podmínky). Article 25.4 determines which language version prevails.

Summary of terms that may be unexpected. These Terms are for businesses only. You accept them by signing up for the Service (Article 3.1). Before signing up, please read in particular: the business-use declaration and the rules for consumers (Articles 3.2 and 3.3), the automatic renewal of paid Plans (Article 7.6), how Tracked Revenue is measured (Article 7.2), how long analytics data is kept (Article 12.6), our right to create anonymised Aggregated Data (Article 11.9), the limitation and exclusion of our liability (Article 15), the shortened one-year limitation period (Article 15.7), and the procedure for changing these Terms (Article 22). These provisions are printed in bold.

1. Introduction

1.1 These Terms of Service (the "Terms") govern the use of the hosted Voidhash service by business customers. The Service is provided by Voidhash s.r.o., company ID (IČO) 23738944, with its registered office at Chudenická 1059/30, Hostivař, 102 00 Prague 10, Czech Republic, registered in the Commercial Register kept by the Municipal Court in Prague, Section C, File 432083, tax ID (DIČ) CZ23738944 ("Voidhash", "we", "us").

1.2 These Terms are business terms (obchodní podmínky) within the meaning of Section 1751 of Act No. 89/2012 Coll., the Czech Civil Code (the "Civil Code"). They form part of every contract under which Voidhash provides the Service to a Customer.

1.3 The following documents form part of the Contract:

(a) the Data Processing Addendum (the "DPA"), which governs our processing of personal data on the Customer's behalf;
(b) the Acceptable Use Policy (the "AUP"), which also contains our content moderation and notice-and-action rules under the Digital Services Act;
(c) any Order Form agreed between the Customer and Voidhash; and
(d) the Plan description on our pricing page at the time the Plan is selected.

1.4 The following documents are provided for information and are referred to in these Terms: the Privacy Policy, the Subprocessors list, the Data portability register, the International data access statement, the SDK data page, and the Cookie Policy.

2. Definitions

Capitalised terms have the following meanings. The singular includes the plural and vice versa.

2.1 "Account" means the Customer's account in the Service, including all Organizations and Projects created under it.

2.2 "Affiliate" means an entity that controls, is controlled by, or is under common control with a party, where control means holding more than 50% of the voting rights or the power to direct management.

2.3 "Aggregated Data" means statistical or other data derived from the use of the Service that is aggregated and anonymised so that it does not identify, and cannot reasonably be used to identify, the Customer, any Authorized User, any End User or any Customer Application (Article 11.9).

2.4 "AI Feature" means any functionality of the Service that uses a machine-learning or generative artificial intelligence model, including AI paywall generation, the assistant and the agent (MCP) integration.

2.5 "API" means the Voidhash application programming interfaces, including REST and RPC endpoints at api.voidhash.com, webhooks and the agent (MCP) interface.

2.6 "Authorized User" means a natural person whom the Customer permits to access the Account, such as an employee, contractor or team member invited to an Organization.

2.7 "Beta Feature" means any feature, version or part of the Service labelled as "beta", "preview", "experimental", "early access" or similarly, or made available for testing and evaluation.

2.8 "Business Day" means a day other than a Saturday, Sunday or public holiday in the Czech Republic.

2.9 "Component" means a reusable paywall component (code, design, assets and metadata) built in or uploaded to the Service. A "Publisher" is a Customer that publishes a Component for other customers; an "Installer" is a Customer that installs a Component published by someone else.

2.10 "Confidential Information" has the meaning given in Article 13.1.

2.11 "Contract" means the contract between Voidhash and the Customer for the provision of the Service, consisting of these Terms and the documents listed in Article 1.3.

2.12 "Customer" or "you" means the legal entity or self-employed person (entrepreneur) that registers for the Service or signs an Order Form, and on whose behalf the Account is created.

2.13 "Customer Application" means any mobile, web, desktop or server application, website or backend system operated by or for the Customer in which the SDKs or the API are used.

2.14 "Customer Content" means paywalls, flows, Components, designs, texts, images, translations, product and offering configurations, experiment and feature-flag definitions, push notification content and other materials that the Customer or its Authorized Users create in or upload to the Service.

2.15 "Customer Data" means all data, including personal data, that the Customer, its Authorized Users, its Customer Applications or Platforms acting on the Customer's configuration submit to the Service, including End User identifiers and attributes, IP addresses, analytics events, purchase and subscription records and push tokens. Customer Data does not include Aggregated Data or Service Data.

2.16 "Dashboard" means the web interface of the Service (including Studio) at voidhash.com through which the Customer configures and administers the Service.

2.17 "Data Act" means Regulation (EU) 2023/2854 of the European Parliament and of the Council on harmonised rules on fair access to and use of data.

2.18 "Documentation" means the technical documentation and guides for the Service, the API and the SDKs published by Voidhash, as updated from time to time.

2.19 "DSA" means Regulation (EU) 2022/2065 on a Single Market for Digital Services (Digital Services Act).

2.20 "End User" means a natural or legal person who uses a Customer Application, including the Customer's own customers and visitors.

2.21 "Entitlement" means the record, maintained in the Service on the basis of the Customer's configuration and information from Platforms, indicating that an End User should have access to particular content, features or services of a Customer Application. An Entitlement is distinct from a store transaction.

2.22 "Event" has the meaning given in Article 7.3.

2.23 "Fees" means all amounts payable by the Customer for the Service under the Plan or Order Form.

2.24 "GDPR" means Regulation (EU) 2016/679 (General Data Protection Regulation).

2.25 "Open-Source Software" means software that Voidhash makes available under an open-source licence, including the SDKs and the Community edition of Voidhash (Article 10).

2.26 "Order Form" means an order, quote or agreement for an Enterprise Plan or other individual terms, signed or otherwise accepted by both parties, that refers to these Terms.

2.27 "Organization" and "Project" mean the organizational units within an Account that separate data, configuration, API keys and access rights. A Project belongs to exactly one Organization.

2.28 "Plan" means the Free, Grow or Enterprise plan, or any other subscription plan offered by Voidhash, together with its features, limits and prices.

2.29 "Platform" means a third-party store, payment or messaging platform with which the Service interacts on the Customer's behalf and with the Customer's credentials, in particular the Apple App Store (including the App Store Server API and App Store Connect), Google Play (including the Google Play Developer API and Real-time Developer Notifications), Stripe, Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM). The operator of a Platform is a "Platform Provider".

2.30 "SDK" means a Voidhash client or server software development kit or library (for example for iOS, Android, React Native, web and server environments) that the Customer integrates into a Customer Application.

2.31 "Service" means the hosted cloud service operated by Voidhash and accessible through the Dashboard, the API and the endpoints the SDKs connect to, including purchase and receipt validation, Entitlements, paywall design and delivery, Components, experiments and feature flags, product analytics, push notifications, webhooks and AI Features, as described in the Documentation and the applicable Plan. The Service does not include Open-Source Software operated by the Customer itself (self-hosting).

2.32 "Service Data" means technical and operational data that Voidhash generates about the operation and use of the Service (for example logs, metrics, performance data, usage volumes, security signals and billing records), excluding Customer Data.

2.33 "Tracked Revenue" has the meaning given in Article 7.2.

2.34 "Retention Period" means the minimum period for which event-level analytics data is kept under Article 12.6: 3 years on the Free Plan, 5 years on the Grow Plan, and the period agreed in the Order Form for Enterprise Plans.

3. Conclusion of the Contract, business use and Accounts

3.1 Conclusion. The sign-up form states that by signing up the Customer agrees to these Terms and links to them and to the Privacy Policy. The Customer accepts these Terms by signing up, that is by submitting the sign-up form or by continuing with a third-party sign-in such as GitHub. Where an Account was created without that statement being shown (for example through a third-party sign-in on the login page, or before these Terms took effect), the Customer accepts these Terms by selecting "Continue" on the acceptance screen shown in the Dashboard. The Contract is concluded when Voidhash then confirms the creation of the Account or gives access to the Dashboard, or when both parties sign or accept an Order Form. Voidhash records each acceptance (time, version of the Terms, IP address, user agent, and whether it was given at sign-up or in the Dashboard) as evidence. Selecting or changing a paid Plan in the Dashboard is a proposal to amend the Contract, which is accepted when Voidhash confirms the change. Voidhash may refuse registration without giving reasons. Voidhash stores the concluded Contract electronically; previous versions of the Terms are available on request at legal@voidhash.com. The Contract may be concluded in Czech or English.

3.2 Business use only. The Service is intended for businesses and is not intended for consumers. Businesses include companies and other legal entities as well as natural persons acting in the course of their business or independent profession, in particular sole traders, freelancers and independent developers who develop, operate or monetise apps as a business activity. By accepting these Terms under Article 3.1, the Customer declares that it will use the Service in the course of its business or professional activity and not as a consumer. Where the person registering does so on behalf of a company or other organization, that person confirms that they are authorised to bind it. The person registering and every Authorized User must be at least 18 years old.

3.3 Consumers. A person who would use the Service as a consumer (for example purely for a personal hobby project unrelated to any business) must contact Voidhash at legal@voidhash.com before registering, so that Voidhash can inform them of their rights and the conditions under which the Service could be provided to them. Voidhash may refuse registration, and may terminate the Contract with immediate effect under Article 17.4, if the business declaration under Article 3.2 is false.

3.4 Account information. The Customer shall provide accurate and complete registration, contact and billing information and keep it up to date. The email address of the Account owner is the primary address for notices under Article 23.

3.5 Authorized Users. The Customer may invite Authorized Users and assign them roles. The Customer is responsible for all actions taken through its Account, by its Authorized Users and through its API keys as if they were its own, and for ensuring that its Authorized Users comply with the Contract. Each Authorized User must use their own login credentials; credentials may not be shared.

3.6 Credential security. The Customer shall keep its passwords, API keys, SDK keys, webhook secrets and Platform credentials confidential, restrict them to those who need them, rotate them if compromised and notify Voidhash without undue delay at legal@voidhash.com of any suspected unauthorised access to the Account. Voidhash is not responsible for loss arising from the Customer's failure to protect its credentials, except to the extent caused by Voidhash's breach of the Contract.

3.7 Agencies. A Customer may use the Service to build, operate or manage Customer Applications for its own clients. In that case the Customer remains Voidhash's sole contracting party, is responsible for its clients' use of the Service and for having the authority and instructions needed from them, and its clients acquire no rights against Voidhash under the Contract.

4. The Service

4.1 Scope. Voidhash provides the Service in the scope of the Plan selected by the Customer or agreed in an Order Form, as described in the Documentation. The Contract is a contract for the provision of a service with an element of licence (Article 11.2); it is not a contract for the sale or transfer of software.

4.2 Development of the Service. The Service is continuously developed. Voidhash may change, improve, replace or discontinue features of the Service, including the API, the Dashboard and supported Platforms. If a change materially reduces the functionality of a paid Plan for the Customer, Voidhash will notify the Customer at least 30 days in advance and the Customer may terminate the Contract free of charge before the change takes effect, with a pro-rata refund of prepaid Fees for the period after termination. This Article 4.2 does not apply to changes required by law, by a Platform Provider or for security reasons, which Voidhash will announce as soon as reasonably possible.

4.3 API and SDK versions. Voidhash will give at least 6 months notice before removing a generally available API version or ending support for an SDK major version, except where a shorter period is required by law, by a Platform Provider or for security reasons. The Customer is responsible for keeping the SDKs in its Customer Applications reasonably up to date; older SDK versions may stop working correctly once they are no longer supported.

4.4 Availability and maintenance. Voidhash makes commercially reasonable efforts to keep the Service available 24 hours a day, 7 days a week. Unless an Order Form provides for a service level agreement, Voidhash does not guarantee any particular availability, response time or error-free operation. Voidhash will announce planned maintenance that is expected to affect availability at least 12 hours in advance where possible, in the Dashboard or by email. Emergency maintenance may be carried out without prior notice.

4.5 Service levels for Enterprise. Enterprise Plans may include an availability commitment (currently 99.9% monthly availability) and service credits as set out in the Order Form. Where an Order Form provides service credits, those credits are the Customer's sole remedy for failure to meet the availability commitment, except in cases of intent or gross negligence.

4.6 Support. Support is provided in English and Czech by electronic means: on the Free Plan through community channels and the Documentation; on the Grow Plan by email at support@voidhash.com, with a target of a first reply within one Business Day; on Enterprise Plans as agreed in the Order Form. Reply targets are not guaranteed resolution times.

4.7 Usage limits and fair use. The Service is subject to the limits of the Customer's Plan and to technical limits (for example API rate limits, payload sizes, the number of Projects, retention periods and storage) set out in the Documentation. The Customer shall not use the Service in a way that places a disproportionate load on it compared with ordinary use for its Plan. Voidhash may throttle or queue requests that exceed technical limits, giving priority where practicable to purchase validation and Entitlement requests.

4.8 Data retention. How long Customer Data is kept depends on its type and on the Retention Period of the Customer's Plan, as set out in Article 12.6.

4.9 Subcontractors. Voidhash may use subcontractors to provide the Service and remains responsible for their performance. Subprocessors of personal data are listed on the Subprocessors page and governed by the DPA.

5. Purchases, Entitlements and Platforms

5.1 Voidhash is not a party to purchases. Voidhash is not a seller, merchant of record, payment service provider or payment processor, and it is not a party to any purchase, subscription or other transaction between the Customer and an End User. Payments by End Users are processed by the relevant Platform Provider (for example Apple, Google or Stripe) under the Platform Provider's terms and the Customer's agreements with it. Voidhash does not receive, hold or transfer End Users' funds.

5.2 Dependence on Platforms. Purchase validation, subscription status, renewals, refunds and other information reflected in the Service depend on data, APIs and notifications supplied by Platform Providers. That information may be delayed, incomplete, duplicated, changed retroactively or incorrect, and Platform APIs may be unavailable or change without notice. Voidhash processes it with reasonable care but is not responsible for the accuracy, completeness or availability of information supplied by Platform Providers, nor for their acts or omissions.

5.3 Entitlements are a tool, not a decision. The Service calculates Entitlements according to the Customer's configuration. The Customer remains responsible for its decisions to grant, restrict or revoke End Users' access, for its refund and cancellation policies, for handling fraud, chargebacks and disputes, and for customer support to its End Users. The Customer is responsible for configuring products, offerings and Entitlement rules correctly and for testing its integration before release, including in sandbox environments.

5.4 Caching and offline use. To keep Customer Applications working when the network or the Service is unavailable, the SDKs may cache Entitlement information on End User devices and rely on it for a limited time. As a result, an End User may retain or lack access for some time after the underlying status has changed. The Customer should design its Customer Application, and the SDK configuration it chooses, with this behaviour in mind.

5.5 Platform policies. The Customer is solely responsible for its relationship with Platform Providers, including compliance with their developer agreements and policies (Article 6.3) and for any fees payable to them. If a Platform Provider restricts, suspends or terminates the Customer's account or the Customer's use of its APIs, Voidhash is not liable for the resulting inability to provide parts of the Service.

6. Customer obligations

6.1 Lawful use. The Customer shall use the Service in accordance with the Contract, the Documentation, the AUP and applicable law, and is responsible for the lawfulness of Customer Data, Customer Content and Customer Applications.

6.2 End User privacy and consent. The Customer is the controller of End Users' personal data processed through the Service, and Voidhash processes that data as its processor under the DPA. The Customer shall in particular:

(a) provide End Users with the information required by Articles 13 and 14 GDPR and comparable laws, including that the Customer uses Voidhash as a service provider and the uses of IP addresses described in point (iv) below; the SDK data page contains a template paragraph;
(b) have a legal basis for all processing it instructs, decide whether End Users' consent is required, obtain and record any consent required and pass the End User's choice to the SDKs using the controls described on the SDK data page;
(c) decide whether to show the App Tracking Transparency prompt or similar consent dialogs in its Customer Applications and respect the End User's choice;
(d) handle End Users' requests to exercise their rights, using the erasure and export tools provided by the Service where appropriate.

Voidhash's position on consent for the features of the SDKs is as follows; it does not replace the Customer's own assessment as controller:

(i) Purchase processing. Validating receipts and transactions, restoring purchases and maintaining Entitlements, including the identifiers and on-device storage needed for them, is part of the service the End User requested and is strictly necessary for it. It runs without consent.
(ii) Revenue analytics. Revenue, MRR, subscription and refund reporting is computed on Voidhash's servers from the purchase transactions already processed under point (i). It requires no additional on-device storage or event collection and keeps working regardless of the End User's analytics consent. The Customer, as controller, determines the legal basis for it, typically its legitimate interest or compliance with its accounting obligations.
(iii) Usage analytics. Automatically collected events (such as app opens and screen views), custom events, paywall impressions and interactions, and person traits may require the End User's consent under rules implementing Article 5(3) of Directive 2002/58/EC (in the Czech Republic, Section 89(3) of Act No. 127/2005 Coll., on electronic communications), depending on the jurisdiction and on how the Customer uses them. Deciding whether consent is needed, obtaining it and passing the result to the SDKs is the Customer's responsibility. Where usage analytics is disabled for some End Users, metrics that rely on impressions (for example paywall conversion rates) are computed only from End Users for whom it is enabled and may be incomplete.
(iv) IP addresses. The Service receives the full IP address with every SDK and API request, stores it with Events and uses it (1) to derive approximate location (country, region, city and timezone), (2) for security, fraud and abuse prevention, and (3) where offered, to recognise the same End User across the Customer's own apps and websites.

6.3 Store rules. The Customer shall comply with the Apple Developer Program License Agreement and App Store Review Guidelines (including guideline 3.1.2 on subscriptions), the Google Play Developer Distribution Agreement and Developer Program Policies (including the subscriptions policy), the Stripe Services Agreement and other Platform terms that apply to the Customer Applications. The Customer is responsible for completing the App Store privacy details ("privacy nutrition labels"), the Google Play Data safety form and similar disclosures accurately, taking into account the data processed by the SDKs as described on the SDK data page.

6.4 Children. If a Customer Application is directed at children or the Customer knowingly processes children's personal data, the Customer is responsible for compliance with the applicable rules, including Article 8 GDPR (in the Czech Republic, consent of a child to information society services is valid from the age of 15), the US Children's Online Privacy Protection Act (COPPA) and the Platform rules for apps in children's categories, and for configuring the Service accordingly. The Customer shall not use analytics or other features where the applicable law or Platform rules prohibit them for such Customer Applications.

6.5 Prohibited data. The Customer shall not submit to the Service, as Event properties, End User traits, identifiers or Customer Content: (a) special categories of personal data under Article 9 GDPR or data relating to criminal convictions and offences under Article 10 GDPR; (b) full payment card numbers, bank account credentials or authentication data; (c) government-issued identification numbers (such as birth numbers, passport or social security numbers); or (d) protected health information, unless expressly agreed in an Order Form. Voidhash has no obligation to check whether the Customer complies with this Article 6.5.

6.6 Paywalls and consumer law. The Customer is solely responsible for the content of its paywalls, offers and purchase flows, including that they comply with consumer protection law and Platform rules. Paywalls in particular must clearly state the price, billing period, any free trial or introductory price and the conditions on which a subscription renews and can be cancelled, and must not use misleading designs (for example fake countdowns, fictitious discounts or hidden renewal terms). Templates, examples and AI-generated proposals provided by Voidhash do not relieve the Customer of this responsibility.

6.7 Push notifications and webhooks. The Customer is responsible for the content and lawfulness of push notifications it sends through the Service, including any consent required for commercial communications, and for the security of the endpoints to which it directs webhooks. Voidhash sends push notifications and webhooks only on the Customer's configuration and with the Customer's credentials.

6.8 Cooperation. The Customer shall provide Voidhash with the information and cooperation reasonably necessary to provide the Service, resolve support requests and investigate security incidents.

6.9 Backups of Customer Content. The Customer should keep its own copies of Customer Content and configuration that are important to it. The Service provides export tools for this purpose (Article 18 and the Data portability register).

7. Plans, Fees and payment

7.1 Plans and prices. Prices and Plan limits are published on the pricing page at voidhash.com/pricing or set out in an Order Form. Prices are stated in US dollars (USD) and exclude VAT. Voidhash is not registered for VAT on the date of these Terms. If Voidhash becomes a VAT payer, VAT will be added at the statutory rate; for business customers established in another EU Member State, the reverse-charge mechanism will apply where applicable. The Customer is responsible for all other taxes, duties and charges relating to its purchase of the Service, other than taxes on Voidhash's income. If the Customer is required by law to withhold tax on a payment, it shall increase the payment so that Voidhash receives the amount it would have received without the withholding.

7.2 Tracked Revenue. "Tracked Revenue" means the revenue from purchases that the Service processes for the Customer's production environments in a calendar month, calculated as follows:

(a) the amount is the price paid by the End User as reported by the store or payment provider, before store commission and before taxes are deducted (that is, including any taxes contained in the reported price), for initial purchases, renewals and one-time purchases that Voidhash processes in that calendar month;
(b) refunds and chargebacks are not deducted;
(c) amounts in other currencies are converted to USD at the reference rate of Voidhash's exchange-rate provider for the transaction date; once calculated, converted amounts are not recalculated;
(d) sandbox and test transactions are excluded; free trials and other zero-amount transactions count as zero; discounted and introductory offers count at the amount actually charged;
(e) transactions dated before the Customer connected the relevant store or payment provider to the Service, and historical transactions imported into the Service (for example when migrating from another provider), are excluded;
(f) revenue counts in the calendar month, determined in Coordinated Universal Time (UTC), that contains the transaction date reported by the store or payment provider; transactions reported to the Service after that month has been billed count in the month in which they are processed. Voidhash's measurement controls billing under Article 7.4 and is visible in the Dashboard, and invoices may be disputed within 30 days under Article 7.10.

7.3 Events. "Event" means each analytics event received by the Service for the Customer's Projects, whether sent by the SDKs (including automatically collected events such as app opens and screen views) or through the API, in a calendar month.

7.4 Measurement. The volumes of Tracked Revenue and Events measured by Voidhash are decisive for billing, unless the Customer proves that they are incorrect. Current volumes are visible in the Dashboard. The Customer may dispute an invoice or charge in accordance with Article 7.10.

7.5 Free Plan. The Free Plan is free of charge, requires no payment card and includes the monthly allowances stated on the pricing page (on the date of these Terms: USD 1,000 Tracked Revenue and 50,000 Events per month). Voidhash will notify the Customer by email when its usage reaches approximately 80% and 100% of an allowance. The Free Plan is never moved to a paid Plan without the Customer's action. If the Customer exceeds an allowance, Article 7.14 applies until the start of the next calendar month or until the Customer moves to a paid Plan. Voidhash may change the scope of the Free Plan in accordance with Article 22.

7.6 Paid Plans and automatic renewal. The Grow Plan is a monthly subscription that renews automatically for successive one-month billing periods until the Customer cancels it. Enterprise Plans run for the term stated in the Order Form and renew as stated there. The Customer may cancel the Grow Plan at any time in the Dashboard; cancellation takes effect at the end of the current billing period, and the Account then returns to the Free Plan unless the Customer terminates the Contract.

7.7 Billing. Unless an Order Form provides otherwise: (a) the base fee for a paid Plan is charged monthly in advance; (b) usage above the volumes included in the Plan (Tracked Revenue and Events) is charged monthly in arrears for the previous calendar month at the rates in effect for that month; (c) included volumes reset at the start of each calendar month and unused volumes do not carry over. Usage-based charges are not subject to tiers or minimums unless stated on the pricing page or in an Order Form.

7.8 Spend cap. The Customer may set a spending cap in the billing settings. Voidhash will notify the Customer as usage approaches the cap. Once the cap is reached, Article 7.14 applies for the rest of the calendar month, and the Customer will not be charged usage Fees exceeding the cap.

7.9 Payment. Fees are charged automatically to the payment card or other payment method the Customer provides, through Voidhash's billing and payment providers (currently Autumn and Stripe). By providing a payment method, the Customer authorises these recurring charges. Voidhash does not store payment card data. Invoices and other tax documents are issued electronically and made available in the Dashboard or by email. Enterprise Fees may be paid by bank transfer within the period stated in the Order Form or on the invoice, otherwise within 14 days of the invoice date. A payment is made when the amount is credited to Voidhash's account. Bank and currency conversion charges on the Customer's side are borne by the Customer.

7.10 Disputes about charges. The Customer may dispute an invoice or charge in writing to legal@voidhash.com, with reasons, within 30 days of its issue. Undisputed amounts remain payable. If no dispute is raised within that period, the invoice is deemed accepted, without prejudice to the Customer's right to claim in court an amount charged in obvious error. The Customer may not set off its claims against Fees owed to Voidhash.

7.11 Late payment. If the Customer fails to pay on time, Voidhash may charge statutory default interest under Government Regulation No. 351/2013 Coll. and the lump-sum compensation for recovery costs set out in that Regulation. Voidhash will send a payment reminder; if the amount remains unpaid:

(a) 14 days after the due date, Voidhash may apply the restrictions permitted by Article 7.14;
(b) ** 60 days** after the due date, Voidhash may terminate the Contract under Article 17.4(c), with at least 30 days' notice.

Voidhash will retain Customer Data at least until the end of the data retrieval period under Article 18.9 and will allow the Customer to export it once the arrears are settled or within that period.

7.12 Price changes. Voidhash may change its prices, including usage rates and included volumes, by notifying the Customer at least 30 days before the change takes effect, by email and in the Dashboard. If the Customer does not agree, it may terminate the Contract free of charge before the change takes effect; Article 22.4 applies accordingly. Price reductions may take effect immediately. Prices agreed in an Order Form for a fixed term do not change during that term unless the Order Form provides otherwise.

7.13 Refunds. Fees already paid are non-refundable, except where these Terms expressly provide for a pro-rata refund (Articles 4.2, 7.12, 17.3, 17.6, 18.13 and 22.4) or where a refund is required by law.

7.14 Continuity of purchase processing. Exceeding a Plan allowance or a spend cap, or a failed or late payment, never interrupts purchase processing, receipt and transaction validation, Entitlement checks, purchase restoration or webhook delivery for End Users (the "Core Purchase Functions"). In those cases Voidhash may only, until the cause is resolved (the Customer moves to a paid Plan, raises or removes the cap, or pays, or the next calendar month begins, as applicable):

(a) pause the ingestion of usage analytics Events; Events received beyond the allowance or cap are not stored and cannot be recovered later; and
(b) restrict access to the Dashboard and to editing, export and analytics features, without prejudice to the Customer's rights under Article 18.

Voidhash may stop the Core Purchase Functions for these reasons only by terminating the Contract under Article 17 with at least 30 days' notice, after which the Retrieval Period under Article 18.9 applies.

8. Suspension

8.1 Grounds. Voidhash may suspend or restrict the Customer's access to all or part of the Service, or to a specific Project, API key or Customer Content, if:

(a) the Customer's use of the Service poses a risk to the security, integrity or availability of the Service or to other customers;
(b) the Customer materially breaches the Contract or the AUP, including by submitting manifestly illegal content;
(c) the Customer is in payment default under Article 7.11, in which case only the restrictions permitted by Article 7.14 apply;
(d) suspension is required by law, a court or authority decision, or the sanctions rules in Article 20; or
(e) Voidhash has reasonable grounds to suspect that the Account has been compromised or is being used fraudulently.

8.2 Proportionality and notice. Suspension will be limited to the extent and duration reasonably necessary to remove its cause. Before suspending, Voidhash will notify the Customer, state the reasons and, where the cause can be remedied, give the Customer a reasonable period to remedy it. In urgent cases under Articles 8.1(a), (d) and (e), Voidhash may suspend without prior notice and will notify the Customer without undue delay afterwards. Statements of reasons concerning illegal content are governed by the AUP.

8.3 Preference for End User access. Article 7.14 governs plan limits, spend caps and payment default. In other cases under Article 8.1, where reasonably possible, Voidhash will first restrict functions that do not affect End Users' access to content they have paid for (for example the Dashboard, analytics ingestion or publishing new paywalls) before restricting purchase validation or Entitlement checks. The Customer acknowledges that a suspension may cause the SDKs to rely on cached Entitlement information or to show no paywall.

8.4 Effects. Suspension does not affect the Customer's obligation to pay Fees, except where the suspension was caused by Voidhash's breach. Voidhash will restore the Service without undue delay once the cause of suspension has been removed.

9. AI Features

9.1 Transparency. AI Features are labelled as such in the Service. Content generated by AI Features, such as paywall designs, texts, images, translations or suggestions ("AI Output"), is generated automatically and may be inaccurate, incomplete, inappropriate or similar to content generated for other customers.

9.2 Review before publishing. The Customer shall review AI Output before using or publishing it and is responsible for its use, including its compliance with consumer law, Platform rules and third-party rights. AI Output does not constitute advice and Voidhash does not warrant that it is suitable for any purpose. Where the Customer publishes AI Output to End Users, it is responsible for any disclosure obligations under Article 50 of Regulation (EU) 2024/1689 (the AI Act) that apply to it as a deployer.

9.3 AI providers. To provide AI Features, Voidhash sends the inputs the Customer provides (prompts, relevant Customer Content and context) to third-party AI model providers acting as Voidhash's subprocessors, namely OpenAI, L.L.C. and Anthropic, PBC (both in the USA), as listed on the Subprocessors page. These providers are used only for AI Features; transfers rely on the EU–US Data Privacy Framework where the recipient is certified, and otherwise on the European Commission's Standard Contractual Clauses. The Customer shall not include End Users' personal data in prompts unless necessary. AI Features are used only when the Customer or its Authorized Users invoke them.

9.4 No training on Customer Data. Voidhash does not use Customer Data, Customer Content or End User data to train artificial intelligence or machine-learning models, and does not permit its AI providers to do so. Our AI providers do not use this data to train their models.

9.5 Agents and automation. The Customer may connect AI agents and automation tools to the Service through the API or the MCP integration. Actions performed by such tools with the Customer's credentials are deemed actions of the Customer. The Customer is responsible for the permissions it grants them and for reviewing their actions, in particular changes to products, prices, Entitlements and published paywalls.

10. Open-Source Software

10.1 Separate licences. The SDKs and the Community edition of Voidhash are Open-Source Software. Their use, modification and distribution are governed exclusively by the open-source licences accompanying the relevant code, such as the MIT License or the GNU Affero General Public License v3.0 (AGPL-3.0), as stated in each repository; certain enterprise features are subject to a separate Voidhash Enterprise licence identified in the relevant source code. Nothing in these Terms restricts rights granted by those licences.

10.2 Scope of these Terms. These Terms govern the hosted Service. When the Customer runs Open-Source Software on its own infrastructure (self-hosting), Voidhash does not provide the Service, these Terms do not apply to that operation and Voidhash does not process any data in it, unless an Order Form provides for support of a self-hosted deployment.

10.3 SDKs connected to the Service. When the SDKs are configured to connect to the Service, the data they send to the Service is Customer Data processed under these Terms and the DPA.

11. Intellectual property

11.1 Voidhash's rights. As between the parties, Voidhash and its licensors own all rights, including intellectual property rights, in the Service, the Dashboard, the Documentation, Service Data, Aggregated Data and the Voidhash name, logos and trademarks, subject to the open-source licences under Article 10. No rights are granted except as expressly stated in the Contract.

11.2 Right to use the Service. For the duration of the Contract, Voidhash grants the Customer a non-exclusive, non-transferable, non-sublicensable right, unlimited in territory, to access and use the Service, and to allow its Authorized Users to do so, within the limits of its Plan, for the Customer's business purposes and in accordance with the Contract. The consideration for this right is included in the Fees; on the Free Plan it is granted free of charge.

11.3 Restrictions. Except as permitted by Article 10 or mandatory law (including Section 66 of Act No. 121/2000 Coll., the Copyright Act), the Customer shall not: (a) copy, modify, decompile or reverse engineer the hosted Service or attempt to extract its non-public source code; (b) sell, resell, rent or provide the Service to third parties as a standalone service, except to its clients under Article 3.7; (c) circumvent usage limits, billing or security measures, including by creating multiple Free Accounts; (d) access the Service through automated means other than the API and SDKs; (e) carry out load, penetration or vulnerability testing without Voidhash's prior written consent obtained through legal@voidhash.com; or (f) use the Service to build a competing product by copying its non-public features or interfaces.

11.4 Customer Data and Customer Content. As between the parties, the Customer retains all rights in Customer Data and Customer Content. Voidhash acquires no rights in them other than those set out in this Article 11.

11.5 Licence to Voidhash. The Customer grants Voidhash a non-exclusive, worldwide, royalty-free licence, for the duration of the Contract and the subsequent periods under Article 18, to host, store, copy, process, transmit, display, adapt (for example for format conversion or rendering on different devices) and distribute Customer Data and Customer Content to the extent necessary to provide, secure and support the Service, including delivering paywalls and Components to End Users and transmitting data to Platforms and endpoints configured by the Customer. Voidhash may sublicense these rights to its subcontractors for the same purpose. The processing of personal data within Customer Data is governed by the DPA.

11.6 Component publishing. When a Publisher publishes a Component for other customers, it grants each Installer a non-exclusive, worldwide, royalty-free licence, for the duration of the Installer's use of the Service and for paywalls published during that time, to use, reproduce, adapt and display the Component in the Installer's paywalls and Customer Applications, unless the Publisher specifies a different licence when publishing. The Publisher warrants that it holds all rights needed to grant this licence and that the Component does not contain malicious code or infringe third-party rights. Withdrawing a Component prevents new installations but does not revoke the licence for existing installations.

11.7 Third-party Components. Components installed from other Publishers are provided by those Publishers, not by Voidhash. Voidhash may, but is not obliged to, review Components, and may remove or disable a Component that breaches the Contract, the AUP or the law. Voidhash provides third-party Components "as is" and, to the extent permitted by law, is not liable for them. The Installer is responsible for checking that a Component is suitable for its use. Voidhash is not a party to the licence between the Publisher and the Installer. Voidhash may introduce paid Components only under separate terms.

11.8 Feedback. If the Customer or its Authorized Users provide suggestions, ideas or other feedback about the Service, Voidhash may use it without restriction or compensation, and the Customer grants Voidhash for this purpose a perpetual, irrevocable, worldwide, royalty-free and transferable licence. Voidhash will not identify the Customer as the source of feedback without its consent.

11.9 Aggregated Data. Voidhash may create Aggregated Data from Customer Data and Service Data and may use it, also after the termination of the Contract, to operate, secure, analyse and improve the Service, to develop new features, and to publish industry statistics and benchmarks (for example typical conversion or renewal rates across apps). Aggregated Data never identifies the Customer, its Customer Applications, Authorized Users or End Users, and Voidhash will not attempt to re-identify it. Aggregated Data is combined from several customers so that individual customers' results cannot be derived from it. The creation of Aggregated Data from personal data is a documented instruction under the DPA. Aggregated Data is not used to train artificial intelligence or machine-learning models (Article 9.4).

11.10 Publicity. Voidhash will name the Customer or use its logo as a reference customer only with the Customer's prior consent, which the Customer may withdraw at any time with effect for the future.

12. Data protection and security

12.1 Privacy Policy. Voidhash processes the personal data of Authorized Users and Customer contacts as a controller in accordance with the Privacy Policy.

12.2 DPA. By accepting these Terms, the Customer and Voidhash conclude the DPA, which governs Voidhash's processing of personal data in Customer Data on the Customer's behalf and includes the standard contractual clauses where required. The Platforms and endpoints the Customer configures with its own credentials receive data on the Customer's instructions and are not Voidhash's subprocessors.

12.3 Security. Voidhash maintains appropriate technical and organisational security measures, as described in the DPA, and may update them provided the overall level of protection is not reduced. Vulnerabilities can be reported to legal@voidhash.com.

12.4 International transfers and access. The Service (application hosting, databases, the analytics store and file storage) is hosted in the eastern United States; network traffic passes through Cloudflare's global edge network. Transfers of personal data outside the European Economic Area are governed by the DPA. Information on the jurisdiction of the infrastructure and safeguards against unlawful governmental access to non-personal data under Article 28 of the Data Act is published on the International data access page.

12.5 Service Data. Voidhash may use Service Data to provide, secure, bill, support and improve the Service and to comply with legal obligations. Where Service Data contains personal data, the Privacy Policy applies.

12.6 Retention of Customer Data. Unless the Customer deletes data earlier:

(a) event-level analytics data (Events, sessions, screen views and custom events, with their properties) is kept for at least the Retention Period, counted from when each Event occurred; after that, Voidhash may delete it or replace it with aggregated statistics that no longer identify End Users, and is not obliged to keep it longer;
(b) aggregated reports (such as revenue, MRR, conversion, retention and cohort charts) remain available for the life of the Account;
(c) purchase, transaction, subscription and Entitlement records are kept for the life of the Account, because access decisions and revenue history depend on them, unless the Customer erases the End User concerned or closes the Account;
(d) records of End Users (persons) with no activity for longer than the Retention Period may be deleted;
(e) Voidhash will notify the Customer at least 30 days before it first deletes data of a Project under this Article 12.6, so that the Customer can export it;
(f) if the Customer moves to a Plan with a shorter Retention Period, the new Retention Period applies, with the same advance notice under point (e);
(g) the Customer may erase End Users at any time, and an Order Form may provide for a shorter Retention Period.

After the Contract ends, Articles 18.9 and 18.10 apply instead of this Article 12.6.

13. Confidentiality

13.1 Definition. "Confidential Information" means all non-public information disclosed by one party (the "Disclosing Party") to the other (the "Receiving Party") in connection with the Contract that is marked as confidential or should reasonably be regarded as confidential given its nature or the circumstances of disclosure, including the terms of an Order Form, non-public pricing, security information, product plans and Customer Data. Information is not Confidential Information if the Receiving Party proves that it: (a) is or becomes public through no fault of the Receiving Party; (b) was lawfully known to the Receiving Party before disclosure without an obligation of confidentiality; (c) was lawfully received from a third party without an obligation of confidentiality; or (d) was independently developed by the Receiving Party without use of the Confidential Information.

13.2 Obligations. The Receiving Party shall use Confidential Information only to perform the Contract or exercise its rights under it, protect it with at least the care it uses for its own confidential information of a similar nature and no less than reasonable care, and disclose it only to its and its Affiliates' employees, contractors, subprocessors and professional advisers who need to know it and are bound by confidentiality obligations no less protective than this Article 13.

13.3 Disclosure required by law. The Receiving Party may disclose Confidential Information to the extent required by law or by a decision of a court or authority, provided that, where legally permitted, it informs the Disclosing Party in advance and cooperates in seeking confidential treatment. Requests from public authorities for Customer Data are governed by the DPA and the International data access page.

13.4 Duration. The obligations under this Article 13 continue for 3 years after the termination of the Contract; for trade secrets, for as long as the information remains a trade secret. Personal data remain protected for as long as the DPA and the law require.

14. Warranties and disclaimers

14.1 Mutual. Each party warrants that it has the authority to enter into the Contract and that it will perform it in accordance with applicable law.

14.2 Voidhash. Voidhash warrants that it will provide the Service with professional care and in all material respects in accordance with the Documentation applicable to the Customer's Plan. If the Service does not conform to this warranty, the Customer shall notify Voidhash without undue delay with a description of the defect, and Voidhash will remedy the defect within a reasonable time or, if it cannot do so, the Customer may terminate the affected paid Plan and receive a pro-rata refund of prepaid Fees for the period after termination. Claims for damages are governed by Article 15.

14.3 Information and recommendations. Analytics, reports, revenue figures, experiment results, recommendations, benchmarks and AI Output provided by the Service are for information only. The Customer makes its own decisions about pricing, offers, paywalls and its business, and Voidhash is not liable for them (Section 2950 of the Civil Code). Revenue figures in the Service are estimates based on Platform information and may differ from the amounts actually paid out by Platform Providers; they are not a substitute for the Customer's accounting records.

14.4 Free Plan and Beta Features. The Free Plan and Beta Features are provided "as is" and "as available", without warranties under Article 14.2. Beta Features may be incomplete, changed or discontinued at any time, may not be covered by support or service levels and must not be relied on for production purposes unless Voidhash indicates otherwise. Their use is at the Customer's own risk.

14.5 Exclusion of other warranties. Except as expressly stated in the Contract and to the extent permitted by law, Voidhash gives no other warranties or representations, in particular that the Service will be uninterrupted or error-free, that it will meet all of the Customer's requirements, that it will be compatible with every device or Platform version, or that it will achieve any particular business result.

15. Liability

15.1 Unlimited liability. Nothing in the Contract limits or excludes either party's liability for harm caused intentionally or through gross negligence, for harm to the natural rights of a person (including life, health and privacy), or any other liability that cannot be limited or excluded under applicable law, in particular Section 2898 of the Civil Code.

15.2 Excluded types of loss. Except in the cases in Article 15.1, neither party is liable for lost profits, lost revenue, loss of business or goodwill, indirect or consequential loss, or loss of data that could have been avoided by reasonable backups or export by the Customer; Voidhash's liability for loss or corruption of data is limited to the reasonable cost of restoring the data from the last available backup. Voidhash is also not liable for loss caused by the acts or omissions of Platform Providers, inaccurate information supplied by them, the Customer's configuration of the Service, Customer Content, third-party Components or the Customer's failure to follow the Documentation.

15.3 Liability cap. Except in the cases in Article 15.1, Voidhash's total liability for all harm arising out of or in connection with the Contract, including harm arising after the Contract ends, is limited to the Fees actually paid by the Customer for the Service in the 6 months before the event giving rise to the claim. Different limits may be agreed in an Order Form.

15.4 Free Plan and Beta Features. Because no Fees are paid for the Free Plan or for free Beta Features, the cap in Article 15.3 means that, except in the cases in Article 15.1, Voidhash is not liable to pay damages in connection with their use.

15.5 Basis of liability. The parties agree that, except in the cases in Article 15.1, Voidhash is liable for harm only where it has breached its obligations culpably (at least through negligence).

15.6 Mitigation and contributory fault. Each party shall take reasonable steps to mitigate harm. A party's liability is reduced to the extent the harm was caused or contributed to by the other party, its Authorized Users or persons for whom it is responsible.

15.7 Limitation period. Claims for damages against Voidhash arising out of or in connection with the Contract are time-barred one year after the limitation period begins to run under Section 619 of the Civil Code. This does not apply to claims for harm caused intentionally or through gross negligence or harm to the natural rights of a person, for which the statutory limitation periods apply.

15.8 Persons acting for Voidhash. The limitations in this Article 15 also benefit Voidhash's employees, managing directors and subcontractors to the extent permitted by law.

16. Indemnities

16.1 By Voidhash. Voidhash will defend the Customer against claims by third parties that the Service, as provided by Voidhash and used by the Customer in accordance with the Contract, infringes their intellectual property rights, and will compensate the Customer for damages and reasonable costs finally awarded against it or agreed by Voidhash in a settlement. This obligation does not apply to claims arising from: (a) Customer Data, Customer Content or third-party Components; (b) combination of the Service with products, data or processes not supplied by Voidhash; (c) modification of the Service other than by Voidhash; (d) Open-Source Software (governed by its licence); (e) use of the Service in breach of the Contract; or (f) the Free Plan or Beta Features. If such a claim is made or appears likely, Voidhash may obtain the right for the Customer to continue using the Service, modify it so that it is non-infringing, or, if neither is reasonably possible, terminate the affected part of the Service and refund prepaid Fees for the period after termination. This Article 16.1 states Voidhash's entire obligation in respect of third-party intellectual property claims.

16.2 By the Customer. The Customer will defend Voidhash against claims by third parties (including End Users, Platform Providers and authorities) arising from: (a) Customer Data, Customer Content or Components published by the Customer; (b) the Customer Applications and the Customer's relationship with its End Users, including purchases, refunds, access decisions and customer support; (c) the Customer's breach of Articles 6 or 11.3 or of the AUP; or (d) the Customer's breach of Platform rules or data protection law, and will compensate Voidhash for damages, fines to the extent legally recoverable, and reasonable costs finally awarded or agreed in a settlement approved by the Customer.

16.3 Procedure. The indemnified party shall notify the indemnifying party of the claim without undue delay, allow it to control the defence and settlement, and provide reasonable cooperation at the indemnifying party's cost. The indemnifying party may not agree to a settlement that imposes obligations on, or admits fault by, the indemnified party without its consent, which shall not be unreasonably withheld. A failure to notify promptly reduces the indemnifying party's obligation only to the extent it is prejudiced by the delay.

17. Term and termination

17.1 Term. The Contract is concluded for an indefinite period, unless an Order Form specifies a fixed term.

17.2 Termination by the Customer. The Customer may terminate the Contract at any time by closing its Account in the Dashboard or by notice to legal@voidhash.com. Termination takes effect at the end of the current billing period of a paid Plan, or immediately on the Free Plan, unless the Customer specifies a later date. If the Customer wishes to switch to another provider, move its data to its own infrastructure or have its data erased, the procedure in Article 18 applies, and the notice period will not exceed 2 months. Fixed-term Order Forms may be terminated early only as provided in the Order Form or by law, subject to Article 18.13.

17.3 Termination by Voidhash for convenience. Voidhash may terminate the Contract without giving reasons by notice of at least 2 months. Voidhash will refund prepaid Fees for the period after termination.

17.4 Termination for cause. Either party may terminate the Contract by notice with immediate effect (or a later date stated in the notice) if the other party materially breaches the Contract and fails to remedy the breach within 15 days of receiving a notice describing it, where the breach can be remedied. Voidhash may also terminate the Contract with immediate effect if: (a) the Customer's business declaration under Article 3.2 is false; (b) insolvency proceedings are commenced against the Customer, its insolvency is declared or the Customer enters liquidation; (c) the Customer is in payment default for more than 60 days, in which case the termination takes effect no earlier than 30 days after the notice (Article 7.14); (d) the Customer repeatedly or seriously breaches the AUP; or (e) continued performance would breach sanctions or export control rules (Article 20).

17.5 Inactive Free Accounts. Voidhash may close a Free Plan Account that has had no Authorized User sign-in and no API or SDK traffic for 12 consecutive months, after notifying the Customer at least 30 days in advance by email. The Customer may prevent closure by signing in or by replying to the notice. Article 18.9 applies to the retrieval of data.

17.6 Consequences of termination. On termination: (a) the Customer's right to use the Service ends, subject to Article 18 (transitional and retrieval periods); (b) all Fees due up to the effective date of termination become payable; (c) the Customer should remove the SDKs or disconnect them from the Service and redirect Platform server notifications (for example App Store Server Notifications and Google Play Real-time Developer Notifications) to its new solution; (d) Voidhash will delete Customer Data in accordance with Article 18.10 and the DPA, except where it must retain data by law. Where the Contract is terminated by the Customer under Articles 4.2, 7.12, 14.2 or 22.4, by the Customer for Voidhash's material breach or by Voidhash under Article 17.3, Voidhash will refund prepaid Fees for the period after termination.

17.7 Survival. Provisions which by their nature should continue after termination survive it, in particular Articles 7 (in respect of unpaid Fees), 11.4, 11.8, 11.9, 13, 15, 16, 18, 24 and 25.

18. Switching provider and data portability (EU Data Act)

18.1 Scope. This Article 18 implements Chapter VI (Articles 23 to 31) of the Data Act for the Service as a data processing service. It applies to all Customers regardless of their Plan and prevails over other provisions of these Terms. It does not apply to Beta Features made available on a non-production basis for a limited period for testing and evaluation (Article 31(2) of the Data Act).

18.2 Switching request. The Customer may at any time request that Voidhash: (a) enable it to switch to the service of another provider; (b) port its Exportable Data and digital assets to its own infrastructure (including a self-hosted deployment of Voidhash Community); or (c) erase its Exportable Data and digital assets (together a "Switching Request"). The Customer submits a Switching Request in the Dashboard or by email to legal@voidhash.com, stating which of the options it chooses and, where known, the date it wishes the notice period to end. A Switching Request is also notice of termination of the Contract, which ends in accordance with Article 18.11.

18.3 Notice period. The notice period for a Switching Request ends on the date chosen by the Customer, which may not be later than 2 months after Voidhash receives the request; if the Customer does not choose a date, it ends 30 days after receipt. During the notice period the Service continues to be provided in accordance with the Contract and the Customer may already export data.

18.4 Transitional period. After the notice period, a transitional period of up to 30 calendar days begins, during which Voidhash will:

(a) complete the switching or porting process, using the export tools and interfaces of the Service;
(b) provide reasonable assistance in the switching process, including to the destination provider where the Customer so requests;
(c) act with due care to maintain business continuity and continue to provide the functions and services under the Contract;
(d) provide clear information about known risks to the continuity of the Service; and
(e) maintain a high level of security throughout the switching process, in particular for data in transit and against unauthorised access.

18.5 Technical unfeasibility. If the 30-day transitional period is technically unfeasible, Voidhash will notify the Customer within 14 Business Days of receiving the Switching Request, give reasons and propose an alternative transitional period not exceeding 7 months. Business continuity will be maintained throughout the alternative period, and the charges applicable to that period will be the same as before.

18.6 Extension. The Customer may extend the transitional period once, for a period it considers more appropriate for its own purposes, by notice given before the transitional period ends.

18.7 Exportable Data. "Exportable Data" means the input and output data, including metadata, directly or indirectly generated or co-generated by the Customer's use of the Service, excluding the data in Article 18.8. It comprises the following categories of data and digital assets, which form an exhaustive list:

(a) Account, Organization and Project data, Authorized Users and their roles, and the audit log;
(b) End User (person) records: identifiers (distinct and anonymous IDs), traits, email and name if submitted, cohort memberships, experiment and feature-flag assignments;
(c) analytics Events with their properties and context;
(d) purchase, transaction and subscription records, Platform transaction data received by the Service, Entitlement states and their history, and revenue records;
(e) product, offering, Entitlement and placement configuration;
(f) paywalls, flows, Components published or created by the Customer, and assets (images, fonts, files) uploaded by the Customer;
(g) experiment, feature-flag and cohort definitions;
(h) push notification configuration, device push tokens and delivery history;
(i) webhook configuration and delivery history; and
(j) other Customer Content.

The Data portability register, which Voidhash keeps up to date, specifies the data within each category, the formats and export methods (for example the API in JSON, file exports and paywall definitions in JSON), the procedures, and known limitations and technical restrictions. Where the register marks a category as available "on request" because no self-service export exists yet, Voidhash will provide that data on the Customer's request, free of charge, in a structured machine-readable format (JSON), within the transitional period. The API is available to the Customer free of charge for the purposes of switching.

18.8 Data excluded from export. The following data is specific to the internal functioning of the Service and is excluded from export because its disclosure would endanger Voidhash's trade secrets, intellectual property or the security of the Service: (a) the non-public source code of the Service, its internal data models, algorithms and configuration; (b) Aggregated Data and benchmarks; (c) fraud, abuse and risk signals and models; (d) security logs, telemetry and other Service Data; and (e) Components published by other Publishers, which remain subject to their own licences. For security reasons, Platform credentials, API keys and secrets stored in the Service (for example App Store keys or service-account files) are not exported in readable form; the Customer holds the originals and can issue new ones with the Platform Provider.

18.9 Retrieval period. After the end of the transitional period (or, where the Contract ends otherwise than under this Article 18, after it ends), the Customer may retrieve its Exportable Data for at least 30 days ("Retrieval Period").

18.10 Erasure. After the Retrieval Period, or earlier at the Customer's request once the switching process has been successfully completed, Voidhash will fully erase all Exportable Data and digital assets generated directly by the Customer or relating directly to it, and will confirm the erasure to the Customer. Copies in backups are deleted on their regular rotation and are not used in the meantime. Data that Voidhash must retain by law (for example accounting records) and Voidhash's own data under Article 18.8 are not affected.

18.11 End of the Contract. Where a Switching Request has been made, the Contract ends, and Voidhash will notify the Customer of its end: (a) on the successful completion of switching or porting; or (b) at the end of the notice period, where the Customer requested erasure only. Articles 18.9 and 18.10 continue to apply.

18.12 Customer cooperation. The Customer is responsible for its contract with the destination provider, for preparing its Customer Applications for the switch (for example releasing app versions with a new SDK) and for changing the server notification endpoints at the Platforms. Voidhash's obligations under this Article 18 do not require it to develop new functionality or formats for the destination provider.

18.13 Charges. Voidhash charges no switching or data egress fees and no early termination penalty for a Switching Request on the Free or Grow Plans. Fees for the Service actually provided during the notice and transitional periods remain payable, and prepaid Fees for the period after the Contract ends will be refunded. Early termination fees for a fixed-term Enterprise Plan are stated in the Order Form, if any, and must be proportionate (Article 29 of the Data Act).

18.14 International access. Information on the jurisdiction of the infrastructure used for the Service and on measures against international governmental access to non-personal data is published on the International data access page.

19. Content and the Digital Services Act

19.1 Hosting service. For Customer Content stored at the Customer's request, Voidhash acts as a hosting service provider under the DSA. Voidhash has no general obligation to monitor Customer Content.

19.2 Content restrictions and moderation. The rules on which content and activities are not permitted, the measures Voidhash may take (warning, removal or disabling of content, restriction or suspension of functions, termination of the Contract), the use of automated tools and human review, statements of reasons and the internal complaint-handling procedure are set out in the Acceptable Use Policy, which forms part of these Terms for the purposes of Article 14 of the DSA.

19.3 Notices of illegal content. Anyone may report content in the Service they consider illegal to legal@voidhash.com, providing the information required by Article 16 of the DSA.

19.4 Points of contact. The single point of contact for authorities of the Member States, the European Commission and the European Board for Digital Services (Article 11 of the DSA) is legal@voidhash.com. The single point of contact for recipients of the service (Article 12 of the DSA) is legal@voidhash.com. Communication is possible in Czech and English.

20. Sanctions and export control

20.1 Customer representations. The Customer represents that neither it, nor any of its Affiliates, owners holding 50% or more, managing directors or Authorized Users is a person or entity subject to sanctions of the European Union, the United Nations, the United States (including the OFAC Specially Designated Nationals list) or the United Kingdom, or is located, established or resident in a territory subject to comprehensive sanctions (on the date of these Terms in particular Cuba, Iran, North Korea and the Crimea, Donetsk, Luhansk, Zaporizhzhia and Kherson regions of Ukraine). The Customer shall notify Voidhash without undue delay if this changes.

20.2 Restricted use. The Customer shall not use the Service, and shall not allow it to be used, in breach of sanctions or export control rules, including Council Regulation (EU) No 833/2014 (in particular Article 5n on the provision of software and IT services to the Russian Federation), Council Regulation (EU) No 269/2014, Council Regulation (EC) No 765/2006 concerning Belarus, and US export control law.

20.3 Consequences. If the Customer breaches this Article 20, or if performing the Contract would breach sanctions or export control rules, Voidhash may suspend the Service immediately and terminate the Contract with immediate effect. Voidhash will refund prepaid Fees unless prohibited by law.

20.4 Anti-boycott. This Article 20 applies only to the extent that it does not breach Council Regulation (EC) No 2271/96 (the blocking statute) or other applicable anti-boycott law.

21. Force majeure

21.1 A party is not liable for failure or delay in performing its obligations (other than payment obligations) to the extent caused by circumstances beyond its reasonable control that it could not have foreseen or avoided, in particular natural disasters, epidemics, war, terrorism, civil unrest, acts of public authorities, changes in sanctions, power or telecommunications failures, large-scale cyberattacks despite reasonable security measures, and outages or changes of Platforms (such as Apple, Google or Stripe) and of the infrastructure providers on which the Service depends, unless the failure of such a provider was caused by the affected party.

21.2 The affected party shall notify the other party without undue delay and take reasonable steps to limit the consequences. If the force majeure event continues for more than 60 days, either party may terminate the Contract by notice; Voidhash will refund prepaid Fees for the period after termination.

22. Changes to these Terms

22.1 Reasons for changes. Voidhash provides the Service to a large number of customers under the same terms, on a long-term basis, and the nature of the Service makes it reasonably necessary to change these Terms in the future (Section 1752 of the Civil Code). Voidhash may change these Terms (including the AUP and, where the DPA so allows, the DPA) in particular due to: (a) changes in legislation, case law or decisions of authorities; (b) changes in the terms or technical requirements of Platform Providers or infrastructure providers; (c) security reasons; (d) the introduction of new features, Plans or services, or changes to or discontinuation of existing ones; (e) changes in Voidhash's business model or pricing; and (f) the need to clarify ambiguities or correct errors.

22.2 Notice. Voidhash will notify the Customer of any change by email to the Account owner and in the Dashboard at least 30 days before the change takes effect, together with a summary of the changes and the new wording.

22.3 Urgent changes. Changes required by law, a decision of an authority or an urgent security need may take effect earlier if necessary, of which Voidhash will inform the Customer in the notice. Changes that are exclusively to the Customer's benefit (for example new features or lower prices) or purely editorial may take effect on publication.

22.4 Right to reject. If the Customer does not agree with the change, it may reject it and terminate the Contract free of charge by notice delivered before the change takes effect. The Contract then ends on the day before the change takes effect, or on an earlier date specified by the Customer, and Voidhash will refund prepaid Fees for the period after termination. The Customer retains its rights under Article 18. The parties agree that a period of 30 days is sufficient for the Customer to obtain comparable services from another provider.

22.5 Acceptance. If the Customer does not reject the change before it takes effect, or continues to use the Service after that date, the change is deemed accepted.

22.6 Order Forms. Changes to these Terms do not change terms individually negotiated in an Order Form during its fixed term, unless the change is required by law or the Order Form provides otherwise.

23. Notices and communication

23.1 Voidhash sends notices under the Contract to the email address of the Account owner (and, for Enterprise Plans, the contact in the Order Form) and, where appropriate, in the Dashboard. The Customer sends notices to legal@voidhash.com; routine operational and billing communication goes to support@voidhash.com.

23.2 The written form is also satisfied by email and other electronic communication enabling the content and the sender to be identified (Section 562 of the Civil Code). Order Forms and their amendments require the electronic acceptance or signature of both parties.

23.3 An email notice is deemed delivered on the Business Day following its sending, unless the sender receives a notice that it was not delivered. The Customer is responsible for keeping the Account owner's email address functional and monitored.

23.4 Voidhash may send the Customer service and transactional messages (such as security notices, changes, invoices and usage alerts) as part of the Service. Commercial communications are governed by the Privacy Policy and may be unsubscribed from at any time.

24. Assignment and subcontracting

24.1 The Customer may not assign the Contract or any rights or obligations under it without Voidhash's prior written consent.

24.2 The Customer agrees in advance (Section 1895 of the Civil Code) that Voidhash may assign the Contract to an Affiliate or to a successor in connection with a merger, sale of all or part of its business or similar transaction, by notice to the Customer. If the Customer has a justified objection, it may terminate the Contract free of charge within 30 days of the notice.

24.3 Voidhash may assign its receivables under the Contract to third parties.

25. Governing law, disputes and language

25.1 Governing law. The Contract and all non-contractual obligations arising from it are governed by the laws of the Czech Republic, excluding its conflict-of-law rules and the United Nations Convention on Contracts for the International Sale of Goods (CISG).

25.2 Amicable resolution. The parties will first try to resolve any dispute amicably. A party may bring court proceedings if the dispute has not been resolved within 30 days of written notice of the dispute; this does not prevent applications for interim measures or steps needed to prevent a claim from becoming time-barred.

25.3 Courts. The courts of the Czech Republic having jurisdiction according to Voidhash's registered office in Prague shall have exclusive jurisdiction (Section 89a of Act No. 99/1963 Coll., the Code of Civil Procedure, and Article 25 of Regulation (EU) No 1215/2012). Voidhash may also bring proceedings against the Customer at the courts of its seat.

25.4 Language. These Terms are made in Czech and English. For Customers with their registered office or place of business in the Czech Republic, the Czech version prevails in case of discrepancy; for all other Customers, the English version prevails.

26. Precedence and final provisions

26.1 Precedence. In case of conflict, the documents forming the Contract apply in this order: (a) the Order Form; (b) the DPA, as regards the processing of personal data (and within it the standard contractual clauses); (c) Article 18 of these Terms; (d) the remaining provisions of these Terms; (e) the AUP; (f) the Documentation.

26.2 Customer's terms excluded. The Customer's own business or purchasing terms do not apply, even if referred to in an order, purchase order or other communication, or attached to an invoice; Section 1751(2) of the Civil Code is excluded. Purchase orders issued by the Customer for its internal purposes do not change the Contract.

26.3 Exclusion of certain statutory provisions. The parties, as businesses, agree that:

(a) an acceptance containing any amendment or deviation, however minor, is not an acceptance of the offer (Section 1740(3) of the Civil Code does not apply);
(b) trade usages do not take precedence over provisions of law that are not mandatory (Section 558(2) of the Civil Code does not apply);
(c) Sections 1799 and 1800 of the Civil Code on adhesion contracts do not apply (Section 1801 of the Civil Code);
(d) each party assumes the risk of a change of circumstances under Section 1765(2) of the Civil Code, and Section 1766 of the Civil Code does not apply.

26.4 Entire agreement. The Contract constitutes the entire agreement of the parties on its subject matter and supersedes all prior proposals, negotiations and communications. Statements in marketing materials do not form part of the Contract unless the Contract refers to them.

26.5 Severability. If any provision of the Contract is or becomes invalid, ineffective or unenforceable, the other provisions remain in effect, and the parties will replace the affected provision with a valid one that comes as close as possible to its purpose. Where a limitation of liability is invalid in part, it applies to the maximum extent permitted by law.

26.6 No waiver. A failure or delay in exercising a right does not constitute a waiver of that right.

26.7 Independent parties. The parties are independent contractors. The Contract creates no partnership, joint venture, agency or employment relationship and confers no rights on third parties, including End Users.

26.8 Effective date. These Terms take effect on 14 October 2026. Previous versions are available on request at legal@voidhash.com.