Data retention & export
Honest limits: soft-delete in-product; export and deletion via support.
Last updated 2026-09-01
What it is
Application keeps Business operational data for as long as the Business and subscription relationship require, subject to the Privacy Policy. These docs describe product behavior: what you can do in the UI/API today, and what requires a support request.
Soft-delete
Many Business resources (catalog, parties, invoices, expenses, and similar) use soft-delete: delete removes them from active lists but does not guarantee immediate hard erasure from storage. Soft-deleted rows may still exist for integrity, audit, or recovery until operator processes apply.
Practical effect
- Deleted items disappear from normal list/detail workflows
- Integrations should not assume hard delete or GDPR erasure from a single DELETE call
- Ask support if you need confirmation of erasure timelines
Export & account deletion
There is no in-product account self-delete flow and no documented CSV bulk export API for Business data. To exercise access, export, correction, or deletion rights, contact support and describe the Business, user email, and request type.
- Use Contact or Support & contact
- Include enough identifiers for us to locate the correct tenancy
- We respond within the timeframes described in the Privacy Policy where applicable
Who can access
Soft-delete in modules follows your role permissions. Rights requests (export / erasure) should come from an authorized Business contact or the data subject as described in the Privacy Policy.
Constraints
- Do not rely on marketing claims of one-click delete/export unless the button exists in your build
- Billing records retained for Stripe/legal obligations may outlive soft-deleted CRM rows
- Backups and logs follow operator retention — confirm with support/privacy if needed