Your job, your data, your call
BuildFlow holds contracts, drawings, photographs of people's homes and the record of how a job was run. Here's how that's kept.
Access decided at the database
Every table has Row Level Security on it. Who can see a project, a document or a diary entry is a rule the database applies to every query — including ones that don't come through our interface. Hiding a button is not a security model.
Roles that are actually distinct
Owner, admin, employee, subcontractor and client are separate roles with separate rights. A client can't read your site diary or your internal messages, and that's enforced rather than assumed.
Files are private by default
Photos, drawings and certificates live in private storage. Nothing has a public URL. Access is a short-lived signed link issued to somebody the database has already agreed should have it.
An audit trail nobody can edit
Database triggers record who changed what and when, with the old and new values, on every table. The log is append-only at the database level — not editable by your team, and not by us.
Sessions handled properly
Authentication runs on Supabase Auth with server-side session verification on every request. Sign-in links and password resets are single-use and expire.
AI within the same walls
FlowAI runs every lookup and every change on your own session, so it inherits exactly your access and no more. It proposes changes rather than making them, and some actions aren't available to it at all.
Sharing is a decision, not a default
Bringing a client into a job shouldn't mean opening the books.
Clients see
- Their own project, and only their own
- Progress, stages and the milestones you share
- Photos of their job
- Documents you've marked visible
- The project thread and their own snags
Clients never see
- Costs, margins or anything financial
- The site diary — hours, workers, issues, deliveries
- Internal notes between your team
- Documents you haven't shared
- Any other project, client or company
What we don't claim
Are you certified to ISO 27001 or SOC 2?
Not today. We'd rather say so than imply otherwise with a badge. What we can describe precisely is above, and we're happy to walk a prospective customer through the actual access model.
Where is the data held?
In Supabase's managed Postgres, in a region chosen when the account is set up. Files sit in the same project's private storage. Get in touch if you have a specific residency requirement.
Can I get my data out?
Yes. Documents and photos download as the files you put in, and the handover pack gathers a project's record into a single PDF. Ask us if you want a full export of an account.
Does FlowAI train on my projects?
No. Project data is sent to the model to answer the question in front of it and nothing more. Turn FlowAI off and nothing leaves the database at all.
What happens if I stop paying?
Your data stays. Dropping to a smaller plan stops you adding more projects, clients or team members — it never deletes what's already there.
Found something?
If you believe you've found a security issue, email hello@example.com with enough detail to reproduce it. We'll come back to you, and we won't take issue with anyone reporting one in good faith.