Your contacts and relationship history, in one local book. See what each source imports and what you need to connect it.
Ready
macOS · Full Disk Access may be required
Reads the Mac's local Address Book as a consistent contact snapshot.
Each Apple contact is authoritative. Two Apple cards that share a field stay separate until a person reviews them.
Ready
macOS · local Messages database
Builds interaction history from content-free Messages metadata already on the Mac.
Only exact normalized email or phone handles can link. Message bodies are never read.
Ready
Google contact scopes · Ghostget authorization
Syncs saved Contacts and Other contacts as separate, fully paginated collections.
The contact-only projection never scans Gmail or reads message bodies.
Ready
Beeper Desktop and pinned CLI on macOS or Linux
Imports account-aware contacts and stages bounded contact or conversation candidates for explicit review.
Body-free interaction counts · macOS arm64 only
Read-only in PeopleBlade. It never sends messages or imports message bodies, attachments, reactions, media, credentials, or local paths.
contacts.search@1contacts.list@3messaging.search@2Body-free interaction counts. Separate bounded exporter 1.1.0; complete one-to-one conversations only, so counts may understate history.
Ghostget 0.18.13 · adapter 2.4.0 · Beeper CLI 0.6.2
Contact imports use Ghostget's beeper-local adapter. Interaction counts are optional. Ghostget supports broader Beeper messaging and actions; PeopleBlade exposes none of those mutations.
Ready
User-approved linked-device pairing
Syncs exact account-scoped contacts and lower-bound interaction metadata.
Display-name overlap never merges identities; a shared exact phone joins records only through a recorded identity decision. Message bodies are not imported.
Ready
Owner-supplied LinkedIn ZIP
Imports connections and body-free message-participant metadata from the official ZIP export, then reads one imported connection's Contact info through Ghostget from your signed-in browser profile.
Exact member profile URLs anchor identities. Names alone never do. Connection lists are never collected from a signed-in browser.
Ready
Owner-supplied Accounts Center JSON archive
Imports reviewed relationship, message-participant, and synced-contact paths from Accounts Center JSON.
Archive records may be structurally parsed and integrity-hashed; message text is not retained. Names alone remain unresolved.
Bounded metadata
Owner-supplied X data archive
Builds a graph from account, follower, following, and body-free interaction coordinates.
Unresolved numeric peers stay inert evidence. Post and direct-message bodies are not persisted.
Blocked safely
Unavailable until a bounded Ghostget route exists
Reserved for a future bounded, account-bound mutual-follow capability.
No API or scraping fallback exists while an exact reviewed Ghostget operation is unavailable.
Validation pending
Unavailable pending a real export fixture
A strict Telegram Desktop JSON importer is designed but not yet enabled.
Support waits for validation against a real owner-supplied export artifact.
The full book stays local. Your graph lives in SQLite on your machine. Optional cloud sync sends a bounded projection.
Matching takes evidence. Exact provider coordinates can anchor a person. Names, fuzzy candidates, and unverified handles cannot.
Every import is inspectable. Each run records its source, completeness limits, and implementation version.
Public CLI · npm 0.4.1