How Billoz protects account boundaries and business records

Billoz uses signed sessions, per-user database queries and protected upload routes to keep one account from reading another account's records.

Connection and authentication

Production traffic is redirected to HTTPS. Passwords use scrypt hashing and browser sessions use signed, HTTP-only cookies.

Authorisation boundaries

Private API, uploads, admin and Google routes require authentication; admin routes also require an admin role.

Receipts and exports

Receipt files are stored under owned upload paths and served through authentication. Users can export their own records.

Account deletion and backups

The deletion workflow removes account rows and owned files and attempts to revoke connected services. Operational backups may persist temporarily under the applicable retention process.

Google Drive scope

Drive tokens belong to one user and are used to upload selected invoice PDFs and receipt images to that user's connected Drive.

Security contact

Report a security concern through the Billoz contact page. Do not include passwords or full payment details.