Processed in transit
Supported API request and response bodies can contain invoices, payments, customer and supplier records, inventory values, and related accounting data. They are forwarded between the calling application and your local connector.
Accounting data handling
Accounting records pass through AcctBridge. They are not kept in our hosted application database.
This page explains the boundary precisely. AcctBridge does not claim that it stores no customer data. It separates accounting request and response contents from the service data required to operate your account and connection.
Not persisted as accounting records
AcctBridge does not persist those accounting request or response bodies in its hosted application database or API usage logs. Temporary network and memory processing still occurs while a request is being forwarded.
Service data is retained
AcctBridge retains account, subscription, connection, request metadata, and support records needed to provision, operate, secure, diagnose, and support the Service.
What AcctBridge keeps
The records needed to run the service.
These categories are different from the accounting document contents that pass through the gateway.
Account and subscription
Name, company, business email, selected accounting product, plan, usage totals, and billing-provider references needed to manage the account.
Connection and setup
Tenant and connection identifiers, tunnel and connector configuration, connection status, and setup credentials needed to provision and operate the connection.
API request metadata
Accounting brand, method, endpoint path without query values, timestamp, status, latency, byte counts, error category, request ID, tenant ID, and API key ID — not the request or response body.
Contact and support
The details and message you submit when asking about a project or requesting support, together with the records needed to manage the response.
Data flow
Where the request goes.
- 1. Calling software sends a supported API request to AcctBridge.
- 2. Hosted gateway authenticates and routes it through the outbound tunnel.
- 3. Local connector handles the supported operation against SQL Accounting or AutoCount.
- 4. Response returns through the same path to the calling software.
Retention
How long service records are kept.
Raw API usage events: normally 30 days by default. They contain technical request metadata, not accounting request or response bodies.
Daily usage aggregates: retained for account reporting and service analysis. They contain counts, status classes, latency totals, and byte totals, not accounting contents.
Account, configuration, billing references, and support records: retained while needed to provide the service and for security, support, disputes, deletion processing, or applicable obligations.
Questions about your data?
Contact privacy@acctbridge.com before onboarding if you need to review a specific data flow, retention requirement, or connection setup. Do not send passwords, API keys, database credentials, or customer financial records by email or through the contact form.