Privacy Policy
Last updated: July 26, 2026 · Operated by 9punk LLC
Pager9 tells you when your Claude Code sessions finish or need you. To do that we watch events, not content. This policy explains — in plain terms, grounded in how the software actually works — what we see, what we deliberately never see, and what happens to the little we keep.
Your work stays on your machine.
The Claude Code hook that powers Pager9 sends us the fact that something happened — not what you were doing. We do not receive, read, or store any of the following, and there is no code path that could:
- Prompt content — nothing you type to Claude
- Code or file contents — nothing from your files
- Transcripts — none of the conversation with Claude
- Full file paths — your working directory is reduced to a single folder name before anything is stored; the full path (which contains your OS username) is discarded
- Notification text — the words in a push ("Finished in 7m") are built in memory, sent to your phone, and never written to our database
This isn't a promise to behave. It's how the pipeline is built: content-bearing fields are either never read or collapsed to a name or a count before they ever reach storage.
On this page
1. What we actually collect
Here is everything Pager9 stores, and where it comes from. There is nothing else.
Account information
- Email address and display name — from your Google sign-in. We use Google (Firebase Authentication) to sign you in; Google provides us your email and the display name on your Google account. Because Pager9 is invite-only during early access, your email and name are also stored on your access-request record so we can approve you.
- Consent record — when you sign in you confirm you agree to these Terms and Privacy Policy and understand Pager9 works with Claude Code (the command-line tool). We store the fact and time you accepted and the version of the Terms you accepted — no more than that. This is erased when you delete your account (see Retention & deletion).
Session & usage data (from the Claude Code hook)
- Event type / status — e.g. a run started, needs your input, finished, hit an error, or was auto-closed when idle.
- Timestamps — when events happened, and derived durations (how long a run worked, how long it waited).
- Project name — the name of the folder Claude Code was launched in (e.g. "my-app"). This is a single folder name, never the full path.
- To-do counts — for multi-step tasks, the number of steps done vs. total (numbers only, never the text of the steps).
Machines that send events
- Hostname — your computer's name (e.g. "DESKTOP-ABC123"), used as the machine label, plus an optional friendly name you choose at setup.
- Per-machine key metadata — the last four characters of each hook key (for display), when it was created or revoked, and a rough count of events that machine sent today.
Phones/devices that receive pings
- Push token — the delivery address your phone or browser gives us (via Google/Firebase Cloud Messaging) so we can send you a notification. It identifies the device to the push service, not you personally.
- Device label and channel — a name for the device (e.g. "moto g stylus") and whether it's a browser or the Android app, plus a "last seen" timestamp.
Payments
- We hold no payment information — none today, and none planned. Pager9 takes no payments at all right now. When a paid plan goes live it is intended to be sold only inside the Pager9 Android app, through Google Play Billing, where Google is the seller and merchant of record: Google takes the payment, handles applicable taxes, and holds your payment details. We never receive or store your card number, billing address, or any payment credential. The only billing fact we expect to keep is a subscription status — trial, active, lapsed, and a renewal or expiry date — mirrored back to us from Google so the app knows whether to unlock. The web app at app.pager9.dev has no purchase path and collects no payment data.
Keys
- Hook keys are stored only as a one-way hash — we keep no retrievable copy of the key itself, and we cannot show it to you again. Each machine holds its own key, minted on that machine and shown once. A key can only trigger notifications — it cannot read your data or make charges. See Security.
We collect no analytics, no advertising identifiers, and no location data. There is no third-party tracker, pixel, or analytics SDK anywhere in the Pager9 website or app.
2. What this can reveal — the honest version
We don't see your work, but the metadata we do keep isn't nothing. In the interest of not underselling it:
- A project (folder) name can hint at what you're working on — a client name, a codename, a side project.
- Timestamps reveal your rhythm: when you work, how late, how long your sessions run.
- Taken together over time, your event history forms a behavioral profile — an activity heatmap of your coding habits.
We think that's a fair trade for a reliable pager, and we keep the surface as small as we can. But you should decide knowing the honest shape of it.
3. How we use it
- To notify you — the core function: turn an event into a push to your paired devices.
- To show your dashboard and stats — live sessions, "time saved," streaks, and history are computed from your own event data.
- To run the service safely — enforce the invite gate, per-key and per-account rate limits, and cost controls (see our Terms of Service).
- To support you — respond when you contact us.
We do not sell your data, share it for advertising, or use it to train machine-learning models.
4. Who we share it with
We use a small set of infrastructure providers to run Pager9. We share only what each needs to do its job.
| Provider | What it does | What it handles |
|---|---|---|
| Google / Firebase | Sign-in, database, hosting, and server functions | Your account, and all the data above, is stored in Google Firebase (Firestore) in the United States. |
| Google / Firebase Cloud Messaging | Delivers push notifications | Your device push token and the notification text at send time. |
| Google Play (future) | Sells and bills the paid plan in the Android app, when paid plans go live | Not yet live — Pager9 takes no payments today, so nothing is shared. When it does, Google is the merchant of record and handles the payment, tax, and your payment details inside the Play Store; we expect to receive only your subscription status, never payment information. |
We may also disclose information if required by law, or to protect the rights, safety, and security of Pager9, our users, or the public.
5. How long we keep it, and deletion
Retention. We keep your account and event data for the life of your account, because your all-time stats are computed from it. There is no automatic expiry. When a live session goes stale it is marked closed — not deleted — so your history stays intact.
Deletion is immediate and permanent.
You can delete your account at any time from the app (Devices & account settings). To protect you, deletion requires a fresh re-authentication. When you confirm:
- Your account data is immediately and recursively erased — sessions, turns, notification records, paired devices, preferences, hook keys, access record, your consent record, and rate-limit counters.
- Your sign-in identity is deleted.
- Deletion is permanent. We keep no backups and point-in-time recovery is disabled, so once the purge runs there is nothing to restore — by us or by you.
The only thing left behind is a minimal tombstone record — your user ID and the fact and time of deletion, with no personal information — kept so we can prove the deletion happened. Because your access record is also erased, returning to Pager9 means requesting an invite again.
One thing deletion will not do, once paid plans exist: it cannot cancel a Google Play subscription. Google owns that billing relationship, not us, so we cannot stop or refund it on your behalf — you cancel it yourself in the Play Store, and if you don't, it keeps renewing even with your Pager9 account gone. Cancel in Play first, then delete. (No subscriptions exist today; nothing can charge you now.)
6. Your choices and controls
- Notification toggles — choose which events ping you (needs-input, complete, errors, long-running, daily summary).
- Per-machine keys — each machine has its own key; revoke any one without affecting the others.
- Remove a device — unpair any phone or browser at any time.
- Delete everything — the account-deletion above.
Depending on where you live, you may have rights to access, correct, or delete your personal data, or to object to certain processing. You can exercise the core of these yourself in the app; for anything else, contact us at contact@pager9.dev.
7. Security
Your data lives in Google Firebase and is governed by database security rules that restrict each record to its owner — your account can read only your own account, sessions, devices, and keys. Sign-in is handled by Google; we never see or store your Google password.
Hook keys are stored only as one-way hashes at rest — we keep no retrievable or unencrypted copy of any key, and the raw key is shown once, on the machine that mints it. A key's only power is to trigger notifications — it cannot read your data or incur charges. No method of storage or transmission is ever perfectly secure, and we cannot guarantee absolute security.
8. Children and age
Pager9 is intended only for people 18 years or older. It is a developer tool and is not directed to children. We do not knowingly collect personal information from anyone under 18. If you believe a minor has provided us information, contact us and we will delete it.
9. Changes to this policy
We may update this policy as Pager9 evolves — for example, when paid plans go live through Google Play Billing. When we make a material change, we will update the "Last updated" date above and, where appropriate, notify you in the app or by email. Continuing to use Pager9 after a change means you accept the updated policy.
10. Contact
Pager9 is operated by 9punk LLC. For any privacy question or request, email contact@pager9.dev.
← Back to Pager9