On this page
Version: privacy-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.
1. Information and purposes
Authentication: Supabase handles Auth identifiers and sessions; Google Sign-In supplies authorized account information needed to authenticate. The public app offers Google sign-in. Legacy sessions and isolated recovery code remain; accounts are not silently merged by email. Auth credentials and private contact details are not part of people-discovery responses.
Profile and avatar: username, display name, biography, interests, activity content, friendships and public avatar are used for supported social features. The 36 character IDs are stable. Optional advanced avatar configuration and flattened previews remain QA-restricted; they are not verification of a person's appearance or identity.
Signup preference: your explicit He/Him or She/Her selection is stored through the private onboarding preference mechanism to filter avatar choices. It is not inferred from a selfie or Google data and is not automatically displayed publicly.
Adult eligibility: SimsMap is intended for adults aged 18 and above. The gated eligibility flow is not yet activated in production. When enabled with its matching backend, it processes a supplied birth date and explicit adult declaration to calculate eligibility against the server date. A client flag alone is insufficient. The birth date is not stored in the profile or adult-declaration table; account ID, current policy version and server-generated acceptance time are recorded. Date entry is self-declaration, not verified identity, liveness or proof that the supplied date is true. The eligibility declaration is distinct from policy acceptance and the private avatar-filter preference. Provider request/security logging is a separate processing boundary; no claim is made that providers retain no request metadata.
Registration selfie: the current signup flow requires a private owner-scoped selfie as part of its registration record and account-completion checks. It is stored separately from public avatars and is not readable by other ordinary members. It is not included in discovery, standard report snapshots or public profile responses. It does not prove age, identity, liveness or trustworthiness; SimsMap does not claim facial recognition or biometric matching. Authorized infrastructure access is a separate privileged boundary. No automated selfie-free registration alternative is currently available. If you do not wish to provide or retain this image, contact the privacy address before registering or request withdrawal/deletion assistance. Removing the required image may affect account-completion access; support must assess the request rather than falsely record a completed erasure.
Location and media permissions: foreground location supports map centering and activity discovery; use may be declined. No background location tracking is implemented. User-created activity venues and coordinates can be public to eligible users. Camera/gallery access supports a chosen selfie upload, not background camera access. Google Maps and Places process requests under their own services and terms.
Safety: report categories, optional explanations, relevant original message/activity snapshots, staff actions, restriction notices and appeals support evidence-based moderation. Reporter references remain confidential from reported users. Do not include passwords, private selfies or sensitive documents in report explanations. Arbitrary evidence-file upload is not implemented.
Unavailable features: SimsMap Plus checkout, Discover People, public advanced avatar editing and push notification delivery are disabled for the initial release. No active subscription payment flow is offered. Separately approved future activation must be reflected in current notices and access controls before new processing is enabled.
2. Public visibility and private records
Public profiles, selected avatars, activities and activity venues are shown through their applicable access rules. Private registration selfies, private onboarding preference, authentication details, exact private contact information and confidential moderation records are not part of a public profile. Activity venue coordinates are social content and differ from the device location used to center a map.
Discover People listing is disabled. Its prepared design is opt-in, not an assumption that signing in makes a member discoverable. Blocking and later removal of information cannot recall screenshots or copies already obtained by another person.
3. Sharing and service providers
Supabase provides authentication, database, Storage and Edge processing. Google provides Sign-In and Maps/Places. These public policy pages are prepared for Cloudflare Pages hosting. These providers may process connection, device, request and security information under their own services and safeguards, including processing outside India. The site uses no advertising or analytics scripts and no externally loaded fonts; hosting access/security logs are a separate provider process. Firebase push delivery and Play Billing checkout are disabled. No specific provider region, universal retention period or international-transfer certification is asserted here.
Necessary authorized staff can access relevant case material. No automatic sharing of private data with law enforcement is implemented. Valid legal demands, urgent disclosure or preservation require lawful authority, necessity, minimization, documented approval and applicable safeguards. This policy does not create an unrestricted disclosure permission.
No implemented advertising-data sale, public selfie feed or biometric profiling service is described. Reassess disclosures and obtain required approval before adding such processing.
4. Security and policy records
Owner-scoped private Storage, row-level security, server authorization, QA isolation and protected staff roles are used to protect covered data. Access to moderator functions requires authorized roles and MFA. Security cannot be guaranteed absolutely; compromised devices, previously downloaded content, infrastructure access and provider logs are separate boundaries.
Once approved published policies are activated, the server records authenticated user ID, bundle/document versions and acceptance time. A new version can require reacceptance without resetting a completed profile. Unpublished review documents are not accepted. The privacy notice is not a substitute for any separate specific consent legally required for a processing purpose.
5. Retention, deletion and recovery
Different stores have different deletion behavior. Profiles, signup records, preferences, activities and activity chats currently have no general automatic time-to-live. Completed signup removes its registration-draft row in the supported client flow; interrupted drafts may remain. Device discovery coordinates, saved activity venue coordinates and provider request/security logs are separate categories and must not be treated as one location-history store.
Private selfie metadata and image bytes are separate. There is no general automatic expiry currently implemented for the registration selfie. Account-completion authorization relies on the referenced private image being present. Contact the privacy address for withdrawal, deletion or access concerns; do not send another private image, password or verification code by email. Support must consider the account-access consequences and any outstanding cleanup safeguards. No maximum provider-fragment retention period is promised.
The currently deployed deletion function checks account eligibility, removes listed owner Storage objects and then requests Auth deletion. Supported foreign-key cascades remove linked data; deleting an activity can also remove associated conversation/participation records for other members. Advanced/ever-QA accounts can remain held for support assistance. The newer coordinated deletion/upload replacement is not deployed to production. Failed or held cleanup is not completion, and ordinary object listings do not prove removal of unfinished provider upload fragments. Some legacy notification references remain a known pending cleanup limitation.
Moderation data has configured cleanup-eligibility thresholds: evidence may become eligible for redaction after 180 days; case records after 180 days from closure or 365 days from creation for open cases; audit records after 365 days; reviewed appeals after 180 days. Restrictions, unresolved appeals and lawful preservation holds can affect eligibility. These are not guaranteed deletion deadlines. Cleanup requires authorized execution and verification, and free-text records may still identify people when an account-reference column is removed. No continuously scheduled purge is represented as verified.
Account deletion does not automatically erase support email, encrypted exports, offsite versions, provider logs or information previously downloaded by other people. Database backups do not include Storage image bytes. No backup rotation period, provider fragment-retention bound, support-mail retention period or complete production service restore is promised. Valid erasure/restriction decisions must be reapplied before any restored copy is returned to service.
The public Data Retention Policy describes current category-specific behavior and cleanup limits. No automatic inactivity, chat, support-mail or backup expiry is invented. Members may ask the privacy contact about continued retention or request applicable rights; unresolved deletion must be tracked as pending, not reported as complete. If subscription processing is introduced later, deleting an app account will not by itself cancel a subscription held with a store.
6. Your controls and requests
Available controls include supported profile/base-avatar edits, optional device permissions, blocking, reporting, sign-out and guarded account deletion. Appeals can be submitted through the supported mechanism where available or the monitored contact. Optional features that are disabled are not offered as active privacy controls. A moderation appeal is distinct from a statutory privacy request.
Send access, correction, erasure, withdrawal, grievance or other applicable privacy requests to the shared privacy contact. Requests from members who cannot sign in are accepted through this channel. Proportionate ownership checks may be needed before disclosing or changing account information. Never send passwords, authentication codes or private selfies as ownership proof. Requests will be considered under applicable law; no automated export or unverified response deadline is claimed.
7. Age, Indian law and changes
SimsMap is intended for adults aged 18 and above. Age is not inferred from a selfie, Google profile or avatar. Date-based self-declaration is not verified age and does not establish parental consent. Child-safety reporting remains available for an adults-only service. Applicable Indian privacy, intermediary, child-safety, consumer and lawful-preservation requirements apply to the service as relevant; this notice does not claim legal certification.
Material processing changes require updated versioned notices and any legally necessary consent. The version and effective date are shown at the top of this page. Contact the privacy or grievance officer with questions.