Do Flutter Push Notifications Need GDPR Consent in the EU? — Security & GDPR article by Rui Codex

Usually, yes. A push token is personal data when it can identify a user, and the ePrivacy Directive requires consent before information is stored on or read from a device, unless it is strictly necessary for a service the user asked for. Operating-system permission is not the same as GDPR consent, so you need a lawful basis, clear information and a way to withdraw.

Key takeaways

  • A push token that can be linked to a person is personal data under the GDPR.
  • Granting an operating-system permission does not by itself prove a valid GDPR consent.
  • Marketing notifications usually need opt-in consent, while essential service messages may rely on other lawful bases.
  • Consent must be specific, withdrawable and recorded, and the app must keep working when a user declines.

What do the GDPR and ePrivacy rules require for push notifications?

The GDPR requires a lawful basis for every processing of personal data, and consent is only one of six bases listed in Article 6. The ePrivacy Directive adds a separate rule for terminal equipment: storing information on a device or gaining access to it generally needs the user's consent, subject to narrow exceptions. A push registration touches both areas, because the app writes a token to the device-linked backend and the token is then used to reach that device.

This article is general information and not legal or tax advice. Whether a particular notification flow complies depends on facts that only your legal counsel can assess.

For the GDPR, consent must be freely given, specific, informed and unambiguous, and it must be as easy to withdraw as to give. Pre-ticked boxes and consent bundled into terms of service do not meet this standard. Rui Codex offers technical implementation support for such flows, and it does not provide legal or compliance advice.

Is a push token personal data?

A push token is usually personal data when your system can connect it to a user account, a device owner or a usage history. A random token on its own may look anonymous, but the moment your backend stores it next to a user ID, it becomes part of a profile. Treat the token like an identifier and map it to a retention rule.

Your architecture determines the answer. A token that is only used for a transient session and deleted on logout carries less risk than a token kept for years and joined to purchase history. Document where each token lives, who can read it and how long it persists.

Tip: Store push tokens in a separate table with a retention field, and delete rows when a user logs out or uninstalls the app.

Operating-system permission is a device-level control that lets an app display notifications. It tells you that the user accepted the system prompt, but it does not tell you why, for which purposes, or whether the user understood that marketing content would follow. GDPR consent needs purpose-specific information and a record you can show later.

On iOS, the system prompt is shown by the operating system and the app can only request it through the user notification API. The Apple developer documentation describes how the request works. On Android 13 and later, notifications require a runtime permission, described in the Android developer guide. Both platforms give the user a control, but neither replaces your own consent record.

A compliant flow separates three decisions: whether the user wants notifications at all, which categories they accept, and whether you may process their data for marketing. Show the explanation before the system prompt, so the user understands what they are agreeing to. The Flutter plugin used for messaging, typically built on the Firebase Cloud Messaging documentation model, handles delivery but not your legal wording.

  1. Explain the notification categories in plain language before any system prompt appears.
  2. Request the operating-system permission only after the user has chosen to receive notifications.
  3. Ask for marketing consent as a separate, unticked choice that the user can change later.
  4. Record the consent version, timestamp, categories and the text shown to the user.
  5. Sync the choice to the backend and stop sending any category that was withdrawn.
  6. Provide a settings screen where the user can change or withdraw each choice.
Tip: Do not re-trigger the system prompt on every launch. Check the current permission status and show your own in-app explanation instead.

Which notifications need consent and which do not?

Notifications that are strictly necessary for a service the user requested, such as a delivery status for an order they placed, are often justified on another lawful basis, but this is a decision for your counsel. Promotional messages, profiling-based offers and sharing tokens with third parties need a clear opt-in. The table below compares the categories using qualitative criteria only.

CategoryTypical purposeConsent handlingRisk if misclassified
TransactionalOrder or account statusOften a different lawful basis; inform the user clearlyMedium
Security alertsLogin or fraud warningsUsually necessary for the service; document the reasonMedium
MarketingOffers and campaignsOpt-in consent, separate and withdrawableHigh
Profiling-basedPersonalised offers from behaviourOpt-in consent with clear explanation of logicHigh

Hypothetical examples of consent flows

Here are two hypothetical scenarios:

In the first, a retail app sends only order updates. The team asks for operating-system permission after checkout, explains the category in one sentence, and stores the choice with a timestamp. Because no marketing is sent, the design stays simple, and the user can switch notifications off in settings.

In the second, the same app adds a weekly promotions feed. A single toggle is added to the existing permission prompt, and the default is on. This design fails: the promotions consent is bundled with the operating-system permission and cannot be withdrawn separately, so the team must redesign it as a separate opt-in.

Where do consent designs fail?

Most failures come from mismatches between the interface and the backend. The app shows that marketing is off, but the backend still sends campaigns because the sync job failed silently. Another common failure is a token that survives logout and keeps receiving messages for a previous user on a shared device.

Consent also fails when the flow is designed for one platform. Android and iOS handle permission differently, and a web-based or cross-platform admin tool may not reflect the change. Test each path, including reinstalling the app and changing accounts on the same device. If you need help designing these flows, the Flutter app development service page describes how Rui Codex approaches mobile delivery, and the security and GDPR articles cover related engineering topics.

Frequently Asked Questions

Do I need consent for every push notification?

No, not every notification needs consent under the same rule. Messages strictly necessary for a service the user requested may rely on another lawful basis, while marketing and profiling generally need opt-in consent. Classify each category and document the reason for each one.

Is operating-system permission enough for GDPR consent?

No, operating-system permission only allows the app to show notifications on the device. It does not explain purposes or record what the user understood. You still need your own information, a separate choice where required and a consent record.

Can a user withdraw push consent easily?

Yes, the GDPR requires withdrawal to be as easy as giving consent. Provide an in-app settings screen for each category, and make sure the backend stops sending a category as soon as it is withdrawn.

Should I store push tokens after a user logs out?

Usually not in a form linked to that user. Delete or unlink the token at logout, and set a retention rule for tokens that remain. The right period depends on your purpose, so confirm it with your counsel.

Conclusion

Push notifications in Flutter apps raise real consent questions under the GDPR and the ePrivacy rules, and the operating-system prompt alone does not settle them. Separate transactional and marketing messages, record each choice and make withdrawal simple. Test the flow across both platforms and check that the backend honours every change. If you want an engineering review of your notification design, request a project consultation at https://ruicodex.com/Contact or email info@ruicodex.com.

Sources

Tags: Flutter push notifications GDPR consent ePrivacy mobile apps data protection EU compliance

Need Help Implementing This?

Our team can help you put these insights into practice. From AI automation to custom software development, we build solutions that deliver real results.

Send a project request