ESSNCL

Privacy choices

Account & Data Deletion

Use this public page to request deletion of an account or selected personal data associated with an application published by ESSNCL. You do not need the application installed or an active sign-in.

01Before you request

If the application offers deletion in its account settings, that route may be faster. You may always use this page instead. A request concerning an application operated for another organisation may be securely referred to that organisation, and we will tell you when this happens.

02Send a request

Provide at least one account identifier. We will use it only to find the relevant records, verify your authority and respond.

Account identifier — at least one required

Enter the email address or phone number attached to the account. You do not need both.

We may contact you to verify the request. Do not include passwords, one-time codes or government identification documents.

03What happens next

  1. ReceiptWe create a traceable manual-intake request and send it to the ESSNCL team.
  2. VerificationWe verify that the requester is authorised to control the account or data.
  3. ScopeWe identify the relevant application records, other service owners and any limited lawful retention before an erasure action is approved.
  4. OutcomeWe report what was completed, what remains pending and what must be retained. Submission alone is not a promise that deletion has already occurred or will finish on a fixed date.

04What the request covers

A whole-account request asks for the application account, profile, preferences, content associated solely with that account, active device tokens and other data identified in that application's disclosures to be erased or irreversibly anonymised where eligible. A selected-data request is limited to the records described by the requester.

Sampark Setu's authenticated in-app route immediately blocks the local Setu account, ends its Setu sessions and disables push delivery. Before acceptance is confirmed, it 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, Sampark Setu 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, not that associated data has been erased. The current source has no automatic account-erasure worker. This public form records a separate manual ESSNCL intake request and does not itself perform that block, create a Setu ledger tombstone or mark a Setu account erasure_pending.

05What may be retained

We may retain the minimum deletion tombstone, audit, security and proof records and organisational evidence needed for the disclosed purpose, legal compliance, fraud prevention or dispute handling. A Help or Contact record whose retention basis is still under review keeps the Setu request pending rather than being silently described as deleted. The current service does not automatically complete permanent erasure; no fixed completion date is promised.

06Shared identities and other providers

A Sampark Setu-local deletion request does not delete a separate HSID identity, direct mailbox credentials, messages or archives, this ESSNCL intake record, or records held by IndiaJewellers, WhatsApp or another provider. If you want a shared identity or provider-held record deleted, say so in the details and we will explain the separate route and effect before proceeding.