Changeset 2376722
- Timestamp:
- 09/07/2020 06:41:54 PM (6 years ago)
- File:
-
- 1 edited
-
better-gdpr/trunk/readme.txt (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
better-gdpr/trunk/readme.txt
r2372143 r2376722 2 2 Contributors: stremovsky 3 3 Donate link: https://paranoidguy.com/ 4 Tags: gdpr, privacy, privacy-tools, compliance, cookie-consent 4 Tags: gdpr, privacy, privacy-tools, compliance, cookie-consent, security, cookie-banner, GDPR-compliance, general-data-protection-regulation, law, saas, regulations 5 5 Requires at least: 4.7 6 6 Tested up to: 5.5 … … 14 14 == Description == 15 15 16 Better-GDPR is GDPR automation service built by <a target='_blank' href='https://paranoidguy.com/'>ParanoidGuy.com team</a>. In addition to regular services like cookie consent and GDPR user request management we can automatically sync user records with different SAAS service. For example Mailchimp, GetResponse, Hubspot, SAP, Salesforce, etc... at the fraction of the cost.16 Better-GDPR is GDPR automation service built by <a target='_blank' href='https://paranoidguy.com/'>ParanoidGuy.com team</a>. In addition to regular services like cookie consent and GDPR user request management, the plugin knows to automatically sync user records with different cloud SAAS service. For example Mailchimp, GetResponse, Hubspot, SAP, Salesforce, etc... 17 17 18 = Plugin main features: =18 = Plugin main advantages: = 19 19 20 1. Cookie consent popup21 2. Better architecture22 3. PrivacyBunker.cloud portal integration23 3. User profile sync and change propagation20 1. GDPR compliant cookie consent popup 21 2. Simple integration 22 3. User privacy portal 23 4. User profile sync and change propagation 24 24 25 = 1. Cookie consent plugin =25 = 1. GDPR compliant cookie consent plugin = 26 26 27 It is very similar to other cookie consent popup plugins. The main difference between most of the similar tools is that we inject not-required components ( javascript) only after we got actual user consent. For example, Advertising related javascript code will be injected after the user gave us Advertising consent. You will need to specify actual javascript code to inject (i.e. Facebook pixel) under specific categories using our management tool.27 It is very similar to other cookie consent popup plugins. The main difference between most of the similar tools is that we inject not-required components (JavaScript) only after we got actual user consent. For example, Advertising related JavaScript code will be injected after the user gave us Advertising consent. You will need to specify actual JavaScript code to inject (i.e. Facebook pixel) under specific categories using our management tool. 28 28 29 Under the hood, user consent categories are saved in a special cookie called: "BETTERGDPR". So, when the page loads, for the user, for the first time in a session, we check the value of the "BETTERGDPR" cookie value and inject approved javascript code. If it is a new user, we will show the user our cookie consent popup.29 Under the hood, user consent categories are saved in a special cookie called: "BETTERGDPR". So, when the page loads, for the user, we check the value of the "BETTERGDPR" cookie value and inject approved JavaScript code. If it is a new user, we will show the user our cookie consent popup. 30 30 31 = 2. Better architecture=31 = 2. Simple Integration = 32 32 33 BetterGDPR plugin does not change your database structure nor it does not create any additional tables to store user consent values. Instead, the plugin will open for your site a tenant subdomain at PrivacyBunker.cloud - a service build and maintained by the PranoidGuy.com team. This domain will be a privacy portal for your users.33 BetterGDPR plugin does not change your database structure, nor it does not create any additional tables to store user consent values. Instead, the plugin will open for your site a tenant subdomain at PrivacyBunker.cloud - a service build and maintained by the PranoidGuy.com team. This domain will be a privacy portal for your users. 34 34 35 35 What are the advantages of this architecture: 36 36 37 37 1. No changes in your WordPress production database. 38 2. The user gets privacy portal covered bellow.39 3. Personal data is encrypted and stored in AWS Aurora PostgreSQL cluster deployed in Frankfurt.38 2. The user can use the Privacy Portal covered bellow. 39 3. Personal data is encrypted and stored in the AWS Aurora PostgreSQL cluster deployed in Frankfurt. 40 40 41 41 42 = 3. PrivacyBunker.cloud privacy portal integration=42 = 3. User privacy portal = 43 43 44 Upon your end-user registration, we will also register him at Custom-Subdomain.PrivacyBunker.cloud service. PrivacyBunker.cloud service gives your customers full control in terms of the GDPR. It automates the execution of the following GDPR user rights:44 All your users will get access to the cloud Privacy Portal. This Privacy Portal will allow your customers to fetch details from other 3rd party SAAS services and give you a solution for the following GDPR requirements: 45 45 46 1. The right to be informed 47 2. The right of access 48 3. The right to rectification 49 4. The right to erasure 50 5. The right to restrict processing 51 6. The right to data portability 52 7. The right to object 53 8. Rights in relation to automated decision making and profiling 54 46 * **Access**: your customers can log in to his Databunker account and view personal data. 47 * **Withdraw**: your customers can withdraw consents given previously. 48 * **Update**: your customers can change their personal data saved in Databunker. 49 * **Delete**: your customers can perform a "forget-me" request inside Databunker. 50 * **Restrict**: your customers can specify what operations they allow with their personal profiles. 55 51 56 52 = 4. User profile change propagation =
Note: See TracChangeset
for help on using the changeset viewer.