Last updated: August 23, 2026
This Privacy Policy explains what information Depthly ("we," "us," or "our") collects from you when you use our chess training platform, how we use it, and your rights regarding that data. By using this platform, you agree to the practices described below.
When you create an account or sign in, we collect your email address, unique account identifier, display name, avatar preferences, and account timestamps. Authentication management is facilitated through our authentication service provider (Clerk). We store your account profile details, puzzle ratings, and preferences securely in our database (Supabase). We do not collect or store your plain-text password.
To provide game reviews and training features, we store the games you import (including PGN move text and game metadata), generated engine analysis results, puzzle attempt history, accuracy metrics, and performance statistics. PGN files may contain player names, event details, and dates supplied in the source file.
If you link a Chess.com or Lichess account, we use that username to fetch public game histories or verify profile details. We store your connected username and imported games you choose to save. We never request or store passwords or login credentials for third-party platforms.
We collect privacy-safe product usage analytics to understand feature usage and improve Depthly. Analytics collection (powered by PostHog Cloud US) is optional and disabled by default until you grant consent. You can change your preference at any time in Settings. Analytics events contain bounded interaction details and never include move content, PGNs, FENs, passwords, or personal message text. We also process short-lived operational records for rate limiting and service reliability.
To make training fast and responsive, Depthly caches public chess data (such as puzzle positions, opening database statistics, themes, and ratings from Lichess). This shared cache is maintained independently of individual user accounts.
We use browser storage and essential cookies to maintain your login session, save dark/light theme preferences, store your analytics consent choice, and cache interface preferences. When product analytics is explicitly allowed, our analytics provider stores a temporary cookie identifier to measure session engagement. We do not use advertising cookies, tracking pixels, or session recording scripts.
We use your data to:
We do not use your data to:
We share your data only in these narrow circumstances:
We use Clerk for authentication, Supabase for application data, database, and private avatar storage, PostHog Cloud US for consent-controlled product analytics, and hosting/CDN providers to deliver the service. When you use chess import or puzzle features, Depthly requests public data from Chess.com or Lichess. Product analytics receives only bounded event names and approved aggregate properties. Depthly does not send imported PGNs, FENs, move lists, profile details, authentication tokens, or free-form form values to PostHog. The application does not use advertising pixels or behavioral advertising.
The current application does not send imported PGNs or saved game analysis to an AI or LLM provider.
We may disclose data if required by law, court order, or to protect against fraud or security threats. We will notify you where legally permitted.
If the platform is acquired or merged, user data may transfer to the new owner. You will be notified in advance.
Account-owned profile, game, review, puzzle-history, identity-mapping, and avatar data is retained while your account is active. When you use the account-deletion control, Depthly removes account-owned application rows and avatar objects during the deletion process, then removes the linked authentication accounts where available. Shared public chess caches and provider-managed operational logs are not account-owned and follow their own lifecycle. Any longer retention requirement must be confirmed with the relevant provider or policy reviewer.
The account controls provide the following self-serve controls:
Additional rights may apply depending on where you live. Questions about the scope of a request can be sent to the contact below.
Email: privacy@depthly.app
Authentication is handled by Clerk, application data is stored in Supabase, and private avatar objects are served through an authenticated server route. Depthly uses HTTPS and security headers, bounds upstream responses, and avoids logging account payloads in the inspected application paths. No system is perfectly secure.
This platform is not directed at children under 13. We do not knowingly collect data from children under 13. If you believe a child under 13 has registered, contact us and we will delete the account promptly.
The platform may link to Chess.com, Lichess, or other external sites. We are not responsible for their privacy practices. Review their policies separately.
We may update this policy as the platform evolves. The "Last Updated" date at the top reflects the most recent revision. Material changes will be handled through the notice process selected by the policy owner.
For any privacy questions or requests:
Email: privacy@depthly.app