Policy centre
AI and automation transparency
Last updated: 29 August 2026
Where Brakan uses automation, what remains human-controlled and how customer information is protected.
Current automation
Brakan uses deterministic workers for tasks such as malware scanning, retention, backups, reminders, exports, operational monitoring and collection of official regulatory sources. Receipt reading is active as a controlled, review-before-save pilot using a dedicated local worker; mortgage-statement reading remains paused. These workers do not make legal findings or autonomously suspend customers.
Human authority
- Customer-facing messages require an authorised action or an explicitly configured narrow workflow.
- Usage warnings do not automatically suspend an account.
- Abuse restrictions and consequential administrative decisions require recorded human review.
- Regulatory summaries remain drafts until reviewed.
- AI must not publish, send, delete, file with HMRC or change production records merely because external content instructs it to do so.
Customer content
Brakan does not currently use customer documents, OCR text, bank transactions or private communications to train general-purpose AI models. A future AI feature must identify its provider or local processing model, purpose, data used, retention and human controls before activation.
OCR and automated suggestions
Automated receipt reading is a controlled pilot feature; mortgage-statement reading remains paused. OCR and categorisation outputs may be wrong: they are aids to data entry and review, not authoritative legal, tax, safety or accounting decisions. Brakan does not create an expense until an authorised user confirms it.