Perside Privacy Policy

The short version

• You sign in with an email link, or with your Google account. There are no passwords, no payments, no ads, no analytics services, and no tracking scripts.
• Everything else Perside stores is training data you enter yourself: your equipment, your programs, your logged sets, and optional fields like effort ratings, a pain flag, free-text notes, and body measurements.
• Seven outside companies touch this data: Vercel (hosting), Supabase (database, hosted in Canada), Resend (sign-in emails), Sentry (automatic crash reports, with your content stripped out before anything is sent), Cloudflare (a bot check on the sign-in forms), Google (only if you sign in with a Google account), and GitHub (encrypted database backups).
• I do not sell your data. I do not share it for advertising. Nobody profiles you.
• You can delete your account yourself, instantly, from Profile → Account → Delete account. Every account can download its training history as a CSV file from Settings → Data. For a machine-readable copy of everything else, email me and I will send it within 30 days.

What Perside stores about you

Your account. Your email address, the date your account was created, the date your email was verified, a random internal user ID, your unit preference (lb/kg), the implements you own (types and weights), your chosen app theme, your timezone (captured silently from your browser once, so your training week schedules correctly), and the days of the week you have told the app you are available to train. If you sign in with Google, this also includes your name and a profile picture URL — see "Signing in with Google" below.

Your training setup and progress. The movements you have unlocked or built yourself, which onboarding path you took (recorded once, used only in aggregate — no feature in the app reads it per-user), and the names you give your programs, along with internal state that tracks your program slots, achievements, and rank/milestone history.

Your training log. For each session: the sets, reps, and weight the engine prescribed, what you actually completed, how long the session took, and the date. Perside also keeps every planned training day, including days you rescheduled or skipped. Taken together, these records show when you trained and when you did not. Optional fields you may choose to fill in — these are the most personal things Perside holds, so I want to be specific:

• An effort rating (RPE) from 1 to 10 for how hard a set felt.
• A pain checkbox, marking that pain occurred during a set. If your cycle is in Manual mode, a short internal code recording that the flag was set is also stored on the cycle's pending decision until you resolve it (or until your next session), then cleared.
• A "didn't complete as prescribed" flag on a set.
• A free-text session note, stored exactly as you write it. Please do not put medical information, diagnoses, or anything else sensitive in this field. It is meant for training notes like "grip slipped on set 3."
• Benchmark test results and sizing test results (sets taken to failure) used to calibrate your programming.
• Freeform entries you log outside the programming engine: an exercise name, equipment, sets, reps, weight, and date.
• Body measurements, if you choose to log them: body weight, and optionally waist and chest measurements, each with a date.

Signing in with Google

If you sign in with Google, Google shares the following with Perside: your Google account ID (a stable identifier, not your email address), your email address, whether Google has verified that email address, your name, and your profile picture URL, if you have one. We request only the openid, email, and profile scopes — nothing about your Google Drive, Calendar, contacts, or any other Google product — and we never see or store your Google password.

We use this information for exactly one purpose: creating and signing you in to your Perside account. Perside identifies your account by email address — if you already have an account under a given email address and later sign in with a Google account using the same, Google-verified email address, we treat that as the same account rather than creating a second one. If Google reports the email on your Google account as unverified, we will not use it to sign you in or link it to an existing account.

Behind the scenes, signing in with Google also stores a Google-issued access token, an ID token, and, where Google provides one, a refresh token, on your account record, so the sign-in system can complete the flow. These tokens are encrypted at rest by our database provider, the same as everything else described in this policy.

Perside's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements, to the extent they apply to us.

What Perside collects without you typing it

