Beta and Early Access Terms (a PST)

Effective Date:

SKRIB, INC.

Beta and Early Access Terms

A Product-Specific Term | Effective Date: 26 May 2026 | Last Updated: 26 May 2026

These Beta and Early Access Terms (the “Beta Terms”) are a Product-Specific Term under the Skrib Terms of Service and the Skrib Software Services Agreement and govern your access to and use of any Skrib feature, capability, integration, model, or service that Skrib designates as “alpha,” “beta,” “early access,” “pilot,” “preview,” or “experimental” (collectively, the “Beta Features”). Capitalised terms used and not defined here have the meanings given in the Terms or SSA.

In the event of conflict between these Beta Terms and the Terms or SSA with respect to a Beta Feature, these Beta Terms prevail.

1. AS-IS and AS-AVAILABLE

Beta Features are made available for testing, evaluation, and feedback. They may be incomplete, contain bugs, behave unexpectedly, lose data, or be withdrawn at any time. To the fullest extent permitted by applicable law, Beta Features are provided on an “AS IS” and “AS AVAILABLE” basis, without warranties or representations of any kind, whether express, implied, statutory, or otherwise.

The disclaimers, limitations of liability, and indemnity provisions in the Terms or SSA apply to your use of Beta Features. The cap on Skrib’s aggregate liability for Beta Features is the lesser of (i) the cap that applies under the Terms or SSA and (ii) US$100, except where applicable law does not permit such limitation.

2. No service-level commitments

No service-level commitment, uptime guarantee, or support entitlement that may apply to Skrib’s generally available Services applies to Beta Features. Skrib provides support for Beta Features on a reasonable-efforts basis only.

3. Skrib may change or withdraw a Beta Feature at any time

Skrib may, at any time and without liability except as required by applicable law:

introduce, modify, expand, or limit any Beta Feature;

change the eligibility criteria, usage limits, or availability of any Beta Feature;

require participation in Beta Feature-specific feedback, surveys, or interviews as a condition of continued access;

convert a Beta Feature into a generally available, paid, or premium feature, or discontinue it without conversion;

delete data and configuration associated with a Beta Feature on withdrawal, with reasonable advance notice where practicable; and

revoke a particular user’s access to a Beta Feature at any time.

4. Confidentiality

Beta Features, related documentation, performance information, error reports, screenshots, recordings, and any non-public information about a Beta Feature (collectively, “Beta Information”) are Skrib’s confidential information. You may use Beta Information only to evaluate and use the Beta Feature in accordance with these Beta Terms, and you must not disclose Beta Information to any third party without Skrib’s prior written consent, except to your employees, contractors, and advisers who need to know in connection with your evaluation and who are bound by confidentiality obligations no less protective than those in this Section.

Confidentiality obligations under this Section continue for two (2) years after termination of your access to the Beta Feature; obligations relating to trade secrets continue for so long as the information remains a trade secret under applicable law.

5. Feedback

Skrib welcomes feedback on Beta Features (bug reports, feature requests, usability observations, integration ideas) (“Feedback”). To the extent that you provide Feedback, you grant Skrib a worldwide, perpetual, irrevocable, non-exclusive, royalty-free licence to use, reproduce, modify, adapt, publish, distribute, and otherwise exploit that Feedback for any lawful business purpose, without compensation or obligation, provided that Skrib will not publicly identify you as the source of Feedback without your consent unless otherwise permitted by law.

6. Data, content, and migration

Some Beta Features process User Content. Where this is the case, the Privacy Policy, the Cookie Policy, and the DPA (where applicable) apply. You should not submit User Content to a Beta Feature that is critical to your business or that you are not in a position to lose. Skrib does not commit to migrating data from a Beta Feature to a generally available successor, or to any other long-term retention or backup.

7. AI Beta Features

Where a Beta Feature uses AI, the AI Terms at https://skrib.com/legal/ai-terms and the Acceptable Use Policy at https://skrib.com/legal/aup apply. AI Beta Features may be more prone than generally available AI Features to inaccuracy, hallucination, bias, or unsuitability for a particular use case. The AI output IP indemnity in the AI Terms does not apply to outputs generated through AI Beta Features.

8. Eligibility and access

Skrib may make Beta Features available only to selected users, customers, or regions. Skrib may apply additional eligibility criteria (plan type, geographic location, compliance status). Beta Features may not be available in all jurisdictions or for all use cases. Skrib may withdraw access at any time.

9. Term and termination

Your access to a Beta Feature begins when Skrib enables it for you and continues until the earlier of (i) Skrib withdrawing the Beta Feature; (ii) the Beta Feature graduating to general availability; (iii) Skrib revoking your access; (iv) you discontinuing use; and (v) termination of the Terms or SSA. Sections 1 (AS-IS / AS-AVAILABLE), 4 (Confidentiality), and 5 (Feedback) survive termination.

10. Contact

Beta-programme contact: contact@skrib.com | Legal: contact@skrib.com | Privacy / DPO: contact@skrib.com.