On this page
Version: deletion-2026-10-29-v1. Effective date: 29 October 2026.
Legal operator and grievance officer: Sunny Shashikant Solanki. Correspondence address: 38 Shreejinagar Society, Godhra, Gujarat, India. Support, privacy, grievances, child-safety reports and account-deletion requests: sunnysolanki6359@gmail.com.
Request deletion without signing in
Email sunnysolanki6359@gmail.com with the subject "SimsMap account deletion" and identify the email address associated with the account. You may use this route if you cannot access the app or the in-app operation is pending or restricted. The operator has confirmed that this inbox is monitored for deletion requests. This page does not submit a request automatically; send an email through your email application.
Do not send your Google password, authentication codes, recovery secret or private registration selfie. Proportionate ownership verification may be required before account data is disclosed or deleted. An email address alone is not permission to delete another person's account.
In-app account deletion
Where available, open SimsMap's profile/settings account controls, choose Delete account and review the confirmation. The backend checks authentication and account ownership. The current production implementation removes listed owner Storage objects and requests Auth deletion, with related database cleanup through applicable cascades. A failed, retrying or held operation is not successful deletion. Keep any error/status information so support can assess what remains.
Data affected and retained
Deletion affects authentication, profile and linked private/account records. Owner-scoped private selfie and uploaded avatar bytes need separate Storage cleanup. Account-created activities can cascade their conversations, invitations and participation; another member's legitimate data must not be erased indiscriminately. Necessary moderation/audit evidence and lawful holds can be treated separately. See the Privacy Policy and Data Retention Policy for current limitations.
Encrypted backups, support mail, provider logs and copies already obtained by others are not automatically erased when an Auth row is deleted. Legacy notification references and unfinished provider upload fragments have known cleanup limits. We do not promise immediate physical erasure, a universal maximum fragment lifetime or that all backup copies have already been purged.
Pending or restricted deletion
Advanced-avatar and previously authorized QA accounts can require support assistance because of upload/deletion safeguards. The coordinated A2 deletion replacement is not yet deployed to production. A request for assistance is not a claim that that replacement or every cleanup path has passed hosted validation. Support must assess ownership, outstanding work and lawful exceptions and explain the outcome; no unverified completion deadline is promised.
Support and safety
Contact the shared monitored address above for a pending deletion, privacy grievance or inability to sign in. This channel is not an emergency service. No payment is required to submit a deletion request. Public optional subscriptions and checkout are disabled in the initial release.