Account Deletion

1. Current request path and status

Use Contact and specify ‘account deletion request’. Opening the contact page does not submit, approve or complete deletion. Contact prepares a mailto draft only; you must send it yourself, and receipt/delivery has not been verified. No account-deletion job, authenticated ownership check, status tracker, retry action or success receipt is wired. Do not provide passwords or tenant documents.

Refreshing clears operational demo state; closing a tab clears tab preferences in normal browser use. These actions do not delete authentication accounts, editorial records, hosting logs, external enquiries or saved/downloaded files. There were no users at the last audit, but this is not evidence of a functioning deletion service.

2. Confirm impact and ownership before erasure

The future request must use an authenticated session, proportionate reauthentication/verification, a scope preview and explicit confirmation. Identify properties owned/managed, memberships, documents, repair/inspection records, invitations, support records and personal information. Explain what can be erased, transferred, redacted or retained and why.

A landlord must not erase tenant-owned documents or shared legal records simply because they created a property. Check other data subjects’ rights, contractual needs, statutory obligations, disputes and legal holds. Tenants leaving a property must not erase another person’s independent records. Transfer property responsibility safely or revoke only the requester’s membership where appropriate. Outstanding bills or disputes do not automatically extinguish data rights; justify any lawful retention separately.

3. Required secure deletion workflow — not implemented

After validated authorization: revoke sessions and active tokens, prevent new writes, invalidate invites/signed access, remove permitted private objects and related records, handle owner transfer and remaining memberships, and retain only a minimal lawful audit record. Storage cleanup and record changes need consistent server-side handling with recoverable failure states; never treat a partial job as completed.

Provide requested → identity check → scope/legal review → processing → completed or partially retained/error states, explanations and a secure manual escalation/retry route. Audit privileged actions without copying document contents. Backups may retain data until verified provider expiry; legal holds and necessary security/accounting records need stated reasons and actual periods. Backup durations, restoration controls and notification procedures remain unconfirmed.

4. Timing and alternative route

Erasure is subject to applicable rights-response rules, ordinarily one month with lawful extensions/exceptions where applicable; it is not an instantaneous purge guarantee. The operator must acknowledge requests, verify identity proportionately, explain refusals/retention and provide complaint rights. There is no configured deletion response SLA. Use Account & Data Rights and the ICO complaint route for further information.