Privacy
The board is local by default. Network processing begins only when a user chooses functionality that requires it.
Local-Only Use
- No account is required for local chess play.
- No Rookies sends no advertising identifiers or cross-site tracking data.
- Up to 100 saved matches, their replay positions, and board PNGs are kept in the current browser or app storage. The oldest records are removed when the limit is exceeded.
- Saved matches can include player and model choices, move history, clock settings, usage summaries, and settings needed to resume play. Saved records do not contain provider API keys or card details.
- Files are written only after the user selects a folder or export.
Position Bridge
The extension reads selected text after a context-menu action, or temporarily inspects the active tab after a toolbar click. It has no broad host or extension-storage permission. Recognized FEN or PGN text is placed in a URL fragment and decoded locally. Browsers may retain that URL fragment in local history.
Optional Relay
When a model-relay player is selected, the app sends a PNG of the current board, the responsible color, and the fixed move instruction. The relay may process account identity, request metadata, provider and model identity, token counts, cost, abuse signals, and payment-credit balance. Provider credentials are never placed in the public web bundle.
Authentication And Security
When a relay account is connected, match diagnostics synchronize to that account: moves and results, model changes, request and retry observations, full recorded errors, timing, and budget and token-limit history. Pending history stays on the device while offline and resumes synchronization with the original account. This diagnostic upload does not include player names, provider credentials, board PNGs or raw prompt bodies. The relay and protected operator diagnostic tools can use the records to investigate a match without a manual export.
A self-service provider key is entered into a password field, sent only over HTTPS, omitted from browser storage, and held only in relay process memory until disconnect, timeout, or relay restart. Operator-configured provider secrets may instead be encrypted at rest. Authentication tokens and session cookies authorize relay operations. Security logs should exclude board images, prompts, credentials, and full tokens. Operational records are retained only for documented security, billing, legal, and recovery periods.
A separate secure, HttpOnly account cookie remembers this browser's billing identity for up to 400 days, renewed when you reconnect a provider. It contains no API key or card details and cannot authorize relay requests by itself. Reconnecting a validated API key restores the same saved payment authorization and server-held fee balance. Explicit sign-out or clearing website data removes this browser's access to that remembered identity; it does not erase fees.
Payments
When paid relay access is offered, Stripe hosts card checkout and the DeviantData payment rail records settlement and issues signed, account-bound credits or licenses. No Rookies receives transaction and invoice identifiers, product, amount, currency, tax, refund, dispute, and account-link information. Card details remain with Stripe.
Saved matches stay in device storage. Billing authorization and payment records are held separately on the server. Deleting matches or clearing app data does not erase accrued fees.
Age
Local-only use is available to all ages. An account, model relay, bring-your-own-key connection, or commerce feature requires age 13 or older. A user under the age of legal majority must have permission from a parent or legal guardian. DeviantData does not knowingly permit a child under 13 to use network or commerce features.
Retention
- Temporary provider keys remain only in relay memory until disconnect, 30 minutes of inactivity, eight hours total, or restart.
- Board PNGs and prompts are not placed in service logs or backups.
- Routine request and security metadata is retained for up to 90 days, unless an incident or legal obligation requires longer retention.
- Support and deletion records are retained for up to three years after closure.
- Payment, credit, refund, dispute, and tax records are retained for seven years after the transaction or account closure.
- Active service data is deleted within 30 days of an authenticated request. Any encrypted backup copy expires within 35 additional days. Required financial or legal records are restricted instead of erased.
Deletion
Synchronized match history remains in the relay diagnostic journal until account deletion. Deleting a local cached match does not delete that synchronized copy. Account deletion removes the relay diagnostic journal; previously exported diagnostic records are separate copies. Clearing browser data also removes history still waiting to upload.
Deleting a cached match removes it from the current browser. Deleting a relay account revokes relay access and deletes account secrets and service data, except records that must be retained for payment, tax, fraud prevention, security, backup expiry, or legal claims. Exported files remain under the user's control. DeviantData sends necessary deletion instructions to applicable processors within the same 30-day period.
Deleting or replacing a local saved match, clearing website data, or losing a provider connection does not delete the server's billing records or cancel fees already incurred. Use the billing cancellation control to stop new fee-bearing requests; existing obligations remain governed by the terms you accepted.
Disclosure And Requests
DeviantData does not sell personal information or share it for cross-context behavioral advertising. Information is disclosed only to a model provider selected by the user, Stripe and necessary service processors, authorities when legally required, or a successor that accepts this notice. Users may request access, correction, export, or deletion without discrimination.
Contact
Privacy requests: support@deviantdata.net.