Skip to content

GDPR Compliance

Last updated: 30 Aug. 2022

The EU General Data Protection Regulation (GDPR) is the most comprehensive change to EU data privacy law in decades. It took effect on the 25th May 2018. We work hard to comply with the GDPR and apply its principles as we build new services.

Does this affect me?

The GDPR regulation applies to any EU residents' data, regardless of where the processor or controller is located. This means that if you’re using Hunter from the US to reach out to other US corporations, the regulation doesn’t affect you. But if some of your customers or leads are in the EU, you should pay attention to it. In practice, most companies need to take the GDPR into consideration.

Data Processing Addendum

Findymail is in most cases a processor. As a data controller, under Article 28 of the GDPR, you need a data processing addendum (DPA) signed with your processors. We've made this procedure simple and have the contract ready to be signed. Contact us at [email protected] to get started.

How Findymail is complying with the GDPR

Even though the GDPR only applies to data from EU residents, we took the decision to apply broadly the requirement of the regulation. This means that except in some rare cases, we don’t restrict any privacy-related feature based on the geographical location of a data subject. Here are some of the actions we’ve taken to ensure we’re compliant:

Purposes of the processing

We process only available online data for informational purposes. Our users have a legitimate interest in having easier access to already public data regarding other businesses. By working as a specialized search engine, we make it possible for companies to connect with each other.

Right of erasure

If a data subject wishes to not appear to our customers, we offer a way to easily claim email addresses here

Our processing is done exclusively in the EU

We store and process all our data exclusively in the EU. We even store our off-site backups within the EU.

Log retention

To improve, debug or prevent fraud on the service, we keep a variety of logs. We now make sure logs are destroyed at most 2 months after there collection date. We never use those logs of anything else than monitoring and debugging.

Questions?

Should you have any other questions, we’re here to help: [email protected]