Privacy Policy
Effective August 20, 2026
Introduction
Onome ("we", "us", "our") operates the Onome mobile application. This Privacy Policy explains how we collect, use, and protect your information when you use our app.
Information We Collect
Account Information: If you create an account, we collect your email address and use it to send you a one-time sign-in code. If you provide your name, we store your first and last name. If you sign in with Google, Google sends us an identity token containing your Google account identifier, your email address, and your first and last name. This information is stored on Onome's servers. Runner Profile: If you complete the onboarding questionnaire or edit your profile, we collect your sex, age, height, weight, running experience, and how much running you can currently do. This is health data, and several jurisdictions treat it as a special category of personal data. It is stored on Onome's servers, and it is sent to our AI model providers, together with your training goal and the fitness history we derive from your runs, to generate your training plan. Device Identifier: We use a device identifier that your phone's operating system provides: Apple's identifier for vendor on iOS, and the Android device ID on Android. We ask the operating system for this identifier rather than create one ourselves; if your phone does not return one, the app generates a random value instead. That fallback value is cached and reused for analytics and crash reporting, but a fresh random value is generated separately each time for registering your device and for our subscription provider, so in that fallback case it does not act as one identifier across every use. On Android, deleting and reinstalling the app does not reset it. On iOS it is reset: Onome is the only app we publish, so deleting the app and installing it again gives you a new identifier. It is stored on your device and on Onome's servers, and used for analytics, usage tracking, and identifying your device when you use the app. When your phone provides this identifier, it is also the identifier we send to our analytics, crash reporting, and subscription providers, which means your activity can be linked across those services. Location Data: GPS data is collected only during active runs (including the countdown phase). Location data is stored on your device while you run. Once a run finishes and syncs, its GPS track is uploaded to and stored on Onome's servers. When the app draws a map, the map provider receives the coordinates needed to render it. Health & Fitness Data: Pace, distance, duration, and related metrics are stored locally on your device while you run, and are uploaded to Onome's servers once the run finishes and syncs. The distance, duration, and average pace of a completed run are also sent to PostHog, our analytics provider, tied to your device identifier. The workout you ran, including its intervals and their targets, is uploaded and stored with the run. The training plans we generate for you are stored on Onome's servers. Motion Data: While you run, the app reads your phone's accelerometer to tell whether you are moving, and, if you grant the motion permission your phone asks for, it also reads your step counter to work out your running cadence. Both are processed on your device. Neither your step count nor your cadence is sent to Onome's servers or to any third party. Usage Analytics: We send usage events to PostHog, our analytics provider, tied to your device identifier. They cover starting and completing runs, creating, editing, deleting, and duplicating workouts, importing a workout from a photo or a voice recording, coaching cues played and the coaching voice used, permission prompts you accept or decline, and settings you change. A completed run reports its distance, duration, average pace, whether GPS was available, how many splits you finished, and whether you finished it. The analytics SDK also reports app lifecycle events such as the app being installed, updated, opened, or moved to the background. Because these events travel over the internet, PostHog also receives your device's IP address. You can turn usage analytics off at any time in the app's settings. Crash & Diagnostics: We use Sentry to collect device information, operating system version, and crash stack traces for stability improvements. Your device identifier is attached to these reports. Crash reporting is deliberately independent of the usage analytics setting and continues when you turn usage analytics off. Onome's servers report their own errors to Sentry as well, and they do so with no filtering step applied: the error is sent to Sentry as the server produced it. Errors can be reported from any request path, including run uploads, email sign-in, your runner profile and preferences, training plan generation, workout import, subscriptions, and account deletion. What is sent is the error text and a stack trace. The request that caused the error is not attached, so no request body, headers, or query string reach Sentry, and the answers you gave in your runner profile are not written into these reports. An error text can carry identifiers such as your device identifier and your account identifier, replies from the third-party services our servers call, including, if our email provider rejects a sign-in email, your email address inside that provider's reply, and fragments of a workout a model produced from your photo or voice recording. Turning usage analytics off does not affect server-side error reporting. Images & Voice Recordings: When you use the workout creation feature, the photo or voice recording is uploaded to Onome's servers. Our server then forwards it to OpenRouter, an AI gateway, which routes it to a model provider that reads the photo or transcribes the recording. A photo is forwarded exactly as your device sent it, including any metadata the image file carries. Onome does not store the photo or the recording; the workout created from it is held for about ten minutes so your device can collect the result. Purchases & Subscriptions: If you buy a subscription, the purchase itself is made through the Apple App Store or Google Play, and we learn about it from RevenueCat, our subscription provider. We store your subscription status, the product you bought, the store it came from, and the store's transaction identifiers, including the purchase token that identifies your purchase to the store, along with a receipt recording the amount, the currency, the tax rate, the country the purchase was made in, and the date. We also keep the notifications RevenueCat sends us about your subscription as we received them. We never receive or store your card details.
How We Use Your Information
We use collected information to: • Provide and operate the running and fitness service • Create and manage your account and keep you signed in • Generate personalized training plans from your runner profile, your training goal, and your run history • Track usage patterns to improve the app experience • Diagnose crashes and technical issues via Sentry • Process voice and image input to create workouts via OpenRouter and its AI model providers • Manage subscriptions and process purchases
Third-Party Services
Our app and our servers use the following third-party services that may process your data: • PostHog: usage analytics, hosted in the United States (receives your device identifier, the usage events and run metrics described above, and your IP address) • Sentry: crash reporting and diagnostics (receives device info, OS version, crash traces, and your device identifier from the app, and unfiltered error reports from Onome's servers) • OpenRouter: AI gateway that routes workout creation and training plan requests to model providers (receives photos, voice recordings, and your runner profile). For training plan generation we name the models we want but allow OpenRouter to fall back, so a plan request, which carries your runner profile, can be served by an inference provider we have not named here • OpenAI: AI model provider used via OpenRouter to read workout photos, transcribe voice recordings, and generate training plans • Anthropic: AI model provider used via OpenRouter when training plan generation falls back from the primary model (receives your runner profile and training history) • Google Maps SDK: map rendering (receives the coordinates of the map area shown, which are derived from your run) • Google Sign-In: account sign-in (Google learns that this device signed in to Onome with your Google account, and returns your email address and name to us) • RevenueCat: subscription and purchase management (receives your device identifier and your purchase and subscription state) • Apple App Store and Google Play: purchase processing and subscription billing • Amazon Web Services: hosting for Onome's servers, in the United States. Your account, profile, plans, and run history are held in a managed PostgreSQL database; GPS track files are held in Amazon S3; sign-in emails are sent through Amazon SES, which receives your email address; a managed cache holds short-lived state, including rate-limit counters keyed on your IP address or your email address, session revocations, and a workout imported from a photo or a voice recording for about ten minutes; load balancer access logs, which include your IP address, are held in Amazon S3; and our own request logs, which record the method, path, status, and duration of each request and no IP address, are held in Amazon CloudWatch for three months • Expo: over-the-air app updates. On every launch the app asks Expo's update service whether a newer version of the app is available. The request identifies the build that is asking, and, because it travels over the internet, Expo receives your device's IP address Each third-party service operates under its own privacy policy. We encourage you to review their respective policies.
Data Storage & Security
Fitness and location data, including GPS tracks, pace, distance, and duration, is stored locally on your device while you run. Once a run finishes and syncs, that data is uploaded to Onome's servers and stored there using industry-standard security measures. Onome's servers run on Amazon Web Services in the United States. Traffic between the app and our servers uses HTTPS, and our servers reach the database, the cache, and file storage over encrypted connections. Data is also encrypted at rest: your account, profile, plans, and run history are held in a managed PostgreSQL database, GPS tracks are held as files in Amazon S3, and short-lived state such as rate-limit counters and an in-progress workout import is held in a managed cache. Usage analytics is transmitted to PostHog, our analytics provider, and stored on its United States cloud. If you use Onome from outside the United States, including from the European Union, the European Economic Area, or the United Kingdom, your personal data is transferred to and processed in the United States.
Children's Privacy
The app is intended for users aged 14 and older, and we do not accept a runner profile that reports an age below 14. We do not knowingly collect personal information from children under 14. If we learn that we have collected data from a child under 14, we will delete it promptly. If you believe a child under 14 has provided us with personal information, please contact us at hello@onome.co.
Data Retention & Deletion
Local Data: Delete the app to remove all on-device data including GPS tracks, workouts, and fitness metrics. How long we keep server-side data: We keep your data for as long as your account exists. Your account, profile, plans, and run history are not deleted automatically on a schedule. They are removed when you use Delete Account, or when you ask us to remove them; Reset Data removes your whole run history from your account, and deleting a single run removes that one run, both as described below. Some operational data does expire on its own: our server request logs after three months, and a workout imported from a photo or a voice recording after about ten minutes. Reset Data: Available in the app under Settings > Data & Privacy. It permanently deletes your run history from this device and removes it from your account on Onome's servers. Your runs stop being available to you or to any of your devices, and we delete the stored GPS track files. The run records themselves are marked as deleted rather than erased from our database, so a summary of each run, including its distance, duration, pace, and timestamps, remains there. Your account, workouts, and settings are left as they are. Delete a Run: Available on a saved run, from the trash action in the header of its detail screen. It permanently deletes that run from this device and removes it from your account on Onome's servers, and we delete its stored GPS track file. The run stops being available to you or to any of your devices, and it cannot be restored or uploaded again afterwards. As with Reset Data, the run record itself is marked as deleted rather than erased from our database, so a summary of the run, including its distance, duration, pace, and timestamps, remains there. Your other runs, your account, your workouts, and your settings are left as they are. Delete Account: Also available under Settings > Data & Privacy. It erases your account and the personal data tied to it. Your user record, name, email address, sign-in identities and sessions, runner profile, training plans and fitness history, run records including the workout attached to each run, and your device registrations along with the language and unit preferences held on them are deleted from our database, and we delete the stored GPS track files. What deletion does not currently cover: Deletion of stored GPS track files is best-effort, and our track storage keeps previous versions of a file, so the raw GPS traces from your runs can remain in our storage after any of these actions even when the deletion itself succeeds. Runs recorded by older versions of the app could also hold their GPS points inside the run record itself; Reset Data and Delete a Run mark that record deleted without removing those points, while Delete Account erases the record entirely. None of these actions deletes the usage analytics held by PostHog, and none of them deletes our server logs, which expire on their own three months after they are written. A small set of billing records, such as receipts and payment references, is kept after account deletion with the link to your account removed, because we are required to retain them for financial and legal reasons. You can also contact hello@onome.co with any data deletion request, including a request to delete your usage analytics.
Your Rights
EU/EEA Users (GDPR): You have the right to access, rectify, erase, port, and object to the processing of your personal data. California Users (CCPA): You have the right to know what data is collected, request deletion, and opt out of the sale of personal information. We do not sell your personal data. You can turn off usage analytics at any time in the app's settings, and you can delete your data using Reset Data or Delete Account under Settings > Data & Privacy, or delete a single run from its detail screen. To exercise any of these rights, contact us at hello@onome.co. The app has no self-service data export today, so we handle access and portability requests by email.
Changes to This Policy
We may update this Privacy Policy from time to time. Changes will be delivered via app updates. Your continued use of the app after an update constitutes acceptance of the revised policy.
Contact
For questions or concerns about this Privacy Policy: Email: hello@onome.co Website: onome.co