Privacy Policy.

Cue AI (“we”, “our”, or “us”) is operated by Anutech Pty Ltd, registered in Australia. We are committed to protecting your privacy and being transparent about how we collect, use, store, and share your information.

This Privacy Policy explains how we handle your data when you use the Cue AI mobile application, website, and related services (collectively, the “Service”). By using the Service, you consent to the practices described in this policy.

2.1 Account Information

• Name, email address, and profile photo
• Authentication credentials (managed via Firebase Authentication or third-party sign-in providers such as Google and Apple)
• Subscription tier and billing status (managed via RevenueCat; we do not store credit card numbers)

2.2 User-Created Content

• Tasks, habits, routines, goals, and notes you create
• Journal entries and reflections
• Calendar events and schedules
• Conversations with the AI assistant
• Photos or files you upload

2.3 Health & Fitness Data

If you choose to connect Apple Health (iOS) or Health Connect (Android), Cue may read the following categories of data based on the permissions you grant:

You also may enter health data manually (e.g., workout logs, water intake, sleep hours). Manual entries are stored separately from device-synced data.

Cue only requests the minimum Health Connect or HealthKit permissions necessary for its current features. We do not request access to heart rate, blood pressure, weight, body composition, nutrition, hydration, menstruation, respiratory, or other sensitive biometric data.

2.4 Google Services Data

If you choose to connect your Google account, Cue AI requests the following OAuth scopes. Connection is optional and can be revoked at any time from your Google Account → Security → Third-party access, or from Settings → Integrations inside Cue.

• Gmail — https://www.googleapis.com/auth/gmail.modify
  Read, compose, send, and organise messages in your connected Gmail account. Cue uses this access to display inbox items you choose to view, draft replies at your request, send those replies only with your explicit approval, organise messages into labels, archive or mark messages as read when you instruct us to, and turn emails into tasks, reminders, or calendar events you accept. We never auto-send, auto-delete, or permanently remove messages without an in-app confirmation from you.
• Google Calendar — https://www.googleapis.com/auth/calendar
  View, create, edit, and delete calendar events and availability. Cue reads your events to understand your schedule and avoid conflicts when suggesting or planning tasks. Cue creates, edits, or deletes events on your connected calendar only when you ask it to, or through a channel you have authorised to act for you:
  • In the Cue app: Cue shows you each new, changed, or deleted calendar event first and makes the change only after you confirm it, including when Auto mode is on. If you don't name a calendar, Cue adds the item to Cue's own schedule rather than your Google Calendar.
  • Through an assistant you have connected to Cue (such as Claude or ChatGPT): Cue creates an event when that assistant requests it for you, subject to that assistant's own approval settings, which may let it act without asking you first. Events created this way do not send invitations. Editing or deleting an existing event this way always requires your confirmation on a Cue page.
  • By email to your Cue Inbox address (where available): when you write to Cue from one of your verified addresses that is set to act on your requests (the default), Cue can create or edit an event on the calendar you name without a further confirmation in the app. Set that address to ask first if you want to approve each change. A contact you have set to let Cue handle automatically can have Cue create an event that invites only that contact and you. Cue never deletes calendar events in response to an email.
• Google Tasks — https://www.googleapis.com/auth/tasks.readonly
  View your Google Tasks lists and items so Cue can import them into your unified Cue task list. We do not modify or delete your Google Tasks.
• Basic profile — openid profile email
  Your name, email address, and profile picture, used only to identify the connected account and sign you in.

Detailed information on how Cue AI handles Google user data, including our Limited Use commitment, is provided in Section 2.5 — Limited Use Disclosure for Google User Data.

2.5 Limited Use Disclosure for Google User Data

Cue AI's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, Cue AI commits to the following:

