How Adamantite Edge handles your data.

Adamantite Edge is operated by an individual sole proprietor in the State of New York, United States (“Operator,” “we,” or “us”). This Privacy Policy explains how we collect, use, store, and share personal information when you use Adamantite Edge and related Operator websites that link to this policy.

Contact for privacy requests: use the support channel published on the site, or the contact method listed in Settings / site footer when available. If you later operate under a registered DBA or company name, that name may appear in an updated version of this policy.

This policy is written for an early-stage educational SaaS. It is not legal advice. Have counsel review it before a public commercial launch, especially if you market to the EU/UK or California consumers at scale.

Account and identity data handled by Clerk: email address, authentication factors (password, passkeys, MFA as you enable them), and account identifiers. We store a mapped application user id in our database.

Profile and preference data you provide: display name, leaderboard alias, training defaults, accessibility settings, and privacy toggles (including whether product analytics is enabled when that control exists).

Training and product data: drill attempts, session and hand history, Daily Table / High Roller balances and events, daily bankroll spin results, leaderboard participation, simulation runs, custom systems, and related Pro artifacts.

Billing data: subscription status, customer and subscription identifiers, and period dates from Stripe. We do not store full payment card numbers; Stripe hosts payment instruments.

Technical and security data: IP address, device/browser metadata, request logs, rate-limit counters, and hashed identifiers used for abuse prevention. Demo play may set a first-party cookie (for example ruby_demo_spent) to enforce daily demo limits.

We do not intentionally collect sensitive government ID numbers or precise geolocation beyond what your browser and hosting provider incidentally process.

Information comes from you (forms, settings, play actions), from Clerk (auth lifecycle webhooks and session state), from Stripe (subscription webhooks when billing is enabled), and automatically from your use of the service (logs, cookies, local storage for client preferences).

Provide, secure, and improve the training product (authentication, persistence across devices, Free/Pro entitlements, Daily Table, High Roller, leaderboards, analysis tools).

Operate billing and account lifecycle when subscriptions are enabled (checkout, portal, cancellation, deletion-linked subscription cancel).

Prevent fraud and abuse (rate limits, demo limits, integrity of server-authoritative game state).

Communicate about the service (security notices, material Terms/Privacy changes, billing receipts via Stripe).

Comply with law and enforce our Terms of Service.

If product analytics is enabled in your preferences, we may use aggregated or product-usage signals to understand feature demand. You can disable that preference when the control is available.

Where GDPR/UK GDPR-style framing applies, we rely on: contract performance (providing the account and subscribed features), legitimate interests (security, product improvement, non-intrusive analytics when enabled), consent where required (certain cookies or marketing, if we introduce them), and legal obligation when applicable.

For US state privacy laws that use “business purpose” language, we use personal information to provide the service, secure it, debug, process payments, and honor consumer requests.

We share personal information with service providers who process it on our behalf:

Clerk — authentication and account security.

Neon — Postgres database for application data, entitlements, daily play, and rate-limit windows.

Stripe — subscription payments when billing is enabled.

Hosting / edge providers (for example Vercel) — application hosting, logs, and request delivery.

We do not sell personal information. We do not share personal information for cross-context behavioral advertising as those terms are commonly defined under US state privacy laws.

We may disclose information if required by law, to protect rights and safety, or in connection with a merger, sale, or transfer of the service (with notice where required).

Our providers may process data in the United States and other countries. Where required, we rely on appropriate transfer mechanisms offered by those providers (such as standard contractual clauses) as described in their documentation.

Account and training data remain until you reset training data or delete your account, or until we delete inactive accounts as part of ordinary operations.

After account deletion we remove application-owned records as described in-product, cancel active Stripe subscriptions when billing is enabled, and request deletion from Clerk. Limited records may remain where needed for security, fraud prevention, legal compliance, or billing disputes (for example hashed identifiers or subscription invoices held by Stripe).

Server logs are retained for a limited operational period and then deleted or aggregated.

Demo-limit cookies expire at the next UTC day boundary (or sooner if cleared by you).

Signed-in users can export a JSON copy of training data and can reset or delete account data from Settings, subject to confirmation and reverification where required.

Depending on your location, you may have rights to access, correct, delete, port, or restrict certain processing, or to appeal a denial. Submit requests through the in-product controls or the published support channel. We will verify requests as required by law.

You may disable product analytics in preferences when that toggle is available. You can control cookies through your browser; note that essential auth cookies may be required for signed-in use.

California residents: we do not sell or share personal information for cross-context behavioral advertising. You may exercise know/delete/correct rights as described above. We will not discriminate against you for exercising privacy rights.

We use essential cookies and local storage for authentication (via Clerk), session continuity, and product preferences.

We may set a first-party demo cookie to enforce the signed-out Ruby daily demo limit.

We do not currently run third-party advertising pixels. If that changes, we will update this policy and obtain consent where required.

The service is not directed to children under 18. We do not knowingly collect personal information from children. If you believe a child created an account, contact us and we will delete it.

We use industry-standard measures appropriate to an early-stage SaaS: TLS in transit, provider-managed infrastructure security, access controls, signed webhooks, and rate limiting on sensitive routes.

No method of transmission or storage is 100% secure. You are responsible for protecting your authentication factors.

This policy is effective as of July 18, 2026. We may update it by posting a new version with a revised effective date. Material changes may also be communicated in-product or by email when feasible.

Use of the service is also governed by our Terms of Service. For healthy practice guidance and problem-gambling resources, see Responsible Training.