Beta and Preview Features Terms

1. Relationship to the Terms

These Beta Terms supplement the Terms of Service. The Trading Risk Disclosure, AI Disclaimer, and Privacy Policy also apply. If these Beta Terms conflict with the Terms of Service about a Beta Feature, these Beta Terms control only for that Beta Feature. Mandatory law always controls where it cannot be varied by contract.

The Service as a whole is not a beta merely because one feature is marked beta. These Beta Terms do not impose confidentiality unless we separately and expressly identify information as confidential before disclosing it.

2. Experimental nature

A Beta Feature may:

• be incomplete, inaccurate, untested, or unsuitable for production use;
• contain defects, security weaknesses, calculation errors, or unexpected behaviour;
• change frequently, including interfaces, APIs, limits, outputs, data formats, and system requirements;
• break integrations or compatibility with earlier versions;
• perform slowly or be unavailable without notice; and
• never become a generally available feature.

Documentation, labels, and examples may be incomplete or become outdated. You are responsible for evaluating whether a Beta Feature is appropriate for your testing purpose.

3. Access and eligibility

Access may be limited by invitation, account, plan, jurisdiction, capacity, device, provider, or other criteria. Access is personal to the approved account and may not be sold, transferred, or shared. We may add or remove participants, impose limits, or require updated acceptance at any time, subject to applicable law.

4. Testing responsibilities

You agree to:

• use the Beta Feature cautiously and only for lawful testing;
• review configuration, output, logs, permissions, and results independently;
• keep independent copies of information you need;
• maintain another method to access and control connected third-party accounts;
• not rely on the Beta Feature for emergency, safety-critical, or mission-critical monitoring or action; and
• promptly stop using it and report behaviour that could cause loss, unauthorized access, or market harm.

5. Trading and financial risk

Unless a Beta Feature is expressly limited to simulation, it may interact with real broker, portfolio, market, or order data. If live use is enabled, a bug or outage can generate, omit, duplicate, delay, or mis-handle an order and cause financial loss. “Beta” does not mean a trade is simulated.

Use paper or observe-only modes first where available. If you choose live use, use the least permission and capital reasonably necessary, continuously monitor the broker itself, and understand that disabling the Beta Feature may not cancel an instruction already transmitted or reverse a completed trade.

6. Data loss and resets

Beta data, strategies, configurations, results, logs, or history may be corrupted, deleted, migrated, truncated, or reset. We do not guarantee that Beta data will be retained, recoverable, exportable, or carried into a later version. Keep a separate copy of any non-sensitive information you need and never use RoboSelf as the sole system of record for broker activity.

Personal information used in a Beta Feature remains subject to the Privacy Policy. A Beta label does not reduce our obligations under applicable privacy law.

7. Feedback and diagnostic information

We may invite bug reports, logs, surveys, examples, or suggestions. You permit us to reproduce an issue and use voluntary non-confidential feedback without compensation or attribution as described in the Terms of Service. Do not include broker secrets, private keys, full payment-card data, material non-public information, or third-party personal information in a report.

8. Confidential beta material

If we clearly identify a particular Beta Feature, document, access program, or unreleased interface as confidential before giving you access, you must use that confidential material only to evaluate the Beta Feature and protect it with reasonable care. This does not apply to information that you can document was already lawfully known, becomes public without your breach, is independently developed without the confidential material, or is lawfully received without a confidentiality duty.

A legally required disclosure is permitted if you give advance notice where lawful and disclose only what is required. General feedback you provide is not treated as your confidential information unless we expressly agree otherwise in writing.

9. Changes, suspension, and termination

We may change, pause, limit, or end a Beta Feature or your access at any time for testing, capacity, security, provider, legal, market-integrity, or business reasons. We may delete Beta accounts or data subject to the Privacy Policy and applicable law. If access ends, verify all broker-side orders, positions, permissions, and automations directly; ending beta access does not itself close a position or cancel an order.

10. No service level or commitment

No uptime, support, maintenance, response, recovery, compatibility, feature, launch, pricing, or roadmap commitment applies to a Beta Feature unless a separate signed agreement expressly provides one. We may decide not to release it or may release a materially different version.

11. Warranty and liability

Beta Features are provided “as is” and “as available” with the heightened risks described here. The warranty disclaimers and liability limits in the Terms of Service apply to the maximum extent permitted by law, including to defects, outages, inaccurate calculations, AI output, data corruption, provider or API failure, and trading loss. Nothing limits a right or remedy that applicable law does not allow us to waive.