Beta / Experimental Features Terms

“Beta Feature” means a feature, product, API, model, integration, workflow, interface, or functionality identified by Asiyst as beta, preview, experimental, early access, testing, research, or otherwise not generally available.

“Experimental Feature” means functionality that Asiyst is evaluating, testing, researching, or developing and that may not be intended for production use.

“Feedback” means suggestions, comments, reports, evaluations, bug reports, or other information you provide regarding a Beta or Experimental Feature.

Access to Beta or Experimental Features may be limited to:

• Certain accounts.
• Selected customers.
• Specific plans.
• Specific projects.
• Geographic regions.
• Approved developers.
• Invitation-only participants.
• Users who meet technical or other requirements.

Access to a Beta or Experimental Feature does not create a right to continued access.

Beta Features may be made available to:

• Test functionality before general availability.
• Evaluate performance and reliability.
• Identify bugs and security issues.
• Gather user feedback.
• Evaluate new AI capabilities.
• Test new integrations.
• Develop new product functionality.
• Determine whether a feature should become generally available.

A Beta Feature may not ultimately become part of the generally available Asiyst Services.

Beta and Experimental Features may be incomplete.

They may contain:

• Bugs.
• Errors.
• Unexpected behavior.
• Performance limitations.
• Interface changes.
• Incomplete functionality.
• Temporary limitations.
• Compatibility issues.
• Incorrect or inconsistent AI output.
• Data-processing limitations.

You should evaluate whether a Beta or Experimental Feature is appropriate for your particular use case before relying on it.

Unless Asiyst expressly states otherwise, Beta and Experimental Features should not be treated as suitable for mission-critical or safety-critical applications.

You should maintain appropriate backups, alternative workflows, and safeguards where loss of access or unexpected behavior could materially affect your operations.

You remain responsible for determining whether the feature is appropriate for production use.

Asiyst may modify Beta or Experimental Features without notice where reasonably necessary.

Changes may include:

• Functionality.
• User interface.
• API behavior.
• Model behavior.
• Performance.
• Usage limits.
• Pricing.
• Availability.
• Data-processing behavior.
• Integration methods.
• Supported configurations.

A Beta Feature may be materially different when you next access it.

Asiyst may suspend or discontinue a Beta or Experimental Feature at any time.

A feature may be discontinued because of:

• Technical limitations.
• Security concerns.
• Product decisions.
• Performance issues.
• Third-party changes.
• Regulatory requirements.
• Insufficient adoption.
• Development priorities.
• Other business or operational considerations.

Discontinuation does not necessarily create a right to a refund or other compensation unless required by applicable law or expressly agreed otherwise.

Depending on the feature, information submitted to or generated through a Beta or Experimental Feature may be processed differently from information processed through generally available Services.

Before using a Beta Feature, review any feature-specific notices or documentation describing applicable data handling.

You are responsible for determining whether the information you submit is appropriate for the feature.

If Asiyst identifies a Beta or Experimental Feature or related information as confidential, you must not disclose that confidential information except as permitted by Asiyst or applicable law.

Confidential information may include:

• Unreleased functionality.
• Non-public product information.
• Private documentation.
• Internal test results.
• Non-public technical specifications.
• Screenshots or recordings where disclosure is restricted.
• Non-public performance information.

Publicly available information is not confidential solely because it relates to a Beta Feature.

As a participant in a Beta or Experimental Feature, you may be asked to provide Feedback.

Feedback may include:

• Bug reports.
• Feature requests.
• Usability observations.
• Performance information.
• Suggestions.
• Test results.
• General comments.

You may voluntarily provide Feedback unless participation terms require specific reporting.

Unless otherwise agreed in writing, you grant Asiyst permission to use Feedback to develop, improve, test, operate, and market its Services.

Feedback should not contain unnecessary personal information, confidential information belonging to another party, or sensitive information that is not required for the report.

Beta Features involving artificial intelligence may produce experimental or unreliable results.

AI outputs may:

• Contain factual errors.
• Omit relevant information.
• Produce inconsistent responses.
• Misinterpret inputs.
• Generate inappropriate content.
• Change as underlying models or systems are updated.

You should independently verify important outputs before relying on them.

An AI-powered Beta Feature may use models or providers that change during testing.

Changes may affect:

• Response quality.
• Response format.
• Latency.
• Availability.
• Token usage.
• Cost.
• Supported capabilities.
• Output consistency.

Asiyst may change the underlying model or provider where reasonably necessary to operate or develop the feature.

Beta Features may depend on third-party services.

Third-party services may have their own:

