🇪🇺 GDPR Compliance
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.
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 TAPKI.COM from the US/RUSSIA/INDIA... 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. "Defect.ru" LLC 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@example.com to get started.
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 publicly available online data for informational purposes.
Right of erasure: because we deal with publicly available web data, information removed from a website are also removed from our database. But if a data subject wishes to speed up the removal of any in our index, we offer a way to claim email addresses. It is then possible to either update the data or entirely remove it.
Security: We’re taking the security of the data we manage very seriously.
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 3 months after there collection date. We never use those logs of anything else than monitoring and debugging.