Privacy Policy

SolveLab is a Rubik’s Cube timer operated by Bhargava Gumpula ([email protected]). This page explains what the app stores, where it lives, and what Google sees when you sign in.

Where your data is stored

• When you are signed in, your solves, sessions, settings (timer options, appearance such as theme and digit style, and view choices such as chart ranges), skill tests, daily checks, coach conversations and summaries, training plans, finished lessons, and algorithm choices are stored in a Postgres database hosted by Supabase under your Supabase user id (rows keyed by your user id). That copy is what restores them on a new device or after you clear this browser. It is not stored as a file on Bhargava Gumpula’s laptop, Raspberry Pi, or git repository.
• A working copy of the same records also stays in this browser, in IndexedDB under the name speedcubing-local, so the timer stays instant while you solve. This browser also keeps a copy of your appearance in localStorage (solvelab.appearance.v1) so the right theme appears before the page finishes loading.
• When you are signed out, solves stay only in this browser. Signing in uploads that local copy to the Google account and merges it with anything already saved there.
• Google account (name, email, profile photo, and a Supabase user id) is stored by Supabase Auth. The browser also keeps a local session so you stay signed in on this device.

Times saved at http://127.0.0.1:5173 do not appear on https://solvelab.bhargava-gumpula.com until you sign in on both. Each website address is a separate browser origin; the Google account is what joins them.

How your solve data is used

Your solve data is used for two things only: saving and syncing your own times (above), and, only if you turn it on, training SolveLab’s coach AI so it gets better at spotting what slows cubers down. It is never sold, never used for ads, and never shared with anyone else.

• What is shared for training. With sharing on, when you finish a skill test (for example the cross or OLL test), the app shares that test’s attempt times, which test it was, whether it used inspection, the goal you picked, the calendar day (not the time of day), the app version, and a summary of your normal timer solves (how many, their average, and how much they vary).
• What is never shared for training. Your name, email, photo, notes, tags, scrambles, individual timer solves, and device details.
• Where it goes. Supabase, under a random id in the same database. Skill tests need an account, so that id is your account id, and only it can read or delete the results. Bhargava Gumpula downloads the results to retrain the coach, with the ids replaced by new random ones, and ships improved coaches in normal updates.
• Off unless you turn it on. Nothing is shared until you turn on Help improve the coach in Settings → Your data. Turn it off to stop sharing; turning it off also deletes from our database everything this browser or your account shared. A coach already trained on your results keeps what it learned, but not the results themselves. Results are otherwise kept until you turn sharing off or email us to delete them.
• Results shared before version 6.0 (October 2026), when sharing was on by default, are kept like any others. To delete them, turn Help improve the coach on and then off, or email us.
• Results shared before October 2026 were kept by the earlier service under an anonymous id. They have moved with everything else, and the browser that shared them re-attaches them to itself the first time it opens the app after the move, so Help improve the coach still deletes them. A browser whose storage was cleared in between can no longer do that itself: email us with roughly when you took the tests and we will delete them.

The Mac app

SolveLab also comes as a Mac app. It keeps your working copy in its own storage on your Mac, the way the website keeps it in your browser. When you sign in, your times sync to your Supabase account exactly as they do on the website. The app checks for updates from time to time. The check sends the app’s version number and the type of Mac, and the server that holds the update file sees your IP address, as with any download.

The coach in the Mac app

• It runs on your Mac. The coach is an AI model that runs on your Mac through Ollama. Your questions, its replies and your numbers summary are not sent to Bhargava Gumpula, SolveLab or anyone else.
• What it is told. Numbers and choices only: your goal, average, course, solve profile and Learning Hub path. Never your name, email, notes, scrambles or individual solves.
• Chats stay on your Mac. They are stored only in the app, are not synced to your account, can be cleared in Settings, and are deleted when you sign out of the app. Your backup from Settings → Your data can include them if you want to keep a copy.
• The model download. The app downloads the model from Ollama’s servers, which see your IP address like any download. No SolveLab data is sent with it.
• Ollama is a separate program with its own privacy terms.

Copy my summary

The website’s “Copy my summary” button only puts the same numbers-only summary on your clipboard. SolveLab sends it nowhere; what you paste into another AI is between you and that service. Earlier versions of the website could connect your own AI with an OpenRouter sign-in or an API key, kept only in your browser. That feature is gone, and any saved key is deleted from your browser the next time you open the site.

Google Sign-In

Coach, Stats, Train and Learn need a Google account, because they hold data of yours that lives on the account. The timer, Algorithms and Settings work without one. When you choose Sign in with Google, Google shares your basic profile (name, email, photo) with this app. We use that to show your account and attach your timer data to that account in Supabase. We do not post to Google on your behalf, read your Gmail, or attach your solves to Google Drive.

What we do not collect

SolveLab does not run ads, does not sell personal information, and does not use third-party analytics pixels. Row level security allow only the signed-in user to read or write their own rows, and only the id that shared a test result to read or delete it.

Your choices

• Sign out from the header or Settings. That ends the Google session on this device and clears this browser’s copy of your data — times, sessions, coach conversations, tests and your solve profile. Only how the app looks is kept. Your account keeps its own copy, so signing back in restores it.
• Export or delete your data from Settings → Data. A backup file holds everything listed above. Deleting solves while signed in also removes them from the Google account copy. Clearing this site’s data in your browser removes the local copy only; sign in again to restore from the account.
• You can remove SolveLab’s access in your Google Account permissions.

Children

SolveLab is a training tool, not a service directed at children under 13, and we do not knowingly collect personal information from them. Do not create a Google sign-in for SolveLab if you are under 13. Sharing results for coach training is off unless someone turns it on; a parent or guardian can email us to delete anything a child shared.

Changes

If how data is stored changes, we will update this page and the effective date above.

Contact

Questions: [email protected].