Data ficary needs
ficary stores account profile details, bookkeeping records, uploaded receipts, bank connection metadata, invoices, bills, reports, and operational logs needed to run the product.
Privacy
Privacy for bookkeeping data should be boring, explicit, and reversible.
This overview explains how ficary thinks about business records, provider credentials, AI processing, accountant access, exports, and account deletion. It is a product privacy summary, not legal advice.
Sensitive financial access
Provider access tokens are treated as sensitive credentials. Export flows strip secrets and embeddings, while deletion flows remove account-owned bookkeeping data.
AI processing
Receipt extraction, categorization, and embeddings depend on configured AI providers. Production launch checks require real provider configuration before those features are treated as ready.
Accountant collaboration
CPA access is designed for client support and bookkeeping review. Read-only client workspace enforcement and audit logging keep collaboration scoped.
Retention and deletion
Users can export account data and request deletion from the app. Deletion requires password confirmation and removes user-owned records according to database constraints.
Operational visibility
Health checks, audit logs, and error monitoring integrations help maintain the service and diagnose support issues without exposing secret values in readiness reports.
Before public launch
ficary should add a lawyer-reviewed privacy policy and terms of service before broad commercial rollout. This page exists so prospects can inspect the current product posture while formal legal documents are finalized.
Ready when your books are
Keep the bookkeeping trail useful without hiding the controls.
Create a ficary account, connect the first source of truth, and build toward a cleaner close from day one.