Privacy Policy

ooolog asks for background location access so iOS or Android can notify the app when you arrive at or leave a saved place, including while the app is closed. Geofence monitoring is performed by the operating system. The app receives arrival and departure events only for places you save — it does not record your route, movement history, or continuous location.

You can revoke location access at any time in Settings. Automatic logging then stops. On Android, place search sends the words you submit and a broad nearby map area through ooolog's Supabase-hosted, rate-limited search service to OpenStreetMap's Nominatim service; search only runs when you press Search. ooolog does not write the raw words to its database. A one-way cache key and sanitized public place results may be kept for up to 30 minutes. OpenStreetMap Foundation may create service-use records, analyze Nominatim queries to improve its map data, and retain detailed usage information for up to 180 days under its privacy policy.

Account.When you sign in with Apple, we receive your name and email address (which may be an Apple private relay address). On Android, you may instead sign in with Google, which provides the account information authorized in Google's sign-in screen. A sign-in provider may also supply a profile picture or picture URL.

Profile. Your display name, username, workout category, avatar emoji and color, and any avatar photo you choose. Signed-in users can discover profile details to send follow requests. Avatar photos are delivered from a public storage URL, so anyone with that URL can retrieve the image.

Workouts and places. The places you save (name, category, address, coordinates) and your workout sessions (place, workout type, start and end time) are stored on your device. On iPhone, they also sync through your private iCloud database when iCloud is available. Private iCloud data is controlled by your Apple account and is not readable by ooolog.

Optional social activity. Sharing starts disabled for each saved place. If you enable it, that place and completed workout times are stored with our backend provider, Supabase. Follow requests must be accepted before another person can see your shared workout activity.

Optional workout-start alerts. On iPhone, start alerts are a separate choice that is off by default for every saved place. To prepare an alert, Supabase processes the sender and recipient account identifiers, a saved-place identifier, a workout-session identifier and start time, notification consent, delivery status, and the recipient's Apple Push Notification service (APNs) device token. The saved-place identifier is used privately to enforce the sender's choice; it is not included in the notification. No location, place name, workout category, address, or coordinates are included in the notification.

No advertising. No third-party analytics or tracking SDKs. We never sell your data or share it with data brokers.

Signed-in users can search for your profile and send a follow request. Only followers you accept can see your completed check-ins at places where you enabled sharing and the associated consistency totals. If you separately enable start alerts for a place, accepted followers who have opted in to receive alerts may get a generic message such as “Alex started a workout.” The notification does not include a location, place name, workout category, address, coordinates, or route. You can stop future sharing for a place or remove a follower.

Workout-start alerts currently operate on iPhone only and require choices on both sides. The person starting a workout must enable alerts for that specific saved place; enabling completed-activity sharing does not enable start alerts. Each recipient must separately turn workout-start alerts on for their account on that iPhone and allow notifications in iOS. Only accepted followers with an opted-in device are eligible to receive an alert.

Apple supplies an opaque APNs device token that addresses the app on an opted-in device. ooolog stores the token privately with Supabase and sends Apple the token, generic alert text, and a random event identifier for delivery. Neither the APNs payload nor its alert text includes a location, place name, workout category, address, or coordinates. Turning alerts off unregisters that device from Apple and asks Supabase to remove its server registration; Apple may still keep technical delivery records under its own policies.

Turning off a place's start alerts removes its consent and addressable queued deliveries. Supabase keeps a bounded anti-abuse ledger containing opaque place and workout-session identifiers, timestamps, and generic alert copy. Entries become eligible for pruning after 24 hours and are removed on a later publication or immediately when the account is deleted.

Removing a saved place in the app deletes your workout history and shared check-ins for that place. Signing out ends your account session but does not delete workout history. Delete Account in the Account tab removes your account, profile, shared workouts, follows, avatar, notification choices, APNs device registrations, and queued notification records from our systems, plus that profile's data from the device. A de-identified shared-place directory record may be retained when it is needed for another person's workout history, but it is no longer associated with your account.

A notification that was already delivered or was already being sent to Apple for delivery cannot be recalled by ooolog. It may remain in a recipient's Notification Center or other device history until the recipient or operating system removes it.

If you cannot access the app, contact us at the address below. We will verify the request and complete deletion within 30 days.

Supabase processes app network requests for sign-in, account management, deletion, Android place search, and optional workout-start alerts. Apple's APNs service processes device tokens and generic notification content to deliver those alerts. Like most hosted services, they may process technical request information such as an IP address, app or device information, timestamps, and interactions needed to operate, secure, and prevent abuse of those services.

ooolog is not directed at children under 13.

If this policy changes, we'll update this page and the effective date above.

Questions or deletion requests: support@ooolog.app