App developer? Here’s everything you need to understand and get started with GDPR and ePrivacy compliance.
Why? Under most countries’ laws it’s mandatory that you disclose details related to privacy and your data processing activities. Failure to do so can result in massive fines, app store/marketplace rejection, leave you open to litigation and negatively affect the credibility of your website or app.
When do you need it? Whenever processing personal data in any way (even ip addresses can be considered personal data).
Did you know that we have a mobile SDK available for Cookie Solution? It’s fully customizable and available as a native component for both IOS and Android. You can contact us directly at email@example.com to access all files and instructions needed for implementation.
These plugins allow you to set up quickly on the most popular platforms and automate much of the prior blocking process
WordPress Plugin Guide | Magento Guide | Joomla! Guide | PrestaShop Guide | PHP class Guide.
Drupal users, you can access the class via direct download or Packagist, and find full instructions in the PHP class guide linked above.
When do you need it? In general, you’ll likely need to set Terms & Conditions if you have app which participates in some form of commerce (whether selling to users directly or facilitating trading). Additionally, some specific instances where they might needed are where you:
Particular emphasis should be given to account termination clauses, payment conditions and the limitation of liability clauses (and disclaimers).
Why? The GDPR requires that you keep and maintain valid records of consent if processing user data based on consent. Without these records, the consent you collect is considered invalid.
When do you need it? When processing the personal data of EU-based users on the legal basis of Consent. Typical examples of this include collecting personal data via forms for newsletters, email lists, subscriptions etc. This does not typically apply to consent for cookies as cookies are still largely governed by the ePrivacy Regulation (Cookie Law).
Note: GDPR requirements also apply if your base of operations is in the EU or if you simply offer goods or services to EU-based persons, even if that offer is free. Read more here.
Why? The GDPR requires that you keep and maintain valid records of processing if processing the personal data of EU-based persons. Without these records, your processing activities would be in violation of the law.
When do you need it? If you fall under the scope of the GDPR and your processing activities are not occasional, could result in a risk to the rights or freedoms of others, involves sensitive data or if you have more than 250 employees — in short, it’s almost always required.
Planning to send emails or newsletters? Read this:
Target children or minors? Read this: