Privacy Policy

solverme.com

Last updated: October 8, 2026

solverme.com is made and run by one person, Kevin Braner (“I”, “me”). This page lists everything the site stores about you, where it goes and who can see it. It covers every page on the site: the game solvers and trainers, the Pet Spot Tracker and the Onion Dicer.

1. What stays on your device

The tools save your settings and progress in your browser's own storage (localStorage, plus IndexedDB for the Pet Spot Tracker). That includes game settings, trainer history and streaks, your darts throw history and accuracy profile, simulated bankrolls, pet records and photos, whether you have unlocked Stud Pro, and, if you are signed in to an account, its handle and code (section 2.11). Some pages also keep a random ID for your browser there, so that anything they send (section 2) can be told apart. It is a random string and says nothing about who you are.

None of this is sent anywhere unless section 2 says so. It stays in the browser and on the device you used, and clearing this site's data in your browser deletes it.

The camera dart tracker uses your phone's camera to score darts. The video is processed on the phone, inside the page, and is not recorded or uploaded. The one exception is the misread snapshot in section 2.6, which is off unless you turn it on. The tracker never uses your microphone.

2. What is sent to the site, and when

The site's server and database run on Cloudflare (section 4). Nothing the site itself stores records your IP address or browser details.

2.1 An anonymous page count

When most pages load, they record which page it was, the page you came from (if your browser says), and the date and time. A few buttons are counted the same way, such as starting a Play session, sharing a daily result or clicking the Stud Pro checkout link. These counts carry no name, no browser ID and no cookie, so they cannot be tied to you or to each other. I use them to see which tools get used.

2.2 Leaderboards

The Dice games, the Mississippi Stud and Hold'em daily puzzles, both Play tables and the onion game have public leaderboards. Nothing is posted until you press the button to post a score, except in the onion game, below. When you do, the site stores the name you typed (up to 20 characters), your score and the time, and anyone visiting the page can see them. Use a nickname if you would rather not be identified. The onion game posts every timed (Play) cut to its board as it is diced, the way the dice games' boards work: under the name you typed, or as "anon" if you left it blank, or, if you are signed in to an account (section 2.11), under your account's handle, with a note of which account posted it. It stores the onion and the cuts that scored, and how long the cutting took, so that anyone can replay them on that onion. Zen and duels are never posted. A duel challenge in the onion game is a link that carries the onion, the cuts, the scores, the times and the names the players typed; it sits in the part of the address a browser never sends, so this site never receives or stores it. It goes only where you paste it.

2.3 Past email sign-ups

Until September 28, 2026, the Mississippi Stud daily puzzle offered a daily reminder and early access to Stud Pro by email. That form has been removed, and the site no longer collects email addresses. The few addresses it did collect are stored with the list each one joined and the date. They are used only for what those people signed up for, and are not shared, sold or added to any other list. To have yours deleted, email me (section 9).

2.4 Stud Pro payments

Stud Pro is paid for through Stripe. The checkout page is Stripe's, and your card details go to Stripe, never to this site. Stripe tells me what it tells any seller, such as your name, your email address, what you bought and whether the payment went through. Once you have paid, Pro is unlocked by a note saved in your browser (section 1), not by an account.

2.5 Darts profile sync

The darts solver and the camera tracker can keep a copy of your darts history off the device. This is off until you name your profile and turn sync on. After that, each page sends a copy of your darts statistics (your throw history, your fitted accuracy and your trainer records) with the profile name you typed and your browser's random ID, and replaces it with a newer copy as you play. The copies are not public: reading them back needs a key that only I hold. Turning sync off stops it.

2.6 Camera tracker misread reports

The camera tracker has a send misread reports setting, off by default. With it on, the tracker sends where each dart landed on the board and a log of game events (darts scored, corrections, new games), with your browser's random ID. When it misreads, and you fix a dart, remove one or add one by hand, the report also includes a small, low-resolution picture from the camera (about 220 pixels wide) so I can see what fooled it. The camera is meant to point at the dartboard, but anything else in the frame is in that picture. Reports are not public. Turning the setting off stops them and discards any not yet sent.

2.7 TV displays

Both darts pages can show a live scoreboard on a second screen. This is off until you turn it on. While it is on, the game (player names, scores and the darts in the current visit) is stored under a short room code so a TV can show it and a tablet can send corrections back. Anyone who has the room code can see that scoreboard and send corrections. Corrections are deleted after about 15 minutes. The latest scoreboard for a code stays stored until a newer game replaces it.

2.8 Pet Spot Tracker shares

