By Brett Kaufman. 8 years using relationships to build sales pipelines, from political fundraising to a 7 figure business to running matchmaking for two communities. Over 1,000 introductions facilitated.

It is safe to upload your contacts to an app when the app encrypts your list at rest, keeps the team out of it, lets you export and delete everything yourself, asks for read only access, and says in writing that it never sells or shares the data. Most apps will not tell you all of that on one page, so you have to check.

You are on the signup screen. The app wants your contacts. You pause.

The pause is right. Your contact list is not a list. It is fifteen years of brokers, bankers, sellers, LPs and the people who introduced you to them. When your income comes from who calls you first, the list is the business.

The notes are worth even more. In political fundraising my edge was a tracking system: kids’ names, favorite teams, what mattered to each donor. That file was worth more than the phone numbers, and it was exactly the kind of thing you never want a stranger reading.

So here is the checklist I would run. It works on any app that asks for your contacts, including ours.

1. Is it encrypted at rest, and whose database is it in?

Encryption in transit (the lock in your browser) is table stakes. Ask about encryption at rest: if someone copied the database file, could they read it?

Then ask the sharper question. Are your contacts in one big shared database with every other customer, separated by a column, or in a database that belongs to your account alone? A shared table means one bad query can show you someone else’s rows. A separate, separately keyed database is a much higher wall.

The FTC’s Start with Security guide for business makes it a lesson of its own: store sensitive information securely and protect it during transmission.

2. Who on the team can see your contacts?

This is the question most privacy pages dodge. “We take your privacy seriously” is not an answer. Look for a plain sentence about whether employees can open your data, and when.

The FTC guide again: restrict access to sensitive data, on a need to know basis. Google sets the bar higher for any app that touches Google user data. Its API Services User Data Policy says people at the company should not read that data without your affirmative agreement, apart from narrow exceptions like security investigations and the law.

Watch the wording, too. An honest app says no one looks at your contacts. A careful app does not claim no one could, because a server that researches your network has to decrypt it to do the work.

3. Can you export everything, any time, without asking?

If leaving means emailing support and waiting, you do not own your data. You rent it.

A real export is a button. It gives you every contact and the notes you added, in a format another tool can read, like vCard. If the export leaves out your notes, it leaves out the part that matters.

4. Can you delete your account yourself?

Same test. Deleting should be in Settings, not in a ticket queue. The privacy page should say what is deleted (contacts, notes, research, messages, the account) and whether anything is kept after.

5. Does it have its own login?

Some tools bolt onto your email or your phone and never ask you to sign in. Then anyone holding your laptop or a leaked link holds your network. You want a real login with sessions you can end, ideally a way to sign out everywhere.

6. What permission does it ask for?

Read the permission screen. It tells you more than the marketing.

On Google, the People API lists two contacts scopes for listing your connections: contacts, full access to manage your contacts, and contacts.readonly, read only. An app that only imports your list has no reason to ask for the first one. Google’s policy tells developers the same thing: request only what your features need.

Also ask whether the access stays open. Some apps hold a standing token and keep syncing forever. You can see and remove what any app can reach from your Google Account’s linked apps page.

On iPhone, you narrow it yourself. Since iOS 18, Apple’s contacts prompt lets you share a selected set of contacts instead of everything. Apple calls it limited access.

7. Does it sell or share, and where does it live?

Look for one sentence: we never sell or share your contacts with third parties. Then look for the list of what does leave, and why. An AI tool that researches people sends something somewhere. The question is what, to whom, and whether it is used for training.

Finally, ask where it is hosted and how backups are handled. An encrypted database with unencrypted nightly backups is not encrypted.

How FRONT OF MIND answers the seven

I would not ask you to run this list without running it on us first. We checked our own code against it before writing this. Here is what it does today.

1. Encrypted, your own database. Every customer account gets its own database file, encrypted with SQLCipher using a random key made for that account. That key is stored only in sealed form (AES 256 GCM, under a master key), so the account list alone cannot open anyone’s contacts. Nightly backups are one sealed file, encrypted again.
2. The team. The app refuses any database read that does not name the account it is for, and our own two account test found no way for one customer to reach another’s contacts. Research on your network runs automatically. No one on our team looks at them.
3. Export. Settings has a download of everything in your account as one file, plus your contacts as vCards. Passwords and keys are left out of the file on purpose.
4. Delete. Settings has “Delete your account and all data,” confirmed with your password, or your email if you signed up with Google. It removes your database file and your account records from the app right away. Nightly backups made before that still hold a sealed copy, opened only to recover from an outage, and the privacy page says so.
5. Login. Your own login, with a sign out everywhere option.
6. Permissions. Connecting Google asks for read only contacts (contacts.readonly) plus your email so the screen can show which account the contacts came from. We read your contacts once, then drop the access, and for Google we revoke it. No standing access. On iPhone, a shortcut brings your contacts in after you tap Allow.
7. Sharing. Our privacy page says we never sell or share your contacts with third parties and never use them to train AI models, and it lists what leaves your account for research and why. And nothing ever goes out to your contacts without your tap.

If you are weighing building this yourself instead, using ChatGPT as a personal CRM runs through the same trust questions from the other side. And if your list needs work before it goes anywhere, start with how to import and clean up your contact list.

What you get for trusting it

The only reason to put your list anywhere is what comes back. FRONT OF MIND opens on your 10 minutes for today: the people worth a text, each with one line on why now. A broker who posted. A deal in your pipeline quiet for 7 days. Someone you met at an event and never followed up with. Every draft is a short text, 40 words max, and it learns from your edits. That is the job your phone’s contact list was never built to do.

Start free with your first 25 contacts. Run the checklist on us first, then see who comes up.

See how it works