Repository navigation
|
How can a team catch Device fingerprinting to track users automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rni 'fingerprint\|deviceFingerprint\|canvas fingerprint' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. Building a persistent device fingerprint from hardware or settings to identify users. Apple bans this regardless of ATT consent. The fix. Do not fingerprint. Use the platform advertising identifier with consent where tracking is genuinely needed. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
BOTH-FINGERPRINTINGwith a coverage line and a proper exit code.What the hit means. Building a persistent device fingerprint from hardware or settings to identify users. Apple bans this regardless of ATT consent.
The fix. Do not fingerprint. Use the platform advertising identifier with consent where tracking is genuinely nee…