Privacy Policy

01Scope

This policy applies to essncl.in and to an ESSNCL-published application when that application or its store listing links here. Before any application is published, its actual data practices, permissions and third-party software will be reflected in this policy and in the relevant Google Play Data safety and Apple App Privacy disclosures. Those disclosures are intended to be consistent.

Some applications are operated for another organisation. In that case the application will identify that organisation and explain the respective responsibilities.

02Data we collect

Website enquiries

When you contact us, we receive the information you enter, which may include your name, email address, phone number, organisation, project needs and message.

Account and deletion requests

When you submit a privacy or deletion request, we receive the identifiers and details needed to locate the relevant application records, verify that the request is yours, communicate with you and record the outcome. The intake identifiers, verification trail and reported outcome remain a separate ESSNCL request record; submitting or completing a Sampark Setu in-app request does not silently erase that publisher-intake record.

Technical information

Our systems may record IP address, browser or device type, requested pages, timestamps and security events for delivery, reliability, fraud prevention and abuse investigation. Administrative areas use strictly necessary session and security cookies.

Sampark Setu — account, profile and community records

Sampark Setu processes account and profile information such as the linked HSID user identifier, name, registered and verified phone number, email address, address and other profile fields, membership and role information, preferences, assigned work, support and deletion requests, and records the user deliberately creates in community, candidate, household, voter-outreach, directory, event, task and field-work features. Some approved directory fields can be published on an unauthenticated page; a verified phone number is published only after the separate phone-publication choice.

Sampark Setu — Android phonebook sync and selected contacts

On Android only, the optional full-phonebook flow uploads and retains the complete device address book after a prominent, versioned disclosure and Android Contacts permission. Depending on what exists on the device, this can include names, phone numbers, email addresses, company, job title, birthday, anniversary, notes, contact photos and other raw Android contact fields. The service retains encrypted full snapshots and VCF archives, raw contact records, a normalised matching copy and encrypted edited-or-deleted history. Exact phone comparisons against verified person-owned account or voter records are review candidates only, not proof of a relationship and never an authentication or authorisation fact. A narrower selected-contact flow retains only cards the user deliberately selects under its own disclosure. The iOS product does not request Contacts access or offer either flow.

Sampark Setu — location, outings and device sensors

When the user chooses a location-dependent action, Sampark Setu can process precise foreground location for field evidence, public-directory verification, household or place mapping and outing routes. Candidate base-departure reminders and an outing the user actively records can use background location after the relevant permission is granted. Outing records can contain route points, times, distance and, on Android, motion-derived step counts; iOS does not collect or transmit steps. Weather Automatic mode uses a time-zone city rather than GPS. A saved city and city-search choice can include place names and centre coordinates.

Sampark Setu — content, communications and activity

Feature content can include photos, videos, documents, arbitrary files selected for Help or Contact (including audio files), field evidence, messages and notifications, mailbox messages and attachments, public-directory material, game participants and moves, Prayer activity and optional private images, saved Panchang/Kundli information, birth details and prepared results. The app does not request microphone permission or record audio. Operational evidence can record account, session and role context; route and action; time; app state and screen; device, operating-system and locale details; IP address and user agent; network state; result, status and duration. A random installation identifier, notification token and device/app metadata are stored when needed for signed-in operation or push delivery. Notification records can include delivery, receipt, open and click events.

Sampark Setu — external feature recipients

HSID supplies the shared sign-in identity used by the app. Firebase Cloud Messaging or Apple Push Notification service receives the device token and delivery data required for notifications. Open-Meteo receives rounded weather coordinates, and Nominatim receives typed city-search queries. After separate versioned storage consent, IndiaJewellers receives and persistently stores a named Kundli or Gochar birth profile, exact birth date and time, birthplace name and coordinates, time zone and historical UTC offset, prepared result, account identity and bounded app/device details. When a user separately creates a recipient share, IndiaJewellers also receives and stores the recipient phone number and link record. The app then opens WhatsApp with that number and a prepared link/message; WhatsApp sends it only if the user continues and presses Send.

