Chirp Privacy Policy
Last updated: 21 November 2025
Audio and text are processed in real time by Google Gemini API for transcription, natural language responses and grounded web search.
Chirp uses the paid Gemini API. For paid services, Google does not use your prompts or responses to train its models.
Chirp does not store your voice, messages, contacts or location history off your device. Chirp only stores small personalisation details locally on your Apple Watch, as described in Section 2.6.
Google may retain API data for a limited period for security and abuse monitoring.
Chirp can request access to:
Contacts – to help draft messages and emails to a specific person.
Location – to improve search results such as weather and nearby places.
These permissions are requested via standard Apple permission modals, and you can deny or revoke them at any time.
No ads, no profiling, no behavioural tracking.
Chirp is for adults only (18+).
Privacy questions: jonny@chirp.watch
AI responses may contain errors or omissions. Do not rely solely on them; always verify important information before taking action.
Chirp: AI for Apple Watch (“Chirp”, “the app”) is developed by Jonathon Lau (“the developer”, “we”, “us” or “our”).
This Privacy Policy explains how Chirp handles your information. Chirp is designed so that all requests are processed in real time, with no long term storage of your content by the app itself.
Chirp uses Google’s Gemini API for:
Speech to text
Natural language responses
Grounded web search
Help composing messages and emails
Please review Google’s terms and policies, which govern how your data is handled once it reaches their systems:
Google Privacy Policy: https://policies.google.com/privacy
Gemini API Additional Terms of Service: https://ai.google.dev/gemini-api/terms
Gemini API usage and abuse monitoring: https://ai.google.dev/gemini-api/docs/usage-policies
Gemini data governance for Google Cloud: https://docs.cloud.google.com/gemini/docs/discover/data-governance
Chirp does not:
Know your name or Apple ID
Create a personal profile or behavioural history
Track you across apps or websites
Use advertising SDKs
We only handle data that is needed in the moment to answer your request.
When you speak to Chirp:
Your audio is captured on the watch.
The audio and related text context are sent securely to Google Gemini API.
Gemini:
Transcribes your speech to text
Generates a response
Optionally calls grounded search for web results
Chirp itself does not store:
Audio recordings
Transcripts
AI responses
Once the request has been sent to Google and a response returned, Chirp discards the content.
Model training
Chirp uses the paid Gemini API. For paid services, Google states that prompts and responses are not used to train or improve their models.
Abuse monitoring and retention
Google may retain prompts, context and responses for a limited period (currently described as up to 55 days) for abuse monitoring and operational purposes.
Chirp does not control or see this retention.
Chirp can help you draft or send messages and emails to a specific contact, such as “Message Ben” or “Email Alex about dinner”.
On first use of any contact feature, Apple shows a system contacts permission modal.
You can allow or deny access. Chirp will only read contacts if you allow it.
Chirp does not upload or scan your entire contacts list.
When you use a contact feature:
Only the single contact you select (for example, Ben) is accessed.
If there are multiple matches for a name, Chirp will ask you to pick one.
For that chosen contact, Chirp may send to Google Gemini:
Contact name
Phone number or email address (as needed to compose the message or email)
This data is sent solely to:
Understand who you are referring to
Help generate a message or email draft
Provide contextual wording
Chirp does not:
Store your contacts
Sync your address book anywhere
Give the developer access to your contacts
You can revoke contacts access at any time in Apple Watch or iPhone settings. If you deny or revoke contact permission, you can still use Chirp, but contact based features will be limited.
Chirp can optionally use your approximate location to improve certain answers, for example:
Local weather
Nearby restaurants or shops
Region specific information
Behaviour:
On first use of a location based query, Apple shows a standard location permission modal.
You can allow once, allow while using or do not allow.
If you deny permission, Chirp will continue to work but results may be less specific.
When Chirp uses location:
Only a single, current approximate location is requested via system APIs.
Chirp does not store or log your location history.
If location is included in a query to Gemini, it is transmitted to Google along with the text of your request so that responses can be tailored.
Location data sent to Google is handled in line with the Gemini API and Google Privacy Policy.
You can change your location permission at any time in system settings.
Chirp uses Firebase Anonymous Authentication to track basic app metrics needed to operate the service, such as:
Anonymous user identifier (randomly generated)
Number of requests or messages
Activation date
Subscription status
We do not collect:
Behavioural analytics
Screen flows or session replay
Advertising identifiers
Data from Firebase is used only to:
Monitor app reliability
Understand overall usage at an aggregate level
Manage subscriptions
Chirp may store small amounts of information locally on your Apple Watch to personalise your experience. This may include:
Your preferred name
Chat preferences (for example, tone, style or language hints)
Light personalisation details you deliberately provide during conversations
This information:
Is stored only on your device. Chirp does not store this memory off your device or maintain any external copy of it.
Is included in requests sent to the Gemini API when generating responses, so that your personalisation, preferences and context are maintained across chats.
Is not retained or stored by Gemini beyond normal API processing under Google’s terms.
Can be cleared at any time in Chirp’s settings.
During chat sessions, Gemini may rephrase, interpret or suggest updated personalisation details. When this happens, Chirp automatically saves the updated information locally on your Apple Watch so your preferences remain consistent across chats.
Chirp itself processes all user content in real time and does not retain:
Audio
Transcripts
Messages
Contact records
Location history
Only minimal configuration data and anonymous identifiers are stored locally or in Firebase.
All AI features in Chirp are powered by Google Gemini API, including:
Speech transcription
Natural language responses
Grounded web search
Drafting message and email content
When you use Chirp, the following data may be sent to Gemini:
Audio or text of your request
Conversation context you provide
Optional approximate location
Selected contact name and phone number or email address (for compose features)
Technical metadata needed to operate the API (for example, language or model choice)
For paid Gemini API usage, Google states that prompts and responses are not used to train or improve their models.
Google may however retain some request and response data for a limited time for:
Abuse detection and safety
Service reliability
Operational monitoring
This processing and retention are governed by Google’s terms, not by Chirp.
Chirp uses Firebase for anonymous authentication and basic usage metrics. Data handled by Firebase is subject to the Firebase privacy documentation and Google Privacy Policy.
Chirp does not use Firebase for advertising, behavioural analytics or profiling.
Google and Firebase may process and store data on servers located outside your country (including outside Australia). By using Chirp, you consent to this international processing in order for the service to function.
By using Chirp, you consent to:
Your voice, text, selected contact details, local on‑device memory and optional location being transmitted to the Google Gemini API for processing.
Google's handling and retention of that data under their terms and privacy policies.
You control permissions and choices as follows:
Contacts: Allow or deny at the system prompt. You can change this at any time in Apple Watch or iPhone settings. If denied, Chirp cannot reference your contacts.
Location: Allow once, allow while using the app or deny. You can change this at any time in system settings. If denied, Chirp will provide less location‑specific results.
Local memory: You may clear all saved personalisation data at any time in Chirp’s settings. Clearing memory resets your preferences and any personalisation stored on your Apple Watch.
Network access: If network access is disabled, Chirp cannot send requests to Gemini and will not function.
Chirp does not store your data off‑device, and cannot retrieve, export or delete data retained by Google or Firebase. Data sent to those services is handled under their respective policies.