The Pet Spot Tracker lets you record your pet's name and details, the places you have marked on its body, how it has been in itself, your notes, and photographs. By default none of that is uploaded anywhere: it is kept in your browser's storage on the device you typed it into (section 1).

If, and only if, you create a share code for a pet, that pet's record is stored on the server so that the people you give the code to can see it and add to it. In plain terms:

• The code is the only credential. Anyone who has it can read and change that record. Nobody can tell one holder of a code from another, and there is no way to un-send it.
• Only the pets you pick are uploaded. Any pet without a share code stays on your device.
• Photographs are never uploaded. Only their internal IDs travel, so a photo taken on one phone is not visible on anyone else's.
• You can stop a share at any time from the Pets & data tab, which deletes the stored record. Copies already on other people's devices are not affected.
• Anything you log carries the name you typed for yourself on that device, if you typed one, so the family can tell who recorded what. It is a label you chose, not an identity anyone checked.

Either way, clearing this site's data in your browser deletes your local copy, which is why the tool has an Export button. Use it now and then. An unshared record made on your phone does not appear on your laptop unless you export and import it yourself.

2.9 Email to me

Mail sent to [email protected] is forwarded by Cloudflare to my personal mailbox. I keep it as I would any email, and use your address only to reply.

2.10 The card-room progressive

The Mississippi Stud, Hold'em and I Luv Suits Play tables share a progressive jackpot, played with their simulated money. It is off until you turn it on at a table. While it is on, each hand asks the server for its deck before it is dealt, saying only which game it is for. The server stores the meters, a count per day of how many progressive hands came out each way, and every jackpot hit and big win: the time, the game, the hand, the amount, a random ticket number, and the deck it came from. The hits and the meters are public on the progressive page. None of it carries a name, a browser ID or your IP address. To slow down anyone flooding the server with requests, it counts requests per address in memory, forgets an address a few seconds after its last request, and never writes that count down. Your own progressive record and the ticket numbers that let a page mark your hits as yours stay in your browser (section 1).

2.11 Accounts

You can make an account so that your name on a leaderboard is yours alone. It is optional: every tool works the same without one. The onion game is the first to use it.

An account is a handle you pick and a code the site gives you. There is no email address and no password, and the site asks for nothing else about you. In plain terms:

• What is stored: your handle; a fingerprint of your code (its SHA-256 hash), never the code itself, which is why the site cannot show it to you again; the day you made the account and the last day you used it; and, on each leaderboard entry you post while signed in, which account posted it.
• What is not: no email address, no password, no IP address, no device ID, and nothing about your browser.
• The code is the only credential. Anyone who has it can sign in and play as you. Keep it somewhere safe, and to yourself. Your browser keeps it in its storage (section 1), which is how you stay signed in.
• Your handle is public: it is shown, with a ✓, on every leaderboard entry you post while signed in. If you change your handle, those entries show the new one. It is also yours alone on the onion game's board: an entry posted under it by anyone who is not signed in to your account goes up as "anon" instead.
• If your code gets out, make a new one from the account button (👤) by the leaderboard. The old code stops working at once, everywhere.
• Deleting your account, from the same place, removes it from the server at once. Your leaderboard entries keep their scores but lose your handle and the ✓, and show as "anon". The handle is then free for anyone to take, and nothing is kept that could undo it.
• Signing in with Google: where the account button offers it, you can sign in with your Google account instead of a code, or connect Google to the account you have. Google then sends the site a signed note saying which Google account it is. The note also carries your email address, name and photo, which the site does not read or keep: it keeps only the number Google uses for your Google account, linked to your account, and the day it was linked. Never your email address, your name or your photo.
• Each browser you sign in on with Google gets a code of its own, kept in its storage (section 1) to keep you signed in, with only its fingerprint on the server. Like any code, it is a key to your account: anyone who copies it can play as you.
• Google's script is loaded only when you open the account button and it offers Sign in with Google, never by any page on its own. From then on Google sees that request as it would for any site that uses its sign-in (your IP address, your browser and the page you are on) and, if you sign in, that you signed in here. Google's privacy policy covers what Google does with that.
• To stop signing in with Google, press Disconnect beside it in the account button: the link is deleted at once. Deleting the account deletes it too, along with every code a Google sign-in gave a browser.
• To slow down anyone flooding the server, it counts requests per address in memory, forgets an address a few minutes after its last request, and never writes that count down.

2.12 The ranked ladder

The onion game has a ranked ladder: a rating for each cook, moved by matches between two accounts. It needs an account (section 2.11), and nothing goes to it unless you put up a ranked challenge or answer one.

