Third-party extensions and privacy
This page is for administrators, project managers and data protection officers. Composer installs several extensions
with Exponential, but they are not active until a site activates them: settings/site.ini [ExtensionSettings] ActiveExtensions[] ships with xrowmetadata only, and the setup wizard adds ezjscore, ezoe and ezformtoken
(Privacy standards: Third-party services).
Some of them send data to a third party once active. Whether a site package activates any of them is something to check
on your installation.
Note This page describes features and common practice; it is not legal advice. Check the law that applies to your organization with your legal counsel.
Contents
The extensions
| Extension | Third party | Data | Page in this section |
|---|---|---|---|
bcwebsitestatistics | Google Analytics / Google Tag Manager | visitors' page views; shop orders if OrderSubmit is on | Analytics |
recaptcha | Google reCAPTCHA | the visitor's browser and interaction on protected forms | CAPTCHAs |
hcaptcha | hCaptcha | as above | CAPTCHAs |
ezgmaplocation | Google Maps | the editor's map lookups; visitors' map views in your templates | Maps and embeds |
sevenx_authentication_2fa social login | the chosen identity provider | sign-in through that provider | Social login |
expai (Exponential Intelligence) | the AI provider configured | content, and images for alternative text, under its data policy | (below) |
cjw_newsletter statistics | none (on-site) | per-person opens and clicks, only with the "Newsletter statistics" consent | Consent records for mail |
expai is installed by composer.json and active only where a site activates it; its data policy decides which
content may go to which provider and region (Exponential Intelligence).
Involve your DPO before activating it.
Checking what is active
./console exp:ini where site.ini/ExtensionSettings/ActiveExtensions --allow-root-useror Setup > Extensions. Look also at ActiveAccessExtensions[] in each siteaccess.
Before activating one
- Purpose and legal basis: why the service is needed, on what basis.
- The provider's role (processor or independent controller) and terms; a processing agreement where needed.
- Transfers outside your jurisdiction, where your law restricts them.
- Consent before loading, where needed (see "Cookie banners and consent").
- The privacy notice updated.
- The Content Security Policy: the provider's hosts added with
AdditionalSources[]only on the siteaccess that needs them. - Accessibility of what the service shows (CAPTCHAs and maps are common barriers).
- A record in your inventory with the date of activation.
Related pages
- Privacy standards
- Extensions
- Controller, processor and the software
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.