• Terms.
• Privacy policies.
• Availability limitations.
• Usage restrictions.
• Security requirements.
• Pricing.
• Data-processing practices.

Asiyst does not control third-party services and cannot guarantee their continued availability.

Beta Features may have separate limits from generally available features.

Limits may include:

• Number of users.
• Requests.
• Tokens.
• Credits.
• Storage.
• API calls.
• Processing capacity.
• Project limits.
• Time-based access.

Asiyst may change or enforce such limits as part of the testing process.

Unless expressly stated otherwise, Beta or Experimental Features may be subject to applicable pricing or usage charges.

A feature being labeled “beta,” “preview,” or “experimental” does not automatically mean that it is free.

Any applicable pricing, credit consumption, or usage terms will be communicated through the relevant product interface, documentation, or applicable agreement.

Beta and Experimental Features may not have the same level of maturity as generally available Services.

You should evaluate security requirements before using such features with sensitive or confidential information.

You must not use a Beta or Experimental Feature to intentionally conduct security attacks, circumvent controls, or compromise Asiyst or third-party systems.

Security vulnerabilities should be reported responsibly through the applicable Asiyst security contact or reporting process.

You are responsible for determining whether your use of a Beta or Experimental Feature complies with laws, regulations, contractual obligations, and industry requirements applicable to you.

This may be particularly important where the feature is used to process:

• Personal information.
• Confidential information.
• Financial information.
• Health-related information.
• Children's information.
• Regulated information.
• Sensitive business information.

You must not use Beta or Experimental Features for purposes prohibited by the Asiyst Acceptable Use Policy, AI Usage Policy, or applicable law.

You must not use experimental functionality as a means to circumvent restrictions applicable to generally available Services.

Beta and Experimental Features may have reduced or variable availability.

They may experience:

• Downtime.
• Increased latency.
• Service interruptions.
• Capacity limitations.
• Unexpected errors.
• Temporary removal.

Unless expressly stated otherwise, Beta and Experimental Features are not subject to service availability commitments applicable to other Services.

Support for Beta and Experimental Features may be limited.

Asiyst may provide documentation, community support, email support, or other assistance depending on the feature.

Asiyst does not guarantee that every Beta Feature will receive the same support level as generally available products.

You are responsible for maintaining appropriate backups of important data submitted to or generated through a Beta or Experimental Feature where backup functionality is not expressly provided.

You should not assume that information associated with an experimental feature will remain available indefinitely.

If a Beta Feature provides export functionality, you may use that functionality according to its applicable limitations.

If a Beta Feature is discontinued, Asiyst may provide migration or export options where reasonably practicable, but is not required to develop a migration path unless otherwise agreed or required by applicable law.

Beta and Experimental Features, including associated software, interfaces, documentation, designs, and technology, remain the property of Asiyst or its applicable licensors unless otherwise stated.

Participation in a Beta Feature does not transfer ownership of Asiyst intellectual property.

You retain rights you otherwise have in content and materials that you submit, subject to the applicable Asiyst terms and agreements.

Participation in a Beta Feature does not mean that the feature will become generally available.

Asiyst may decide not to release, commercialize, or continue a Beta or Experimental Feature.

Beta and Experimental Features are provided for testing and evaluation and may not meet the performance characteristics of generally available Services.

Unless expressly stated otherwise, Asiyst does not guarantee specific performance, accuracy, availability, or functionality for Beta or Experimental Features.

When using a Beta or Experimental Feature, you are responsible for:

• Evaluating whether the feature is appropriate for your use case.
• Maintaining necessary backups.
• Protecting credentials.
• Reviewing AI-generated output.
• Complying with applicable laws.
• Protecting personal and confidential information.
• Monitoring application behavior.
• Maintaining appropriate fallback procedures.
• Reporting significant issues where appropriate.

Asiyst may suspend or remove your access to a Beta Feature if reasonably necessary to:

• Protect the Services.
• Protect other users.
• Address security issues.
• Investigate abuse.
• Manage capacity.
• Conduct testing.
• Enforce applicable terms.
• Comply with legal requirements.

These Terms supplement the Asiyst Terms of Service and other applicable policies.

If there is a conflict between these Beta / Experimental Features Terms and a feature-specific agreement, the feature-specific agreement will control for that feature to the extent of the conflict.

Asiyst may update these Terms as its Beta and Experimental programs evolve.

Continued use of applicable Beta or Experimental Features after updated Terms become effective constitutes acceptance of the updated Terms where permitted by applicable law.

For questions regarding Beta or Experimental Features, contact:

Asiyst Website: https://asiyst.com Email: support@asiyst.com