Privacy Policy

You can use Baros locally without creating an account. Signing in enables sync through Clerk authentication and Convex account-backed storage. You can export workout history and delete account-backed or local data from Settings.

Baros does not use third-party advertising, cross-app tracking, or product analytics in the v1 release.

Baros stores workout-related data such as exercises, sets, workout sessions, notes, settings, and workout history. You can use the app locally on your iPhone without creating an account.

If you create an account, Baros uses Clerk for authentication. Clerk may process account information such as your email address, authentication identifiers, session information, and Sign in with Apple details.

If you use Sign in with Apple and choose Hide My Email, Apple may provide a private relay email address instead of your personal email address.

When you sign in, Baros uses Convex to sync supported workout, exercise, settings, and history data for your account. Sync data is scoped to your authenticated account.

• You can export workout history from Settings.
• Signed-in users can delete their account and account-backed data from Settings under Privacy & Data.
• Signed-out users can delete local data stored on the device from Settings under Privacy & Data.

Baros does not use third-party advertising, cross-app tracking, or product analytics. Standard platform and provider diagnostics may be processed by Apple, Clerk, Convex, Sentry, or hosting providers to keep Baros and its services reliable and secure.

Baros uses Sentry to receive crash, app-hang, and classified synchronization diagnostics from production builds. These diagnostics can include the app version and build, operating-system and device technical details, the sync phase and outcome, and bounded retry or pending-change counts.

When you are signed in, Baros sends Sentry a one-way pseudonymous code so the maintainer can count how many distinct accounts are affected. Baros does not send Sentry your raw account identifier, email address, display name, authentication token, workout names, workout notes, set notes, record identifiers, request bodies, or full synchronization entries. The pseudonymous code is cleared from the active diagnostic scope when the current account changes or signs out.

For privacy questions or support, email support@tatooles.dev.