ShifaTH guide

Account closure and platform-controlled erasure

Closing an account and erasing data are different processes. Neither gives ShifaTH control over independent Provider systems.

01

Closure stops account activity

A verified closure request blocks ordinary new activity. You retain restricted access to closure status, blockers, permitted unresolved matters, export status and support while closure is pending. A closed account cannot be used normally.

02

Some matters must be resolved

Ownership or management conflicts, pending claims or merges, administrator responsibilities or scoped holds can block closure. An active request, appointment or historical visit alone does not. Closure can be cancelled before irreversible erasure begins.

03

Erasure follows an authorized plan

Eligible owners or primary managers can request profile erasure under the applicable rules; a delegate cannot erase the whole profile. Pending deletion blocks new profile requests, uploads and Provider deliveries. Erasure completes only after platform-controlled targets finish processing.

04

Some history and external records differ

A minimized record may remain for shared-history integrity, audit or unresolved matters under the approved plan. Closure does not automatically delete shared conversations or cancel Provider appointments. Independent Provider-held copies remain outside platform erasure.