BUCKUP. Download
LEGAL · LAST UPDATED 2026-07-10 · POLICY v1.3

Privacy Policy.

BuckUp is built privacy-first. Sign-in is optional; when you sign in, your sessions, saved peaks, rig profile, and photos sync to your private BuckUp account so they survive a new phone. We never store your raw GPS coordinates on our servers, and we never sell your data.

BuckUp ("we", "us", "the app") is a mobile altimeter and session-logging app for iOS, built and published by Michael Leger. BuckUp keeps your sessions on your device. Sync is opt-in. This policy explains what we collect, why, and what we never do.

1. The short version

  • We do not sell your data. Not to advertisers, data brokers, aggregators, or anyone else.
  • We do not track you across other apps or websites.
  • Your raw GPS coordinates never leave your device. Latitude/longitude are used only to compute altitude on the Gauge screen, in memory — we never store your coordinates on our servers.
  • Your trip data is on your iPhone, and syncs to your account when you sign in. Saved peaks, your rig profile, and your session log are stored on-device; while you're signed in they also sync to your private BuckUp account (hosted on Supabase) so they restore on a new phone.
  • Per-session photos save locally first. Even when signed out. When you're signed in, photos upload to your account's private cloud storage.
  • Signing in is optional. An account ties your Apple ID, Google account, or email to a user identifier so you can restore your in-app purchases on a new device.
  • You can delete your account at any time from inside the app. Deletion is server-first and irreversible.

2. What we collect

Always (whether or not you sign in):

  • Barometric altitude readings from your iPhone's pressure sensor (CMAltimeter), used to compute vertical gain during a session. Stays on your device.
  • GPS location (when you grant permission), used to compute absolute altitude for the Gauge display. Raw coordinates are processed in memory and are never stored on our servers.
  • Session data — altitude peaks, gain, distance, the elevation profile of your climb, duration, optional peak name and notes, and your registered rig — stored locally via Apple's SwiftData framework. When you're signed in, this session data also syncs to your BuckUp account (Supabase) so it restores on a new device.
  • Per-session photos (Build 51 onward) — when you attach a photo to a Buck Log entry, it's stored locally first. When you're signed in, it uploads to your account's private cloud storage (Supabase Storage).
  • Diagnostics — Not Linked to You via Sentry crash reporting and Sentry Session Replay (10% of sessions, 100% on error — as of v1.0.8). The Sentry SDK runs with sendDefaultPii = false (no IP capture) plus a beforeSend scrubber (strips user identifiers), and Session Replay runs with maskAllText = true + maskAllImages = true — replays carry only screen geometry and tap locations, never your photos, callsign, peak names, or any other on-screen text. Used solely for identifying and fixing bugs.

Only if you sign in — synced to your private BuckUp account (Supabase, US):

  • Your email address (or Apple "Hide My Email" relay alias) and a user identifier (UUID).
  • Your profile and rig: display name, callsign, vehicle make/model/year, and anything you add to your rig profile — including a free-text location and optional Instagram/TikTok handles.
  • Your saved peaks (Buck List) and your session log — altitude, gain, distance, and the elevation profile of each logged climb, plus any peak name or notes you add.
  • Per-session photos you attach, stored in your account's private cloud storage.

Only if you make a purchase:

  • A transaction receipt from Apple's StoreKit. We never see your credit card number.

3. What we never collect

  • Contact list, microphone, camera (only PhotosPicker for the attach), HomeKit, Health data.
  • Your raw GPS coordinates (latitude/longitude) — computed in memory on your device and never written to our servers. (We do store the altitude, gain, distance, and elevation profile of the sessions you log while signed in.)
  • Advertising identifiers (IDFA) or tracking identifiers of any kind.
  • Browsing history or behavior in other apps.

4. How we use it

  1. Running the app: computing altitude, saving your log, showing your history, driving the widget and Live Activity.
  2. Authenticating you across launches and devices so your purchase unlocks restore on a new phone.
  3. Fixing bugs and crashes via Sentry, with all text and all images masked in any captured Session Replay (no user identifiers, no IP, no on-screen text).

5. Where it lives

On your device (always): your session log, saved peaks, rig profile, callsign, per-session photos, and Buck Shots are stored locally first.

On your private BuckUp account, only if you sign in (hosted on Supabase, US): your email, user identifier and federated identity link, your profile (display name, callsign), your rig profile (vehicle details, free-text location, optional Instagram/TikTok handles), your saved peaks, your session log (altitude, gain, distance, elevation profile, peak name, notes), and your per-session photos (in private cloud storage). This is what lets your data restore on a new phone.

We do not store your raw GPS coordinates on our servers. All transmission is encrypted with TLS. For email sign-in, passwords are stored only as salted bcrypt hashes by Supabase — we never see or store your plaintext password.

6. Sharing

  • Supabase — authentication processor.
  • Sentry — crash reporting and Session Replay (all text + all images masked, no user identifiers attached).
  • Apple — purchase receipt verification.
  • Google — only if you choose Google Sign-In, only the OAuth handshake.
  • Legal compliance — only on valid court order.

7. Your rights

  • Export your data — your local Buck Log is in SwiftData (covered by iCloud Backup). For a copy of the data in your signed-in account, email admin@buckup.app and we'll provide a JSON export.
  • Sign out from Settings. Local data stays intact.
  • Revoke location or motion permission — iOS Settings → BuckUp.

8. Account deletion

Delete your account anytime from Profile tab → gear icon → Account Actions → Delete Account. Type DELETE to confirm. The Edge Function verifies your token, best-effort revokes your Apple sign-in, deletes your server record, then BuckUp wipes local data on next launch. Server-first, irreversible.

9. Children

BuckUp is not directed at children under 13. We do not knowingly collect data from children under 13.

10. Changes

If we update this policy, we'll update the date at the top. Material changes are surfaced in-app before they take effect.

11. Contact

Privacy questions, data export requests, or account deletion issues:

admin@buckup.app