User data deletion mechanism implemented
Why it matters
GDPR Art. 17 (right to erasure) and CCPA §1798.105 (right to delete) both create legal obligations for apps that collect personal data from users in the EU or California. Google Play Data Safety now explicitly asks whether users can request data deletion, and apps that answer 'yes' in the Data Safety form but provide no mechanism are flagged by reviewers. An 'account deletion' that only signs the user out — without deleting server-side records — is not deletion: it is de-authentication. If a user files a GDPR deletion request and your app's only mechanism is sign-out, you are non-compliant. The backend deletion must remove or anonymize all personal data: profile, activity logs, uploaded content, and third-party data processor records.
Severity rationale
High because lacking a data deletion mechanism creates direct legal liability under GDPR Art. 17 and CCPA §1798.105, and Google Play Data Safety discrepancies can result in listing removal.
Remediation
Implement a Delete Account flow that calls your backend deletion API and clears all local storage. Add it to your Settings screen and link to it from your privacy policy.
async function deleteUserAccount(userId: string) {
const confirmed = await showConfirmationDialog(
'Delete Account',
'This permanently deletes your account and all associated data. This cannot be undone.'
)
if (!confirmed) return
// 1. Delete server-side data
await api.delete(`/users/${userId}`)
// 2. Clear local secure storage
await SecureStore.deleteItemAsync('authToken')
await SecureStore.deleteItemAsync('refreshToken')
// 3. Clear non-sensitive local storage
await AsyncStorage.clear()
// 4. Navigate to logged-out state
navigateToWelcome()
}
For Google Play Data Safety, also provide a web-accessible deletion URL (https://yourapp.com/delete-account) so users can request deletion even after uninstalling the app — Play now requires this URL in the Data Safety form.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Mobile Permissions & Privacy Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- gdpr · Art. 17 — Right to erasure
- ccpa · §1798.105 — Right to deletion
- external · google-play-data-safety-deletion — Google Play: Data Safety — provide in-app data deletion
Taxons
History
- 2026-04-18·v1.0.0·Initial import from mobile-permissions-privacy·automated