How your data is protected

Your contacts and the sign-in details ContactZapp uses to reach your accounts are encrypted before they are stored. Each person has their own encryption key, and a master key protects those keys. The master key isn't kept in the database.

What is encrypted

• Your contacts. The personal details in your contacts are encrypted in every place ContactZapp keeps them, including the earlier versions it keeps for History.
• Your accounts' sign-in details. The password or access ContactZapp holds for a connected account is encrypted. So are the account's email address and name.

How the keys work

Two levels of key protect your data:

1. Your own key. Each person has one key of their own. It encrypts your contacts and your accounts' sign-in details.
2. The master key. It protects every person's own key. It isn't stored in the database. ContactZapp gets it from the environment it runs in.

Because of this, a copy of the database alone doesn't show your contacts or your accounts' passwords.

What isn't encrypted

A few values that say nothing about who a person is stay readable, so ContactZapp can count, sort and show them quickly. They are counts, yes-or-no flags, dates and coarse categories. Examples are whether a contact has a phone number, when a contact last changed, how many records a contact was formed from, and the contact number you see as CS-0042.

When you remove data

• To disconnect one account, see Unlink an account. ContactZapp no longer keeps that account's password or access.
• To erase everything ContactZapp holds for you, use Factory reset. See Factory reset.
• To keep a copy of your contacts yourself, see Export your contacts.

If something goes wrong

If you think your data has been exposed, or you have a question about how it is protected that this page doesn't answer, contact support.