Privacy Policy

Last updated: August 6, 2026

Chirp is a voice-first application for operating your Claude Code sessions and listening to briefings hands-free. Chirp is operated by PulseIQ Labs, Inc. ("PulseIQ," "we," "us," or "our"). This Privacy Policy explains what information we collect, how we use it, who we share it with, and the choices you have. It applies to the Chirp website at chirp.dev, the Chirp iOS app, and the services we provide through them (together, the "Service").

By using the Service you agree to the practices described in this policy. If you do not agree, please do not use the Service.

The short version

We collect the information you give us (like your name and contact details), the voice and content you route through Chirp so we can operate the Service, and basic usage data that helps us keep the app working.
Your microphone is only used while you are in an active voice session.
We rely on trusted third-party providers to power features like real-time audio, speech-to-text, text-to-speech, and AI reasoning. We do not sell your personal information.
If you choose to connect your Google account, we access your Gmail and Google Calendar only to power the features described below, and our use of that data follows Google's Limited Use requirements. See Google user data.
You can ask us to access or delete your data at any time by emailing privacy@chirp.dev.

Information we collect

Account and identity information. When you join the waitlist, sign in, or create an account, we collect information such as your name, email address, and phone number. Account creation and sign-in are handled through our third-party authentication provider.

Voice and audio. Chirp is voice-first. When you start a voice session, your microphone audio is captured on your device and streamed to our services so it can be transcribed and acted on in real time. Audio is only captured while a voice session is active.

Content you route through Chirp. To provide the Service we process the content you connect to it — for example the "topics" and briefings you stage, and the prompts, replies, and other content exchanged with the Claude Code sessions you choose to connect. This content is transmitted through our servers so we can narrate it back to you and relay your voice instructions.

Google user data. If you choose to connect your Google account, we access your Gmail and Google Calendar data as described in the Google user data section below. Connecting Google is optional; the core voice features of the Service work without it.

Usage and device information. We collect information about how you interact with the Service, such as the screens you view, the features you use, app and device characteristics (like device type and operating system version), and diagnostic and log data. We use product analytics to understand and improve the Service.

Communications. If you contact us for support or join our waitlist, we keep a record of your message and contact details so we can respond and follow up.

How we use your information

We use the information we collect to:

provide, operate, and maintain the Service, including voice sessions, briefings, and connections to your Claude Code sessions;
transcribe your speech, generate spoken responses, and produce the narrations and asides that Chirp reads to you;
authenticate you and secure your account;
understand how the Service is used so we can fix problems and improve it;
communicate with you about the Service, respond to your requests, and send administrative messages;
protect the Service, our users, and the public against fraud, abuse, and security risks; and
comply with legal obligations and enforce our terms.

We do not sell your personal information. We share it only in the following circumstances:

Service providers. We share information with vendors that process data on our behalf, under contract and only as needed to run the Service. These include:

cloud hosting, database, and storage providers;
real-time audio and communications infrastructure that carries your voice session;
AI providers that perform speech-to-text, text-to-speech, and language-model reasoning on the audio and content you route through Chirp;
an authentication and identity provider;
a product-analytics provider;
an email delivery provider; and
an observability and logging provider that helps us monitor and debug the Service.

These providers are permitted to use your information only to provide services to us, not for their own purposes.

Legal and safety. We may disclose information if we believe in good faith that it is required to comply with a law, regulation, legal process, or governmental request, or to protect the rights, property, or safety of PulseIQ, our users, or others.

Business transfers. If we are involved in a merger, acquisition, financing, or sale of assets, your information may be transferred as part of that transaction. We will continue to protect it consistent with this policy.

Google user data (Gmail and Google Calendar)

You can optionally connect your Google account to Chirp so it can brief you on your inbox and calendar by voice. This section describes how we access, use, store, and share Google user data. It is in addition to, and takes precedence over, the general practices described elsewhere in this policy.

What we request. When you connect Google, we request the following OAuth scopes:

Gmail (gmail.modify) — lets Chirp read your messages and, at your direction, draft and send replies, archive messages, and mark them as read. Chirp never permanently deletes messages.
Google Calendar (read-only, calendar.readonly) — lets Chirp read your calendar events so it can tell you about your day. Chirp never creates, changes, or deletes events.

Authentication is handled by our identity provider; we never see or store your Google password. Access tokens are held by our servers only transiently while serving your requests.

How we access it. Chirp reads messages from your inbox and fetches their content when it builds your briefings, and reads the current day's events from your calendar when you ask about your schedule. If inbox briefings are enabled for your account, Chirp also scans your inbox periodically in the background so new items are ready when you open the app. Actions that change your mailbox — sending a reply, archiving, marking as read — happen only when you ask Chirp to take them.

