Beta & Early Access Terms

VERA ships features early so customers can shape them. Anything labelled beta, preview, or early access in the product is covered by these terms, which sit on top of the Terms of Service and take precedence over them for those features only. VERA does not currently run a separate enrolled beta program with its own application process; beta features appear in the product for the accounts they are enabled for.

Version
1.0
Effective
July 28, 2026
Last updated
July 28, 2026
Revisions
1
On this page (5 sections)
  1. 1. What counts as a beta feature
  2. 2. What to expect
  3. 3. Your obligations
  4. 4. Data and privacy in beta
  5. 5. Graduation and withdrawal

1. What counts as a beta feature

A feature is covered by these terms when it is marked in the interface or in release notes as beta, preview, early access, or experimental. If a feature is not marked, the ordinary Terms of Service apply to it.

A demonstration or mock mode is not a beta feature. Where VERA is running a connector against sample data because no real credential is configured, that is labelled as such and produces no external effect.

2. What to expect

Beta features are provided as is, without any warranty, and without the availability expectations that apply to the rest of the Service. They may be incomplete, may behave inconsistently, may lose data written through them, and may be changed, restricted, or removed at any time without notice and without compensation.

Beta features may not have the documentation, support coverage, or accessibility work that generally available features have. Do not adopt one for a process where failure would harm your business without keeping an independent record.

Credits consumed by a beta feature are consumed normally. If a beta defect causes a failed generation, contact support and we will look at restoring the credits.

3. Your obligations

You may not publicly benchmark a beta feature or publish screenshots of unreleased functionality without our written permission, and you must not describe a beta feature as a generally available VERA capability to your own customers.

Feedback you give about a beta feature is voluntary and may be used freely by VERA without obligation to you, as set out in the Terms of Service.

4. Data and privacy in beta

The Privacy Policy, the Data Processing Addendum, and the security controls described in the Security Policy apply to beta features exactly as they apply to the rest of the Service. Beta status never lowers the standard for how your data is handled.

If a beta feature would introduce a new subprocessor or a new category of data, we will list it on the Subprocessor List before the feature is enabled for you.

5. Graduation and withdrawal

When a beta feature becomes generally available, these terms stop applying to it and the ordinary Terms of Service take over.

If a beta feature is withdrawn, we will make a reasonable effort to give notice and to make any data created through it exportable or visible elsewhere in the product before it is removed.

Change history

Every revision of this document, newest first. Material changes are notified to account holders before they take effect where practicable.

  1. v1.0July 28, 2026

    Initial Beta & Early Access Terms published.

Questions about this document?

Legal and contracts: support@myvera.io. Privacy and data rights: support@myvera.io. Security reports: support@myvera.io.

Related

This document is a carefully drafted policy written against how VERA actually works. It is not legal advice, and it should be reviewed by a licensed attorney in your jurisdiction before you rely on it.