Skip to main content

Security/Compliance FAQs

V
Written by Victor Dong

Privacy By Design

Our core security principal is Privacy By Design:

  • We avoid storing data wherever possible (ex: real-time requests are processed in memory and not stored for long-term processing)

  • We require the minimum amount of info for any given transaction (ex: we do not need to consume your entire CRM record to validate just the email field)

  • We offer multiple ways to access our system that have different security postures (ex: you can call our API with only the fields you want from your CRM OR you can allow us to pull from your CRM).

What Data Does Your Service Consume?

Only the minimum data points required.

  • For verifyEmail requests, only email.

  • For findEmail requests, name, company website and optionally linkedin profile url.

GDPR Compliance

We offer a standard Data Processing Agreement (DPA) for GDPR compliance which can be found here, presigned. Simply execute the agreement on your side and submit it to [email protected]. You will receive an acknowledgement of receipt after which it will go into full effect.

CRM Integration Best Practices

In the event you have concerns about us having access to your CRM, the recommended path is to create a user that has visibility only to the objects/fields that we require functionally and do the Oauth integration using this user.

Did this answer your question?