A clear view of how Billflow handles business data.

Businesses remain responsible for the customer information they choose to put into Billflow. Billflow uses that information to provide the invoicing, payment, collections and configured AI/admin features requested by the business.

Workspace owners can download a machine-readable export from Settings → Privacy & data. Requests concerning access, correction, restriction, deletion, objection or portability can also be recorded there for review.

Billflow does not need to store raw card details. Card and payment-account processing is handled by the connected payment provider. Billflow stores the payment and invoice status information needed to operate the service.

Automation is not treated as unrestricted authority. Billflow includes business-level AI controls, approval requirements and escalation paths. A customer saying that an invoice is paid does not, by itself, mark that invoice as paid; payment status is verified against Billflow payment records.

Every new accounting, CRM or communications integration is expected to follow these rules:

• request the minimum practical permissions and fields;
• keep credentials and refresh tokens server-side;
• scope every synced record to the authorised Billflow business;
• document what data moves, why it moves and which provider receives it;
• support disconnection and an appropriate deletion or retention workflow; and
• review processor terms and international-transfer safeguards before production use.

Billflow maintains an incident-response process covering containment, evidence preservation, risk assessment, customer notification and regulatory assessment. Security or privacy concerns can be reported to hello@billflowinvoicing.com.

Billflow relies on specialist providers for hosting/database services, payments and transactional email. See the current subprocessor list and our Data Processing Addendum for the contractual framework we use when Billflow acts as a processor.