Document owner: Proofey Information Security / Compliance
Effective date: March 12, 2026
Last reviewed: March 12, 2026
Next review date: March 12, 2027
Version: 1.0
This policy defines how Proofey retains and disposes of personal data and sensitive information, in support of our Privacy Policy and compliance with GDPR, CCPA/CPRA, and other applicable regulations.
This Data Retention and Disposal Policy defines how Proofey ("we," "us," or "our") retains and disposes of personal data and other sensitive information. It ensures that we:
This policy supports our Privacy Policy and is intended for use by personnel responsible for data handling, development, and compliance.
This policy applies to:
| Term | Definition |
|---|---|
| Personal data | Any information relating to an identified or identifiable natural person (e.g., account details, email, financial data, receipts). |
| Retention period | The length of time we keep data before it is deleted or anonymized. |
| Disposal | Secure deletion, anonymization, or destruction of data so it can no longer be used to identify an individual (except where we are permitted or required to retain it). |
| Active account | A user account that has not been deleted and is in good standing. |
| Account deletion | User-initiated or process-driven removal of an account and associated data in accordance with this policy. |
We retain personal data only:
| Data category | Retention period | Notes |
|---|---|---|
| Account and profile data (e.g., email, name, profile information) | Duration of active account | Deleted or anonymized upon account deletion. |
| Financial / Plaid-related data (e.g., linked account metadata, transactions, plaid_items, plaid_accounts) | Duration of active account | Stored only while the user maintains linked accounts and an active account. Deleted as part of account deletion. |
| Receipts and receipt-derived data (images, OCR text, categories, matches to transactions) | Duration of active account | Deleted as part of account deletion; associated storage objects (e.g., receipt images) are removed. |
| Support and communications (e.g., support tickets, emails) | As long as needed to resolve the matter, then in line with legal/operational need | May be retained longer if required for disputes or legal obligations. |
| Logs and operational data (e.g., access logs, error logs, audit trails) | As needed for security, debugging, and compliance; typically not longer than 90 days–1 year for routine logs | Logs that contain personal data should be minimized and retained only as necessary. |
| Backups | Up to 60 days after deletion from active systems | Data in backups may persist for up to 60 days to allow disaster recovery. After the backup cycle, data is overwritten or backups are disposed of in accordance with this policy. |
| Data retained for legal/legitimate purposes | As required by law or legitimate interest | e.g., tax, audit, legal hold, fraud prevention. Documented and reviewed periodically. |
| Anonymized or aggregated data | Indefinitely, where it no longer identifies individuals | Not considered personal data; may be retained for analytics and improvement. |
When a user requests account deletion (e.g., via the Proofey app or our designated process, including https://proofey-app.com/delete-account):
users table).plaid_items, plaid_accounts, transactions, failed_webhooks.The technical implementation of the above is supported by our account deletion service and the delete-user-account Edge Function, which perform the deletions in the correct order.
For data categories with a defined maximum retention period (e.g., certain logs), we will delete or anonymize data when that period is reached, using automated or scheduled processes where possible. Disposal methods must be appropriate to the system (e.g., permanent delete in database and object storage; secure deletion or decommissioning of media).
Where we use third parties (e.g., Supabase, Plaid, email providers) to process or store personal data, we: choose providers that support secure deletion and comply with our instructions and applicable law; rely on contract terms and provider documentation for retention and deletion behavior; we do not retain copies in our primary systems beyond the periods stated in this policy. Upon account deletion, we remove data from our primary systems; any residual data in a third party's environment is governed by our agreements and their policies (e.g., backup retention). We do not request restoration of backups solely to delete a single user's data.
| Role | Responsibility |
|---|---|
| Policy owner | Maintain this policy, ensure periodic review, and approve changes. |
| Engineering / Development | Implement retention and disposal in systems (e.g., account deletion flow, retention logic, logging). |
| Operations | Ensure backup and log retention align with this policy; support secure disposal procedures. |
| Support / Privacy | Process deletion and access requests in line with this policy and the Privacy Policy. |
| Compliance / Legal | Advise on legal retention and disposal requirements; support audits and regulatory responses. |
| Version | Date | Author | Summary of changes |
|---|---|---|---|
| 1.0 | March 12, 2026 | Proofey Team | Initial policy. |
lib/account-deletion-service.ts, delete-user-account Edge Function, Supabase storage buckets (e.g., profile-pictures, receipt-images)This document is intended for internal use and compliance. It supports our public Privacy Policy and account deletion process.