This page explains how a FinFriend user or authorized customer representative can route an account-deletion request.
What the request should identify
Deletion requests should identify the relevant FinFriend account, workspace, or organizational context and explain whether the request concerns:
- closure of the user account itself;
- deletion of planning data or support history;
- a broader privacy-right request under applicable law.
Requests without enough detail may require follow-up before BrasMedia can verify scope and act safely.
Verification and review
Because FinFriend can involve planning history, support records, and operational logs with financial context, BrasMedia may need to confirm:
- the requester identity and authority;
- whether any billing, accounting, fraud-prevention, or dispute-related records must remain available;
- whether backups or short-lived technical copies still need time to rotate out.
If the request is made on behalf of a business customer, employer-sponsored deployment, or managed organization, BrasMedia may need confirmation from the relevant administrator or contracting party.
What users should do before deletion
Before final deletion, users should preserve any planning data, reports, exports, or records they need for their own financial administration or recordkeeping. A deletion request is not a substitute for the user’s own retention or documentation needs.
How to route the request
Use Contact and Privacy Requests and identify the relevant FinFriend account or organization.
For the broader retention framework, see the FinFriend Data Lifecycle Notice.