Last updated: May 14, 2026 — beta soft-launch terms.
Cymba is intended for business, developer, and professional use, not for consumer use. By using the service you agree to these terms. We may update these terms as the product matures. If we make material changes, we will publish the updated terms here and, where practical, notify active users by email before the changes take effect. Changes required for legal, security, abuse-prevention, or operational reasons may take effect immediately.
The service is provided as-is during beta with no warranty of availability, accuracy, uptime, fitness for a particular purpose, or suitability for production use. Free-tier accounts may be rate-limited, suspended, or deleted without notice if usage threatens platform stability, violates these terms, or appears abusive. Free-tier limits may change when paid tiers go live.
Cymba provides developer infrastructure for probabilistic game outcome generation, simulation, math testing, and related audit workflows. Cymba receives game configuration and request data, then returns generated outcomes, multipliers, hashes, and related response data.
Cymba does not operate games of chance, accept or settle wagers, custody funds, manage player balances, issue prizes, process payments, provide wallets, operate player accounts, or provide gambling, financial, legal, tax, licensing, or compliance services.
You are solely responsible for your application, your users, your jurisdictions, and your compliance with all applicable laws and regulations. You must not use Cymba for unlawful activity, unlicensed gambling, underage gambling, fraud, money laundering, sanctions evasion, or any activity prohibited in your jurisdiction or your users' jurisdictions.
You may not use Cymba for real-money gambling, wagering, sweepstakes, lotteries, prize-linked promotions, crypto or token wagering, or other regulated gaming activity unless you have obtained all required licences, approvals, and legal clearances. If you intend to use Cymba in a regulated gaming context, you must notify us at [email protected] and receive written confirmation before doing so.
You must not send Cymba player names, email addresses, identity numbers, wallet addresses, payment details, balances, deposit or withdrawal records, or other personal, financial, or regulated transaction data unless Cymba has expressly agreed to process that data in writing. Your systems remain responsible for player accounts, wallets, balances, payments, payouts, and transaction records.
Spin logs, API keys, and game configs are stored at rest. API keys are stored hashed (SHA-256); the plaintext is shown to you once at creation and never persisted in retrievable form. Server seeds are encrypted at rest using the application's encryption key (AES-256-CBC via Laravel's Crypt facade) and decrypted in-process only when a spin or verification flow needs them. A database compromise alone does not expose plaintext seeds. Seeds are never exposed via the API except via POST /api/v1/seed/rotate, which reveals the prior seed exactly once at rotation time.
Where practical, we will provide advance notice of behavioral changes to config interpretation, RNG mapping, win evaluation, or feature resolution. During beta, the engine is under active development and config behavior may change without prior notice. If you require stability guarantees for a certified or approved deployment, please contact us to discuss a separate written agreement.
Cymba is provided on a reasonable-efforts basis during beta. We do not guarantee uptime, response times, or uninterrupted access, and we do not offer a service level agreement during the beta period.
Cymba is designed to support deterministic retry and replay for identical inputs, but you are responsible for implementing appropriate timeout, retry, and reconciliation logic in your own platform. You are solely responsible for wallet reconciliation, open-round resolution, and all player-facing dispute resolution arising from API unavailability, timeouts, or incomplete responses. We recommend treating any unresolved round as void on your side until the outcome can be confirmed via the verify endpoint or replay flow.
If we become aware of a security incident that has materially compromised the confidentiality of server seeds or API keys associated with your account, we will notify you at your registered email address as soon as reasonably practicable. You are responsible for storing server_seed_hash and nonce values from spin responses in your own systems. Those records form the basis for any post-incident replay, dispute resolution, or audit review. Our liability for any security incident is subject to the limitation in the Liability section below.
You retain full ownership of all game configs, reel strip designs, paytable structures, math parameters, and other content you create, upload, or store through the service. You grant Cymba a limited, non-exclusive, royalty-free licence to store, process, and transmit that content solely to provide the service to you. Cymba will not use your configs, math patterns, PAR sheet data, or any derivative thereof to inform or develop configurations for other customers. PAR sheet exports generated from your configs are your property.
Cymba retains ownership of the service, the engine, the platform, the dashboard, and all underlying software and infrastructure. Nothing in these terms transfers any Cymba intellectual property to you.
You agree to indemnify, defend, and hold harmless Cymba and its officers, directors, employees, and agents from and against any claims, damages, losses, fines, penalties, and costs (including reasonable legal fees) arising out of or relating to: (a) your use of the service; (b) your application, platform, or product built on the service; (c) any claim by a player, regulator, licensor, or third party arising from your operation of games or products that use Cymba's output; (d) your violation of these terms; or (e) your violation of any applicable law or third-party right.
Paid subscriptions, if enabled, grant access to Cymba during the applicable billing period and are subject to the plan limits shown at checkout, in your account, or on the pricing page. We may suspend or limit access for failed payments, abuse, excessive load, security risk, or violation of these terms.
To the maximum extent permitted by law, Cymba is provided as-is and our total aggregate liability for any and all claims relating to the service is limited to the fees you paid for Cymba during the twelve months before the claim arose. We are not liable for indirect, incidental, special, consequential, exemplary, punitive, lost-profit, lost-revenue, lost-data, or business-interruption damages, even if we have been advised of the possibility of such damages.
You may close your account at any time by contacting us at [email protected]. On account closure we will delete your API keys, game configs, and spin logs within 30 days, except where we are required to retain records by applicable law or to resolve an outstanding dispute.
We may suspend or terminate your account immediately if you breach these terms, engage in activity that poses a legal, security, or reputational risk to Cymba, or if we discontinue the service. On termination we will, where practical, give you a reasonable opportunity to export your configs before deletion.
The sections covering customer responsibility, indemnification, intellectual property, liability, and governing law survive termination.
These terms are governed by the laws of South Africa. Any dispute arising out of or in connection with these terms shall be subject to the exclusive jurisdiction of the South African courts, except that either party may seek injunctive or other equitable relief in any competent jurisdiction to protect its intellectual property or confidential information.
If any provision of these terms is found to be unenforceable or invalid, that provision will be limited or eliminated to the minimum extent necessary so that the remaining terms remain in full force and effect.
Questions: [email protected].