chalk.bar has no accounts and never asks who you are. Benchmarking keeps nothing: the numbers you enter are used to answer your question and discarded. The one thing that is kept is a comp-prep record, and only if your coach issued you a retaining code — it is held under a one-way hash of that code, carries no name, and is described in full below. The lifter database is OpenPowerlifting, a public-domain archive of competition results.

When you request a standing, the details you entered — sex, equipment, tested status, age, bodyweight, lifts, and optionally a competition total or comp-day lifts — are sent to our server, used to compute the answer, and returned. They are not linked to you: there is no sign-in, no advertising identifier, no tracking pixel, and no analytics service on this site or in the app.

If you search your name, the search runs against the public OpenPowerlifting archive. Choosing a result pre-fills the form with data that is already public. We do not record who searched for whom.

If you share your standing, we store the numbers behind that link so the short link works. If you picked yourself — or a rival — from the OpenPowerlifting search, that name rides along too, so a shared comparison replays whole; those names are already public in the archive, and nothing else about you is stored. Anyone with the link can see the standing it describes — that is its purpose. Share cards are images generated on your device; we never see them.

Comp prep runs on an access code from your coach. We keep the code and its bookkeeping — when it was redeemed, when it expires, how many times it has been used — and no name attached to any of it. What happens to the numbers you enter depends on which kind of code your coach issued. The page tells you which one you are on.

Single-prep codes keep nothing. The lifts, gym markers and meet details you enter are used to compute the recommendation and returned. They are not stored and not linked to your code, so each prep starts fresh — the model reads your public competition record and whatever you enter that day.

Retaining codes keep a record, and that is the point of them. Your access code doubles as the key to a profile, so the model keeps learning your gym-to-platform conversion across preps and your sixth comp is planned by something that watched the first five. Held against that key: the prep inputs you or your coach save — sex, age, bodyweight, equipment, tested status and meet dates, and the meets you enter — and a rep-max record the server writes each time it computes, being the date, the lift, the estimated one-rep max with its 95% band, and the two-to-five-rep figures derived from it. Your browser can save inputs; it cannot write the record.

The profile is reachable only by presenting the key. We do not build accounts, and the profile carries no name — your name is public in the archive and a stranger could type it. It is stored under a one-way hash of your code rather than the code itself, and it is not joined to your coach's batch or its labels, so the profiles table on its own admits nobody and identifies nobody. A profile with no activity for 730 days is deleted.

Two consequences of holding it that way: the code is the only credential, so anyone with your link can read your record — keep it like a password; and you can delete the record yourself, from the entry page, whenever you like; that is immediate and permanent, and it is the only way it leaves us before the 730 days.

Your coach can see which codes in a batch they issued have been redeemed, and the label they wrote on them. They cannot see anything you entered, the record the model built, or the plan it produced. That conversation belongs to the two of you, not to us.

There is a real trade-off in the retaining kind: lose the key and you start afresh. We cannot recover it for you: recovering it would mean knowing who you are, and we have chosen not to.

The site and API run on Cloudflare, which processes IP addresses to serve requests and to rate-limit abuse, per Cloudflare's privacy policy. Our servers keep standard, short-lived operational logs (no profile inputs are logged against identities).

Questions or requests: privacy@chalk.bar.