Draft Data Rights and Account Deletion Procedure
DRAFT · INTERNAL COMPLIANCE REVIEW AND OWNER APPROVAL PENDING
Request-for-review route and required safeguards; no automatic deletion or legal fulfilment claim.
- Version
- fleet-data-rights-draft-2026-11-15-v2
- Prepared date
- 2026-11-15
- Effective date
- Not set — not published or approved
- Internal compliance review/owner approval
- Not recorded
This is review material for local development. No acceptance or production legal approval is available.
1. Record a request
A signed-in member can use the company support workflow to record an account access or data request for human review, including in the narrow permitted restricted-mode path. Provide only the minimum information needed; do not send passwords, authenticator secrets or full payment details.
This local route does not verify a legal requester, compile every personal-data category, remove an identity or fulfil an erasure/access request automatically. A verified external contact, authority/identity procedure and complaint route remain required for publication.
2. Review and response
The responsible controller/reviewer must establish the request and relevant company/resource scope, applicable role and lawful basis, any justified exceptions and the required response. The company’s operational records and Fleet’s own service/security activities may need separate handling.
Requests must not grant unrestricted access to other members or companies. Standard asset CSV is not a complete personal-data export. A support case reference or logout is not proof that account data has been deleted.
3. Proposed deletion safeguards
Before any destructive implementation, approve the retention/hold matrix and provider process; identify ongoing safety/work/billing/claim dependencies and affected document versions, offline copies, notifications, exports and backups. Define what may be deleted, what must be retained, and how direct identifiers can be minimised lawfully.
The final user flow must distinguish access removal, actual deletion/anonymisation, retained categories and unresolved provider outcomes. It must not display completed deletion for a suspension or an uncertain purge. No destructive account deletion is implemented or authorised by this draft.
Internal compliance review and owner approval — pending
The owner decision of 15 November 2026 replaces a blanket mandatory external solicitor sign-off stage with internal legal compliance review and owner approval. It does not approve this draft. AI assistance is not a qualified lawyer or legal certification. Specific high-risk issues or legally mandated professional or regulatory review must still be escalated.
Operator and ICO/VAT status, actual contact routes, legal/privacy duties, data flows, lawful bases, subprocessors, transfers, retention, cookie consent and commercial disclosures still require evidence and review as applicable. Owner attestation and engineering tests do not establish compliance. No effective date, approved acceptance, publication or deployment is authorised by this draft; deployment needs separate explicit owner approval.
Request human review
Use your company workspace’s private support request route. No destructive account/data action or signed DPA is executed by this draft.
Open company workspaceA verified external privacy/legal contact is still required for release.
Required evidence before approval
Draft content SHA-256 (not acceptance evidence): ffd311db686e8e03182a539b5588ec2543f6930aa26259315490d291cf3c075f