Skip to content

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 can, with your consent, send 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.

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.
  • Everything we collect is listed on this page.
  • You can turn this off at any time.

How to opt out

When you install Drupal CMS, or deploy it to a new environment, you will see a pop up message asking whether you consent to sending anonymous data.

You can change your mind at any time by going to the 'Basic site settings' page under Configuration > System > Site information (/admin/config/system/site-information).

What we collect

Event What we send
You install Drupal CMS Which site template was used
You install a module 1 Name of the module (e.g. webform)
You uninstall a module Name of the module
You apply a recipe Name of the recipe
Every 30 days 2 Nothing
You visit certain admin pages 3 Which page you visited
You create a code component Nothing
Someone logs in 4 An anonymous user ID

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 appears to be a production site, so we can filter out test data and local environments.

  1. We only record modules you add after your site is up and running, not anything installed during setup. ↩

  2. This is a ping to let us know your site is still active. ↩

  3. The only pages we record are: the module updates form, the SEO and language checklists, the list of webforms, and the recommended add-ons. ↩

  4. The user ID is hashed in a way that can't be reversed. This lets us count how many different people log in, without knowing anything about who they are. ↩