Privacy
Analytics
We count visits to dojovim.com with Umami Cloud. Umami's tracking uses no cookies and does not collect personal data by default. The site sends Umami's collection request itself; it loads no script from Umami.
With each page view and event the site sends the page's address and title, the site that sent you, your screen size and your browser's language. From the request Umami also works out your browser, operating system, device type and approximate location. The events are Lesson Start, Lesson Finish, Module Finish, Practice Start, Practice Finish and Sign In.
Umami never receives ids, keystrokes, editor text or your progress, which stays in your browser. Umami Cloud's servers are in the US and the EU; our account is in the EU region, so the data is stored in the EU.
About Dojo Vim
Dojo Vim is operated by Mario Širić, based in Czechia. He is responsible for the personal data used to provide Dojo. Contact support@dojovim.com for privacy questions or requests.
All learning is free during public beta. You can practise without an account. An optional account saves completed practice and preferences across browsers. There are no payments or marketing subscriptions.
What stays on your device
Progress, preferences, unfinished edits, the text in Your own text and detailed recordings are stored in your browser when storage is available. Unfinished editor text and detailed recordings are not part of account sync. A device backup can contain this private text; you choose where to keep it.
Clearing browser storage can remove your work. Signing out can keep local work for your next sign-in, or you can choose to remove that account’s local data. Account deletion cannot erase copies kept on other offline devices or copies you exported.
What the online service uses
For an account, we use your email address, account identity and authentication records, completed lesson and challenge results, review progress and supported preferences. Results can include example language, key counts and elapsed time. Your email is needed for sign-in, not for guest practice.
Website and API requests include technical information such as your IP address and browser information. We use a secure session cookie, sign-in checks, request limits and service diagnostics to operate and protect Dojo. These are functional features; Dojo does not add advertising or marketing trackers.
We process account data to provide the service you request (GDPR Article 6(1)(b)). Our legitimate interests in protecting the service, preventing abuse and recovering from failures support the necessary security and recovery processing (Article 6(1)(f)). We use information needed to meet applicable data-protection duties under Article 6(1)(c).
Contacting support
When you write to support, do not share passwords, sign-in codes, API keys or confidential code.
Email to support@dojovim.com passes through Namecheap forwarding to the operator’s personal Gmail inbox. Google handles that email under its Privacy Policy; this is not a Google Workspace mailbox. Replies may come from the operator’s Gmail address.
We use your message, sender address and attachments you send to answer your request, based on our legitimate interest in responding. We review resolved support conversations monthly and remove them after 90 days, including their attachments and trash copies, unless a specific unresolved incident or legal obligation requires continued retention.
Providers and locations
Netlify hosts the website and API; Supabase provides accounts and the database; Resend sends sign-in emails. Cloudflare Turnstile checks sign-in attempts and also processes information for its own bot-detection purposes.
Backblaze stores encrypted recovery material. Separately encrypted recovery copies and the recovery-key vault are also retained in Google Drive. Healthchecks receives limited service-health signals, and GitHub runs release checks and operational jobs. Namecheap provides the domain and support forwarding.
The database is in Ohio, United States; the Backblaze bucket is in the EU. Providers may process information in other countries. The standard service agreements for Supabase, Netlify and Resend include data-processing terms and EU standard contractual clauses for applicable international transfers. This does not mean that all processing stays in the EU. Contact us for information about the safeguards that apply to your data.
Retention and deletion
Account data is retained while you use the account. In Your account, Export account data downloads synced progress, and Delete account requests deletion. Deletion removes learning records and revokes application access; provider account cleanup may finish later. The account panel reports that distinction.
Encrypted database snapshots are hidden by the storage rule after 30 days and scheduled for deletion one day later; provider processing may take longer. Independently retained recovery copies are reviewed separately each month and retired after that 31-day window once any associated recovery investigation is resolved. We keep minimal encrypted account-deletion decisions while older recoverable copies could otherwise restore a deleted account. These records contain account and request identifiers, not editor text.
Session and abuse-prevention records expire according to their operational purpose and are cleaned up separately. Service providers may retain their own security, email or diagnostic records under their policies. The snapshot period is not a promise that every record or independently retained copy disappears after 31 days.
Your rights
Contact support@dojovim.com to ask for access, correction, erasure or restriction, or to object to processing based on legitimate interests. Where applicable, you can request a portable copy. We may need to verify that the request concerns your account; do not send identity documents unless we explain why they are needed.
You can complain to a data-protection authority, including where you live or work. In Czechia, contact the Office for Personal Data Protection (ÚOOÚ).
We will update this notice when Dojo’s data practices change. The date above identifies this version.