Terms of Service

By using Chirp, you agree to these Terms of Service. If you do not agree, do not use the service.

Chirp is a developer notification platform that lets you send push notifications and Live Activity updates to your own devices from scripts, CI pipelines, AI agents, a CLI, or an MCP server. The service includes a mobile app, a backend API, and integration tools.

You are responsible for maintaining the security of your account and integration credentials. Do not share bearer credentials in public repositories, prompts, URLs, or insecure channels. Interactive hosts use revocable paired credentials. Provider-webhook credentials are bound to one bridge, expire, and can be revoked in the dashboard; a provider-console URL containing one is still a bearer secret. General-purpose headless credential issuance and self-service rotation remain launch-gated. Contact support immediately if a legacy credential may be compromised.

You may not use Chirp to send unsolicited messages, spam, or content that violates applicable law. You may not attempt to bypass rate limits, overload the service, or reverse-engineer the backend. Activities and notifications must originate from your own authenticated integrations.

Chirp offers subscriptions through supported mobile stores. The store checkout sheet is authoritative for price, trial eligibility, taxes, renewal, and cancellation terms in your region. Web signup provisions an account; it does not itself begin a trial or store purchase. Refunds are handled by the store that processed the purchase.

Chirp, its logo, and related marks are the property of the Chirp team. Notification content you send through the service remains yours. By using Chirp, you grant us a limited license to process and deliver your content as part of the service.

Chirp is provided “as is” without warranty. We are not liable for missed, delayed, or undelivered notifications. Push notification delivery depends on Apple, Google, and Expo infrastructure outside our control.

You may terminate your account at any time by deleting it from Settings. We may suspend or terminate accounts that violate these terms or abuse the service. Account deletion first asks RevenueCat and Clerk to delete the applicable customer/identity, then commits deletion of the Chirp backend account and dependent service rows only after those requests succeed. A provider failure is reported rather than represented as completed deletion. If provider deletion succeeds but the local database deletion does not commit, operator completion is required. Legal, fraud-prevention, security, and provider-specific retention obligations may still apply, and Clerk, Apple, Google, and RevenueCat may retain records under their own terms. The complete production deletion path remains a launch verification gate.

We may update these terms. Continued use after changes constitutes acceptance. Material changes will be communicated via the app or email.

Questions about these terms? Email support@chirpapp.dev.