Privacy Policy
This draft describes the data processing that TyperLab implements today.
Version 1.0 · Effective date: 2026-09-04
Александр А. Кудрявцев · Technical deployment test · privacy@typerlab.com
Operator and contact
- The operator and privacy contact are shown from the deployment configuration. Contact the privacy email for access, correction, deletion, or withdrawal requests.
Account and authentication
- TyperLab processes email, nickname, account identifiers, password hashes, and linked provider identifiers to create and secure accounts.
- Passwords are stored only as password hashes. GitHub sign-in is disabled for new sign-ins in the current release.
Training and progress
- TyperLab stores completed exercise identifiers, aggregate speed and accuracy metrics, errors, elapsed time, mistake summaries, personal bests, course progress, goals, and preferences.
- TyperLab does not store raw typed text, raw code input, key sequences, keyboard-test keystrokes, clipboard contents, or IME composition contents.
Leaderboard
- Public leaderboard participation is optional and disabled by default.
- With separate public-data consent, TyperLab may publish your nickname, rank, CPM, WPM, accuracy, and ranking context. You can withdraw consent in settings; private progress remains stored.
Cookies and similar technologies
- Necessary cookies and browser storage support sign-in, anonymous progress, theme, and training preferences. Optional product analytics and Yandex Metrica are disabled unless you consent to Analytics in Cookie settings.
- Read the Cookie Policy for technology categories, retention, controls, and provider information.
Storage, processors, and transfers
- Optional product analytics is configured only when enabled by the deployment and your consent. Hosting, database location, processors, retention periods, and cross-border transfers require deployment-specific legal review before production launch.
Your choices
- You can request access, correction, deletion, or withdrawal through the privacy contact.
- Account deletion and retention exceptions must follow the approved production retention policy. This draft is updated when processing changes materially.