Legal and trust
Everything here is either true today or clearly marked as outstanding.
We would rather show you an unfinished trust centre than a complete-looking one built from template text and certifications we do not hold.
Published
These pages describe what is in place now, including the gaps.
- Security overviewThe controls actually in place: per-user sign-in, role and branch-scoped access enforced at the database, private evidence files, audit history, server-side credentials, and no certification claims.
- Accessibility statementThe accessibility features built into BranchFlow, the known gaps, and why we make no formal conformance claim yet.
- Service statusThere is no automated status page yet. This explains how availability issues are communicated today and what commitments we do not make.
Outstanding
How BranchFlow handles your data, access and service. Terms take effect on signing of your agreement.
What we will never put on these pages
- A certification, audit or compliance badge we do not hold.
- An uptime figure or support response time that is not contractually agreed.
- Template legal text borrowed from another company and presented as ours.
- A subprocessor or hosting claim we have not confirmed in writing.
How access and records are handled
Each organisation's records are separated in the database, and people only see the branches they are assigned to. Status changes, approvals, rejections and verifications are recorded with who did them and when. We do not claim any external certification or audit at this stage; if you need a formal security review, ask us and we will tell you exactly what exists today.