The General Data Protection Regulation (GDPR)
Dashbot takes the privacy and security of our customer data very seriously. We are committed to working with our customers to provide actionable insights while maintaining the privacy and security of their critical data. With the General Data Protection Regulation (GDPR) due to become effective on May 25th, 2018, we have put together this documentation to explain in detail how to comply with the regulations while using Dashbot.
What is the GDPR?
According to Wikipedia:
“The General Data Protection Regulation (GDPR) (EU) 2016/679 is a regulation in EU law on data protection and privacy for all individuals within the European Union. It addresses the export of personal data outside the EU. The GDPR aims primarily to give control back to citizens and residents over their personal data and to simplify the regulatory environment for international business by unifying the regulation within the EU.”
The GDPR goes into effect on May 25, 2018.
Here are some of our favorite links to understand GDPR:
The General Data Protection Regulation (“GDPR”) is a
How does GDPR impact Dashbot and its customers?
The GDPR regulates the “processing” of personal data of any EU resident, known as the “data subject”.
In the terms of the GDPR, Dashbot is the “data processor” and the customer is the “data controller.” The data controller collects data from “data subjects” (ie. the customer’s end users) and the data processor receives this data from the data controller.
Will Dashbot be compliant with the GDPR?
Yes. Dashbot is committed to complying with the GDPR and working with our customers to enable them to comply with the GDPR as well.
Who are Dashbot's sub-processors?
As a “data processor,” Dashbot’s sub-processors are:
- Amazon Web Services, Inc. — Seattle, WA, USA
- Snowflake Computing Inc. — San Mateo, CA, USA
Does Dashbot have a Data Processing Agreement (DPA) in place?
Yes. Dashbot has updated our Terms and Conditions with a Data Processing Agreement (DPA) that outlines the specific requirements and obligations as a data processor. Dashbot also has DPAs in place with all of our sub-processors to ensure downstream compliance.
What should I do if I receive a data subject information or deletion request?
In the event that you receive an information or deletion request from a data subject, email [email protected] with the subject “GDPR Request” from the email address associated with the bot account, with the following information:
- Type of request: information or deletion
- Bot Settings URL: eg. https://reports.dashbot.io/bots/123
- API Key, as found on the Bot Settings URL
- User ID
The user ID is the user ID that is passed to Dashbot as found in the integration API — for Facebook bots, this is typically the “Page Scoped User ID” or (PSID).
Information and deletion requests will be processed in a timely manner, and is irreversible.
What happens to my analytics after a data subject deletion request?
Personal data associated with this user ID will be deleted — any data that is rolled up in anonymous aggregates will not be recalculated.
For this example, a user with the user ID “123” chats with your bot on Facebook. From Facebook, we have: first name, last name, timezone, profile photo URL, gender, locale and timezone offset.
After a deletion request is received, we will remove the record that stores the association between the user ID “123” and the associated user data.
If the user is included in the “Top Users” report, the user with the user ID “123” will be removed from that report. If you were to access the transcripts for user ID “123”, you will not be able to see this user’s messages.
Anonymous aggregate reports will not be recalculated.
If you send Dashbot new data with this user ID after the deletion request, data processing will occur once more for this user ID, so it is possible that their personal data may re-appear.
What about the website you operate at www.dashbot.io?
We use the following “data processors” to improve and analyze our website product, and have DPAs in place with all of them to ensure GDPR compliance for our own data subjects:
- Heap Analytics
And finally, a legal disclaimer...
Nothing stated here is legal, compliance or other advice. It is provided only for your informational and convenience purposes, and is our commentary on the GDPR, as Dashbot interprets it, as of the date of publication. You should work closely with legal and other professional advisors to determine exactly how the GDPR may or may not apply to you. We have spent a lot of time understanding what the GDPR means for us and our customers, and we hope you do the same.
As stated, Dashbot is a processor of data which you, as the controller of your users’ data, make available to us. Dashbot can never engage directly with your users nor address their requests. You remain in charge of meeting your data subject users’ requests and we can help you by providing tools to streamline this process.