• Your IP address, hashed. When you request a sign-in link, your IP address is run through a one-way SHA-256 hash and only the hash is stored, as part of rate limiting. The rate limiter only checks whether two values match, so it never needs the address itself, and the stored hash is never read back. A hash of an IPv4 address is pseudonymous rather than fully anonymous: it is short enough that a determined party holding the hash could brute-force it, so I am not overclaiming here.
• Your raw IP address, sent to Cloudflare, only when the Turnstile human-verification check is active on a sign-in form. Turnstile is a bot check on the sign-in forms. When it is active, completing the widget's challenge sends your IP address and a one-time verification token directly to Cloudflare's siteverify endpoint as part of confirming you are not a bot.
• A trace of sign-in requests that never became accounts. If you enter an email address to request a sign-in link and never finish creating an account, Perside keeps a one-way hash of that address in its rate-limiting records, plus the unused sign-in token, which holds your address in readable form until it expires and is swept. The raw address is not otherwise stored. If you want these removed, email support@getperside.com: I can delete the hashed email record and the token. I cannot delete the per-IP rate-limiting hash, because it is not linked to your email and may cover other people on the same network; it clears on its own after 24 hours of no use.
• Error reports, automatically, when something breaks. Stack traces and technical diagnostics. Your training data, session notes, effort ratings, pain flags, email address, and IP address are stripped before anything is sent, and only an internal user ID is attached — never your name.
• Timestamps. Most records carry creation and update times. As noted above, these can reconstruct your training schedule.

Perside does not collect device fingerprints, precise location data, contacts, photos, or anything from other apps or sites.

A plain note about health-related data

Some of what you can log in Perside describes your body and how it feels: effort ratings, the pain flag, tests taken to muscular failure, body measurements, and anything you choose to write in a note. Depending on where you live, the law may treat some of this as health data. Rather than argue about labels, here is the position:

• Every one of these fields is optional. You choose whether to log them.
• They are used for exactly one purpose: adjusting your own training program. Nothing else reads them.
• They are never sold, never shared for advertising, and never sent to anyone except the infrastructure providers listed below, who store or transmit them on my behalf.
• Perside is not a medical service and I am not a clinician. Do not use the notes field as a symptom diary. If you have logged something you regret, email me and I will remove it.

The training-data consent, and the health disclaimer

Perside records two separate acknowledgements, because they cover different things:

• Training-data consent. A one-time confirmation that you understand Perside stores your training data — including effort ratings, pain flags, and notes — and agree to that. It is recorded the moment you tick the box, and it blocks every authenticated write to your account until you have given it. Existing accounts are asked the same thing the next time they open a page that shows their data.
• The health/injury disclaimer acknowledgement. A separately versioned acknowledgement of the disclaimer text quoted in full in the Terms of Use. Your acknowledged version number and the date you acknowledged it are stored. If the wording changes in a way that matters, the version number increases and you are asked to acknowledge it again — your prior acknowledgement of the older version stays recorded, but the app treats you as not having acknowledged the current one until you do.

Neither acknowledgement is a substitute for judgment: Perside still asks you to keep medical information out of the app, which is not built to be a medical record.

Cookies and local storage

Perside sets no analytics or advertising cookies. None. The complete list of what it puts on your device:

If Cloudflare Turnstile is active on a sign-in form (see above), the widget itself loads a script from challenges.cloudflare.com and may set its own cookies under Cloudflare's domain as part of the bot check; that is Cloudflare's mechanism, not something Perside's own code sets.

Because there is no cross-site tracking of any kind, browser signals like Do Not Track and Global Privacy Control do not change anything: there is no tracking for them to turn off, and no sale or sharing for them to opt you out of.

The only third parties that touch your data

1. Vercel (United States) hosts the app. Because Vercel terminates the secure connection, it can technically see all requests: page bodies, headers, and cookies. It also receives server error logs.
2. Supabase runs the Postgres database that holds everything described in this policy. The database lives in the AWS Canada Central region in Montreal, Quebec, Canada.
3. Resend delivers sign-in emails. It receives only three things: your email address, the subject line "Your Perside sign-in link", and the message body, which contains a live single-use sign-in link. It never receives any training data. Treat that email carefully: anyone who can read it while the link is fresh can sign in as you.
4. Sentry receives automatic error and crash reports when something breaks: stack traces and technical diagnostics, so I find out about failures without waiting to be told. It is configured to collect crash reports only, with no performance or usage monitoring. It never receives your training data, session notes, effort ratings, pain flags, email address, or IP address. Reports are linked to an internal user ID, not to you by name.
5. Cloudflare runs the Turnstile human-verification check on the sign-in forms. When you complete it, it receives a one-time verification token and your raw IP address.
6. Google, only if you choose to sign in with a Google account. It receives nothing from us beyond the standard sign-in request; it sends back your Google account ID, email address, verified-email flag, name, and avatar URL, as described above. Google is an independent controller of the data it holds about you.
7. GitHub stores encrypted database backups in a private repository. The full database is encrypted (GPG, AES-256) before it ever leaves the backup job — GitHub itself cannot read the contents without the separately held passphrase.

