Repository navigation
|
How can a team catch Account deletion is a mailto or deactivate only flow 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 -rn 'deleteAccount\|delete account' --include='*.swift' . && grep -rn 'mailto:\|deactivate' --include='*.swift' . # deletion must truly delete, not mailto or deactivateRead 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. The only account removal path is a mailto link, a web form the user must leave the app to reach, or a deactivate that does not delete. The fix. Provide genuine in app deletion of the account and its data, not a deactivate or an external form. 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
APPLE-ACCOUNT-DELETION-WEAKwith a coverage line and a proper exit code.What the hit means. The only account removal path is a mailto link, a web form the user must leave the app to reach, or a deactivate that does …