LexiMint respects your privacy and complies with the General Data Protection Regulation (GDPR). This policy explains what data we collect, why we collect it, and what rights you have over it.
Provided when you create an account.
You can sign in with GitHub, Google, Discord, a magic link sent to your email, or a traditional email and password. We store your email address, display name, and profile avatar. If you use email and password, we store a securely hashed version of your password, never in plain text. OAuth providers only grant us access to your basic profile (name, email, avatar).
Words you submit to the Lexicon.
Any words you submit become part of the shared public Lexicon. Your submissions are associated with your account for leaderboard attribution, ticket ownership, and MASTERY progress.
Only with your explicit consent.
With your consent, we use PostHog for product analytics. PostHog is only initialized after you grant analytics consent. It is never loaded by default. It is not used for advertising. Manage your preferences.
Only with your explicit marketing consent.
If you grant marketing consent, we load Google Ads measurement to understand whether paid ads bring visits to LexiMint. It is never loaded before that consent, and you can withdraw consent at any time from the cookies page.
Minimal campaign diagnostics without cookies.
When a visitor who is not signed in opens LexiMint for the first time in a day, with or without campaign parameters such as UTM tags or known ad click markers, we store a minimal first-party log to check whether paid or community traffic actually reached LexiMint and where the signup funnel drops off. This log stores campaign buckets, referrer host, page path, CTA or outcome buckets, device class, browser family and operating-system family. When infrastructure headers provide it, it also stores a coarse two-letter country code. It does not store IP addresses, cookies, user IDs, emails, full URLs, raw user-agent strings, raw ad click IDs or precise location. To count a first visit once a day, the server keeps for 24 hours a one-way hash of the date, the network address, the browser string and the campaign, which points only to a random visit identifier and is then deleted; the address and the browser string are not stored in the log.
Stability monitoring with privacy safeguards.
Sentry collects technical error reports to maintain application stability under legitimate interest (GDPR Art. 6(1)(f)). Automatic default PII collection is disabled; the event filter removes email addresses and discards IP addresses. If you consent to account identification in error reports, we attach your account ID, not your email or username. This ID is pseudonymous, not anonymous.
When you submit feedback or bug reports.
If you use the feedback widget, your message and optional screenshot are stored. Screenshots are uploaded to Cloudflare R2 (object storage). Feedback is linked to your account but this link is removed if you delete your account.
System emails and alpha updates you may receive.
We use Postmark to send transactional emails: email verification, password resets, magic link sign-in, and game achievement notifications (e.g. legendary discoveries). These are operational emails and contain no tracking pixels.
During the alpha we also send product updates: a weekly recap of the game and occasional news about seasons, live events, major improvements or feedback requests. These updates use Postmark's broadcast stream, include an unsubscribe link, and are not used for third-party advertising.
We write to you in one language: the one you choose in Settings or, if you have not chosen one, the language you use LexiMint in, which we store on your account for this purpose. Push notifications follow the same rule.
Your data is used exclusively to operate LexiMint: maintaining your account, attributing your word discoveries and tickets, running leaderboards, powering MASTERY and missions, sending transactional emails, sending the weekly recap and other product updates, measuring whether paid or community traffic reaches the landing page and moves through the signup funnel, and improving the stability and fairness of the game.
We do not sell your data. We do not share gameplay or account data with ad networks. If you grant marketing consent, Google Ads receives basic ad measurement signals so we can understand whether paid ads work.
Hosting and infrastructure
Runs our application server, background workers, WebSocket server, PostgreSQL database, and Redis instance. Data is stored in managed environments.
Game data and accounts
Stores all game data, accounts, tickets, submissions, and achievement progress in a managed cloud database.
Rate limiting, caching, and real-time
Used for rate limiting, stamina management, ECHO pools, and real-time pub/sub for notifications. Connected via direct TCP. No personal data is persisted, only operational counters and transient game state.
Error monitoring (always active)
Technical error reporting remains active under legitimate interest, with privacy filters. Attaching your account ID requires your consent.
Bot protection
A privacy-preserving CAPTCHA alternative used to verify that form submissions come from real humans, not bots. Turnstile does not use visual puzzles. It runs silently in the background.
Email delivery
Delivers system emails (verification, password reset, magic link, achievement notifications) and the product updates described above. Your email address is shared with Postmark solely for delivery. Open and link tracking are turned off.
Object storage
Used to store feedback report screenshots uploaded by users. Files are stored securely and are not publicly accessible.
Product analytics (opt-in)
Helps us understand how players discover and use LexiMint. Only initialized after you grant analytics consent. The PostHog script is never loaded without your opt-in. You can withdraw consent at any time.
Ad measurement (opt-in)
Measures whether paid Google traffic reaches LexiMint and how those visits perform at a basic level. The Google tag is only loaded after you grant marketing consent. You can withdraw consent at any time.
Enhanced error context (opt-in)
Allow Sentry error reports to include your account ID to help investigate bugs. Technical error reporting remains active without account identification when this option is off.
Request a copy of your personal data.
Ask us to correct inaccurate information.
Delete your account and personal data.
Ask us to pause processing of your data.
Download your data as a portable JSON file from your profile settings.
Object to certain types of processing.
Self-service exports and the 30-day deletion grace period.
You can download a complete copy of your personal data (account, wallet, tickets, submissions, MASTERY progress, notifications) at any time from your profile settings in a machine-readable JSON format. This satisfies your right to data portability under GDPR Article 20 without requiring you to contact us.
You can also request deletion of your account from the same page (Danger zone). Deletion is not immediate: your account enters a 30-day grace period during which it is inactive but recoverable. You will receive a confirmation email with the date of permanent erasure. If you sign in within 30 days and restore your account, the deletion is cancelled.
After the 30-day window, the erasure is finalized: name, email, avatar, sessions, wallet, badges, and notifications are permanently removed. Your authored words and tickets remain in the public Lexicon under anonymous ownership, preserving the game history for all players. Where required by law (for example, retention of billing records under EU tax obligations for purchases), minimal accounting data may be retained in anonymized form.
For any GDPR request you cannot handle yourself, email [email protected] or write to us from the contact page.
Send privacy questions to [email protected] or through the contact page. We aim to reply within 48 hours on working days.