Privacy policy

What DeckLex is

DeckLex is a platform for playing and creating card games. You can play anonymously, or sign in with your email to author games, publish them, and keep your identity across devices.

What we collect

Email address

Collected only if you sign in. We use it solely to send you magic sign-in links and to associate your account across devices. Sign-in emails are delivered through our email provider (Resend); your address is shared with them for delivery only.

Device identifier

A random identifier generated on your device or browser (not a hardware ID, not an advertising ID). It lets anonymous players keep their seat in a game across restarts. It is not used for tracking across apps or sites.

Game play records

Every move accepted in a game session is recorded in an append-only log keyed to the session. These records are how games resume, how disputes are auditable, and how the engine proves that a replayed game reconstructs identically. They reference your internal account id, not your email.

Game and authoring content

If you author a game, we store your conversation with the authoring assistant, the evolving game specification, and any games you build or publish. Your authoring conversation is processed by our AI provider (Anthropic) to generate responses; it is not used at play time — the game engine runs without AI.

AI usage metadata

For each authoring AI call we record token counts (how much text went in and out). This is spend accounting and abuse prevention — it contains no message content.

Ratings and reports

If you rate a game or report a listing, we store the rating or report attributed to your account so aggregates are honest and moderation is accountable.

Network addresses

Our servers see your IP address, as all servers do. We use it transiently in memory for rate limiting. We do not build profiles from it.

Crash reports

When the app, the website, or our server crashes or hits an internal error, a crash report is sent to Sentry (our crash-reporting provider): the error message, a stack trace, the app or site version, and basic device metadata (operating system and version, device model or browser type). Crash reports are not tied to your account — they carry no user identifier — and they never include your email, your game or authoring content, or the contents of your requests. Crash reporting is switched on per deployment; in builds where it is not configured, nothing is sent to Sentry at all.

Product analytics

We record a small, fixed set of product events in our own database — first-party, with no third-party analytics service and no analytics scripts or cookies in your browser. The full list: a game session started or finished (which game, which session, how it ended), an authoring session started, built a game, or was abandoned, a game was published, and a sign-in happened. Each event carries only internal identifiers, a timestamp, and the outcome — never card contents, game state, conversation text, or any other free text.

What we do NOT collect

• No advertising identifiers, no cross-app or cross-site tracking.
• No contacts, location, photos, microphone, or camera access.
• No payment information (there are no purchases today).
• No sale of personal data, to anyone, for anything.

Who we share data with

• Anthropic — processes authoring conversations to generate the assistant's responses.
• Resend — delivers magic sign-in link emails.
• Sentry — receives crash reports (error, stack trace, device metadata; no account identifier, no content) when crash reporting is enabled for a deployment.
• Hosting providers — our servers and database run on cloud infrastructure; data is stored and processed there on our behalf.

No other third parties receive your data.

Deleting your account

You can delete your account in-app (mobile: Account screen; web: the account page). Deletion is immediate and permanent:

• Your email, device link, and display name are erased.
• Every sign-in credential is revoked.
• Your authoring conversations and drafts are permanently deleted.
• Games you published are removed from the public catalog.

What remains: records of game sessions that other people played with you (required so their games remain resumable and auditable), game artifacts needed to replay those sessions — including the title and description you gave a game you published, retained unlisted so existing sessions keep working — anonymous aggregate counts (for example a game's rating average, or total AI tokens spent), and the product analytics events described above, which carry only internal identifiers and outcomes. The free text of any reports you filed is erased. Nothing else retained identifies you — the records reference only an internal random id whose identifying attributes were erased.

Retention

Account data is kept while your account exists. Sign-in link records expire within minutes and are deleted on account deletion. Game play logs are kept for as long as the game session needs to remain resumable and auditable.

Children

DeckLex is not directed at children under 13, and we do not knowingly collect personal information from them.

Contact

Questions or requests: [contact address — to be confirmed before publication]. You can exercise deletion yourself in-app at any time.