Draft Provider and Transfer Register
DRAFT · INTERNAL COMPLIANCE REVIEW AND OWNER APPROVAL PENDING
Intended vendors are distinguished from the actual local implementation and unverified contractual roles.
- Version
- fleet-subprocessors-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. Current implementation
The Fleet application currently uses local PostgreSQL, local private files, synthetic identity and a no-send email adapter. No hosted customer-data environment or real email/payment integration is connected. This application inventory is not the full contractual inventory of a future deployment.
The processing role, contract, region, subprocessor chain, transfer mechanism, security evidence, retention/deletion and last reviewer must be recorded for each actual service before real-data activation.
2. Selected and intended providers
Resend is the owner-selected intended transactional email vendor; current Fleet delivery is a deterministic no-send simulation. Stripe is the selected intended subscription vendor; live billing is not connected. Their activity-specific processor/controller roles, contracts, locations and operating evidence remain open.
Supabase/PostgreSQL and Vercel are the approved technical direction for later hosted work, not evidence of account/project activation or verified hosted protection. No HERE, Google Maps, HGV marketplace analytics, Apple native service or AI processor is added to Fleet by reference to HGV.
3. Review and change control
Before any provider receives production information, record the data/purpose, authorised recipient/service scope, contract and privacy position, security/secret handling, locations/transfers, cost limits and rollback. Do not publish a provider as an approved subprocessor solely because a package or intended architecture names it.
The final register, customer change notice process and contact route require privacy/owner review. No DPA/region/UK-only processing or vendor certification is asserted here.
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): 4f6a238d65cd2795576e9d1cced1b649896d3955b9dd50bcf4858728cd76ac0b