Publisher: Sampark Setu is published by ESSNCL PRIVATE LIMITED.

Other applications

Each other published application will disclose the specific data it collects and why. Depending on its documented features, this can include account details, content deliberately submitted by a user, device or diagnostic information, notification tokens, and information needed to provide a requested location or media feature. An application does not collect a category merely because it is mentioned here.

03How we use data

We use personal data to provide and secure the requested service, respond to enquiries and rights requests, maintain accounts, deliver features chosen by users, diagnose faults, prevent misuse, meet contractual duties and comply with law.

04Other organisations and service providers

We use service providers only where needed to host, secure, communicate, diagnose or operate a service. Sampark Setu's known feature recipients are identified above so that a provider transfer is not hidden behind a general label. A recipient's own service and retention terms can also apply; opening a link does not make ESSNCL responsible for that external service.

Where an application is operated for a client organisation, that organisation may decide why and how its operational records are processed. ESSNCL acts on its documented instructions and does not combine that information with another client’s records for its own purposes.

05Retention and deletion

We retain personal data only for as long as needed for the disclosed purpose, security, legal compliance or the applicable client instruction. Sampark Setu keeps operational, mailbox, activity, support, game, Prayer, directory and field-work records while the account, feature or assigned work requires them. The current service does not apply one automatic fixed deletion period to all of those records.

Android users can use the separate Delete synced phonebook control to turn off phonebook ingestion and request removal of the server snapshots, raw contacts, matching copies, encrypted archive and edited-or-deleted history. A failed removal remains pending and sync stays off until deletion is confirmed. Incomplete current-format uploads are retired after 24 hours without upload activity; phonebook edited-or-deleted history is limited to 180 days. This feature-specific control does not delete the whole account or data held by another provider.

An authenticated whole-account request in Sampark Setu immediately blocks the Setu account, ends its Setu sessions and disables push delivery. Before acceptance is confirmed, the service durably records a rollback-detecting deletion tombstone in an independent ledger outside the database failure domain, binds that proof to the request and marks it erasure_pending. On startup after a database restore, the service reconciles and replays the ledger to reassert the account block and session and push revocation. erasure_pending means Setu access has been revoked and the request awaits authorised retention review; it is not evidence that associated data has been erased or irreversibly de-identified. The current source has no automatic account-erasure worker. The minimum deletion tombstone, audit, security and proof records and organisational evidence may be retained under the disclosed purpose; a Help or Contact record whose retention basis is still under review keeps the request pending rather than being silently described as deleted. No fixed completion date is promised.

The public form creates a separate manual ESSNCL intake request and does not itself sign in to or immediately block an account. A Setu-local request does not delete a separate HSID identity, direct mailbox credentials, messages or archives, the ESSNCL intake record, or records held by IndiaJewellers, WhatsApp or another provider.

A Kundli recipient link expires after 14 days and can be revoked, but that does not prove deletion of IndiaJewellers' recipient-phone row. No verified IndiaJewellers retention period or Setu-to-IndiaJewellers whole-account deletion path is presently documented. Moving mailbox content to Trash, removing a public-directory item, resetting Prayer, or finishing or discarding a game likewise must not be read as proof that every underlying record or archive was erased.

Use Sampark Setu's Profile → My details → Delete my account route, or the public Account & Data Deletion page even if the app is no longer installed.

06Security

We use encryption in transit, access controls, authenticated administrative interfaces, limited privileges and security logging appropriate to the service. No system is perfectly secure, and we do not claim otherwise.

07Your choices and rights

Subject to applicable law, you may ask for access to relevant personal data, correction or updating, erasure, withdrawal of consent, and grievance redressal. We may need to verify your identity before acting.

Email sumeet.mehta@essncl.in or use our privacy choices form.

08Children

The ESSNCL corporate website is directed to organisations and adults. Any application intended for children will have age-appropriate disclosures, consent and store classifications before publication.

09Changes

We update this policy when our services or practices change and revise the date shown above. Material changes will be communicated through the affected service where appropriate.

10Contact and grievance officer