Privacy policy

// Controller

Michael Ochsner · hello@alpenriderchain.ch · see imprint.

// What we process

• Account: Email and username.
• GPS-Daten: Track points are processed during a ride for pass validation. On ride completion, timestamps and all sensor data are deleted from every single point. Per point exactly eight values remain: sequence number, latitude, longitude, altitude, accuracy, altitude accuracy, tunnel flag and the ride number. The route line (coordinates, altitude) is kept for the rider's personal ride review — accessible only with the rider's login, never public, and stored until the rider deletes it. Also retained: date, start and end time of the ride, the aggregates (distance, elevation gain, crossed passes) and the moment each pass was reached — that moment IS the proof the badge rests on and is therefore stored permanently. Rides that were started but never finished are deleted completely after six hours. Full deletion is available at any time via in-app data deletion.
• Live-Tracking (optional): Only when the rider actively starts a live link are positions transmitted — end-to-end encrypted. The server stores only encrypted position data; decryption is possible only for holders of the shared link containing the key. Tracks end automatically when the day pass expires.
• Profile ID: The public ID of your profile is stored in our DB so your profile and badges can be shown to other riders. The private key stays on your device.
• Sensoren: Barometer, accelerometer and magnetometer run locally on the device only (pressure-based elevation, compass reference) — the only value from them that feeds into ride aggregates is the computed elevation gain.
• Badges: For every pass reached we store the pass, the visit number and the moment. The badge image is rendered once and stored content-addressed (checksum instead of file name) — it contains pass name, altitude and artwork. The artwork of the day it was earned is frozen and never swapped later. With Tier 1 the proof is additionally written to public servers, see below.
• Receipts: If you photograph a workshop invoice for a service entry, the photo is stored apart from the public image store and is retrievable only with your login. On your tap a language model (OpenAI) reads date, amount, workshop and mileage from the photo and proposes them; you confirm or correct. The photo goes into the vehicle service booklet you generate yourself for a sale. It disappears with the entry, the vehicle or your account; photos from abandoned forms after 24 hours.
• Push-Token: Apple/Google push token — only if you allow notifications. Used for incoming tips, road reports on your passes, security notices for your account and app news.

// What becomes public

• Social export: Badge awards are published <em>only</em> if you buy the export in the shop and sign it with your own key. They are copied to public servers. Deletion can be requested — but third-party servers and clients are not required to honour it. Do not rely on deletability: only publish what may stay public.

// Your rights

Under DSG (CH) and GDPR (EU) you have the right to access, rectification, erasure, restriction, objection and data portability. Write to us at hello@alpenriderchain.ch. Account deletion in the app: Profile → Settings → Delete account.

// Third parties

• Social servers (relay.damus.io, nos.lol, relay.primal.net, relay.snort.social, nostr.mom, offchain.pub): Only with Tier 1 and only on your request: your badge proof is signed by you and published there. It is then public, permanent and can NO LONGER be withdrawn by us — only you can remove it. A badge leaves the app only with Tier 1.
• Image servers (blossom.band, blossom.primal.net, blossom.nostr.build): Badge images, addressed by their checksum, so a badge stays visible even if our servers are unreachable.
• Hostpoint (Switzerland): Web hosting + MongoDB.
• Apple / Google: Push notifications + app distribution.
• Sentry: Crash and error diagnostics for the app — technical error data is transmitted.
• Expo / EAS (expo.dev): Delivery of app updates (OTA).
• Mapbox: Map tiles — loaded/proxied server-side for map rendering in app and web.