Beta and Preview Features Terms
CIQRA OÜ · Version 1.1 · Last updated: 3 November 2026
These Beta and Preview Features Terms are issued by CIQRA OÜ, a private limited company registered in Estonia under registry code 16465907, with its registered address at Veskiposti tn 2, 10138 Tallinn, Harju maakond, Estonia ("CIQRA", "we", "us", "our"). They elaborate Section 6.3 of the Terms of Service and supplement the Merchant Agreement and the AI Features Terms. Terms defined in the Terms of Service ("Services", "Merchant", "Storefront", "Merchant Content", "Order Form", "Policies") have the same meaning here.
Effective date. This document applies to new customers from its publication on 3 November 2026. It applies to existing customers on the date stated in CIQRA's notice, which is at least 30 days after the notice (Terms of Service Section 14.2).
Contact: info@ciqra.com
1. Scope and definitions
1.1 Beta Features. A "Beta Feature" is any feature, integration, app, theme, tool, API, model or other part of the Services that CIQRA designates, in the dashboard, in the documentation or in a message, as beta, preview, early access, pilot, experimental, alpha, "coming soon", labs or by a similar word, or that CIQRA makes available before general availability.
1.2 Free-of-Charge Features. A "Free-of-Charge Feature" is a Beta Feature or any other feature or service that CIQRA makes available to a Merchant for no fee and that is not part of what the Merchant pays for under its plan or Order Form (for example a pilot, an add-on offered without charge for a limited time, or a pre-release component). A feature that is part of the plan the Merchant pays for is not a Free-of-Charge Feature merely because it is also labelled beta.
1.3 No free plan or free trial. CIQRA has no free plan and no free trial. Access to a Beta Feature does not create a free plan, a free trial or a right to any Service without the subscription fee that applies. A Beta Feature is available only to Merchants that hold a paid subscription, unless CIQRA states otherwise in writing.
1.4 Order of precedence. For a Beta Feature, these terms apply as a Policy under Section 1.6 of the Terms of Service, ranked under Section 1.5, and prevail over the Terms of Service only on the matters in Sections 2 to 9 of this document; Sections 13 to 16 of the Terms of Service are not affected. Terms stated for a particular Beta Feature in its documentation, in the dashboard or in a notice that CIQRA gives you prevail over these terms, but only to the extent that they do not reduce the protections in Sections 5.5 and 9.4.
2. Access
2.1 Opt-in and default. CIQRA may offer a Beta Feature by invitation, by a switch in the dashboard or by enabling it for a store. Where the dashboard offers a switch, the Merchant may turn the Beta Feature off at any time. A Merchant that uses a Beta Feature agrees to these terms for that feature.
2.2 Eligibility and limits. CIQRA may limit a Beta Feature to selected Merchants, plans, markets or volumes, may change who may use it, and may set usage limits.
2.3 Not for critical use. A Merchant should not rely on a Beta Feature for anything that its business, its Shoppers or the law cannot do without. A Merchant should test it first, keep its own backups and exports of data that the feature touches, and keep a fallback.
2.4 Special categories of data. A Merchant must not use a Beta Feature to process special categories of personal data (such as health data), payment card numbers, or other data whose loss or disclosure would be especially serious, unless the feature's documentation expressly allows it.
3. "As is" and changes
3.1 As is. To the maximum extent permitted by law, a Beta Feature is provided "as is" and "as available". It may have errors, be incomplete, behave differently from its documentation, be slower or less secure than a general-availability feature, and lose or alter data. CIQRA gives no warranty about it, including of fitness for a purpose, accuracy, reliability, non-infringement or availability.
3.2 Change and withdrawal. CIQRA may change, limit, suspend or withdraw a Beta Feature at any time, including by ending the beta without launching the feature. A Beta Feature is not a committed feature of the Merchant's plan, so the notice and credit rules in Section 3.6 of the Terms of Service for removing a feature of a paid plan do not apply to it. CIQRA will nevertheless give the Merchant notice by email or in the dashboard, which is at least 14 days where practicable, and as much notice as it can where the change is urgent (for example for security, legal or third-party reasons).
3.3 No surprise charges. CIQRA will not start charging for a Beta Feature that the Merchant has been using without charge unless it first tells the Merchant the price, gives at least 30 days' notice, and the Merchant accepts the charge in the dashboard or in writing. If the Merchant has not accepted it by the effective date, CIQRA switches the feature off for the Merchant and does not charge for it.
3.4 Migration to general availability. A Beta Feature that becomes generally available may differ from the beta in function, limits, price and terms. The general-availability terms apply from the date stated in CIQRA's notice.
4. No service levels
4.1 No uptime, no credits, no support commitment. No service level applies to a Beta Feature. It is not covered by any availability or response commitment, including the targets in Section 8 of the Terms of Service and the Enterprise Service Level Agreement, and its unavailability gives no right to service credits or to a refund. A Beta Feature is excluded from the measurement of Downtime under Section 3 of the Enterprise Service Level Agreement.
4.2 Support. CIQRA may give support for a Beta Feature as a courtesy but is not obliged to, and gives no response time. Reports of faults and security problems are welcome at info@ciqra.com.
5. Data, privacy and security
5.1 Data protection continues to apply. CIQRA processes personal data in a Beta Feature under the Data Processing Agreement and the Privacy Policy, unless the Beta Feature's documentation states a different arrangement before the Merchant starts to use it.
5.2 Providers. A Beta Feature may use a provider or technology that is not yet in the Subprocessor List. CIQRA will not send the Merchant's personal data to a new sub-processor in a Beta Feature without following the notice procedure of the Data Processing Agreement for new sub-processors.
5.3 AI. A Beta Feature that uses AI is also governed by the AI Features Terms. AI output may be wrong, and the Merchant must review it before it publishes or relies on it (Terms of Service Section 9.2).
5.4 Loss of data. The Merchant is responsible for keeping copies of data it puts into, or generates with, a Beta Feature. If CIQRA ends a Beta Feature, the data that the feature holds may be deleted, and CIQRA will, where practicable, give the Merchant a means and a reasonable time to export it. On an Enterprise plan, CIQRA does not delete the Merchant's own records that a Beta Feature holds: before ending the feature, CIQRA moves them to the Merchant's store data or gives the Merchant an export, and Section 9.6 of the Data Processing Agreement applies to them.
5.5 What does not change. Nothing in this document reduces the rights of data subjects or the duties CIQRA has as a processor or controller under data-protection law, or a Merchant's right to export its Merchant Content under Section 13.3 of the Terms of Service.
6. Feedback
6.1 CIQRA may ask the Merchant for feedback and reports on a Beta Feature, which the Merchant may give but need not. Section 5.5 of the Terms of Service applies: CIQRA may use feedback, ideas and suggestions without restriction, payment or attribution, and the Merchant grants CIQRA a worldwide, perpetual, irrevocable, royalty-free licence for that purpose. This does not give CIQRA any right in the Merchant's Merchant Content, trade secrets or personal data, which are not feedback.
7. Confidentiality of non-public betas
7.1 What is confidential. A Beta Feature that CIQRA has not announced publicly, and non-public information about it (including its existence, functions, performance, documentation, roadmap and the results of tests), is CIQRA's Confidential Information if CIQRA designates it as confidential, or a reasonable business would understand it to be. CIQRA says so when it invites a Merchant to a non-public beta.
7.2 Duties. The Merchant uses that information only to evaluate and use the Beta Feature for its own business, protects it with at least reasonable care, discloses it only to staff and advisers who need to know it and are bound by confidentiality, and does not publish screenshots, benchmarks or reviews of it or tell the press or competitors about it without CIQRA's written consent.
7.3 Exceptions and term. The duties do not apply to information that becomes public through no fault of the Merchant, that the Merchant already knew or developed independently, or that law requires it to disclose (after telling CIQRA first where lawful). They continue until the information becomes public, or for two years after the Merchant's access ends, if earlier.
8. Ending use
8.1 The Merchant may stop using a Beta Feature at any time. CIQRA may end a Merchant's access to a Beta Feature at any time, for any reason, and in particular for breach of these terms, misuse, a security risk or a legal requirement. Section 7.2 of the Terms of Service applies to a suspension of the Services, and this Section applies to access to a Beta Feature only. Ending a Beta Feature does not end the Merchant's subscription or its other Services.
9. Liability
9.1 Terms of Service apply. Sections 10, 11 and 12 of the Terms of Service apply to Beta Features, with the additions in this Section.
9.2 Beta Features that are part of a paid plan. For a Beta Feature that is included in what the Merchant pays for, CIQRA's liability is subject to Section 11 of the Terms of Service, including its cap, and CIQRA owes no service credit or other remedy for a defect that is typical of a beta.
9.3 Lower cap for Free-of-Charge Features. To the maximum extent permitted by law, CIQRA's total aggregate liability to a Merchant arising out of or in connection with all Free-of-Charge Features in any 12-month period is limited to EUR 100. This amount is part of, and not in addition to, the cap in Section 11.2 of the Terms of Service. The exclusion of indirect, incidental, special and consequential loss and of loss of profit, revenue, goodwill and anticipated savings in Section 11.1 of the Terms of Service applies to Free-of-Charge Features, subject to Section 9.4. This Section 9.3 applies to a Free-of-Charge Feature that the Merchant switched on itself or joined by invitation; for a Free-of-Charge Feature that CIQRA switched on without the Merchant's act, Section 9.2 applies.
9.4 What is never limited. Nothing in this document excludes or limits liability for intent, for gross negligence, for death or personal injury, for fraud, or for anything that cannot be excluded or limited by law, or affects the rights of data subjects and the statutory rights of consumers. In those cases the EUR 100 limit in Section 9.3 does not apply.
9.5 Merchant's indemnity. Section 12.1 of the Terms of Service applies to the Merchant's use of a Beta Feature, including claims by third parties arising from Merchant Content processed by it.
9.6 Backups and mitigation. The Merchant must take reasonable steps to limit loss, including keeping its own backups and not relying on a Beta Feature for critical use (Section 2.3). CIQRA is not liable for loss that reasonable steps would have avoided.
10. Changes, law and general terms
10.1 Changes. CIQRA may amend this document under Section 14 of the Terms of Service. A change that is to a Merchant's disadvantage takes effect for an existing customer no earlier than 30 days after notice. A change in the terms for a particular Beta Feature is made under Section 3.2.
10.2 Governing law and courts. This document is governed by the laws of the Republic of Estonia, excluding its conflict-of-laws rules and the United Nations Convention on Contracts for the International Sale of Goods. Subject to Section 15.5 of the Terms of Service, disputes between CIQRA and a Merchant are subject to the exclusive jurisdiction of Harju County Court (Harju Maakohus) in Tallinn, Estonia. Section 15 of the Terms of Service applies to disputes under this document, including Section 15.5 for a Merchant established in the United States, and this document does not depart from it.
10.3 Language. This document is drawn up in English, and the English version prevails over any translation, except where mandatory local law requires a version in another language to prevail for that market.
Contact: CIQRA OÜ, Veskiposti tn 2, 10138 Tallinn, Harju maakond, Estonia · info@ciqra.com