How GPC, Do Not Track and browser privacy choices affect Persir

Browser privacy settings can communicate a preference, but different signals have different purposes and legal treatment. A useful explanation should name what the application actually does. Persir uses GPC and Do Not Track as reasons to keep optional analytics off, alongside its own browser-level consent and internal-testing exclusion.

Understand GPC’s role

Global Privacy Control is a browser signal used to express an opt-out preference. The California Attorney General’s CCPA guidance discusses opt-out rights and GPC for covered businesses. Whether a particular legal duty applies depends on the business and processing, so a signal should not be described as a universal erasure command.

In Persir, a detected GPC signal blocks optional analytics even if the browser previously stored an accepted analytics choice. That is an application behavior you can understand directly. It does not authorize a new purpose, and it does not require the app to turn a stored refusal into acceptance.

Understand Do Not Track separately

Do Not Track is another browser preference signal. It is not identical to GPC, and you should not assume identical recognition across websites. Persir treats a recognized DNT preference as a reason to leave optional analytics disabled.

A website’s response should be checked against its policy and actual controls. Turning on a browser signal does not necessarily change the behavior of every third-party page you later visit. Review the relevant service independently, especially before transferring private archives or using a sharing feature.

Check the app’s local preference

Persir records the analytics choice in browser storage. A declined choice stays declined across ordinary visits in that browser. Another browser or device can have a different stored choice. Clearing browser storage can remove the local record, after which optional measurement remains off until a new accepted choice is recorded.

Privacy and Settings provide controls for changing the choice. When a supported privacy signal is active, the interface explains that analytics is off. A displayed accepted local choice should not be interpreted as active collection if a higher-priority signal or exclusion prevents it.

Distinguish optional measurement from essential service activity

Disabling analytics does not remove authentication cookies or stop the application from saving information you explicitly submit for the service. Account access, source imports and gameplay use their own necessary processing. These operations should be described separately from optional visit measurement.

Similarly, a privacy signal does not delete an existing account, remove a local export or retract a shared image. Use the relevant controls for those goals. If you want a broader removal plan, map source accounts, downloaded files, imported records and external copies rather than relying on one setting to cover them all.

Verify without sending private information

You can review the visible analytics status and use browser tools if you are comfortable with them. Do not paste session cookies or private network requests into a public forum. If a setting appears inconsistent, describe the browser, relevant signal and observed stage to Help or the verified operator.

Persir’s analytics bridge receives only fixed guest-event categories and bounded source labels when tracking is permitted. It does not replay pre-consent events later. Browser signals are one part of a clear control system; they work best alongside understandable purposes, accessible withdrawal controls and separate decisions for any future commercial sharing.