1. Permitted application use. Google user data is used only to provide or improve the user-facing features of Cue AI described in Section 2.4 above. No other use is permitted.
2. No advertising. Google user data is never used for advertising, including personalised, re-targeted, or interest-based advertising, and is never shared with ad networks or data brokers.
3. No sale or independent transfer. Google user data is never sold, rented, or licensed. We do not transfer it to any third party for that party's own purposes. Data may flow to sub-processors acting on our behalf (listed in Section 8) solely to deliver the features you use, to comply with applicable law, or in connection with a merger, acquisition, or sale of assets in which the acquirer honours this policy.
4. No generalised model training by Cue. Cue AI does not use Google user data — including Gmail content, email metadata, Calendar events, or Google Tasks — to develop, improve, or train generalised or non-personalised artificial intelligence or machine learning models, including large language models. When a feature you request sends Google user data or selected Cue context to Gemini, Google's handling depends on whether the Gemini API project has active billing and on the feature and settings used. Google states that paid-service prompts and responses are not used to improve Google products, though abuse-monitoring retention may apply; where Google's unpaid-service terms apply, submitted content and generated responses may be used to improve Google products and reviewed by humans. Google's abuse-monitoring guidance describes retaining prompts, context, and outputs for 55 days. Zero-data-retention has feature-specific conditions and exceptions; this policy does not represent every Gemini request as zero-retention. See the Gemini API Terms, abuse-monitoring guidance, and zero-data-retention guidance.
5. No human reading of data. No human at Cue AI or Anutech Pty Ltd reads Google user data, except in the following narrow circumstances:
   • With your affirmative agreement for specific messages (for example, when you explicitly request Cue support to help with a specific email);
   • When strictly necessary for security, abuse prevention, or compliance with applicable law;
   • For internal operations, and only after the data has been aggregated and anonymised so that individual users cannot be identified.
6. Encryption and access control. Google user data is encrypted in transit (TLS 1.2+) and at rest (AES-256) using Google Cloud default encryption. Access is restricted to authenticated Cue backend services using Firestore security rules and IAM policies. No user data is written to application logs or error reports.
7. Retention and deletion. Google user data is retained only for as long as necessary to deliver the feature you use. Gmail, Calendar, and Tasks tokens are immediately revoked when you disconnect the integration. Any cached Google content is deleted from our servers within 30 days of disconnection, and backups are purged within 6 months, as described in Section 5.
8. Revocation. You can revoke Cue AI's access to your Google account at any time through your Google Account → Security → Third-party access, or by disconnecting the integration inside Cue at Settings → Integrations.

2.6 Device & Usage Data

• Device type, operating system version, and app version
• Optional product usage analytics (via PostHog, subject to your analytics consent)
• Crash reports and performance diagnostics (via Firebase Crashlytics)
• Push notification tokens (for delivering notifications)

When a new account is authenticated, Cue records a one-time, coarse signup surface (“web”, “iOS”, or “Android”) and sign-in provider category for account-integrity, service-measurement, and fraud-prevention purposes. This record is sent to PostHog by our authenticated server using the Firebase account identifier already required to operate your account. It does not include your name, email address, content, precise location, device model, advertising identifier, fingerprint, or session replay, and it does not set an analytics cookie or use optional client-side analytics before consent.

2.7 Location Data

With your permission, Cue may access your approximate or precise location to support location-based reminders and automations. Location data is processed on-device for triggering automations and is not stored on our servers.

2.8 Camera & Microphone

The camera is used only when you choose to upload a photo. The microphone is used only for voice input to the AI assistant. Audio is processed for transcription and is not stored after the conversation ends.

We use your information to:

• Provide personalised AI coaching, task management, and routine suggestions
• Display health metrics on dashboards and track goals
• Deliver notifications, reminders, and proactive nudges
• Sync your data across your devices
• Improve our AI models and service quality
• Provide customer support
• Ensure security, prevent fraud, and enforce our terms
• Comply with legal obligations

Account email and optional outreach

If you provide a Cue account email, account/service messages may include a one-time signup welcome, trial-start or access confirmation, purchase or subscription confirmation, security notices, and support replies. Whether a particular welcome or other message is optional outreach depends on its purpose and applicable law; opening an account is not blanket consent to marketing.

To send these messages and handle replies, Cue processes the recipient email address, saved name where available, message and reply content, delivery records, and preferences used for sending and reply handling.

