Security and data

What your IT person and your insurer will ask

Plain answers about where client data lives, who can see it and what the AI sees.

Where data is kept

Hosted in the UK by us, or on your own servers if you prefer. Statements and documents are stored in encrypted object storage.

Each practice kept apart

Every record belongs to one practice's workspace, and every request is checked against it. Each client sees only their own data.

Roles

Partner, accountant, bookkeeper and client roles, each with only the access it needs. Read-only roles for reviewers.

Sign-in

Two-step sign-in with an emailed code, Google sign-in, and SAML single sign-on so staff use your Microsoft Entra ID, Okta or Google Workspace account.

Audit trail

Corrections, reviews and filings are recorded with who did them and when.

HMRC fraud-prevention headers

HMRC requires software to send details about the device and connection with each call. Daybook sends them on every MTD request.

Which AI model sees what

You choose: a local model on our servers or yours, so statements never leave that network, or a hosted model for speed. Rules and last year's choices are applied first, so the model only sees the lines they couldn't settle.

Leaving

Your data is yours. Export your clients' records when you need to.

Our ICO registration number will be shown in the footer once registration is complete.

For your IT team

For your IT team

Daybook runs on OpsAPI, a self-hosted, multi-tenant API platform (OpenResty, Lua and PostgreSQL) with tenant isolation, role-based access, SAML single sign-on and Prometheus metrics. The technical documentation and a separate technical demo are on opsapi.org.

opsapi.org · Technical demo · Multi-tenancy and roles

Next step

See it with your own clients in mind

Book a 30-minute call. We show the demo practice, answer your questions, and scope a pilot on your sample statements.

Brochures for each trade, and for landlords, are on the demos page.