A clear view of how Avriloq handles business data.

Avriloq requires authenticated access to private workspaces. Customer, invoice, payment, automation and integration records are intended to remain scoped to the authorised business. Database row-level security and server-side ownership checks are used where applicable; privileged server operations are not exposed as general browser credentials.

Production Avriloq and supported OAuth callback endpoints use HTTPS/TLS. Hosting, database, authentication, platform availability and backup controls are also provided in part by contracted infrastructure providers. Those inherited controls remain the provider's controls and are not presented as Avriloq's own independent certification.

Accounting, CRM and payment integrations are expected to follow these rules:

• request only the practical provider scopes and data needed for the enabled feature;
• keep OAuth client secrets, access tokens and refresh tokens server-side;
• encrypt supported long-lived integration credentials before database storage;
• validate OAuth state and callback inputs before completing a connection;
• scope imported records to the authorised Avriloq business;
• provide a disconnect path and remove local credentials when access is revoked; and
• review provider legal/security terms before enabling production customer data.

QuickBooks production access is separately gated in Avriloq configuration so a development or sandbox integration is not automatically treated as approved for live accounting data.

Avriloq is not designed to store raw card numbers or card security codes. Card processing is handled by the relevant payment provider. Avriloq stores only the payment-provider identifiers and invoice/payment status information needed for the configured workflow. A connected business's invoice receipts are processed through that business's own connected payment-provider account; Avriloq subscription billing is a separate flow.

Transactional invoice and reminder email credentials are kept server-side. Delivery records are used so Avriloq can track whether a provider accepted a send and avoid intentionally marking an email as sent before provider acceptance. Automation can be paused and is designed to stop or change behaviour when an invoice is settled or the configured workflow requires review.

AI and automation are not treated as unrestricted authority. Avriloq includes configurable controls, approval requirements and escalation paths for supported workflows. A customer saying an invoice is paid does not itself establish payment status. QuickBooks and Xero API data is not used to train or fine-tune general-purpose AI or machine-learning models.

Avriloq records selected security, integration and operational events to support investigation and accountability. Avriloq maintains an incident-response process covering containment, evidence preservation, risk assessment, remediation, customer notification and regulatory assessment where required. Security or privacy concerns can be reported to hello@billflowinvoicing.com.

Before a provider is relied on for material production Customer Personal Data, Avriloq reviews the service purpose, required data, available security/privacy documentation, contractual terms and relevant international-transfer safeguards. See Service providers & integrations and the Data Processing Addendum for the current contractual framework.

Businesses remain responsible for the customer information they choose to put into Avriloq. Avriloq uses that information to provide the invoicing, payment, collections and configured administration features requested by the business. Workspace privacy/export functionality is intended to support access, correction, deletion and portability workflows, subject to legal retention and the Customer's role as controller.