Public review draft, pending legal and technical approval
Data deletion and correction · review draft
Guidance on erasure, corrections and access. Account closure must be distinguished from lawfully retained workplace evidence.
Reviewed 2026-11-06 · No approved effective date
01. Which data can be deleted?
Enquiries, accounts, logos, worker profiles, TBM, hours, location, media and logs have different legal treatment. Data must first be classified as personal, operational or legally retained.
02. How to make a request
Requests for access, correction or deletion may be sent using the listed company contact route. Identity-verification and handling procedures require operational confirmation. This page does not claim an automated erase-account button exists.
03. How requests are assessed
The controller, identity, third-party rights, preservation duties and active disputes must be checked. If an exemption prevents deletion, the lawful reason and available routes must be communicated.
04. Append-only history and privacy rights
An append-only correction history does not authorize indefinite retention of identifiable data. Data minimization, separation, access restriction and lawful destruction may be required. Technical implementation is still being verified.
05. Backups and providers
Deletion from the primary database does not prove removal from backups, indexes, uploaded files or processors. Actual expiry schedules and mechanisms must be documented.
06. Account closure versus business records
Closing an individual account differs from retention of business and site records. Access may be revoked while legally retained TBM or work history remains. Scope and periods must be defined separately.
07. Outcome and review
Requests should conclude with a statement of what was corrected or erased, what remained under lawful retention and how to seek further review. Verified contacts, deadlines and procedures are prerequisites to final publication.