Data Retention and Deletion Policy
The Bailey Family Plan LLC
dba Signarama Temecula and Fully Promoted Temecula Valley
41785 Enterprise Cir, Ste B, Temecula, CA 92590
Effective date: October 12, 2026
Policy owner: Mark Bailey, Owner (mark.bailey@signarama.com)
1. Purpose and Scope
This policy explains how long we keep data in Signmetry, our internal web app, and how we delete it. It covers financial data received through Plaid from the company's own business bank accounts, Plaid access tokens, and related records stored in the Signmetry database hosted on Render.
2. Retention Periods
| Data | How long we keep it |
|---|---|
| Financial transaction and account data used for bookkeeping | As long as needed for bookkeeping and tax purposes, generally 7 years from the end of the tax year it relates to |
| Plaid access tokens | Only while the bank account remains connected; deleted within 30 days of disconnecting or on request |
| Linked Plaid data not needed for tax or bookkeeping records | Deleted within 30 days of disconnecting the account or on request |
| Employee user accounts in Signmetry | Disabled within 1 business day of the employee leaving; deleted when no longer needed |
We will keep data longer only if required by law, a tax audit, or a legal hold.
3. Disconnecting an Account or Deletion Requests
When a bank account is disconnected from Signmetry, or when deletion is requested by the Owner, Plaid, or the account holder, we will within 30 days:
- Revoke the Plaid access token through Plaid's API (item removal) so no further data can be pulled.
- Delete the access token from our database.
- Delete linked Plaid data that we are not required to keep for bookkeeping or tax records.
Deletion requests should be sent to mark.bailey@signarama.com.
4. Secure Deletion
- Data is deleted from the Signmetry production database, not just hidden.
- Copies in exports or working files are deleted when no longer needed.
- Database backups managed by Render expire on the platform's backup schedule; deleted data is not restored to active use.
- Secrets and tokens are never kept in chat, email, or spreadsheets, so they do not need separate cleanup there.
5. Responsibility
The Owner is responsible for this policy and for confirming that deletions are completed.
6. Policy Review
We will review this policy at least once a year, and sooner if our systems, vendors, or legal requirements change.
Approved by: Mark Bailey, Owner — October 12, 2026