Security & data handling
Your clients’ financial data, protected at every layer
BizFlow Financial holds imported invoice and expense records, which is sensitive business data. This page describes the controls that are actually enforced — encryption, access control, hosting and privacy — and states the limits honestly rather than hiding behind a badge.
- 256-bit TLS encryption
- Role-based access control
- Secure cloud hosting
- No data selling, no model training
The four controls that matter
Encryption, access control, hosting and privacy are the pillars a bookkeeping practice asks about first. Here is what each one means in this product.
256-bit data encryption
Every connection to BizFlow Financial is served over HTTPS with 256-bit TLS, and imported client files never sit in a public bucket.
- There is no plain-HTTP endpoint: certificates are issued and renewed by the hosting platform.
- Import files are held in private file storage, and downloads are served through short-lived signed links.
- Records live in the app’s managed database; the app itself stores no card numbers and no bank credentials.
Role-based access control
Two workspace roles plus a per-client grant decide who sees which client books, and the check happens on the server.
- Workspace admins manage the workspace, teammates and grants; finance staff see the clients they were granted.
- Every client company is granted individually and a grant can be revoked at any time.
- Access is re-checked on the backend for every request, so a changed id in the address bar reveals nothing.
Secure cloud hosting
The app runs on managed cloud infrastructure with its own database and private file store, on an isolated application instance.
- There are no servers for you to patch: the runtime, database and storage are managed for this app.
- OAuth tokens for Google Calendar, Drive and Slack live in the backend and are never sent to the browser.
- Secrets are held server-side, and no integration credential is ever exposed to a visitor or a teammate.
Data privacy protection
Client data is used to run the features you switched on, and for nothing else.
- We do not sell your data, share it with advertisers, or use imported records to train models.
- No advertising or third-party tracking scripts run on the workspace screens.
- A client company, or all records imported for it, can be deleted by an admin and the removal is recorded.
How access is enforced on every request
These controls are part of the application itself, not settings you have to switch on. Each one is checked on the server before any client record leaves the database.
Authorization is enforced on the server
Every dashboard request resolves your workspace and your access to the client company on the backend before any record is returned. Changing an id in the address bar or in a request cannot reveal another company.
Access is granted per client company
A teammate sees only the client companies an admin has granted them. Deactivating a member stops their access immediately, on their next request.
Client companies are separated
Records are stored against their workspace and client company, and the portfolio, calendar, reports and exports are all built from the companies you are allowed to see.
Imported financial records stay read-only
BizFlow never edits an imported invoice or expense. The only changes it writes are your team’s own annotations: review status, expense approval, and follow-up notes.
Every figure traces back to its source
Each record keeps the import job, source system, source filename and last-import time, and balances that have not been verified are held out of outstanding and overdue totals.
Card details never reach BizFlow
Billing is handled by Stripe when a card is used. BizFlow stores the subscription status Stripe reports and nothing about your card.
Connected accounts are used server-side only
Google Calendar, Google Drive and Slack are connected with OAuth. Their tokens stay in the backend and are never exposed to the browser.
A history of what changed, and who changed it
Review decisions, approvals, reassignments and resolutions are written to the client company’s history with the teammate and time attached.
Data privacy, in plain terms
Financial oversight only works if you are comfortable putting real client books in it, so here is exactly what is stored, who can reach it, and how it leaves.
Your data, and what happens to it
What we hold
Your name, work email and workspace role; the client companies you set up; the invoice and expense rows you import; the annotations your team adds, such as review status, approvals and follow-up notes.
What we never do with it
No selling, no sharing with advertisers, no use of imported records to train models. Tracking on the workspace screens is limited to product usage, with no advertising pixels or third-party tags.
Who inside BizFlow can see it
Inside the app, only the teammates your admins grant access to. The administrator account that owns this application can reach its database, so ask for a written access agreement if your own policy requires one.
How long we keep it
Imported records stay until an admin deletes them or asks us to remove them. There is no automatic retention schedule inside the app yet, and nothing disappears without a recorded action.
Connected services
Nothing is connected until an admin connects it, and each connection sends only what that feature needs.
Google Calendar
Invoice due dates BizFlow writes as events. Revocable from the workspace settings at any time.
Google Drive
Invoice PDF archiving, written only into the folder an admin selects.
Slack
Overdue, due-soon and assignment alerts posted to the channel an admin chooses.
Stripe
Subscription billing only. Stripe never receives the client records you import.
Where the controls stop
A security page is only worth reading if it is specific. These are the limits of what is enforced today, so nothing here has to be taken on trust.
Not claimed
- No SOC 2 certification, ISO certification or audit report has been issued for BizFlow Financial.
- No uptime guarantee or service level agreement is published, and none should be assumed from any page.
- Encryption at rest, backups and platform availability are provided by the hosting platform rather than configured in this app, and no independent report on them is published here.
- BizFlow Financial is not a bank or a payment processor, and it does not move money or collect client payments.
- Data-accuracy statements on this site describe how imported records are traced and checked, not a guarantee that a client’s source data is correct.
Open items
- No independent security audit, penetration test or certification report has been published for BizFlow Financial.
- There is no automatic retention or deletion schedule inside the app: imported records stay until they are deleted by an admin or on request.
- Google Calendar, Google Drive and Slack connections are granted by an admin and can be revoked from the workspace settings at any time.
Have a security questionnaire to complete?
Send it over. We will answer it in writing, and we will tell you plainly if a control you need is not in place yet. The full privacy policy and terms are linked below.