TreaxuresPilot contact
Legal

Data Deletion Request

Draft — pending legal review. This document has not yet been reviewed by Indian-jurisdiction counsel and is not in effect. Content is subject to change before publication.

Data Deletion and Export

Status: Draft — not effective

Last reviewed for product accuracy: 2026-07-19 Operator: Treaxures, operated by ESPR Creative Lab Private Limited, Aizawl, Mizoram, India

1. Request paths

A signed-in user can open Profile → Settings → Privacy to request account deletion or data export. If account access is unavailable, contact privacy@treaxures.com from the account email where possible.

Assisted requests require proportionate identity verification. Support must not ask for a password, UPI PIN, full payment credential, or unnecessary identity document. The approved workflow records request status, scope, owner, reason, and an audit history.

The response and completion periods shown to users must come from the counsel-approved policy and request type, not from a hardcoded generic promise.

2. Data scheduled for deletion or de-identification

Subject to the approved retention and legal-hold rules, account deletion covers:

  • authentication links, contact details, device/push tokens, preferences, and private profile fields;
  • precise field progress, private observations, private Passport visibility, and non-retained completion details;
  • drafts, unpublished content, private workspace submissions, and media the requester is authorised to remove;
  • posts, comments, reactions, follows, blocks, notification preferences, reports, and eligible reviews, with public attribution removed as required;
  • optional uploaded photos, audio, video, transcripts, and associated metadata;
  • search/recommendation history and user-linked analytics not required under an approved exception;
  • booking participant details and affiliate consent identifiers when their purpose and approved retention period end.

Deletion of one account must not silently delete another person's rights, transaction evidence, organisation records, or a released work that has independent contributors and a lawful continuing basis. Those cases require a scoped review, de-identification or credit decision, and a user-facing explanation.

3. Records that may need limited retention

The final retention matrix must state the exact period, lawful purpose, access scope, and deletion/anonymisation action for categories such as:

  • orders, receipts, refunds, disputes, tax/accounting entries, settlements, and payouts;
  • fraud, abuse, security, moderation, grievance, and legal-hold evidence;
  • contributor credit, rights, consent, release, source, and correction history;
  • booking or redemption fulfilment evidence needed by another party;
  • immutable audit records needed to prove an approval or reversal;
  • encrypted backups and disaster-recovery copies.

Retained records must be minimised, removed from public display where required, and inaccessible for unrelated product or marketing use. Earlier generic promises of a universal seven-year period or fixed backup window have been removed pending counsel, accountant, and infrastructure verification.

4. Impact Passport and estimates

Private Passport records should be deleted when no approved exception applies. A transaction-linked record may instead need de-identification or a visible reversal while the underlying financial ledger is retained. Environmental estimates do not survive as a personal status claim after their source record is removed.

5. Published content and contributor credit

Released guides and programmes can contain work and rights belonging to several contributors or an organisation. An account-deletion request therefore triggers a rights/credit review rather than automatic reassignment to a fictional or generic author. Withdrawal, takedown, continued licence, public credit, and historical audit treatment follow the applicable approved agreement.

6. Export

An export should include the requester's account/profile data, private Passport records, completion and visibility history, posts/reviews, reports, relevant workspace contributions, consent history, and transaction summaries within the requester's authorised scope. Private data belonging to other participants, partners, reviewers, or staff must be excluded.

The export is generated by a bounded, audited job and delivered through an authenticated, expiring channel. The final notice must state the approved format, availability period, and response time.

7. Cancelling a pending request

If the approved workflow includes a grace period, cancellation requires re-authentication and is recorded in the request audit. It cannot restore data that has already been lawfully and irreversibly deleted.

8. Contact and unresolved release gates

Privacy and deletion: privacy@treaxures.com

Data-protection contact: dpo@treaxures.com General support: support@treaxures.com

This page cannot become effective until the privacy owner has tested deletion, export, legal hold, de-identification, backup expiry, failed-job recovery, and restoration against the production retention matrix and counsel has approved the wording.