Private local development · Not available for operational use · No live services connected
HOULVEK Fleet
Draft legal centre

Draft Retention and Legal Hold Schedule

Per-category review framework with no invented retention periods or destructive automation.

Version
fleet-retention-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. Required schedule fields

For each category approve the purpose, controller/processor role, lawful basis, trigger, retention period, hold conditions, erasure/anonymisation approach, backup expiry and accountable reviewer. The categories include identity/membership, checks, defects, repairs, maintenance, documents/versions, financial records, audit, offline device data, notifications, exports, support and backups.

All legal periods remain unresolved. HGV accounting examples, browser cookie lifetime, queue retry backoff and export availability TTL are not Fleet legal retention decisions.

2. Current local behaviour

Runtime protects original safety/evidence/history and held records from destructive writes. Document disposal is a review request rather than deletion. Expired access does not automatically erase data. Local recovery backups are private synthetic artifacts and must not be uploaded with source.

The session cookie has an eight-hour access lifetime and CSV download availability is one hour after generation. Underlying audit/session/export records and bytes are not automatically erased at those boundaries. Offline records are scoped and cleared on supported actor/logout flows, with browser/device limitations still open.

3. Holds, descendants and disposal

A final policy must define authorised typed holds and all required descendants/evidence, review/release conditions, disposal verification and legal/accounting exceptions. It must distinguish retained facts from unnecessary direct identifiers without destroying required evidence.

No retention worker, account purge or backup expiry is enabled from this draft. A future approved disposal action must recheck holds and authority at execution, report partial/uncertain outcomes honestly and avoid cross-company loss.

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.

Required evidence before approval

Draft content SHA-256 (not acceptance evidence): b76e1dba56b346d3e6085acd6c844b1d82e547afe9bffec128b01f8d798f1517