Optional promotional tips, reactivation messages, and campaigns are separate. We send them only where permitted, with any required consent and in line with your preferences. The unsubscribe link or available Cue preferences affect optional outreach; essential account/security messages and support replies remain separate. We do not use private Cue content, such as tasks, notes, or conversations, to select or create promotional outreach.

On-Device Storage (Raw Samples)

Raw health samples (individual step counts, sleep stage transitions, etc.) are stored only on your device in an encrypted local database. Raw samples are never uploaded to our cloud servers. Data is encrypted at rest using the device's native encryption (iOS Data Protection / Android file-based encryption).

Cloud Storage (Summaries Only)

If you explicitly enable cloud sync, Cue uploads summarised data to Google Cloud Firestore:

• Event summaries — Session-level records (e.g., one workout session, one sleep session). These contain aggregated metrics, not raw samples.
• Daily aggregates — One summary per day with totals and averages (total steps, total sleep hours, etc.).

All cloud data is encrypted in transit (TLS 1.2+) and at rest (AES-256 via Google Cloud default encryption). Data is stored in Google Cloud Firestore.

You may request deletion of your data at any time through:

• In-app: Settings → Account → Delete Account. This immediately initiates deletion of your account and all associated data.
• Health data only: Settings → Integrations → Health → Delete Health Data. This removes cloud-stored health summaries and schedules local data deletion.
• Email: Send a request to privacy@cueai.app with the subject “Data Deletion Request”.

Deletion Timeline

• Your account will be deactivated immediately upon request.
• Primary data deletion will be completed within 45 days.
• If additional time is needed, we will notify you and complete deletion within an additional 45-day extension (90 days total).
• Data in backup systems will be permanently removed within 6 months of the deletion request.

You will receive an email confirmation once deletion is complete. Deletion is permanent and cannot be undone.

We implement the following security measures:

• All data encrypted in transit (TLS 1.2+) and at rest (AES-256)
• Firebase Authentication ensures only authenticated users can access their data
• Firestore security rules enforce per-user document isolation
• Rate-limited API endpoints to prevent abuse
• No health data is logged in application logs or error reporting
• Regular security reviews of infrastructure and code

We do not sell, rent, or license your personal information. We may share information with:

• Service providers that support the features you request (listed below; handling and retention depend on the applicable provider terms and settings)
• Legal authorities when required by law
• Third-party messaging channels (Slack, Telegram) if you explicitly enable insight sharing to those channels

Sub-Processors

AI provider selection can vary by feature and current routing. A selected provider may receive relevant request inputs and source context; its terms and retention controls vary by service and settings.

Depending on your jurisdiction, you have the right to:

• Access — Request a copy of all personal data we hold about you.
• Rectification — Correct inaccurate data.
• Deletion — Request deletion of your data (see Section 6).
• Portability — Export your data in a machine-readable format (JSON). Use Settings → Privacy → Export My Data, or email privacy@cueai.app.
• Restriction — Object to or restrict certain data processing.
• Withdraw consent — Withdraw consent for health data collection at any time by disconnecting the health integration in Settings. Withdrawal does not affect lawfulness of processing performed before withdrawal.

To exercise any of these rights, contact privacy@cueai.app. We will respond within 30 days.

For users in the European Economic Area, we process data under the following legal bases:

• Contract performance — Processing necessary to provide the Service (account data, user content).
• Legitimate interest — Essential account-integrity telemetry, security, fraud prevention, and service measurement.
• Consent — Optional product analytics and session replay.
• Explicit consent — Health data (GDPR Article 9(2)(a)), Google API data, location data, and notifications.

Health data is classified as special category data under GDPR Article 9. You may withdraw consent at any time. Data transfers outside the EEA are governed by Standard Contractual Clauses with our sub-processors. You have the right to lodge a complaint with your local data protection authority.

California (CCPA/CPRA)

We do not sell personal information. California residents may exercise their rights to know, delete, and opt out by contacting privacy@cueai.app.

Washington (My Health My Data Act)

This policy serves as the dedicated consumer health data privacy policy required by the Act. Opt-in consent is obtained before collection of health data. Deletion requests are honoured within 45 days (with a 45-day extension if needed). Processor contracts with Google include instruction limitations.