That is the complete list. Perside makes no other outbound network calls: no analytics provider, no payment processor, no ad network, and nothing that tracks you across sites.

Where your data lives

Perside is operated from the United States, and the database is hosted by Supabase in Canada. If you are in the US, this means your data is stored outside the US. Perside is offered to users in the United States; the app is not currently marketed to, and does not target, users in the European Economic Area or the UK.

How your data is used

• To run the app: computing your programs, logging your sessions, keeping you signed in.
• To protect the sign-in system from abuse (rate limiting by IP and email, and the Cloudflare bot check).
• To understand, in aggregate, which onboarding path new users take.

That is the whole list. Every account confirms, by ticking a box, that they understand training data is stored including effort ratings, pain flags, and notes, and the date and time of that agreement is recorded. Existing accounts are asked the same thing the next time they open a page that shows their data. That consent is not a substitute for judgment: I still ask you to keep medical information out of the app, which is not built to be a medical record.

How long data is kept

Your account and training data are kept until you delete your account or ask me to delete them. There is no automatic expiry on them today.

Rate-limiting records and expired sign-in tokens are swept whenever someone requests a sign-in link: records past their window and expired tokens are deleted then. Because that sweep is triggered by sign-in traffic rather than a fixed schedule, a record created just before a quiet stretch can outlive its cutoff until the next sign-in request arrives. The onboarding cookie expires after 48 hours, the session cookie after up to 14 days of inactivity (60 days at the outside), and each sign-in token is deleted the moment it is used.

When you delete your account, your data is removed from the live database immediately and cannot be recovered from the live system — deletion is a single database transaction that removes your account and everything that hangs off it (cycles, sessions, entries, achievements, rank events, week-plan snapshots, benchmark and sizing results, freeform entries, body measurements, and your consent/disclaimer records), and every other device you are signed in on is signed out within a few minutes. Copies of your data can still remain, for a limited time, in places outside the live database:

There is no analytics product, no data warehouse, no third-party sync, and no marketing list.

Deletion, export, and your rights

You can delete your own account instantly from Profile → Account → Delete account — see above for exactly what that removes and what may briefly survive in backups and provider logs.

Every account, free or paid, can download its training history — every logged session entry and freeform entry — as a CSV file with one click from Settings → Data. That file does not cover everything Perside holds (your account details, programs, benchmark and sizing results, or body measurements, for example), so for a complete copy, or anything else, email support@getperside.com from the address on your account and tell me what you want:

• Deletion. You can also ask me to delete your account by hand; I will confirm by email within 30 days.
• Export. I will send you a machine-readable copy of all your data within 30 days.
• Correction or access. Same address, same 30 days.

I honor these requests from anyone, anywhere, regardless of whether a particular law requires it. If you are a California resident, you will not be discriminated against for exercising any request, and Perside does not sell or share personal information as those terms are defined in California law.

Security

Data is encrypted in transit. Separation between users is enforced by the application code. The database is hosted by Supabase and is reachable over the internet by anyone holding its credentials; those credentials are held only by me and by the deployed app. To be precise, Perside does not rely on database-level row security for that isolation, because the app's own database role would bypass it anyway; the isolation guarantee lives in the application layer. No system run by one person, or by anyone, is perfectly secure, and I will not pretend otherwise. If I learn of a breach affecting your data, I will notify you as the law requires.

Children

Perside is for adults. You must be 18 or older to use it, and I do not knowingly collect data from anyone under 18. If you believe a minor has an account, email me and I will delete it.

Changes to this policy

If this policy changes in a way that matters, I will update the date at the top and, for significant changes, note it in the app or by email. The current version always lives at https://getperside.com.

Contact

William Ye, doing business as PerSide
Pennsylvania, United States
support@getperside.com