|In Progress||Have a legal justification for your data processing activities.||
Processing of data is illegal under the GDPR unless you can justify it according to one of six conditions listed in Article 6. There are other provisions related to children and special categories of personal data in Articles 7-11. Review these provisions, choose a lawful basis for processing, and document your rationale. Note that if you choose "consent" as your lawful basis, there are extra obligations, including giving data subjects the ongoing opportunity to revoke consent. If "legitimate interests" is your lawful basis, you must be able to demonstrate you have conducted a privacy impact assessment.
|Completed||Take data protection into account at all times, from the moment you begin developing a product to each time you process data.||
You must follow the principles of "data protection by design and by default," including implementing "appropriate technical and organizational measures" to protect data. In other words, data protection is something you now have to consider whenever you do anything with other people's personal data. You also need to make sure any processing of personal data adheres to the data protection principles outlined in Article 5. Technical measures include encryption, and organizational measures are things like limiting the amount of personal data you collect or deleting data you no longer need. The point is that it needs to be something you and your employees are always aware of.
|Completed||Have a process in place to notify the authorities and your data subjects in the event of a data breach.||
If there's a data breach and personal data is exposed, you are required to notify the supervisory authority in your jurisdiction within 72 hours. A list of many of the EU member states supervisory authorities can be found here. The GDPR does not specify whom you should notify if you are not an EU-based organization. For those in English-speaking non-EU countries, you may find it easiest to notify the Office of the Data Protection Commissioner in Ireland. You are also required to quickly communicate data breaches to your data subjects unless the breach is unlikely to put them at risk (for instance, if the stolen data is encrypted).
|In Progress||Encrypt, pseudonymize, or anonymize personal data wherever possible.||
Most of the productivity tools used by businesses are now available with end-to-end encryption built in, including email, messaging, notes, and cloud storage. The GDPR requires organizations to use encryption or pseudeonymization whenever feasible.
|Completed||Create an internal security policy for your team members, and build awareness about data protection.||
Even if your technical security is strong, operational security can still be a weak link. Create a security policy that ensures your team members are knowledgeable about data security. It should include guidance about email security, passwords, two-factor authentication, device encryption, and VPNs. Employees who have access to personal data and non-technical employees should receive extra training in the requirements of the GDPR.
|Completed||Know when to conduct a data protection impact assessment, and have a process in place to carry it out.||
A data protection impact assessment (aka privacy impact assessment) is a way to help you understand how your product or service could jeopardize your customers' data, as well as how to minimize those risks. The UK Information Commissioner's Office (ICO) has a data protection impact assessment checklist on its website. The GDPR requires organizations to carry out this kind of analysis whenever they plan to use people's data in such a way that it's "likely to result in a high risk to [their] rights and freedoms." The ICO recommends just doing it anytime you're about to process personal data.
|Completed||Designate someone responsible for ensuring GDPR compliance across your organization.||
Another part of "data protection by design and by default" is making sure someone in your organization is accountable for GDPR compliance. This person should be empowered to evaluate data protection policies and the implementation of those policies.
|In Progress||Sign a data processing agreement between your organization and any third parties that process personal data on your behalf.||
This includes any third-party services that handle the personal data of your data subjects, including analytics software, email services, cloud servers, etc. The vast majority of services have a standard data processing agreement available on their websites for you to review. They spell out the rights and obligations of each party for GDPR compliance. You should only use third parties that are reliable and can make sufficient data protection guarantees.
|In Progress||If your organization is outside the EU, appoint a representative within one of the EU member states.||
If you process data relating to people in one particular member state, you need to appoint a representative in that country who can communicate on your behalf with data protection authorities. The GDPR and its official supporting documents do not give guidance for situations where processing affects EU individuals across multiple member states. Until this requirement is interpreted, it may be prudent to designate a representative in a member state that uses your language. Some organizations, like public bodies, are not required to appoint a representative in the EU.
|Completed||Appoint a Data Protection Officer (if necessary)||
There are three circumstances in which organizations are required to have a Data Protection Officer (DPO), but it's not a bad idea to have one even if the rule doesn't apply to you. The DPO should be an expert on data protection whose job is to monitor GDPR compliance, assess data protection risks, advise on data protection impact assessments, and cooperate with regulators.
|Completed||It's easy for your customers to request and receive all the information you have about them.||
People have the right to see what personal data you have about them and how you're using it. They also have a right to know how long you plan to store their information and the reason for keeping it that length of time. You have to send them the first copy of this information for free but can charge a reasonable fee for subsequent copies. Make sure you can verify the identity of the person requesting the data. You should be able to comply with such requests within a month.
|Completed||It's easy for your customers to correct or update inaccurate or incomplete information.||
Do your best to keep data up to date by putting a data quality process in place, and make it easy for your customers to view (Article 15) and update their personal information for accuracy and completeness. Make sure you can verify the identity of the person requesting the data. You should be able to comply with requests under Article 16 within a month.
|Completed||It's easy for your customers to request to have their personal data deleted.||
People generally have the right to ask you to delete all the personal data you have about them, and you have to honor their request within about a month. There are a five grounds on which you can deny the request, such as the exercise of freedom of speech or compliance with a legal obligation. You must also try to verify the identity of the person making the request.
|Completed||It's easy for your customers to ask you to stop processing their data.||
Your data subjects can request to restrict or stop processing of their data if certain grounds apply, mainly if there's some dispute about the lawfulness of the processing or the accuracy of the data. You are required to honor their request within about a month. While processing is restricted, you're still allowed to keep storing their data. You must notify the data subject before you begin processing their data again.
|Completed||It's easy for your customers to receive a copy of their personal data in a format that can be easily transferred to another company.||
This means that you should be able to send their personal data in a commonly readable format (e.g. a spreadsheet) either to them or to a third party they designate. This may seem unfair from a business standpoint in that you may have to turn over your customers' data to a competitor. But from privacy standpoint, the idea is that people own their data, not you.
|Completed||It's easy for your customers to object to you processing their data.||
If you're processing their data for the purposes of direct marketing, you have to stop processing it immediately for that purpose. Otherwise, you may be able to challenge their objection if you can demonstrate "compelling legitimate grounds."
|Completed||If you make decisions about people based on automated processes, you have a procedure to protect their rights.||
Some types of organizations use automated processes to help them make decisions about people that have legal or "similarly significant" effects. If you think that applies to you, you'll need to set up a procedure to ensure you are protecting their rights, freedoms, and legitimate interests. You need to make it easy for people to request human intervention, to weigh in on decisions, and to challenge decisions you've already made.
In order to provide its services, Requestly may engage third parties or other members of the Requestly corporate group (affiliates) to carry out data-processing activities that involve access to customer data. These organizations, called “subprocessors,” are identified below with their locations and the types of services they provide to Requestly.
|Name||Country||Description||Type of Service||Mandatory|
|Amplitude||United States||Product Analytics for the Digital Era||Product analytics platform||Required|
|Clarity||United States||Clarity is a free user behavior analytics tool that helps you understand how users are interacting with your website through session replays and heatmaps.||Technology||Required|
|Crisp||United States||Discover our Business Messaging Platform for Startups & SMBs. The one-stop for sales, marketing & support in one platform: Crisp. 14 Days free trial. No credit card required. Try now! We provide Knowledge base, Team Inbox, Chatbot, CRM and multiple other features to let you build your own way to customer success.||Technology||Required|
|GitHub||United States||GitHub is how people build software. We’re supporting a community where more than 31 million people learn, share, and work together to build software.||Web-based hosting service||Required|
|Google Cloud||United States||Google LLC is an American multinational technology company that specializes in Internet-related services and products, which include online advertising technologies, search engine, cloud computing, software, and hardware. It is considered one of the Big Four technology companies, alongside Amazon, Apple and Facebook||Internet-related services and products||Required|
|GrowthBook||United States||GrowthBook is an open source platform that gives any company the power of a customized feature flagging and A/B testing system||Technology||Required|
|Google CDN||United States||A content delivery network (CDN) offered by Google.||Content delivery network||Required|
|Icons8||United States||Download design elements for free: icons, photos, vector illustrations, and music for your videos. All the assets made by designers → consistent quality ⚡️||Technology||Required|
|Country.is||United States||Privacy-conscious, and open-source geolocation API that finds the country of IP address.||Technology||Required|
|Sentry||United States||Open-source error tracking that helps developers monitor and fix crashes in real time. Iterate continuously. Boost efficiency. Improve user experience.||Error monitoring||Required|
|Stripe||United States||The new standard in online payments||Payment processing||Required|
|Cloudflare||United States||Cloudflare makes your applications faster & safer.||Internet security service||Required|
|Google Analytics||United States||a web analytics service offered by Google.||Web analytics||Required|
|Webflow||United States||Webflow gives designers and developers the power to design, build, and launch responsive websites visually, while writing clean, semantic code for you.||Web design service||Required|
Please see our frequently asked questions below. Please keep in mind that this is not legal advice and we recommend consulting with your internal compliance team or privacy attorney for guidance on compliance matters. Requestly is committed to helping our customers comply with applicable laws, but we cannot guarantee that your use of our products will be fully compliant. As always, we recommend seeking professional legal counsel for any specific questions or concerns.
|Should I get consent from a customer to collect their personal data?||
While it is always good practice to receive explicit consent from your customer, certain laws and regulations (such as the GDPR) require consent prior to collecting personal data of certain individuals (such as those in the EU).
It is also important to note that under GDPR, consent is one of a number of legitimate interests for processing data. Others include the need to process for the performance of a contract, the need to process in order to comply with a legal obligation, and the need to process in order to protect the vital interests of the data subject or another natural person. Full details can be found in Article 6 of GDPR.
|Can I modify a customer’s personal data?||
Yes, you can modify all data to correct personal data as required by GDPR when you receive a Subject Access Request, or for other reasons. Simply contact us and we will work with you to make the adjustments.
|Can I delete personal data?||
Yes, you can delete any data, including data that contains personal data, as required by GDPR. You can also remove all other requested customer data by sending us a data request.
|Is personal data permanently deleted when I remove it?||
A deleted data or person is initially flagged for deletion, and may be recovered by our team upon request. After 90 days, the deletion becomes permanent and unrecoverable.
|How long is personal data retained in Requestly if I don’t delete it?||
Requestly’s philosophy is that customers own and control all the data they collect. Any retention period required by law or your company policy is controlled by you.
You should ensure that all people and personal data are deleted prior to stopping your usage of Requestly, especially if required by policy, law, or regulation.
|Does my data get included in backups, and if so, for how long?||
Yes. Requestly backs up all customer data, and retains the backups for 90 days. After 90 days, the backup is deleted.
|Can I delete customer’s personal data from Requestly backups?||
No. The backup dataset contains all customer data, and is used for disaster recovery purposes only. This is required for legal and compliance reasons related to availability obligations. Any personal data in these backups will be permanently deleted after 90 days.
|If my data centre is located in the EU, does Requestly transfer my personal data outside the EU at any point?||
Our data centers are with Amazon Web Services in the United States. However, data transfer is covered by the EU-US Privacy Shield framework, of which we are a member, and allowed by GDPR as providing adequate safeguards.
|Does Requestly ensure that my data is accessed only by employees with reasonable justification for doing so?||
As required by GDPR, only qualified Requestly employees with a specific need are permitted to access your account. The typical reason for accessing your account would be upon your specific request for support.
|Does Requestly use sub-processors that process my data?||
Requestly presently uses sub-processors to provide the service. As required by GDPR, Requestly maintains a list of those sub-processors here.
|If a data breach occurs with the Requestly platform that affects my data, how and when will I be notified?||
If a confirmed data breach occurs that is caused by Requestly’s actions or inactions, we will, without undue delay, notify the account owner. Information about the breach will be released as it becomes available, as allowed by GDPR. The account owner will be the main point of contact for all notifications, and will be kept aware of the investigation and remediation efforts as they progress.
|How can I comply with a Subject Access Request and portability as required by GDPR?||
As you know about the data you are collecting, you are responsible for handling any Subject Access Request (SAR). Requestly only provides the platform and wouldn’t know the details about your customizations, properties, or your customers.
A SAR means that a customer is asking about information being collected about him or her. If you collected personal data of an EU citizen or a person residing in the EU, you may have a legal obligation to respond to a SAR.
Data may be downloaded in industry-standard formats for data portability to comply with GDPR.
If Requestly receives a SAR, it will do its best to contact the owner. It may not always be possible to know what who the rightful owner is.
|How do I comply with a Subject Access Request to “be forgotten?”||
Similar to the above, you know what data you have. If you collected personal data of an EU citizen or a person residing in the EU, you may have a legal obligation to respond and comply with a request to delete all identifiable data.
As previously stated, you have the ability to delete a customer's data.
|How does Requestly comply with its GDPR obligations to return or destroy all EU personal data?||
Requestly provide easy ways to download all your data in industry-standard formats. And, as previously described, you may easily delete data, and entire histories for a customer.
|How does Requestly comply with its GDPR obligations to encrypt personal data?||
All data stored in our primary databases and backups are encrypted using an industry standard strong cipher. All data transmitted to the Requestly platform are encrypted using the industry standard TLS protocol.
|How can I ensure my customers that Requestly security meets applicable law and the GDPR (Article 32)?||
Requestly is committed to safeguarding your data. We use sophisticated controls during processing to maintain the confidentiality, integrity, availability, and resilience of your data. Our Security page outlines the details of our application security, network security, policies, and more.
As related to Article 28 in the GDPR, Requestly will only process personal data according to your instructions. In other words, the commands you use in the product are the “instructions,” and Requestly does not use personal data for any other means. In addition, it does not transfer personal data to a third party without your consent. If personal data is transferred from the EU to a third country, then adequate safeguards will apply to the transfer (such as the EU-US Privacy Shield Framework).
Requestly has developed recovery procedures to minimize downtime related to a disaster, with the ability to restore access to personal data in a timely manner in the event of a physical or technical incident.
We regularly test, assess and evaluate the effectiveness of our technical and organizational measures to ensure the security of the processing.