Does a game SDK count as storing or reading data on the device?
Yes, in the EDPB's reading. Its Guidelines 2/2023 say that software placed on a device that then calls an API endpoint with stored information is "gaining access" under Article 5(3). The rule covers "information", not only personal data.
The guidelines also say there is no minimum time and no minimum amount for information to count as stored, and that any medium counts: disk, SSD or RAM. So a random player ID in a file under user:// is stored information, and an SDK that sends it is access.
The EDPB does not decide which uses are exempt. It says that depends on the case, on each country's law and on national regulators. That is why the next section looks at two national regulators.
Sources: EDPB Guidelines 2/2023, version 2.0, paragraphs 1, 6, 33, 37 and 38.
Which exemptions exist for analytics?
France and the UK both have a narrow exemption for statistics, with conditions. Read them as limits. Both are about counting how a service is used, not about following people or measuring marketing.
The CNIL also recommends that a tracker lives at most 13 months without automatic extension on new visits, and that the data is kept at most 25 months. Its self-assessment tool lists marketing measurement, such as acquisition channels and campaign performance, as a purpose that must be off by default. The ICO says the exception does not apply if you keep individual-level information after you aggregate it.
| Regulator | Exemption | Main conditions | Not covered |
|---|---|---|---|
| CNIL (France) | Audience measurement trackers | Purpose strictly limited to audience measurement, for the publisher only. Produces anonymous statistics only. | Combining the data with other processing, passing non-anonymous data to third parties, following a person across sites or apps. |
| ICO (UK) | Statistical purposes exception in PECR | Sole purpose is statistics about how the service is used, to improve it. Clear information and a simple, free way to object. | Tracking or profiling individual visitors, online advertising, keeping individual-level data after aggregation. |
Sources: CNIL, audience measurement page (4 July 2025) and self-assessment tool; ICO storage and access guidance (29 April 2026).
Does Manalens fit those exemptions by default?
Probably not, for most game setups. We say this plainly, because the product measures things the exemptions leave out.
Three facts matter. The web SDK keeps a persistent anonymous ID for 1 year and refreshes it on each event, where the CNIL recommends no automatic extension. Retention, funnels and player profiles need event-level data per player, where the ICO exception expects you to aggregate and not keep individual-level data. And the product measures acquisition: UTM fields, creators, Steam sources and install attribution, which the CNIL tool lists as marketing measurement.
So if your adviser says you need consent, turn on consent mode. It is built for that case.
Sources: Manalens data collection documentation; CNIL self-assessment tool; ICO storage and access guidance.
What does consent mode do in each SDK?
It stops the SDK from storing an ID until the player agrees. The web SDK and the game SDKs behave differently before consent, so check the table.
The web SDK does not save the choice, so call setConsent() on each page load after your consent tool reports it. The Godot and Unity SDKs save the choice, so the next launch uses it. Before consent, link_url() and LinkUrl() return the URL unchanged.
| SDK and option | Before consent | After consent | When consent is withdrawn |
|---|---|---|---|
| Web SDK: requireConsent or data-require-consent | No cookies and no localStorage. Page views and events are still sent, without anonymous_id, session_id or user_id. They count in totals, not as visitors, and not in retention or funnels. | Creates or restores the persistent visitor ID. | setConsent(false) clears identity storage and removes identity fields from queued events. |
| Godot SDK: consent_required | Records no events and writes no ID. An identify() call waits until consent. | set_consent(true) starts tracking and sends game_open. | set_consent(false) deletes the ID, the session and the queue, and writes an opt-out marker file. |
| Unity SDK: ConsentRequired | Records no events and writes no ID. | SetConsent(true) starts tracking and sends game_open. | SetConsent(false) deletes the ID, the session and the queue, and writes an opt-out marker file. |
GDScript
Manalens.init({
"publishable_key": "YOUR_PUBLISHABLE_KEY",
"endpoint": "https://YOUR_COLLECTOR_ENDPOINT",
"consent_required": true,
})
# Later, from your consent screen:
Manalens.set_consent(true) # starts tracking; sends game_open
Manalens.set_consent(false) # deletes the ID, the session and the queueSources: Manalens consent, Godot SDK and Unity SDK documentation.
What does the collector store about players?
Events, a random anonymous ID, the session ID and a country code. It does not store IP addresses or raw user agents.
The collector uses the IP address in memory to find the country, then discards it. It keeps the device, OS and browser that it derives from the user agent, not the user agent itself. Page URLs lose their query strings and fragments, except for allowlisted campaign fields. The collector sets no cookies. The game SDKs send no device ID and no hardware details.
One exception: for projects with a game, install attribution keeps a keyed hash (HMAC-SHA256) of the project ID and the IP address for 72 hours, then deletes it. You can turn it off. Custom properties are data that you choose to send, so keep names, emails and free text out of them.
Sources: Manalens data collection and install attribution documentation.
How do I ask for consent in a game?
Start the SDK in consent mode, show a clear choice on the first launch, and let players change it later in settings.
- List what the game collects and why: events, the player ID, the country and install attribution. Put it in your privacy policy.
- Decide with your legal adviser which players need consent.
- Start the SDK with consent_required (Godot) or ConsentRequired (Unity) set to true.
- On the first launch, show a short screen that explains analytics and offers a clear yes and no.
- Call set_consent(true) or set_consent(false) with the answer.
- Add a settings toggle, so a player can change the choice at any time.
- Test a build: before consent, no events reach the activity feed.
Sources: Manalens Godot SDK and Unity SDK documentation; ICO storage and access guidance.
What does consent cost me in data?
You lose the players who say no. In the game SDKs they send nothing, so retention, funnels and installs count only the players who agreed.
This is a smaller problem than it sounds, because most decisions compare groups: build 571 against build 570, or one creator against another. Those comparisons still work when the same rule applies to both sides. Avoid comparing a consent build with an older build that had no consent screen, because the populations differ.
On the web, events sent before consent still count toward page view and event totals. So traffic totals stay complete, while visitor counts cover consenting visitors only.
Sources: Manalens consent and metrics documentation.
How do I set it up?
Manalens is the analytics and growth engine built for games. Turn on consent mode in the Godot, Unity or web SDK, and read what each SDK stores before and after consent.
Sources: Manalens product documentation.
Frequently asked questions
Does Manalens make my game GDPR compliant?
No tool can do that on its own. Compliance depends on what you collect, why, where your players live and what you tell them. Manalens gives you technical controls: consent mode, opt-out, no stored IP addresses and an install match you can turn off. Decide the rest with your legal adviser.
Is a random player ID enough to avoid consent?
Not by itself. The EDPB says Article 5(3) covers any information stored on a device, not only personal data, and an SDK that sends a stored ID gains access to it. Whether an exemption applies depends on your purpose and on national rules, such as the CNIL and ICO conditions.
What happens to queued events when a player withdraws consent?
In the Godot and Unity SDKs, withdrawing consent deletes the anonymous ID, the session and the queue of unsent events. The SDK also writes an opt-out marker file, and it records nothing while that file exists. In the web SDK, setConsent(false) removes identity fields from queued events.
Can I turn off install attribution?
Yes. Install attribution keeps a keyed hash of the project ID and the IP address for 72 hours, to match a first game launch to a recent website visit. You can turn it off. The collector never stores the IP address itself, with or without install attribution.
Sources and implementation
- EUR-Lex: Directive 2002/58/EC (ePrivacy Directive), consolidated text of 19 December 2009, Article 5(3) ↗
- EDPB: Guidelines 2/2023 on Technical Scope of Art. 5(3) of ePrivacy Directive, version 2.0 (adopted 7 October 2024) ↗
- CNIL: Cookies, solutions pour les outils de mesure d'audience (4 July 2025) ↗
- CNIL: Outil d'auto-évaluation, mesure d'audience exemptée de consentement (July 2025) ↗
- ICO: Guidance on the use of storage and access technologies, What are the exceptions? (final guidance, 29 April 2026) ↗