Beta / Evaluation Agreement

This Beta / Evaluation Agreement governs your access to Zynth Auth (the "Service") during its private beta. It applies in addition to our Terms of Service, Privacy Policy and Data Processing Addendum. Where it and any of those differ, this agreement governs for the duration of the beta.

Access is by invitation only and is personal to your organization. You may not transfer it, share credentials outside your organization, or use it to provide the Service to a third party.

The Service is offered for business and professional use, not to consumers, and evaluation is at no charge. Nothing here obliges either of us to enter a paid agreement afterwards.

Private beta, AI-first operations. Zynth Auth is built and operated with AI agents in the loop and may change or be interrupted without notice. It carries no service level during the beta. Back up your own data; Zynth does not guarantee its retention during the beta.

Concretely: features may be added, changed, or removed without notice; interfaces may break between releases; data may be migrated, and in a reset environment may not be preserved; and defects are expected — that is what the evaluation is for.

No service level applies during the beta. Our Service Level Agreement — its uptime commitment, its measurement, and its service-credit remedy — does not apply to beta access, and no credit accrues. Because the beta is free of charge, the credit remedy would in any event have nothing to compute against.

We do not commit to availability, maintenance windows, response times, or a support channel during the beta. We will make reasonable efforts, and we will tell you when we plan an interruption we know about in advance.

The Service is provided "AS IS" and "AS AVAILABLE" during the beta, without warranty of any kind — express, implied, or statutory — including any warranty of merchantability, fitness for a particular purpose, non-infringement, accuracy, or uninterrupted or error-free operation, to the fullest extent permitted by law.

In particular, we give no warranty that the platform's automated detection, containment, or response identifies every threat, or that any specific finding is correct. Detection is a control, not a guarantee.

Zynth Auth is not recommended as your sole production control during the beta. Do not make it the only thing standing between an attacker and a system that matters, and do not make it the only path by which your people or services can obtain access.

• Keep an independent way to authenticate and to reach your own systems if the Service is unavailable — a break-glass path that does not depend on us.
• Where the platform takes an automated protective action — containment, quarantine, throttling, an agent kill switch — keep a human-owned route to reverse it on your side.
• Treat findings as input to your own security process, not as a substitute for it.
• Prefer non-production or replica data while evaluating, and load only the personal data you actually need to test with.

You remain responsible for your own security programme and for regulatory obligations that attach to your systems. Evaluating our platform does not transfer either.

You are responsible for maintaining your own backups and exports of any data you place in the Service. We do not guarantee retention of your data during the beta, and a reset environment may not be recoverable.

The platform's data-protection tooling and its API let you extract identities, memberships, configuration, and access records at any time. Use them on a schedule that matches how much the data matters to you.

Feedback is the point of the beta. If you give us feedback — bug reports, feature requests, evaluations, benchmarks, or suggestions of any kind — you grant Zynth Media Technology a perpetual, irrevocable, worldwide, royalty-free, sublicensable licence to use, reproduce, modify, and incorporate it into our products and documentation, without restriction and without obligation to you.

You give feedback voluntarily; we are under no obligation to act on any of it, and we may develop something similar independently. Please do not include your confidential information, personal data, credentials, or third-party material in feedback — send us a reference to it instead, and we will arrange a secure channel.

Feedback is not confidential to you, and we may act on it publicly. Nothing here transfers ownership of your own products, data, or trade marks.

During the beta you will see things that are not public. Non-public features, unreleased functionality, roadmap, pricing not yet announced, performance and benchmark results, architecture and security details you learn through your access, and the existence and content of defects you find are our confidential information.

• Use it only to evaluate the Service, and disclose it only to your own people who need it and are bound to keep it confidential.
• Do not publish screenshots, benchmarks, or public comparisons of non-public features without our written consent.
• This does not restrict information that is or becomes public through no act of yours, that you already had, that you develop independently, or that you receive lawfully from someone else.
• If you are legally compelled to disclose, tell us first where you lawfully can, so we can seek protection.

These obligations last for three years after your beta access ends. Nothing in this section prevents you from reporting a security vulnerability to us under our Vulnerability Disclosure Policy, or from disclosing that you participated in the beta.

We may modify, suspend, or discontinue the beta — in whole, or for your organization — at any time, and we may reset or delete beta environments and the data in them.

Except where we must act immediately for security, legal, or abuse reasons, we will give you at least 14 days’ notice before ending your access or wiping an environment, sent to the administrative contact on record for your organization.

After that notice you have an export window of at least 30 days from the date of the notice in which to retrieve your data through the platform's tooling and API. We will help you export if the tooling cannot reach something you need. Once the window closes we may delete the environment and its data permanently, and we are not obliged to retain a copy.

You may stop participating at any time, for any reason, by telling us. Ending your participation ends your access; the feedback licence, the confidentiality obligations, and the disclaimers and limits above survive.

Where we suspend or contain your environment immediately for a security or abuse reason, we will tell you as soon as we reasonably can and, unless the law or the nature of the incident prevents it, still give you an opportunity to export.

The limitations and exclusions of liability in our Terms of Service apply to beta access in full. Because the beta is provided at no charge, any cap expressed as fees paid is effectively nil — which is the bargain: you get the Service for nothing, and it comes with no assurances.

Nothing in this agreement excludes liability that cannot lawfully be excluded, including for death or personal injury caused by negligence, or for fraud.

We may revise this agreement during the beta. Material changes are notified to the administrative contact on record and take effect on the date stated in that notice; continuing to use the Service after that date is acceptance. If you do not accept a change, stop using the Service and tell us, and the export window above applies.