You're viewing help content for version:
- 6.4
- Older Versions
The European Union's General Data Protection Regulation on data privacy rights takes effect as of May 2018.
AEM Sites is ready to help customers with their GDPR compliance obligations. This page guides customers through the procedures to handle GDPR requests in AEM Sites. It describes the location of private data stored, and how to remove them manually or with code.
For further information see the GDPR page at the Adobe Privacy Center.
Note:
See AEM GDPR Readiness for further details.
User accounts and UGC content on the author server are covered in the Platform GDPR documentation.
User accounts used to authenticate visitors on the site, and UGC content on the publish server are covered in the Platform GDPR documentation.
By default AEM Sites components do not store form-data entered by visitors on the
AEM has a cookie opt-out service that can be used for managing the opt-in/opt-out for users.
AEM provides an optional data layer with ContextHub. This keeps visitor-specific data in the browser, to be used for rules-based personalization.
By default, this visitor-data is not stored in AEM; AEM sends rules to the data layer to make personalization decisions in the browser.
Note:
Prior to Adobe CQ 5.6, the ClientContext (an earlier version of ContextHub) did send the data to the server, but did not store them.
Adobe CQ 5.5 and earlier are now EOL and not covered by this documentation.
The site owner needs to implement an opt-out component according to the following guidelines.
These guidelines implement opt-in as the default. Thus, a website visitor must clearly agree, before any Personal Data is stored in the browser's (client-side) persistence.
To preview persistance used ContextHub, a user can:
- Use the browser's console; for example:
- Chrome:
- Open Developer Tools > Application > Storage:
- Local Storage > (website) > ContextHubPersistence
- Session Storage > (website) > ContextHubPersistence
- Cookies > (website) > SessionPersistence
- Open Developer Tools > Application > Storage:
- Firefox:
- Open Developer Tools > Storage:
- Local Storage > (website) > ContextHubPersistence
- Session Storage > (website) > ContextHubPersistence
- Cookies > (website) > SessionPersistence
- Open Developer Tools > Storage:
- Safari:
- Open Preferences > Advanced > Show Develop menu in menu bar
- Open Develop > Show JavaScript Console
- Console > Storage > Local Storage > (website) > ContextHubPersistence
- Console > Storage > Session Storage > (website) > ContextHubPersistence
- Console > Storage > Cookies > (website) > ContextHubPersistence
- Internet Explorer:
- Open Developer Tools > Console
- localStorage.getItem('ContextHubPersistence')
- sessionStorage.getItem('ContextHubPersistence')
- document.cookie
- Open Developer Tools > Console
- Chrome:
- Use the ContextHub API, in the browser's console:
- ContextHub provides following data persistence layers:
- ContextHub.Utils.Persistence.Modes.LOCAL (default)
- ContextHub.Utils.Persistence.Modes.SESSION
- ContextHub.Utils.Persistence.Modes.COOKIE
- ContextHub.Utils.Persistence.Modes.WINDOW
The ContextHub store defines which persistence layer will be used, thus to view the current state of the persistence all layers should be checked.
- ContextHub provides following data persistence layers:
For example, to view data stored in localStorage:
To preview persistance used ContextHub, a user can:
- Use the browser's console:
- Chrome - open Developer Tools > Application > Storage:
- Local Storage > (website) > ContextHubPersistence
- Session Storage > (website) > ContextHubPersistence
- Cookies > (website) > SessionPersistence
- Firefox - open Developer Tools > Storage:
- Local Storage > (website) > ContextHubPersistence
- Session Storage > (website) > ContextHubPersistence
- Cookies > (website) > SessionPersistence
- Chrome - open Developer Tools > Application > Storage:
- Use the ContextHub API, in the browser's console:
- ContextHub provides following data persistence layers:
- ContextHub.Utils.Persistence.Modes.LOCAL (default)
- ContextHub.Utils.Persistence.Modes.SESSION
- ContextHub.Utils.Persistence.Modes.COOKIE
- ContextHub.Utils.Persistence.Modes.WINDOW
The ContextHub store defines which persistence layer will be used, thus to view the current state of the persistence all layers should be checked.
- ContextHub provides following data persistence layers:
For example, to view data stored in localStorage:
var storage = new ContextHub.Utils.Persistence({ mode: ContextHub.Utils.Persistence.Modes.LOCAL }); console.log(storage.getTree());
-
// in order to be able to fully access persistence layer, Opt-Out must be turned off ContextHub.Utils.Cookie.removeItem('cq-opt-out'); // following call asks all currently loaded stores to clear their data ContextHub.cleanAllStores(); // following call asks all currently loaded stores to set back default values (provided in their configs) ContextHub.resetAllStores();
-
var storage = new ContextHub.Utils.Persistence({ mode: ContextHub.Utils.Persistence.Modes.SESSION }); storage.setItem('/store', null); storage.setItem('/_', null); // to confirm that nothing is stored: console.log(storage.getTree());