• What is stored: for a challenge, the account that made it, the onion, the cuts, and the score and time its page gave them; for an answer, the same for the account that answered, and what each player's page re-diced the other's cuts to; when each was made and decided; and for each account, its rating, its wins, losses, draws and disputes, its best rating and when it last changed.
• What is public: the standings, and each player's ladder record (rating, record, disputes and matches) under their handle. A match's cuts can be watched by its two players at once, and by anyone once its challenge has stopped taking answers, after 14 days. A challenge's own link shows its onion, its cuts and its score to whoever opens it, because the page that answers has to re-dice them.
• Your handle is not stored with any of it: the ladder keeps your account's random ID and reads the handle when a row is shown, so a new handle shows everywhere at once.
• Deleting your account deletes your rating at once. Your matches stay on the other players' records, with your side shown as "a deleted cook"; your open challenges close, and an answer still waiting to be checked expires. Nothing is kept that links them back to you.
• An answer that could not reach the site is kept in your browser (section 1) until it can, for at most 14 days, and sent only while the account that made it is signed in.
• To slow down anyone flooding the server, it counts requests per address in memory, forgets an address about half a minute after its last request, and never writes that count down.

3. Cookies

The site sets no cookies of its own. Cloudflare, which hosts it, may set a strictly necessary security cookie when it needs to check that a visitor is not an automated attack; that cookie is not used for tracking or advertising. The browser storage in section 1 stays on your device like a cookie does, but unlike a cookie it is never sent to the server on its own.

4. Advertising and other companies

There is no advertising on this site, and no third-party analytics, social-media buttons or tracking pixels. Every script the pages include is served by the site itself, with one exception: Google's sign-in script, which the account button loads only when it offers Sign in with Google and you open it (section 2.11). If advertising is ever added, this page will be updated before it is.

Two companies handle data on the site's behalf, and a third if you choose to sign in with Google:

• Cloudflare hosts the site, runs its server and database, and forwards email. Like any web host it handles your IP address and browser details to deliver pages and protect the site from abuse. See Cloudflare's privacy policy.
• Stripe handles Stud Pro payments (section 2.4). See Stripe's privacy policy.
• Google, only if you sign in with Google, tells the site which Google account you used (section 2.11). See Google's privacy policy.

Links to other websites, such as the articles a tool credits, lead to sites with their own policies.

5. Who can see what

• Everyone: the names and scores you post to a leaderboard (and, for the onion game, the onion, the cuts that made the score and how long they took), an account's handle on the entries it posted, the ranked ladder's standings and records (section 2.12), and the progressive's meters and jackpot hits (section 2.10), which carry no name.
• Anyone with the code: a TV scoreboard (section 2.7), a shared pet record (section 2.8), or an account (section 2.11).
• Only me: everything else the site stores: the page counts, past email sign-ups, synced darts profiles, misread reports, and the code fingerprints, dates and Google account numbers kept with accounts.

As the person who runs the server, I can technically see everything stored on it. I don't sell or rent any of it, and I don't share it with anyone beyond Cloudflare and Stripe as described above, unless the law requires it.

6. How long it is kept

TV corrections are deleted after about 15 minutes, a shared pet record is deleted when you stop sharing it, an account is deleted when you delete it, and its link to Google when you disconnect it. Nothing else expires on a schedule: page counts, leaderboard entries, past email sign-ups, darts profiles, misread reports, TV scoreboards, the ranked ladder's matches and the progressive's hits and daily counts are kept until I delete them or you ask me to. Stripe keeps payment records for as long as the law requires.

7. Your choices

• Every tool works without posting a score, making an account, syncing, sending reports, sharing anything or turning on the progressive.
• Clearing this site's data in your browser deletes everything in section 1. For the Pet Spot Tracker, use Export first if you want to keep the record. If you are signed in to an account, it also forgets your code: keep the code somewhere else first, or the account cannot be signed in to again.
• You can delete your account yourself at any time, and disconnect Google from it (section 2.11).
• You can ask me for a copy of what the site holds about you, to correct it, or to delete it. Most of it carries no name, so tell me something I can find it by: the name on a leaderboard, an account's handle, the email address you signed up with, a darts profile name, a room code or a share code.

8. Children

This site is meant for adults and is not directed at children under 13 (or the minimum age for online consent where you live). I don't knowingly collect personal information from children. If you believe a child has posted something here, email me and I will remove it.

9. Changes and contact

When this policy changes, the date at the top changes with it. Questions, corrections and deletion requests go to [email protected].