Legal
Privacy Policy
Last updated April 4, 2026
Chirp only collects what we need to route notifications to your devices. We don't sell your data, we don't read your payloads beyond routing, and you can delete your account any time.
Information we collect
When you create an account, we collect your email address and generate an API key. We store device identifiers (push tokens and install IDs) to deliver notifications. We log notification delivery events for diagnostics but do not read notification content beyond what is necessary for routing.
How we use your information
Your email is used for account identification and support. Device tokens are used exclusively to deliver push notifications and Live Activity updates that you or your integrations initiate. API keys authenticate your external tools (scripts, CI, CLI, MCP) against the Chirp service.
Data sharing
We do not sell your personal information. We share data only with service providers necessary to operate Chirp: Clerk (authentication), Expo (push delivery), Apple (APNs), Google (FCM), and RevenueCat (subscription management). Each provider processes data under their own privacy policy.
Data retention
By default, Chirp writes no notification or Live Activity logs at rest. Records never touch disk beyond the request that produced them. The account itself (email, API key, subscription status) and paired device tokens are kept for as long as the account exists — those are what the service needs to actually function.
If you’d like a short history window for debugging, your dashboard lets you opt up to 7 or 30 days. Longer windows are not supported. Device tokens that haven’t been refreshed in 90 days are automatically removed. You may delete your account at any time from the iPhone app, which permanently removes everything we hold about you.
Your rights
You may access, correct, or delete your data at any time. Account deletion is available in-app under Settings › Manage › Delete Account. To request a data export or raise a privacy concern, contact support@chirpapp.dev.
Security
API keys are generated with cryptographic randomness and stored securely on our servers. All communication between the app, your integrations, and our backend uses TLS encryption. Revoked API keys are immediately rejected.
Children
Chirp is a developer tool and is not intended for children under 13. We do not knowingly collect information from children.
Changes
We may update this policy from time to time. Material changes will be communicated via the app or email. Continued use after changes constitutes acceptance.
Contact
For privacy inquiries, email support@chirpapp.dev.