Privacy Policy

Last updated: May 31, 2026

This policy describes how Niro Software handles information for the Cue Timer app, including what it collects, how it is used, and the choices you have.

Who We Are

Cue Timer is provided by Niro Software. You can contact us about privacy requests at [email protected].

Information We Collect

Cue collects the minimum information needed to build and run custom timers, protect the service, process purchases, and diagnose failures.

• Voice recordings. When you use the microphone, Cue records a short audio prompt so it can be transcribed and turned into a timer. Audio is sent to our API for transcription and is not retained after normal timer creation unless you explicitly submit a correction or debug sample.
• Transcripts and timer prompts. Cue processes voice transcripts and typed prompts to generate timer specifications. These may be associated with a Firebase user ID, client install ID, request ID, and provider metadata while the request is processed.
• Generated timer data. The timers you save are stored locally on your device and synced to Cue's API under your Firebase user ID so they can be restored after reinstall. Server-side saved timer sync stores the timer specification and library metadata, such as the timer ID, favorite state, and timestamps; it does not store raw voice audio, voice transcripts, typed prompts, or correction text as part of the saved timer record. Drafts and settings stay on your device.
• Prompt and generation logs. To monitor and improve timer quality, Cue logs the prompt text and the timer specification produced for each request to our observability provider (Axiom), along with technical metadata such as the model provider used and a request ID. These logs expire automatically and are not used for advertising.
• Account and device identifiers. Cue uses Firebase Authentication, including anonymous authentication, Firebase App Check, a client install ID, and request IDs to protect the API from abuse and keep usage tied to the correct app install.
• Purchase records. Cue uses RevenueCat, Apple, and Google to process purchases, restore purchases, and maintain credit balances. We receive purchase and entitlement events needed to grant and reconcile credits.
• Crash and diagnostic data. Cue uses Sentry and Cloudflare logs to understand crashes, API errors, rate limits, and service health. We scrub prompt and transcript fields from Sentry events before they are sent.
• Optional correction samples. If you choose to submit a correction or debug sample, Cue may retain the audio, transcript, corrected transcript, client install ID, Firebase user ID, device platform, app ID, project ID, transcription provider, transcription model, and timestamps so we can improve transcription and timer quality.

Information We Do Not Collect

Cue does not collect contacts, location, photos, calendar data, health data, browsing history, voice biometric identifiers, or advertising identifiers. Cue does not sell personal information, does not use third-party ad networks, and does not use your data for cross-app tracking.

How We Use Information

• To transcribe voice prompts and generate timer specifications.
• To save and run timers you create.
• To authenticate requests, prevent abuse, enforce rate limits, and protect paid provider usage.
• To process purchases, restore entitlements, manage credits, and reconcile purchase events.
• To debug crashes, production incidents, and failed requests.
• To monitor and improve the quality of timer generation, including by reviewing prompt and generation logs.
• To improve Cue when you explicitly submit a correction or debug sample.

Service Providers

Cue relies on service providers to operate the app. Depending on the feature and current routing configuration, information may be processed by:

• Cloudflare, including Workers, D1, R2, Workers AI, AI Gateway, Pages, rate limiting, and operational logs.
• OpenAI for transcription and timer generation.
• Anthropic, Google Gemini, OpenRouter, or Cloudflare Workers AI as model providers or fallback providers.
• Firebase Authentication and Firebase App Check.
• RevenueCat, Apple, and Google for purchases, entitlements, and purchase restoration.
• Sentry for crash reporting and diagnostics.
• Axiom for operational logging, including prompt and timer-generation logs used to monitor and improve quality.

Model-provider policies may change. As of this policy date, OpenAI states that API inputs and outputs are not used to train OpenAI models by default unless the customer opts in, and Anthropic states that commercial API data is not used to train generative models unless the customer opts in or submits feedback. Cue does not intentionally opt in to provider model training with your prompts, transcripts, or audio.

Retention

• Normal voice audio: processed transiently for transcription and not retained after normal timer creation.
• Optional correction samples: retained for up to 90 days unless a longer period is needed to investigate abuse, security, or legal obligations.
• Saved timers: timer specifications and library metadata are retained while your account exists so timers can restore after reinstall. Deleting a timer records a server-side deletion marker so it does not come back during sync.
• Drafts and settings: stored only on your device and removed when you delete the app.
• Prompt and generation logs: prompt text and generated timer specifications are retained in our observability logs for up to 30 days, then deleted automatically, unless a longer period is required by law or abuse prevention.
• Crash and diagnostic data: typically retained for 30 to 90 days depending on the provider and plan.
• Purchase records: retained as long as needed for purchase restoration, tax, accounting, dispute, fraud-prevention, and legal requirements.

Security

Cue uses HTTPS in transit and relies on provider-managed encryption at rest for production services. Access to production systems is limited to operational needs. No internet service can be guaranteed completely secure, but we work to keep collection limited and logs scrubbed.

Your Choices and Rights

You can choose not to grant microphone permission and use typed prompts instead. You can decline optional correction or debug-sample submission. Depending on where you live, including the European Economic Area, United Kingdom, California, and other jurisdictions, you may have rights to access, correct, delete, export, or object to certain processing of your personal information.

To make a privacy request, email [email protected]. We may need information sufficient to verify the request and locate relevant records.

Data Deletion

The saved timers you create are synced to Cue's API so they can be restored after reinstall. Deleting a timer removes it from your visible library and records a server-side deletion marker. Drafts and settings remain device-local.

A few records are kept on our servers because they cannot live only on your device: your saved timer specifications and library metadata, your credit balance and purchase history (tied to an anonymous Firebase user ID and a client install ID so paid credits can survive a reinstall on the same device when that anonymous identity is preserved), prompt and generation logs (which expire within 30 days), and any correction or debug samples you explicitly submitted. To delete these, email [email protected] with your App Store purchase receipt or other detail that helps us locate your records, and we will delete or anonymize them, typically within 30 days, except where retention is required for tax, accounting, dispute resolution, fraud prevention, or other legal obligations.

Children

Cue is not directed to children under 13. If you believe a child under 13 has provided personal information through Cue, contact us and we will take appropriate steps to delete it.

International Processing

Cue and its service providers may process information in the United States and other countries where they operate. Those countries may have privacy laws that differ from your location.

Changes

We may update this policy as Cue changes. We will update the "Last updated" date above and, for material changes, provide additional notice where appropriate.

Contact

Niro Software
Privacy: [email protected]
Support: [email protected]