Privacy notice

Information handled

• Account and access details such as name, email address, sign-in/session data, authenticator settings, and the scopes and audit history for service credentials.
• Bookkeeping records that an owner or an authorized agent enters or imports, including transaction dates, amounts, currencies, account references, merchant or payout details, ledger activity, notes, and supporting evidence.
• Information needed to connect a provider. Plaid handles bank authorization. Bean Tally requests Transactions data only, does not ask for a bank password in its own forms, and does not initiate payments or transfers.
• Technical and usage signals such as device/browser details, network information, page paths, and performance or error diagnostics, when the corresponding service is configured.

Bean Tally can receive requests from a person or from an agent using an owner-scoped service credential. An external agent provider is a separate service; its handling of information sent to it is governed by its own terms.

How information is used and shared

We use this information to authenticate owners, operate bookkeeping and reconciliation features, provide reports, sync owner-authorized provider data, maintain an audit trail, protect the service, and deliver account emails.

Bean Tally runs on Vercel for web hosting and Convex for application data, authentication, and backend functions. Resend delivers production account emails. Plaid handles owner-authorized bank connections. When an owner configures them, Xero, Shopify Payments, and statement-file imports can supply additional bookkeeping records. These paths are not active unless configured and authorized.

The website loads a Google Tag Manager container on every page. Its configuration may send website usage data to Google Analytics. The production homepage also sends page-path-only events to a Kaizen-managed Plausible service. That request omits query strings, fragments, cookies, and referrers. PostHog, Vercel Analytics/Speed Insights, and Sentry can receive pageview, performance, or scrubbed error information when deployment settings enable them.

Security

Bean Tally uses authenticated access checks and scoped service credentials. We encrypt provider access tokens with AES-GCM before storage. Convex describes its hosted database and file storage as encrypted at rest and in transit.

Retention, deletion, and provider disconnection

Bean Tally retains bookkeeping, transaction, and tax-supporting records for seven years after the relevant fiscal year ends. Records stay longer when law, property-basis rules, contracts, audits, litigation, or a legal hold requires it. Seven years is a company default, not a guarantee that it satisfies every legal obligation. The policy requires manual review of the record type, any holds, and backup expiry before disposal. It does not authorize automatic deletion. Removing an account marks the application user as removed but does not erase financial or audit history.

Daily hosted snapshots include file storage and are configured for seven-day retention. This backup period is separate from the record-retention policy. A record in a snapshot may remain there until that snapshot expires.

To stop a provider sync, open Workspace, then Sources, and choose Disconnect for the connection. This disables future sync and clears the provider token held by Bean Tally, but it does not delete previously imported records or call Plaid to revoke the connection. Contact us if you also want help with a provider-side revocation.

For access, correction, or deletion requests, email paul@kaizenbrands.com. We review requests against accounting-record obligations and applicable legal holds. We do not promise to delete financial records that must be retained.