GDPR compliance: Provide instructions on how to clear stored state of the pro version about fingerprintjs HOT 3 CLOSED

Hi @bugreporter321
To be able to help you, can you please provide additional information:

1. The name and type of the identifier you're having troubles deleting. Once we know which identifier you refer to, we'll help you delete it.
2. Can you please link to the GDPR part that doesn't allow storing identifiers of this type? I'd be curious to learn more about this.

from fingerprintjs.

Maybe my observation is not correct in which case please accept my apology; yet could you shed some light on why in case of ios a device reset would alter the visitorID technically? The system software should not change on a reset, and the open source fingerprint does not change either. Unless on ios certain obvious system properties accessible to javascript are randomized on device initialization, I fail to understand what else except state encoded in favicon, tls session resumption, or similar could cause this behaviour? As the cookies can be and are cleared in safaris private mode, these are out of the game as easy explanation. While I understand you have to keep your business secrets, could you give a hint about the things you store in a browser state with regard to GDPR? Thanks

from fingerprintjs.

It's possible that some properties change during the factory reset and that may cause the identifier to change.
If you need more information about why it changed in your particular case, please contact [email protected] with your account and the visitorID before and after and we'll help you.
Regarding browser storage, Fingerprint Pro JavaScript agent can store a random string in cookies and local storage.
Hope this answers your question. I'm closing this ticket as not related to FingerprintJS (the library).

from fingerprintjs.