Retention Summary
Last updated: 12 April 2026
This page provides a practical summary of how ExpressCSV approaches retention. Exact periods can vary based on legal obligations, security needs, customer contracts, and incident response requirements.
General approach
ExpressCSV keeps personal data only for as long as needed to:
- provide the service
- secure and support the platform
- meet contractual obligations
- comply with tax, accounting, and legal requirements
Main categories
Account and workspace data
- Examples: user accounts, team membership, configuration, and authentication records
- Approach: retained while the account is active and for a limited period afterward where needed for security, support, dispute handling, or legal obligations
Billing and financial records
- Examples: subscription metadata, invoice records, payment status, and related accounting records
- Approach: retained for the periods required by tax, accounting, and financial reporting laws
Support records
- Examples: support conversations and support context
- Approach: retained as long as reasonably needed for customer support history, service quality, and legal protection
Product analytics and monitoring
- Examples: analytics events, error reports, traces, and diagnostic replay data
- Approach: retained in vendor tooling for limited operational and product-improvement purposes, subject to vendor retention settings and internal review
Importer operational records
- Examples: import-session events, workflow state, and delivery-related metadata
- Approach: retained for reliability, abuse prevention, billing, debugging, and service operations for a limited period appropriate to those purposes
Browser-side importer session persistence
- Examples: in-progress review data stored in IndexedDB when session saving is enabled by the embedding application
- Approach: stored in the browser environment on the user device until cleared, replaced, expired through product behavior, or removed via browser/site-data controls
Customer import data
- Examples: rows, headers, mapped fields, transformed values, and delivery payloads
- Approach: ExpressCSV is designed to process this data for the active import workflow rather than maintain it as a long-lived customer data warehouse
Deletion and return
Where ExpressCSV acts as a processor for customer import data, deletion and return are handled under the customer relationship and any applicable DPA or service terms.
Where ExpressCSV acts as a controller for its own account, billing, support, or analytics data, we delete or de-identify data when it is no longer needed, subject to legal and operational exceptions.
Questions
For retention questions or data-deletion requests, contact care@expresscsv.com or use the Contact page.