StrideSafe is designed to help two trusted people share walking progress and selected journey information without hidden tracking. This policy describes the current app and website implementation. The legal entity and privacy contact still require confirmation before public release.

Information you provide

  • Account identity and authentication information, including display name and email.
  • Personal daily and weekly step goals and onboarding choices.
  • Pairing invite actions and one active trusted pairing.
  • Journey labels, entered timing, status, and current sharing choice.
  • Supported encouragement reactions and notification preferences.

Health and motion information

When you choose Apple Health, the iPhone requests read access to steps, workouts, and recorded workout routes. Raw Health samples and workout routes are not uploaded by StrideSafe or shown to a partner. The app syncs one daily step total and a source label to support personal and shared progress.

You may instead choose steps recorded by this iPhone. Apple Health and iPhone totals are never added together.

Location and journey information

Planning a journey leaves location off. A new journey preselects Precise unless you chose a different default in Settings. Review the visible mode before starting; Start applies that selection.

Location is off by default. A selected walk or commute can use Off, Approximate, or Precise sharing. StrideSafe Plus also includes a separately approved continuous mode outside a commute. Both modes use one replaceable latest-location record; StrideSafe does not create a partner-visible coordinate route history.

Approximate detail is reduced server-side before partner access. Precise mode returns only the latest approved precise point. Partner access requires the current server-authoritative pairing and consent state.

Private walk route history can be saved in a protected store on the walker’s device. These route points are never written to StrideSafe’s server or database.

How information is used

  • Authenticate the account and keep the session available.
  • Calculate daily progress, goals, and personal or couple streaks.
  • Enforce pairing and independent consent choices.
  • Present current journey and permitted latest-location state.
  • Deliver opt-in, privacy-safe local or partner notifications.
  • Process an eligible StrideSafe Plus purchase through Apple.

Sharing

StrideSafe shares partner-visible information only with the one active paired account and only when the relevant server rules permit it. Pairing alone does not enable steps or location. Push payloads do not include coordinates, destinations, exact steps, Health data, or reaction rows.

Apple processes App Store purchases. Supabase provides authentication, database, Realtime signalling, and server functions. Apple operating-system services provide Health, motion, location, notifications, and StoreKit capabilities.

Retention and deletion

Daily step summaries, profiles, pairing, journey metadata, preferences, and reactions remain according to the current product data model until removed by their applicable lifecycle or account deletion. Latest approved coordinates are replaced rather than appended. Account deletion cascades through profiles, pairing, invites, steps, commutes, reactions, and latest location.

Security

Access is enforced by authenticated accounts, server-side relationship checks, Row Level Security, and narrowly scoped functions. The app contains a Supabase publishable key, not a service-role secret. No system is guaranteed to be completely secure.

Your controls

You can change step source, step sharing, commute sharing, continuous sharing, notification preferences, and goals; pause or stop current sharing; revoke a pairing; sign out; or delete the account and associated data. System permissions can also be changed in iOS Settings.

Website analytics

The website includes no third-party analytics or behavioural replay by default. Its local event abstraction sends no network requests. If analytics is added later, this policy and the site configuration must be updated first.

Contact

A public privacy contact address has not yet been confirmed. It will be added before public release.