Privacy

Your contact book lives on your computer.

Your contact book is a SQLite database on your computer. Data leaves it only when you run a command that sends something: device sync, cloud sync, a research check on public profiles, an exposure check against breach and public-record sources, a Hunter work-email lookup, or sending a signed exposure summary to one contact. Each of those commands states what it sends. PeopleBlade never sees your account passwords: you sign in through GhostGet, which never stores them. Imports keep no message text, and the paths of files you import are never uploaded.

CLI updates

Supported global installs contact registry.npmjs.org at most once a day and use their package manager to fetch newer code. The service receives the package name and ordinary connection metadata, such as your IP address. It receives no contacts, command arguments, imported files, or account credentials. Local update settings contain preferences, check times, and installation and process identifiers. Run peopleblade update disable to stop automatic checks, or set HRANESS_NO_UPDATE=1 for one invocation. Explicit update check and update commands contact the release service.

Sync between your devices

Device sync replicates your whole book between devices you approve: contacts and their details, notes and their history, reminders, tags and saved searches, exposure findings and remediations, Photos evidence links, identity decisions, source records, and research results. Every change travels inside an end-to-end encrypted envelope sealed on your device; the server stores only the ciphertext and what relaying needs: sizes, timestamps, the sending device ID, key IDs, per-device sync positions, the joining device's name, the pairing public keys, and the book key wrapped for each device. It cannot read the contents. Approving a device takes a six-digit code confirmed on a device you already trust, or the account recovery key. A device you remove stops receiving envelopes, and with no enabled device and no recovery key the encrypted copy is unrecoverable.

Optional cloud copy of your contacts

Cloud sync uploads a separate, optional copy of your contact details. It sends names, organizations, titles, birthdays, email addresses, phone numbers, profile URLs and account handles, interaction counts and dates, and source names for every contact to your PeopleBlade account. Devices you approve can read that copy through /api/v1, and hosted research runs on it; its results are stored there too and can be copied back into your local book. It carries no notes, note revisions, exposure findings, or Photos evidence, and there is no web view of your contacts.

Hosted research

Hosted research is optional and runs only for contacts you select and confirm. For those contacts, PeopleBlade sends names, organizations, titles, and stored profile URLs and work emails to its research providers: Exa search and the extraction model, both through Vercel AI Gateway; Hunter, when it is configured, for a work email; and the free public checks at Gravatar, GitHub, and Keybase. A run costs at most $0.16 per contact. Payment goes through the Hraness credits service and Stripe Checkout, and PeopleBlade never sees card details.

Sending an exposure summary

The one command that sends through your messaging accounts, exposure attest-send, sends one contact a signed summary of an exposure check, after you allow attachment sending in GhostGet and pass --confirm.

Mailing consent

PeopleBlade mailing consent is separate from a cloud account and every other Hraness audience. An unsubscribe link in a PeopleBlade message removes only that subscription.

Analytics

The public website uses PostHog analytics when its production project key is configured. Analytics starts before cookie acceptance where regional rules permit. It waits for your choice where consent is required or the region is unknown. Rejecting analytics stops tracking. PeopleBlade never sends your contact book to analytics.