Australia (Privacy Act 1988)

Anutech Pty Ltd complies with the Australian Privacy Principles. You may lodge a complaint with the Office of the Australian Information Commissioner (OAIC) if you believe your privacy has been breached.

Cue uses AI models to generate personalised coaching suggestions, task recommendations, and health insights based on your data. These AI-generated outputs are informational only and do not produce legal, financial, or medical effects. You are never subject to a decision based solely on automated processing that significantly affects you. You may contact privacy@cueai.app if you have questions about how AI is used in the Service.

In the event of a data breach affecting your personal or health data, we will:

• Notify affected users within 60 days of discovery
• Notify relevant regulatory authorities as required by law
• Provide details of what data was affected and remedial steps being taken
• Offer guidance on protective measures you can take

Our Service is not directed to individuals under the age of 13 (or 16 in the EEA). We do not knowingly collect personal information from children. If we learn that we have collected data from a child under the applicable age, we will delete it promptly.

We may update this Privacy Policy from time to time. Material changes will be communicated through in-app notification and by updating the “Last updated” date on this page. If changes materially expand how we use health data, we will obtain fresh consent. Continued use of the Service after notification constitutes acceptance of the updated policy.

If you have questions about this Privacy Policy or want to exercise your data rights, please contact us:

ANUTECH PTY LTD provides Cue (Cue Personal AI Assistant). When you connect Cue to ChatGPT, Codex or Claude, you sign in to your existing Cue account and choose the permissions and eligible records you want to share. Cue uses those permissions to read permitted records and carry out the specific actions you request. Your Cue password, Firebase sign-in token and plugin signing keys are not given to the model or included in tool arguments.

Depending on your choices, shared records may include tasks and commitments, authorised calendar details, selected notes and lists, nonclinical personal plans and progress, goals and habits, programs and sessions, selected memories and journal entries, Pulse items and automation approvals, and eligible career, learning, home, bookkeeping, relationship or challenge records. Private categories require individual record selections, and installed tools retain their assistant-access restrictions. Limit information about other people to what the selected task needs.

Cue returns permitted content and action results to the ChatGPT or Codex environment in which you use the integration. OpenAI handles that content according to the terms, privacy controls and data policies applicable to your OpenAI account. Review those controls before sharing personal information. Specifically requested existing Cue generation features may use Cue's configured AI providers under this privacy policy; the integration supplies only inputs permitted for that requested feature.

Cue is also available in Claude, including Claude Cowork and Claude Code where supported, through the Cue connector. The sign-in, permissions, record selection, revocation and retention terms in this section apply in the same way. Cue returns permitted content and action results to the Claude environment in which you use the connector, and Anthropic handles that content according to the terms, privacy controls and data policies applicable to your Anthropic account. Review those controls before sharing personal information. Claude's own tool-approval settings decide whether Claude asks you before it calls Cue; actions that Cue requires you to confirm, such as editing or deleting a calendar event (see Section 2.4), still wait for your confirmation on a Cue page. The Claude connector guide links to the data policies and terms of each AI provider Cue may use.

This integration does not support clinical or health integrations, bank linking, payments, card credentials, government identifiers, broad mailbox access or precise-location requests. Do not put those details into an integration workflow. Selecting records is an access boundary; it does not make every possible free-text record appropriate to share.

Changes you request are saved through Cue's normal account services. Saved records remain part of your Cue account and can be managed using its normal edit and deletion controls. Removing integration access does not delete records you chose to save in Cue or copies already present in your host conversation.

You can revoke a Cue grant from the Cue connection controls or disconnect it in the host. A revoked grant cannot authorise further integration calls. Account deletion also removes integration access according to Cue's account deletion process. Authorization and execution metadata is kept through its associated authorization, replay and security support windows. Expired records are queued for automatic deletion, which uses asynchronous cleanup. Expiry and revocation prevent access independently of that cleanup. Cue account records and canonical operation receipts remain subject to Cue's normal account and operational retention policies. Routine integration events contain technical outcome and timing fields rather than tokens or raw note, prompt or journal content.

For integration questions or deletion and access requests, use Cue support.