Capydox Beta Features Terms
Specific terms governing access to Capydox beta, preview and experimental features.
Last updated: May 21, 2026
Capydox Beta Features Terms
Last updated: 21/05/2026
These Beta Features Terms (the "Beta Terms") govern your participation in beta, preview, early access or experimental Capydox features (collectively, "Beta Features").
Beta Features are optional and supplement the public Capydox Terms of Service and other legal documents.
1. Definition of Beta Features
"Beta Features" include any features, modules, integrations or versions of the Service that:
- Are labelled in the interface or documentation as "beta", "preview", "pre-release", "experimental" or similar; or
- Are offered to a limited set of customers for testing and feedback before general availability.
Capydox may determine at any time which features are considered Beta and when they cease to be Beta.[web:132]
2. Voluntary participation and scope of use
2.1 Optional participation
Access to Beta Features is optional. You may opt in (or request access) and may discontinue use at any time, unless otherwise stated in a specific beta program.
2.2 Limited purpose
Beta Features are provided solely for your internal use for testing, evaluation and feedback, and are not intended for production-critical workloads.
2.3 Not suitable for mission‑critical use
Given their experimental nature, Beta Features are not recommended for mission‑critical systems or use cases where failure could cause significant harm. You are responsible for assessing suitability for each use case.[web:138]
3. "As is" status and warranty disclaimer
3.1 No warranties
Beta Features are provided "as is", without warranties of any kind, whether express, implied or statutory, including but not limited to implied warranties of merchantability, fitness for a particular purpose, non‑infringement, or uninterrupted or error‑free operation.[web:136][web:138]
3.2 Changes and removal
Capydox may change, limit, suspend or discontinue any Beta Feature at any time, without obligation to maintain backwards compatibility or to release the Beta Feature as a generally available product.
3.3 No roadmap commitment
Participation in a beta program and related communications do not constitute any commitment by Capydox to commercially release the Beta Feature or to include specific functionality in the generally available product.[web:132]
4. Service levels, support and data
4.1 SLA exclusion
Unless expressly agreed otherwise, the Capydox SLA does not apply to Beta Features. This means:
- No uptime or response time commitments specifically apply to Beta Features.
- Incidents related solely to Beta Features may be excluded from uptime calculations.
4.2 Best-effort support
Support for Beta Features is provided on a best‑effort basis. Capydox may prioritise issues affecting security or the stability of the overall Service and does not guarantee response or resolution times.
4.3 Data risks
Due to their experimental status, Beta Features may contain bugs, cause unexpected failures, or behave differently from stable parts of the Service, which could result in:
- Loss, corruption or inconsistency of data.
- Partial or incomplete outputs.
You are responsible for maintaining appropriate backups and for not relying solely on Beta Features to store or process data without reasonable recovery options.
5. Feedback and usage data
5.1 Customer feedback
Capydox may request or receive comments, suggestions, bug reports or improvement ideas related to Beta Features ("Feedback"). You agree that Capydox may use such Feedback:
- To improve Beta Features and the Service.
- To develop new features or services.
Without creating any additional IP rights for you or any obligation to compensate you.[web:139]
5.2 Aggregated usage data
Capydox may collect aggregated, anonymised technical and usage data relating to Beta Features to analyse performance, stability and adoption, in line with the Privacy Policy.
6. Confidentiality and communications
6.1 Confidential nature
Unless otherwise indicated, Beta Features and related information (for example documentation, screenshots, roadmap details) may be considered confidential information of Capydox. You agree not to disclose such information publicly without Capydox's permission.
6.2 References
Capydox may ask for your permission to reference your participation in a beta program as a case study or testimonial; such use will be subject to a separate written agreement where applicable.
7. Liability
7.1 Specific limitation for Beta Features
To the maximum extent permitted by law, Capydox will not be liable for any indirect, special, incidental or consequential damages, loss of profits, loss of data not properly backed up, or reputational harm arising from or in connection with your use of Beta Features.[web:139]
7.2 Aggregate liability
Any aggregate liability of Capydox arising directly and exclusively from Beta Features will, if applicable, be counted towards and limited by the general liability cap set out in the Terms of Service or applicable Enterprise agreement.
8. Termination of Beta access
8.1 Termination by Capydox
Capydox may suspend or revoke your access to any Beta Feature at any time, with or without cause, and without any compensation beyond any rights you have under your main subscription.
8.2 Opting out
You may stop using Beta Features at any time by disabling them or by requesting removal. Capydox may provide reasonable data export mechanisms depending on the nature of the Beta Feature.
8.3 End of beta
Once a beta program ends:
- Access to the Beta Feature may cease.
- Any replacement or generally available version will be governed by the Terms of Service, SLA and other applicable documents.
9. Relationship with other documents
These Beta Terms are part of the Capydox legal documentation and must be read together with:
- The Capydox Terms of Service.
- The Privacy Policy and Cookie Policy.
- The DPA and SLA, where applicable.
In case of conflict specific to Beta Features, these Beta Terms prevail over the general Terms of Service for the matters they expressly govern.