Privacy Policy

Last updated: March 29, 2026

Lorcana Quest is a free, non-commercial fan project. We collect only the minimum data necessary to provide the service.

Account Information

When you sign in via Google or Discord, we receive your username, email address, and profile image from the OAuth provider. We use this solely for authentication and displaying your profile within the app. We do not access your contacts, messages, or other account data.

If you register with email and password, your password is securely hashed before storage. We never store or log plaintext passwords.

User Data

We store data you create within the app, including:

  • Deck lists and deck versions
  • Card collection quantities
  • Game tracker sessions

This data is associated with your account and is not shared with third parties.

Cookies

We use a single, strictly necessary session cookie to keep you logged in. We do not use marketing, advertising, or tracking cookies.

Third-Party Services

Our infrastructure relies on the following services:

  • Cloudflare Pages — Hosting, CDN, and DDoS protection
  • Neon — Serverless PostgreSQL database (US-East)
  • Google / Discord — OAuth authentication only
  • Ravensburger CDN — Card images served directly from the official source

We do not use any analytics, tracking, or advertising services.

Local Storage

We use your browser's IndexedDB to store offline deck drafts and localStorage for UI preferences (layout widths, color mode). This data stays on your device and is never sent to our servers unless you explicitly save a deck.

Data Deletion

You may request deletion of your account and all associated data by contacting us via our GitHub repository. Requests will be processed within 30 days.

Children's Privacy

Lorcana Quest does not knowingly collect personal information from children under 13. If you believe a child has provided us with personal data, please contact us and we will promptly delete it.

Changes

We may update this policy as the project evolves. Significant changes will be noted on the changelog.