How we use it. We use Gmail and Calendar data solely to provide the user-facing features of the Service to you: identifying messages worth your attention, building the topics and briefings Chirp narrates, answering your questions about your inbox and schedule, and preparing replies you have asked for. We do not use Google user data for advertising, and we do not sell it.

What we store. When Chirp builds a topic from your inbox, it stores the relevant messages' subject, sender, date, and message content in our database so your briefings can be generated and replayed, along with the briefing text and audio derived from them. Calendar data is processed to answer your requests and is not retained beyond that. Stored Google user data is deleted when you delete the related topic or your account, per the Data retention section below.

How we share it. We share Google user data only with the service providers that process it on our behalf to deliver features you use — our cloud hosting and database provider, the AI providers that generate the summaries, briefings, and spoken audio you request, and the observability provider we use to monitor and debug the Service. These providers act under agreements that prohibit them from using your data for their own purposes.

AI and machine learning. We do not use Google user data to train or improve generalized artificial-intelligence or machine-learning models, and we do not allow our AI providers to do so. Google user data is sent to AI models only to generate the specific output you requested (for example, a briefing of your inbox or a draft reply).

Human access. Humans at PulseIQ do not read your Google user data except (a) with your explicit consent, (b) as necessary for security purposes such as investigating abuse, (c) to comply with applicable law, or (d) in aggregated, de-identified form for internal operations.

Limited Use disclosure. Chirp'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.

Disconnecting Google. You can disconnect your Google account at any time in the Chirp app's Settings, or revoke Chirp's access from your Google Account security settings. After you disconnect, Chirp can no longer access your Gmail or Calendar; you can also ask us to delete previously stored Google user data at privacy@chirp.dev.

Analytics

We use PostHog to understand how people find and use Chirp — which pages get visited, which steps of setup people complete, and where they get stuck. PostHog processes this on our behalf and stores it in the United States.

While you are signed out this is limited to pages viewed and in-product interactions, tied only to a random identifier stored in your browser. Once you sign in, we associate that activity with your account, along with your email address and first name, so that your activity on this site and in the Chirp iOS app is understood as one person rather than two.

We do not record your screen or session. We do not sell this data or share it with advertisers.

You can opt out by enabling Do Not Track in your browser, or by using any tracker-blocking extension — we do not attempt to defeat them.

A note on your voice

Because Chirp is operated by voice, we want to be clear about how audio is handled. Your microphone is only active during a voice session you have started. The audio is streamed to our services and to the AI providers described above so it can be transcribed and responded to in real time. We use audio to operate the Service and improve its reliability and quality; we do not use it for advertising and we do not sell it.

Data retention

We keep your information for as long as your account is active or as needed to provide the Service, and thereafter as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements. When you ask us to delete your account, we will delete or de-identify your personal information within a reasonable period, except where we are required or permitted by law to retain it.

Security

We use administrative, technical, and organizational measures designed to protect your information, including encryption in transit. No method of transmission or storage is completely secure, however, and we cannot guarantee absolute security.

Your choices and rights

You can:

Access, correct, or delete your personal information by emailing privacy@chirp.dev;
Control your microphone through your device's operating-system permissions;
Opt out of marketing emails using the unsubscribe link in any such message (we may still send you administrative messages about your account); and
Adjust analytics where the Service or your device offers such a control.

Depending on where you live, you may have additional rights — such as the right to access, correct, delete, port, or restrict the processing of your personal information, or to object to certain processing, under laws like the GDPR and the CCPA/CPRA. We do not sell your personal information and do not share it for cross-context behavioral advertising. To exercise any of these rights, contact us at privacy@chirp.dev. We will not discriminate against you for exercising your rights.

International users

We are based in the United States and process information there. If you access the Service from outside the United States, you understand that your information will be transferred to, stored, and processed in the United States and other countries where our providers operate, which may have different data-protection laws than your own.

Children's privacy

The Service is intended for adults. It is not directed to children, and you must be at least 18 years old to use it. We do not knowingly collect personal information from anyone under 18. If you believe a child has provided us personal information, please contact us at privacy@chirp.dev and we will delete it.

Changes to this policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the "Last updated" date above and, where appropriate, provide additional notice. Your continued use of the Service after an update means you accept the revised policy.

Contact us

If you have questions or requests about this Privacy Policy or your personal information, contact us at:

PulseIQ Labs, Inc.

privacy@chirp.dev