Privacy Policy
Last updated: 1 October 2026
PaceBeep is an open-source interval-running app run by Gad Shushan. This page explains what data PaceBeep keeps, why, who else handles it, and how to delete it. Questions: 2713065@gmail.com.
What we collect
- Account: your email address and name. If you sign in with Google, also your Google account id and profile picture link. If you sign in with Apple, also your Apple account id; the email may be a private relay address from Apple. If you use a password, only a one-way hash of it.
- Sign-in sessions: a session cookie, and the IP address and browser/device description of each session.
- Training data you or your assistant add: workout plans, runs (times, distance, per-interval durations and pace), and your feedback (effort rating and notes).
- Assistant connections: which AI assistants you approved, when, and the access and refresh tokens issued to them.
We do not use advertising, tracking or analytics cookies, and we do not collect location or health data from your device.
How we use it
Only to run PaceBeep for you: to sign you in, store and show your training, and let the assistants you approve read and write it. We do not sell your data, use it for advertising, or use it to train AI models.
Google sign-in
When you choose “Continue with Google”, Google shares your email address, name and profile picture with PaceBeep. We use them only to create and identify your account. PaceBeep’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not access your Gmail, Drive, contacts or any other Google data.
Sign in with Apple
When you choose “Continue with Apple”, Apple shares an account id, your email address (your own or, if you choose to hide it, a relay address that forwards to you) and, the first time only, your name. We use them only to create and identify your account.
AI assistants you connect
If you connect an assistant (for example ChatGPT), you approve it on a consent screen, and it can then read and change your PaceBeep training data through PaceBeep’s MCP interface. What the assistant’s provider does with that data is governed by the provider’s own terms and privacy policy. You can disconnect an assistant at any time from the dashboard; its access ends immediately.
Who else handles the data
- Vercel – hosts the app (United States).
- Neon – hosts the database (United States, us-east-1).
- Google – only if you use Google sign-in.
- Apple – only if you use Sign in with Apple.
We share data with no one else, unless the law requires it.
Keeping and deleting data
We keep your data while your account exists. Delete account on the Account page removes your account and all of your training data, sessions and assistant connections from the database right away. Backups kept by our database provider expire within its retention window. You can also ask us by email to see, correct or delete your data.
Security
Connections use HTTPS. Every request is checked against the signed-in user or the assistant token, so one user cannot read another user’s data. Assistants never receive your password or a long-term key, only tokens you approved and can revoke.
Children
PaceBeep is not directed at children under 16, and we do not knowingly collect their data.
Changes
If this policy changes, we will update this page and its date. Significant changes will be shown in the app.