Data handling

Search results

Search results are kept only if you save them. A prospect or company search comes back to you, and nothing from it is stored unless you save someone. Through the APIs, the results come back to your code, and what you store is up to you.

The seven fields

A person from prospect search has seven fields. When you save someone, those seven are kept, with the work email found for them:

• name, job title and seniority;
• company and its website domain;
• country;
• the address of their public profile.

Email checks and the finder

• Checking an address never sends an email.
• When the finder confirms an address, only the company's format is remembered, such as first.last, never the person's name or the address.
• Hosted copies of MagpieCRM share those formats, for companies of 10 or more people, once 3 addresses from 2 different workspaces back one up. Whether a domain is catch-all is shared too, and remembered for 30 to 180 days. Both are facts about a company, not a person.

Opt-outs

Anyone can opt out of prospecting, and is then left out of searches. An opt-out is stored as a keyed hash of the address, not the address itself, and is shared across every hosted copy of MagpieCRM, so opting out once works everywhere we host.

The shared database

MagpieCRM on Magpie Cloud keeps a shared database of business contacts, so a person one customer has found and verified isn't bought and checked again by the next. Only contacts saved from prospect search with a verified work email go into it. Self-hosted copies don't take part.

• It's on by default, and off in Settings, Prospect search, Shared database.
• Each person is emailed a notice before anyone else is shown them.
• They're kept 12 months from their email's last verification, and checked again before that ends.
• Names, email addresses and profile addresses are stored encrypted.
• Anyone in it can remove themselves in one click.

The Contributor Terms say exactly what a workspace sends, what we do with it, and how to switch it off.

Where it's hosted

Magpie Cloud is hosted in the EU. Each hosted MagpieCRM runs as its own copy, with its own data. The companies that help us run the service, and the terms, are on Trust and legal. The APIs will have terms of their own, published before they launch.

What you keep

Keep only what you need from each answer:

• From a check, the verdict and when you checked, not the whole response.
• From a find, the email and its status. If a catch_all or not_found comes back, there's nothing to keep.
• From a search, only the people you'll contact, and drop the rest.

The engine's code is open source under the AGPL-3.0: you can read how it handles data on GitHub.