Privacy
What EverData reads, where it keeps it, and the few occasions on which anything leaves your Mac.
Last updated 4 September 2026
The short version
- Your contacts live on your own Mac, in an encrypted vault. The one exception is a contact file you may send us to build that vault from — encrypted, held in the EU, and deleted automatically after fourteen days.
- If you connect Google, EverData reads contacts and calendar, read-only, and writes what it reads into that same local vault.
- EverData asks for no access to Gmail, and cannot read a message.
- Nothing about a person is sent anywhere unless you press the button that sends it, having first been shown exactly what it contains.
- We sell nothing to anyone, and there is no advertising or tracking in the app.
Who this is
EverData is the operator of the EverData application and of this website. Write to privacy@everdata.one with any question about this policy or about data held about you.
[owner to confirm: registered legal entity, its address, and the EU/UK representative or Data Protection Officer, if one is appointed.]
Where your data lives
EverData is a single-tenant desktop application. Its vault is an encrypted file on your Mac, sealed with a passphrase that only you hold — it is not stored by us and cannot be recovered by us. There is no EverData account, no shared database, and no synchronisation between machines.
Deleting the vault deletes the data. The only copy that has ever been on our side is the file you may have sent us to build it from, and that is the next section.
The file you send us to build the vault
A vault has to be filled from somewhere. If you send us a contact export — through the private upload link, with the confirmation code that reaches you separately — that file is handled as follows, and is used for one purpose only: building the vault that is then handed to you.
- Encrypted, in the European Union. It is stored in a private, access-blocked store in AWS eu-west-1, under a key kept for this purpose alone.
- Barely reachable, deliberately. It can be read only after an automated malware scan passes, and only by the person building your vault. The website itself has no route that can download it back.
- Deleted after fourteen days, automatically. That happens whether or not the vault has been built. If you want it gone sooner, write and ask.
It is never sold, never shared, and never used for anything but the vault it was sent for.
Google data, and what we do with it
Connecting Google is optional. When you choose to connect, you sign in with Google yourself and grant exactly two scopes:
- .../auth/contacts.readonly — the contacts you already keep with Google. Used to build one record per person and to fill in ways of reaching them.
- .../auth/calendar.readonly — events and their attendees. Used to record that you have met someone, and when, so a record can say how current it is.
Both are read-only. EverData writes nothing back to your Google account, and requests no scope that can read the body of a message.
Where it is kept. The contacts and calendar data EverData reads are written into the encrypted vault on your Mac. The sign-in tokens are held in your macOS Keychain, marked so that they require an unlocked Mac, never sync to iCloud, never enter a backup, and never reach a second machine.
How long. For as long as you keep the vault. Revoking access stops any further reading; deleting the vault removes what was read.
How to end it. Revoke EverData at myaccount.google.com/permissions. You may also disconnect inside the app, and delete the vault.
Limited Use
EverData’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide and improve the features described on this page. It is never sold, never used for advertising or ad profiling, never used to train generalised machine-learning models, and no human reads it except where you have explicitly asked us to help with a specific problem, or where the law requires it.
What leaves your Mac, and when
The application is built to be quiet. Exactly these things reach the network, and there is nothing else:
- The update check. On launch the app may ask one fixed HTTPS address whether a newer build exists. The request carries no body, no query and no identifying header — nothing about you, your Mac, or your vault beyond the fact that a copy asked. It never installs anything.
- Feedback you write. If you send a note from inside the app, that note is sent to us with the kind of note it is, the screen you were on, and the version of the app. It carries nothing from your vault.
- Looking a person up, when you ask. EverData can check a public source to fill a gap in a record. Before anything leaves, the app shows you the exact fields and values that would be sent, for that one person, and waits for you to press the button. Nothing is sent in the background, and nothing is sent for a person you did not ask about.
- Google, if you connected it — as described above.
[owner to confirm: the providers behind the look-up service and the region their data is processed in, so this section can name them rather than describe them.]
This website
everdata.one sets no cookies, runs no analytics, and embeds nothing from a third party. Its host keeps ordinary server logs, which include IP addresses, for the short period needed to serve and secure the site. There is nothing to opt out of because there is nothing collecting.
Your rights
Where the GDPR applies, you have the right to access, correct, export and erase personal data held about you, and to object to its processing. For the vault, those rights are yours to exercise directly: it is your file, on your machine, and the app can export it. For anything you have sent us — a feedback note, an email — write to privacy@everdata.one and we will answer within thirty days.
Changes
If this policy changes, the date at the top changes with it, and a material change will be described here rather than absorbed quietly.