Account and Data Deletion

DutyStack does not yet have a verified self-service personal-account deletion control in the mobile or web application. This is a launch blocker that must be resolved before app-store submission.

For now, a user can open Settings, choose Help & legal, then open Account & data deletion and contact support from the public page. If the user cannot sign in, they can use the public support address below. Support will verify identity and the scope of the request before action is taken.

Deleting a login ends that person's ability to sign in. It does not automatically erase organisation-owned inspections, attendance, signatures, safety or compliance records that the organisation may need to retain as controller.

An organisation owner or authorised administrator may revoke a person's organisation access. Access should be removed promptly when it is no longer required.

Historical organisation-owned records may remain where needed for audit integrity, safety, contractual or legal purposes. Removing access must not silently destroy the organisation's evidence trail.

The export is strongly recommended but the current interface permits an owner to continue without waiting for it. Owners should not do so unless they have confirmed that no export is required.

Limited information may remain where required for billing, fraud prevention, dispute management, legal obligations or a legal hold.

1. The organisation owner opens web Settings, then Organisation.
2. The owner requests a complete organisation data export.
3. DutyStack prepares the export pack. The owner downloads and reviews it when it is ready.
4. The owner starts Delete organisation and confirms the organisation name.
5. DutyStack locks normal access immediately and marks the organisation pending deletion.
6. The owner may cancel during the 30-day pending-deletion period. Permanent purge is scheduled after that period.

Contact support from the public address below. Include the email address used for DutyStack, the organisation name if known and whether the request concerns a login, an organisation membership or the entire organisation. Do not send passwords, authentication codes, unnecessary identity documents or confidential records by email.