One record per person.

The instrument

What it is

A signed macOS application. It opens with a passphrase only its owner holds, and closes itself when left alone.

Where data lives

On the owner’s Mac, in an encrypted vault on disk. There is no shared account and no multi-tenant database: one person, one vault.

What it holds

Contacts the owner already has — names, ways to reach them, the companies and places they have been — each field carrying its source and the time it was read.

What it will not do

Speak for its owner. It never sends a message, posts, or reaches out on anyone’s behalf; it hands the owner the address and stands back.

Connecting Google

Read-only, optional, and revocable in one click.

EverData can read the contacts and calendar an owner already keeps with Google, so that a record can say where a person came from and when the two of them last met. Making the connection is the owner’s own act, in their own browser, and it can be withdrawn at any time.

What it reads

Google Contacts, and Calendar events with their attendees. Both read-only: contacts.readonly and calendar.readonly.

Why

Contacts say who the owner knows; calendar attendance says who they have actually met, and when. That is what makes a record current rather than a name in an old export.

What it never asks for

Gmail. EverData requests no mail scope of any kind, and cannot read a message.

Where it goes

Into the vault on the owner’s Mac. The sign-in tokens stay on that machine; the contacts are not copied to a server run by us.

Undoing it

Revoke access at myaccount.google.com/permissions, or delete the vault. Both end it completely.

The full account is in the privacy policy.

Availability

EverData is handed over directly, not sold from a store.

Each copy is built for the person who receives it. If you were sent here to ask about one, write and say so.