Terms, privacy, risk and licensed-engine conditions.

1. Scope and account registration

These terms govern creation and use of a RAYOK client account, portal access, server onboarding and related support services.

A user may create an account immediately after accepting the current required documents. Account creation does not activate an engine license, authorize trading or confirm Trade Ready status.

2. Client ownership and responsibility

The client owns and controls the client AWS account, server, broker account, capital, risk decisions and legal or regulatory compliance.

The client must provide accurate information, protect login credentials and promptly report suspected unauthorized access.

3. Permitted use

RAYOK may be used only by the registered client for the licensed account and server configuration.

The client must not copy, reverse engineer, redistribute, resell, bypass licensing, interfere with service controls or use the platform unlawfully.

4. Availability and changes

Technology, broker APIs, exchanges, cloud services, internet connectivity and third-party services may be interrupted or changed.

RAYOK may issue security, compatibility and operational updates. Safety-critical gates may block trading, mode changes, service restarts or deployment when proof is missing or uncertain.

5. Suspension and termination

Access or license activation may be suspended or revoked for expiry, security risk, non-payment, misuse, invalid binding, unsupported versions or breach of these terms.

Termination does not transfer ownership of client infrastructure or broker accounts to RAYOK.

6. No investment advice or guaranteed outcome

RAYOK provides software and operational tooling, not individualized investment, tax or legal advice.

No performance, profit, uptime, fill price or loss limitation is guaranteed.

7. Liability boundary

To the extent permitted by applicable law, each party remains responsible for its own systems, decisions, acts and omissions.

Nothing in these terms excludes liability that cannot lawfully be excluded.

8. Contact and updates

Questions may be sent to support@rayok.in.

Material changes will use a new terms version and require fresh acceptance before affected protected actions continue.

1. Financial risk

Trading in derivatives and other market instruments can cause rapid and substantial loss, including loss of the full deployed capital and additional obligations where permitted by the broker or market.

Past records, simulations and factsheets do not predict or guarantee future results.

2. Execution risk

Orders may be rejected, delayed, partially filled, filled at unexpected prices, duplicated by external failures or remain open during disconnection.

Stop-loss, limit and cancellation instructions are requests to the broker and are not completed until broker evidence confirms the final state.

3. Technology and third-party risk

Broker APIs, market data, cloud servers, power, internet, time synchronization, authentication, browser automation and external services may fail or change without notice.

Fail-closed controls reduce risk but can also block expected operation until reliable proof is restored.

4. Client monitoring and emergency responsibility

The client must maintain broker access, monitor alerts and remain able to intervene manually when required.

The client is responsible for capital limits, quantity approval, broker permissions and responding to emergency or MANUAL_REQUIRED states.

5. No guarantee

RAYOK does not guarantee profitability, continuous operation, market access, order completion, data accuracy or recovery within a fixed time.

1. Information collected

RAYOK may collect account identity, contact details, acceptance records, server identity, license binding data, operational status, audit events and support communications.

Broker credentials are intended for encrypted one-time delivery to the client-owned server and central deletion after acknowledgement or expiry; they are not intended for long-term central storage.

2. Purpose

Information is used to authenticate users, operate onboarding, bind licenses, secure servers, provide support, detect misuse, maintain audit evidence and meet legal obligations.

3. Sharing

Information may be processed by necessary infrastructure, email, cloud and security service providers under appropriate controls.

RAYOK does not authorize sale of client personal data or broker secrets.

4. Security and retention

RAYOK uses access controls, encryption where appropriate, audit logs, least privilege and retention limits, but no system can guarantee absolute security.

Records are retained only as reasonably necessary for operations, security, dispute handling and legal requirements, then deleted or anonymized where applicable.

5. Client choices and requests

Clients may request access, correction or deletion of eligible personal information, subject to identity verification and lawful retention requirements.

Privacy requests may be sent to support@rayok.in.

6. Updates

Material privacy changes will be versioned and presented for renewed acceptance where required.

1. License model

The engine is licensed per approved client account, server fingerprint, broker-client identity and approved engine version.

A registered portal account does not itself grant an active trading license.

2. Trade authorization

Trading is allowed only when the current license and all required bindings exactly match and the system reports Trade Ready.

Missing, stale, mismatched or revoked proof results in NO_TRADE.

3. Protection and restrictions

Editable proprietary source is owner-private. The protected Client release may not be copied, modified, reverse engineered, redistributed or used outside its approved binding.

4. Updates and revocation

RAYOK may require approved updates for security, broker compatibility or operational safety.

A license may be limited, suspended or revoked for expiry, unsupported versions, binding changes, misuse or security risk.

1. Monitoring

The central platform may receive non-secret heartbeat, version, readiness, license, audit and safety evidence needed to operate the licensed service.

Central monitoring is not authority to place trades and does not replace client broker monitoring.

2. Support access

Owner/Admin support access must be explicitly client-approved, time-limited, role-controlled and audit logged.

Only one Engine UI control session is permitted per server; additional permitted sessions are monitor-only, with a maximum of four active sessions.

3. Secret handling

Clients must not send passwords, API secrets, TOTP seeds, private keys or broker session tokens through ordinary support messages.

Any one-time sensitive delivery must use the designated encrypted workflow and expiry controls.

4. Emergency limits

Support may assist with diagnosis or approved emergency controls but cannot guarantee recovery, order completion or prevention of loss.