Privacy Policy

what we collect

BirdyBeep is designed to collect as little as possible to send you a push when an agent needs you. We store:

• your account email (for sign-in, via our auth provider);
• an encrypted push token per device (to deliver notifications);
• a hashed machine fingerprint and a hash-only machine token per paired machine;
• minimal lifecycle event metadata per agent session (status, timestamps, harness), kept transiently;
• your notification preferences and mute scopes;
• aggregate usage counters and subscription entitlements (for billing and abuse limits).

what we never store

We never store the title or body content of a notification server-side — only metadata and hashes. Repository, branch, file paths, and command summaries are not persisted; absolute paths are hashed or redacted by default. Notification content is held only transiently in memory to deliver the push, then discarded.

private mode (free for everyone)

Private Mode is available to all users at no cost. With it on, a push carries only generic, category-derived copy — for example “an agent needs your approval” — and never your repo, branch, path, command, or any agent-emitted title/body. The original content is never read when composing the redacted push, so nothing sensitive can leak into the notification.

tokens & pairing

Machine tokens are shown to you exactly once and only their peppered hash is stored server-side — never the raw token, and never in logs. Pairing a machine uses a short-lived, single-use code carried by the QR; it is never a durable token and is matched by hash. Agents never write tokens into your repository files.

data retention

A daily sweep deletes agent event metadata and stale completed sessions older than 30 days. Aggregate usage counters and entitlements are retained longer for billing, abuse prevention, and analytics. Encrypted push tokens are removed when a device is unregistered or revoked.

deleting your account

When you delete your account, BirdyBeep: revokes your Sign in with Apple token at Apple, if you signed in with Apple; revokes all of your devices (removing them from notification dispatch); revokes all paired machines (adding their token hashes to an immediate deny-list) and their integrations; hard-deletes your agent sessions, event metadata, notification preferences, and mute scopes; and marks your user record deleted. Minimal billing records (entitlements and aggregate usage counters) are retained where required for billing and abuse obligations. You can request deletion in the app or from our public account-deletion page.

third parties

We rely on a small set of processors to run the service:

• Cloudflare — backend hosting, database, and delivery queues;
• Expo Push with Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM) — notification delivery;
• RevenueCat with Apple App Store and Google Play Billing — subscription management.

your rights & contact

You can access app data, change notification settings, enable Private Mode, and delete your account at any time. For privacy questions or requests, contact privacy@birdybeep.com.