Anonymous usage data¶
Drupal CMS is free and open source. We want to make it as useful as possible for our users.
To help guide us, Drupal CMS sends a small amount of usage data to the Drupal CMS team. We use Amplitude to store this data in the European Union and analyze it. Amplitude is fully compliant with GDPR but we do not collect any data that is identifiable to any individual person.
This page explains what we collect, and when.
The short version¶
- We never collect any identifying information about you.
- We never collect your site's content, your users' data, or your visitors' data.
- Data is only transferred between the web server and Amplitude.
- No client-side information (e.g. cookies and local storage) is collected.
- Custom modules are recorded as
**custom**. - Only certain known recipes are recorded.
- Everything we collect is listed on this page.
- You can turn this off at any time.
How to opt out¶
You can opt out at any time by going to the 'Basic site settings' page under Configuration > System > Site information (/admin/config/system/site-information).
You can also opt out without touching the browser:
- Before installing Drupal, set the
DRUPAL_CMS_TELEMETRYenvironment variable to0. - On an existing site, run
drush state:set drupal_cms_telemetry 0.
Your choice is stored in the site's database, so it only applies to that environment. A fresh environment, (e.g., a new local copy or a preview site), will ask again.
To opt your site out of telemetry across all environments, add this to your settings.php file:
What we collect¶
| Event | What we send | Notes |
|---|---|---|
| You install Drupal CMS | Which site template was used and, if installing at the command line, whether it was explicitly chosen | Only certain site templates are recorded. |
| You install a module | Name of the module and whether it was installed by Project Browser and/or a recipe | We only record modules you add after installing Drupal. |
| You uninstall a module | Name of the module | |
| You apply a recipe | Name of the recipe and whether Project Browser applied it | Only certain recipes are recorded. |
| Every 7 days | The number of times we have sent this event | Lets us know your site is still active. If this is the first ping from your site, includes an opt-in flag and the name field from the project's composer.json (if it is drupal/cms or drupal/cms_cpanel). |
| You visit certain admin pages | Which page you visited | See the table below. We do not track who visited the page, how, or when. |
| You create a code component | No additional information |
We track visits to the following admin pages:
| Page | Path |
|---|---|
| Module updates form | /admin/reports/updates/update |
| SEO checklist | /admin/config/search/seo-checklist |
| Language checklist | /admin/config/regional/multilingual-checklist |
| Recommended add-ons | /admin/modules/browse and /admin/modules/browse/recommended |
| Module list | /admin/modules/browse/drupalorg_jsonapi |
| List of Canvas pages | /admin/content/pages |
| List of menus | /admin/structure/menu |
| List of views | /admin/structure/views |
| List of webforms | /admin/structure/webform |
| List of content | /admin/content |
| Status report | /admin/reports/status |
Every event also includes:
- A randomly generated identifier. It's unique to your site, but not connected to you, your server, or anything else in the real world. This identifier lets us tell the difference between "one site that installed ten modules" and "ten sites that each installed one module."
- A flag that says whether your site's environment appears to be DDEV, the Drupal CMS launcher app, another local environment, or a dev, staging, or production server. This is not a host name or URL, so it doesn't reveal anything about your site.
How we identify custom modules¶
We don't want to collect the names of custom modules, since those could reveal something about your site or business. A module is considered custom if its info file doesn't have the project key which is normally added by drupal.org.
Known recipes¶
Only certain recipes and site templates are reported to telemetry. The exact lists can be seen in the \Drupal\drupal_cms_helper\Telemetry enum.