Privacy policy

Who we are

REPSBASE is operated by Peter Cziczlavicz, the data controller for the information described here. Questions or requests: hello@repsbase.com.

What we collect and why

• Waitlist. If you joined the waitlist before registration opened: your email address, the country your request came from, and when you signed up — so we can let you know you can now join.
• Account. When you sign in with Google we receive your email address and Google’s account identifier. We do not receive your name, photo, contacts or Google password, and we ask for no other Google data. During the beta we use your address to tell you now and then what has changed; reply to any of those emails to stop them.
• Training data. The programs, sessions, exercises, sets, weights, notes and settings (such as time zone and units) you enter. This is the service itself.
• Body weight. Only if you enter it: each value and when you entered it, and a copy on each workout you start, so older workouts keep the weight they were done at. Only you can see it. Removing it on your profile deletes all of it, including those copies.
• Connected AI apps. Only if you connect one (such as Claude, ChatGPT or Gemini): which app you allowed and when, and its access tokens, stored only in a form that cannot be reused. The app can then read your training data and body weight. If you also allow it to change your plans when you connect it, it can create programs and workouts, add exercises and change this week; it can never delete anything or change a logged workout. What it does with what it reads is up to that app’s provider and its own privacy policy, not us. Disconnect it on your profile at any time. Read-only access is offered to an AI assistant built into your browser while you have REPSBASE open, if you use one.
• Notifications. If you turn on push notifications, your browser’s push subscription and user agent.

To run the service, the operator can see basic account activity: when you joined, when you last trained, and how many workouts you have logged. Not your sets, weights or notes. For the waitlist, the operator sees your address, when you signed up, the country your request came from, and whether you have been invited or joined.

The legal basis is your consent for the waitlist, and performance of the service you asked for once you have an account. We do not sell data, show ads, or use analytics or tracking scripts.

Cookies

Only strictly necessary ones: rb_login protects the Google sign-in for 10 minutes, and rb_session keeps you signed in for 30 days after your last visit. No advertising or analytics cookies.

Who processes it for us

• Cloudflare — hosting and database.
• Google — sign-in only.
• Resend — sending your invite email and the beta update emails.
• GitHub — only if you send a problem report: what you wrote, your name and email address.
• Your browser’s push service (e.g. Google, Mozilla, Apple) — only if you enable notifications.

These providers may process data outside the EU under their own standard contractual safeguards.

How long we keep it

Waitlist entries until you ask us to remove them. If you join, the entry stays as a record of when you signed up and is removed with your account. Account and training data for as long as you have an account; sessions expire 30 days after your last visit. Profile → Delete account removes your account and everything attached to it at once; exercises you added to the shared catalog stay there without your name. You can also ask us to do it.

Your rights

You can ask for access to, a copy of, correction or deletion of your data, restrict or object to its processing, and withdraw consent at any time — email hello@repsbase.com. You can also complain to your data protection authority; in Hungary that is the NAIH (naih.hu).