Your data, explained clearly.
What the site uses, why it needs it and how to contact us about your information.
Last updated: 6 October 2026.
Email registration uses a private email address for sign-in. Other signed-in players can search your public nickname. Published tests and qualifying duel results appear on public leaderboards.
1. Privacy contact
For questions about data used on Spijuniro, corrections or a request to remove information, email munchoits@gmail.com or use the contact form with the “Privacy & data” topic.
2. Information used by the application
- Account: nickname, private email if provided, registration date, Facebook identifier if linked, a protected password record and a protected recovery-code record. Passwords are not stored as plain text.
- Results: exercise type and duration, speed, accuracy, errors and completion time. Results from signed-in users may be linked to their account.
- Duel rooms: a nickname and game state are needed to connect players and display the match. Your opponent can see your name and game results.
- Contact and suggestions: the content you submit, an optional name and the email address entered in the contact form. Do not send passwords, recovery codes or sensitive information.
- Technical information: requests and connection information may be used to operate the server, identify errors and limit abuse. The hosting provider may keep access and security logs.
Friends: we store requests, accepted friendships and temporary duel invitations. Accepted friends can invite you to a room. Facebook linking uses your account identifier; we do not import Facebook friends or store your Facebook password or access token. Email addresses are not yet verified by email and are not public.
3. Why information is used
Information supports sign-in, saved progress, result validation, duel connections, replies to messages and service protection. Publishing to a leaderboard is a separate action after a test; finishing a test alone does not publish your nickname. Qualifying duels between two signed-in players automatically enter statistics and public rankings. A win earns 3 points, a draw 1 and a loss 0.
4. Browser storage
Your browser stores local progress, some preferences and whether the beta popup has appeared. A session cookie connects requests and supports sign-in. Details and removal options are explained under Cookies & storage.
5. Service providers
Hosting runs the application and database. Contact messages and beta suggestions are relayed through FormSubmit to the Gmail inbox at the contact address above. Those services process information needed to deliver and store messages under their own policies.
FormSubmit’s documentation describes a submission archive of up to 30 days. Read its privacy policy and Google’s privacy policy. These services may process information outside your country.
If you choose Facebook sign-in, Meta processes that sign-in under its privacy policy.
6. Retention and removal
Sessions expire after 30 days; temporary attempts have a one-hour validity period. The application periodically removes expired records. Guest results that are not published to a leaderboard are removed after 30 days. Accounts, friendships, duel statistics and published records have no automatic deletion period. Temporary OAuth records and invitations expire after 10 minutes and are removed periodically. You can remove friendships on the Friends page.
You can request removal of an account, result or message by contacting us. To protect accounts, we may need to verify that the information belongs to you. Clearing browser data removes local history but does not remove database records or email messages. Hosting backups may follow a separate retention cycle.
7. Changes
If our handling of information changes, we will update this page and its date. Use the contact details above for questions or corrections.
Password reset
A random six-digit code is sent to your account email through the configured email provider. It expires after 10 minutes and can be used once. We store a protected code digest, expiry and attempt count. Password changes sign out existing sessions. An address without an account receives no code. No password is sent by email.