Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,090 of 9,090 pages
About the help in other languages
All help pages

Third-party extensions and privacy

For public bodies - the extensions installed with Exponential that send visitor or content data to third parties when activated (analytics, CAPTCHAs, maps, social login, AI providers), that none is active by default…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/government/privacy/third-party-extensions.md

On this page

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

  1. The extensions
  2. Checking what is active
  3. Before activating one
  4. Related pages

The extensions

ExtensionThird partyDataPage in this section
bcwebsitestatisticsGoogle Analytics / Google Tag Managervisitors' page views; shop orders if OrderSubmit is onAnalytics
recaptchaGoogle reCAPTCHAthe visitor's browser and interaction on protected formsCAPTCHAs
hcaptchahCaptchaas aboveCAPTCHAs
ezgmaplocationGoogle Mapsthe editor's map lookups; visitors' map views in your templatesMaps and embeds
sevenx_authentication_2fa social loginthe chosen identity providersign-in through that providerSocial login
expai (Exponential Intelligence)the AI provider configuredcontent, and images for alternative text, under its data policy(below)
cjw_newsletter statisticsnone (on-site)per-person opens and clicks, only with the "Newsletter statistics" consentConsent 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-user

or Setup > Extensions. Look also at ActiveAccessExtensions[] in each siteaccess.

Before activating one

  1. Purpose and legal basis: why the service is needed, on what basis.
  2. The provider's role (processor or independent controller) and terms; a processing agreement where needed.
  3. Transfers outside your jurisdiction, where your law restricts them.
  4. Consent before loading, where needed (see "Cookie banners and consent").
  5. The privacy notice updated.
  6. The Content Security Policy: the provider's hosts added with AdditionalSources[] only on the siteaccess that needs them.
  7. Accessibility of what the service shows (CAPTCHAs and maps are common barriers).
  8. A record in your inventory with the date of activation.

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.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x