Privacy & your data.

Typeabit beta · updated 7 November 2026

Typeabit is operated by the Typeabit project owner. Privacy, account and support requests: addict3dlife@gmail.com.

What we save

• Your account email and authentication records are handled by Supabase Auth. Typeabit’s application does not store your plaintext password. If you choose Google sign-in, Google authenticates you and Supabase receives your verified identity and basic profile information. Typeabit does not receive your Google password or request Gmail/Drive access.
• Signed-in practice progress includes completed lessons, speed, accuracy, time, mistake patterns and recent round history (up to 200 rounds per language). Existing local practice data remains in browser storage.
• Miso access requests include your optional note, decision and allowance. We store daily request counts to enforce limits.
• Preferences remain on this device. Signed-in, verified players’ Miso conversations are saved privately to their Supabase account and cached in this browser, separated by account and language. Existing account-owned browser conversations are merged into cloud history; guest chats are not uploaded. Starting a new chat preserves previous conversations. Other signed-in devices can retrieve saved history. Offline messages remain locally and retry syncing when connected. Clearing browser storage removes local copies but does not delete cloud conversations. Chat storage is limited to 1 MB per conversation and 10 MB per account; if a limit or sync failure occurs, the app keeps local copies and displays a warning. For the introductory assessment, input and correction events are sent to our server to calculate the result. The application stores the summary rather than retaining that raw event stream. Your Hamlet assessment metrics and mistake summary are saved once with your account. The assessment does not call an AI provider or generate Miso advice.

When you use Miso’s AI

A live AI question sends your question, a limited recent conversation and a bounded summary of your typing progress through our server to OpenAI. The API key stays on the server. Local coaching does not send a question to OpenAI. Avoid sending passwords, sensitive personal information or information about other people.

AI requests use store: false. This is not a promise of zero provider retention; OpenAI’s applicable data policies still apply. AI advice can be mistaken and cannot observe your hands or posture.

Who processes the data

Render hosts the website/server, Supabase handles accounts, cloud progress and private conversation history, and OpenAI processes live AI requests. Google Fonts supplies interface fonts. If CAPTCHA is configured, Cloudflare Turnstile processes verification information. An email delivery provider processes confirmation and recovery messages when custom email is connected. These providers may process network information and maintain operational or security logs under their own policies.

Typeabit currently adds no advertising trackers and does not sell your practice data. Browser storage is used for sessions, preferences, local practice and chat history.

Who can see your information

Players can access their own cloud progress and saved conversations. Database permissions prevent other players from reading these conversations. Authorized Typeabit administrators can review access requests, email addresses, approval status, daily usage and the action log. Ordinary players cannot approve themselves, read another player’s progress, or reset their usage allowance. The admin panel does not display your chat conversations.

Deleting your account

Open Your account → Delete my account. Confirm with your current password and type DELETE. Google-only accounts sign in with Google again, then return within five minutes to confirm deletion; this does not delete the Google account itself. This removes the login, cloud progress, saved cloud conversations, first assessment, access request/approval and personal usage records, and clears this account’s stored data in the current browser. The last administrator must appoint another administrator before deleting their own account.

Other devices may retain local copies; clear Typeabit’s site data on those devices to remove them. Shared daily totals remain to prevent allowance resets. Action records remain with account identifiers removed. Provider backups, security logs and billing records may expire on their own schedules rather than disappearing immediately. We do not promise a retention period we cannot enforce.

Your choices

You can switch sounds off, use local coaching after signing in, and contact the project owner about access, correction, export or deletion of your data. Your browser can clear locally saved site data; guest history cannot then be recovered. Essential account emails are used for account access, not marketing subscriptions.

Current beta limitations

Public registration remains closed until reliable email delivery is configured. This notice describes the implemented beta, and will be updated as providers and features change.