Privacy Policy

Last updated: March 2026

Our Privacy Commitment

RepsXtension is designed with your privacy in mind. The extension works fully without an account — your core fitness data is stored on your device by default. Optional features like cloud sync, social feed, and Pro membership involve transmitting data to our servers, but only when you explicitly opt in.

Data Stored Locally

By default, all your exercise data is stored on your device using Chrome's built-in storage API. This includes:

  • Exercise logs, rep counts, and personal bests
  • XP progression, level, and achievements
  • Streaks, weekly challenges, and weight tracking
  • Extension settings and preferences

This data is tied to your Chrome profile. Uninstalling the extension will remove all locally stored data. You can also clear the data anytime through Chrome's settings.

Optional Cloud Sync & Account

If you choose to sign in, the following data is synced to our cloud infrastructure (hosted on Supabase):

  • Your email address and display name
  • Exercise data, progression, achievements, and streaks
  • Social profile information (display name, avatar)
  • Subscription status (for Pro members)

Cloud sync is bi-directional — it backs up your data and lets you access it across devices. You can sign out at any time, and your local data remains on your device.

Social Features

If you use social features (available to signed-in users), your shared achievements, workout summaries, reactions, and follow relationships are stored on our servers. Social posts are visible to other users who follow you. You can delete your social data by removing individual posts or by deleting your account.

Pro Membership & Payments

Pro subscriptions are processed through Stripe. We do not store your payment card details — Stripe handles all payment information securely. We receive your subscription status and billing email from Stripe to manage your Pro membership. See Stripe's Privacy Policy for details on how they handle payment data.

No Analytics

We do not use Google Analytics, Facebook Pixel, or any other tracking or analytics services within the extension.

No Account Required

You do not need an account to use RepsXtension. All core features — exercise tracking, streaks, achievements, challenges, and break reminders — work without signing in. An account is only needed for cloud sync, social features, and Pro membership.

Permissions Explained

RepsXtension requests the following Chrome permissions:

  • Storage: To save your exercise data and settings locally
  • Alarms: To schedule break reminders at your chosen intervals
  • Idle: To detect active browsing time for smart reminders
  • Notifications: To display break reminder notifications

None of these permissions allow us to access your browsing data, history, or any personal information.

Third-Party Services

RepsXtension integrates with the following third-party services when you opt in:

  • Supabase: Cloud database and authentication for sync and social features
  • Stripe: Payment processing for Pro subscriptions

These services are only used when you sign in or subscribe. The extension functions fully without them.

Chrome Web Store

When you install RepsXtension from the Chrome Web Store, Google may collect standard installation data according to their privacy policy. This is handled by Google, not by us, and we have no access to this information.

Data Deletion

You can delete your local data at any time by uninstalling the extension or clearing Chrome's storage. If you have a cloud account, you can request full deletion of your server-side data by contacting us. Upon account deletion, all cloud-stored data including social posts and sync data will be permanently removed.

Changes to This Policy

We may update this policy as features evolve. Changes will be reflected by updating the "last updated" date at the top of this page. Continued use of the extension after changes constitutes acceptance of the updated policy.

Contact

If you have any questions about this privacy policy, please open an issue on our GitHub repository.