Who we are
On Cue is operated by Zimmerman Legacy Holdings, LLC. In this policy, "On Cue," "we," and "us" refer to Zimmerman Legacy Holdings, LLC and the On Cue service.
Information you provide
Inside the app, you can choose settings such as Cue Mix preferences, receptivity, quiet state, context preferences, and music guardrails. These are instructions you give On Cue and are separate from the private context it learns on your device.
If Apple provides your name during the first Sign in with Apple authorization, On Cue may use it to seed your account display name. On Cue does not ask for an email address as part of Sign in with Apple.
If you contact support, we receive the information you choose to include in your message, such as your device model, iOS version, screenshots, or diagnostic details.
Apple Music & MusicKit
With your permission, On Cue uses Apple's MusicKit to find the recordings available for playback, play music, and display album artwork. Once Apple Music is connected, On Cue also keeps a list of the songs in your library on your iPhone, so it can choose Cues from your own music. That list holds each song's title, artist, genres, Apple identifiers, and whether Apple marks it explicit. Unless you turn on Learn my music, described below, it does not include how often or when you played a song, or when you added it to your library.
Learning from your listening is a separate choice inside On Cue, called Learn my music. It stays off unless you turn it on. On Cue offers it once during setup, after Apple Music connects, and it is always available in On Cue's Music screen, where you can turn it on or off at any time. When it is on, On Cue uses MusicKit to understand signals from your music experience, such as recently played or frequently played music, how often you play a song, your playlists, and your favorites. What it learns stays on your iPhone.
Your Apple Music listening history and On Cue's private learned taste state are processed for the experience on your iPhone. On Cue does not upload raw Apple Music listening history, your private taste graph, song titles, artist names, or album titles to PostHog analytics or to our Supabase account and settings backend.
MusicKit communicates with Apple as needed to authorize access, search Apple's catalog, retrieve artwork, and play music. You can revoke Apple Music access at any time in iOS Settings. When you do, On Cue stops using your library list the next time you open the app.
Location
If you grant location access, On Cue can use your current location and, with Always access, Core Location visit events such as arrivals and departures. Precise coordinates, visit history, and learned place patterns are stored on your iPhone for On Cue's contextual reasoning. Where you live, precise location may be treated as sensitive information; On Cue uses it only on your device and only with the separate permission you grant through iOS.
On Cue does not send precise coordinates or location history to Supabase or PostHog. PostHog separately derives an approximate, city-level location from the IP address of each analytics request, as described under Analytics. Apple platform services may process a coordinate when On Cue requests WeatherKit information or optional reverse geocoding. Those requests are handled by Apple services rather than by an On Cue location-history backend.
Location is optional. You can change When In Use, Always, precise-location, or denied access at any time in iOS Settings.
Weather & contextual information
On Cue can use weather, time of day, season, and other structural context to decide whether a moment fits a Cue. Weather information is obtained through Apple's WeatherKit for the location needed for the request. On Cue does not maintain a server-side history of your weather or location context. The approximate location that PostHog derives from the IP address of each analytics request is described under Analytics.
Calendar
If you grant calendar access, On Cue reads a bounded window of calendar events to understand the shape and rhythm of your day. On-device observations may include event title, event location, start and end times, all-day or recurring status, and EventKit identifiers needed to recognize the same event across reads.
Calendar event content stays on your iPhone. On Cue does not send calendar titles, locations, event identifiers, notes, attendees, or raw event content to Supabase or PostHog analytics.
Calendar access is optional and can be revoked at any time in iOS Settings.
Motion & Fitness
If you connect Motion & Fitness, On Cue uses Apple's Core Motion activity recognition to tell when you have recently been driving or cycling, so it can recognize a moment such as arriving after a drive. On Cue asks for this access only when you tap to connect it, and you can choose not to.
Motion activity is read and processed on your iPhone only. On Cue keeps only the latest reading that iOS recognized with high confidence as driving or cycling, and a newer reading replaces it, so no history of your movement is kept. That reading holds the activity and how confident iOS was, not speed, route, or location. Other activities, such as walking or standing still, are not kept.
Motion activity is not sent to Supabase, PostHog, or any On Cue-operated backend. When On Cue schedules a Cue, analytics may record only whether the moment was supported by your calendar, by motion, or by both, never which activity iOS recognized or when. Like other permissions, analytics also records the outcome of the Motion & Fitness permission request. On Cue never uses motion activity for fitness or health information and does not use HealthKit.
Motion & Fitness is optional and can be turned off at any time in iOS Settings.
On-device intelligence
On Cue performs context interpretation, Cue scoring, and private taste reasoning on your iPhone. On supported devices, On Cue may use Apple's Foundation Models framework as part of that local interpretation.
The current release does not send private context to an On Cue-operated generative-model service. Model prompts and reasoning are not sent to Supabase or PostHog analytics.
Accounts & settings
On Cue uses Sign in with Apple and Supabase to provide an account. Supabase stores the account identifier, the optional display name described above, and selected user-controlled settings so they can be associated with your account. The account identifier is also used to keep subscription and analytics identities aligned after sign-in.
Supabase does not receive raw GPS history, Apple Music listening history, the private learned taste graph, raw calendar content, model prompts, or model reasoning.
Saved Moments in the current release are stored locally on the device. They are not represented as cross-device synced history in this release.
Subscriptions
Subscriptions are purchased through Apple's App Store. On Cue uses RevenueCat to read subscription entitlement and purchase state. After you sign in, RevenueCat is associated with the same On Cue account identifier used by Supabase so purchases and restores can be applied to the correct account. When a product experiment is running, On Cue also records the name of the version of the app you were shown with RevenueCat, as described under Analytics.
Apple handles payment information. On Cue does not receive your full payment-card details.
Analytics
On Cue uses PostHog for deliberately limited product analytics. When analytics is enabled for a build, events can record coarse outcomes such as whether sign-in, a purchase, a permission request, a Cue scheduling pass, playback, Save, or Skip succeeded, failed, or was cancelled. Signed-in events may be associated with the On Cue account identifier.
Analytics may also include app version, build, environment, and ordinary technical metadata needed to operate the analytics service. Purchase and restore events also record whether the App Store handled the transaction as a real purchase or as a test (sandbox) purchase. PostHog derives an approximate, city-level location from the IP address of each request the app makes to it (country, city, postal code, and approximate latitude and longitude) and stores that location with the event. PostHog does not store the IP address itself with the event. Session replay, interaction autocapture, console capture, and performance capture are disabled in On Cue's PostHog configuration.
If you installed On Cue after tapping or seeing one of our ads in the App Store, Apple tells the app which of our Apple Ads (formerly Apple Search Ads) campaigns, ad groups, keywords, and ads led to the install, together with the identifier of our own Apple Ads account, whether you tapped the ad or only saw it, and whether the install was a first download, a redownload, or a pre-order. This is Apple's standard attribution: it does not use your device's advertising identifier, it does not track you across other companies' apps or websites, and it involves no permission prompt. On Cue records Apple's answer once per install with its analytics. The campaign identifiers describe our ads, not you, but they are stored with your analytics profile, so once you sign in they are associated with the On Cue account identifier like other analytics. On Cue uses them only to measure whether our ads work. If your install did not come from an ad, only that fact is recorded. Test versions of the app, such as TestFlight builds, do not record these identifiers.
Crash reports are part of analytics. If On Cue crashes in a way the PostHog software in the app can record, it writes a crash report on your iPhone and sends it to PostHog the next time the app launches. Some terminations, such as the system ending the app for memory pressure or a force-quit, cannot be recorded this way. A crash report contains the kind of crash (for example, the exception class or signal name), the stack of app and system code that was running, and the binary image information needed to read that stack, together with the same app version, build, and environment values as other events. Like other events, it may be associated with the On Cue account identifier when you are signed in. Before a crash report leaves the device, On Cue removes the written error message and does not attach a breadcrumb trail of prior activity, so what remains describes where in the code the crash happened rather than any content the app was handling.
On Cue may occasionally show an optional in-app survey through PostHog. PostHog decides when to offer a survey based on the analytics described in this section. Surveys ask you to choose from set answers, and On Cue does not send written answers: if a survey offers a text field, the app removes anything typed there before the response is sent. If you answer, the choices you select are sent to PostHog with the same identifiers as other analytics events, including the On Cue account identifier when you are signed in. PostHog also records whether a survey was shown or dismissed. You do not have to answer, and closing a survey does not change how On Cue works.
On Cue also uses PostHog to run product experiments, in which different people see different versions of part of the app, such as the moment the subscription screen appears. The app asks PostHog which version to show, and the assigned version is recorded with analytics events so the versions can be compared. On Cue also records the version's name ("control" or "test") with RevenueCat as an attribute of your subscription record, so subscription outcomes can be compared between versions. The version name says which version of the app you saw and nothing else about you.
On Cue does not send precise coordinates, location history, street addresses, raw Apple Music listening history, song titles, artist names, lyrics, raw calendar content, model prompts or reasoning, Apple identity tokens, or Supabase access and refresh tokens to PostHog. On Cue does not add coordinates or any location field to analytics events; the approximate location described above is derived by PostHog from the IP address that each request necessarily comes from.
How information is used
We use the information described above to:
- Recognize moments and surface Cues
- Personalize Cues to your taste, preferences, and rhythms
- Operate Sign in with Apple accounts and selected settings sync
- Operate subscriptions, purchases, and restore behavior
- Understand coarse product reliability and usage
- Compare versions of parts of the app through product experiments
- Measure whether our App Store ads lead to people who set up and subscribe
- Ask for optional feedback through in-app surveys
- Provide support and respond to requests
- Maintain security and reliability
Service providers
On Cue relies on Apple services for Sign in with Apple, MusicKit, WeatherKit, Core Location, EventKit, Core Motion (Motion & Fitness), notifications, and App Store billing; Supabase for account identity and selected settings storage; RevenueCat for subscription entitlement and purchase state, including the experiment version name described under Analytics; PostHog for coarse product analytics, crash reports, optional surveys, and product experiments; and Cloudflare for the public lifeoncue.app website.
These providers process data under their own agreements and privacy policies. The data sent to each provider is limited by the roles described above.
International transfers
Zimmerman Legacy Holdings, LLC is based in the United States, and the limited account, subscription, and analytics information described in this policy is stored and processed in the United States by Supabase (account identifier, display name, and synced settings), RevenueCat (subscription entitlement, purchase state, and experiment version name), and PostHog (coarse product analytics, crash reports, survey answers, and experiment versions). Apple processes Sign in with Apple, MusicKit, WeatherKit, and App Store data under Apple's own terms and in the regions Apple operates.
If you use On Cue outside the United States, this information is transferred to and processed in the United States, where privacy law may differ from the law where you live. We rely on contractual commitments with each provider that limit its use of the data to the roles described above, on the security measures described below, and on your consent where the law where you live requires it. Your private context, including precise location, calendar content, motion activity, and listening history, is not part of these transfers: it is not sent to Supabase, RevenueCat, PostHog, or any On Cue-operated backend. The one exception is described under Location: when you allow weather or reverse geocoding, a coordinate is sent to Apple's WeatherKit or geocoding services for that request, under Apple's terms, and is not retained by On Cue.
Data retention
Your Supabase account and synced On Cue settings are retained while your account exists and are deleted through the in-app account-deletion process, subject to backups, security needs, and legal obligations that may require limited retention.
| Information | Purpose | Kept for |
|---|---|---|
| Account identifier and display name | Provide your account and keep subscription and analytics identities aligned | Until you delete your account |
| Synced settings (Cue Mix, receptivity, context preferences, and music guardrails: the genres you lean toward, avoid, or stay within, and whether to avoid songs Apple Music marks as explicit) | Personalize Cues and restore your preferences | Until you delete your account |
| Subscription entitlement and purchase state | Provide paid access and restore purchases | Until you delete your account; Apple and RevenueCat keep transaction records for as long as their accounting, fraud-prevention, and legal obligations require |
| Coarse product analytics and survey answers | Reliability and product improvement | 12 months |
| Support correspondence | Respond to you and resolve problems | 24 months after the last message |
Local-only context, learned taste, observations, and Saved Moments remain on your iPhone until you remove them through available product controls or uninstall the app. Deleting the cloud account does not erase local-only data from the device.
Where a legal, accounting, security, or dispute-related obligation requires us to keep specific information longer, we keep only what that obligation requires and delete it when the obligation ends. You can contact us about a privacy or deletion request using the address below.
Your choices & permissions
Apple Music, location, calendar, Motion & Fitness, and notifications are controlled through iOS permissions. You can change or revoke them in Settings. On Cue is designed to work with the signals you choose to share, although fewer signals can mean fewer or less-specific Cues.
Inside On Cue, you can also change Cue Mix, receptivity, context preferences, quiet behavior, and music guardrails without editing raw learned context.
Your privacy rights
Depending on where you live, you may have the right to access the personal information we hold about you, to correct it, to delete it, to receive a copy in a portable format, to object to or restrict certain processing, to withdraw consent you previously gave, and to not be discriminated against for exercising these rights. Many of these rights are built into the product: iOS permissions let you withdraw access to Apple Music, location, calendar, Motion & Fitness, and notifications at any time, and the in-app account-deletion flow deletes your account and user-owned server data.
For anything you cannot do in the app, write to [email protected]. We will confirm your identity in a way proportionate to the request, usually by asking you to write from the Apple Account email associated with your On Cue account, and respond within 30 days. If we need more time, we will tell you why. Our privacy officer is Corey Zimmerman, reachable at the same address.
You also have the right to complain to the privacy regulator where you live. Examples in the regions where On Cue is available include the Autoridade Nacional de Proteção de Dados (Brazil), the Personal Information Protection Commission (South Korea and Japan), the Office of the Australian Information Commissioner, the Office of the Privacy Commissioner of Canada, the National Privacy Commission (Philippines), the Information Regulator (South Africa), the Office of the Data Protection Commissioner (Kenya), the Nigeria Data Protection Commission, and the Saudi Data and Artificial Intelligence Authority. We would appreciate the chance to address your concern first.
Deleting your account & data
A signed-in user can initiate account deletion from On Cue's account controls. The deletion flow asks you to confirm with Apple, revokes On Cue's Sign in with Apple authorization, and deletes the Supabase account and user-owned server data tied to it.
Deleting an On Cue account does not cancel an App Store subscription. Subscriptions are managed by Apple and must be cancelled separately through your Apple Account. RevenueCat may retain transaction history required to restore or reconcile purchases.
Account deletion also does not erase local-only data from your iPhone, including local Saved Moments, observations, learned music state, and device preferences. Uninstalling On Cue removes app-local data from the device. For privacy questions or requests that cannot be completed in the app, contact [email protected].
Children's privacy
On Cue is not directed to children. You must be at least 13 years old to use it, and older where the law where you live sets a higher age for consenting to a service like this on your own, for example 14 in South Korea and 18 in India. We do not knowingly collect personal information from anyone below the applicable age. If you believe a child has created an On Cue account, contact [email protected] and we will delete it.
Security
We use reasonable technical and organizational safeguards designed to protect information handled by On Cue, including platform authentication, access controls, encryption in transit, and database row-level security for user-owned account data. No service can guarantee absolute security.
Changes to this policy
We may update this policy as On Cue changes. When a change is material, we will provide notice appropriate to the change and update the date at the top of this page.
Contact
Questions about privacy can be sent to [email protected].
Zimmerman Legacy Holdings, LLC
Privacy officer: Corey Zimmerman
Texas, United States