What optional analytics consent does—and does not—permit

Analytics consent concerns measurement of visits and product actions. It is not permission to sell a personal profile, read every conversation or send promotional messages. Keeping those decisions separate makes it easier to understand what happens when you allow or decline optional measurement.

Understand the measurement purpose

Persir’s optional Google Analytics integration measures sanitized page paths and allowlisted product-action events. Profile facts, conversation content, filenames, emails and authentication tokens are excluded from event payloads. Advertising signals and personalization are disabled in the application’s configuration.

That does not make the service anonymous or automatically exempt from consent. Google’s script can use browser cookies and technical information for measurement. The operator must also manage the analytics property’s external settings, retention and provider arrangements. Application code alone cannot establish every aspect of the provider’s processing.

Understand the current default

Persir keeps optional analytics off until a browser records an accepted choice. Missing configuration, a blocked storage mechanism or an applicable exclusion keeps collection off. An account or a game can function when optional analytics is disabled.

The app does not treat account creation, Google sign-in or Terms acceptance as analytics permission. It also does not convert an existing refusal into acceptance. These are important distinctions when a product simplifies its interface: removing a footer shortcut should not silently change a recorded choice.

Know why some analytics exceptions do not settle the question

Official ICO guidance describes a statistical-purpose exception with conditions, including limits on purpose and a simple free way to object. CNIL guidance also describes specific conditions for exempt audience measurement. An exception depends on actual processing, provider use and applicable law.

Persir has not established that its current GA configuration qualifies everywhere or determined each visitor’s jurisdiction reliably. It therefore retains opt-in. IP handling or disabled advertising features alone do not establish exemption. The linked guidance is a starting point for the operator’s assessment, not a statement that every analytics tool must use the same controls.

Change the choice where it remains accessible

Privacy contains optional analytics controls that work without signing in. Settings provides the same controls for account users. Choices are stored in the current browser, so another device can have a different setting. GPC and Do Not Track signals also keep collection off.

Withdrawing permission disables collection and clears app-created GA cookies where the browser allows it. It does not erase reports already collected by Google. Contact the operator about earlier data or unresolved provider retention questions. Avoid assuming that a new browser choice can identify and remove every prior observation.

Keep other decisions separate

Daily Draft works without analytics permission: its necessary browser proof and seven-day server saves serve gameplay. A funnel event can indicate a start, completion or sign-in stage without transmitting answers or identity. The bridge accepts only reviewed event names, the fixed daily-draft identifier and listdle, direct or other source labels. Events before tracking is allowed are dropped without later replay.

Summary import requires its own confirmation, and any future commercial disclosure would need a separate scoped decision. Read the purpose attached to each control. Allowing visit measurement should mean allowing visit measurement, with clear limits and a practical route to change your mind.