Permission and consent: what the CNIL tells mobile apps

If a request for notifications or location gets stuck, the first thing to check is what we are talking about: a permission or a consent. The CNIL published its recommendations on permissions in mobile applications on September 24, 2024. I summarize them step by step. This is not legal advice.

Léna PerottaCustomer Success & Support Manager, 1 min

Photo: Alexander Andrews alex_andrews, CC0. Photo credits

The permission: a phone setting

A permission is a technical system setting. It lets the person block an app’s access to a sensor or to data, whatever the purpose.

First thing to remember: the iPhone or the Android phone manages it, not the app.

The consent: another notion

The CNIL writes that these technical permissions are not designed to collect consent in the GDPR sense.

A permission can also be requested when consent is not required. Example given: location for a navigation app.

Conversely, a simple permission grant is not always enough. In most cases, the CNIL says a consent management platform is needed in addition.

When to ask

Consent can be collected before or after the permission request. Both orders are possible.

The CNIL does consider it good practice to collect it in context, as the person acts, rather than on one single screen at first launch.

If the person says no

The CNIL invites apps not to show the second request when the permission or the consent is refused. The idea is not to bother the person for nothing.

So after a refusal, leave them alone: no new window the next time the app opens.

For a specific case

Notifications, location, camera: each request has its purpose and its moment. For each one, note what you ask, why and where in the app.

For a specific case, the CNIL page and legal advice prevail. My summary stops at what the page says.

Sources