Data deletion

Disconnect access and define what is removed.

SIX separates provider connections, unapproved staged records, canonical history, and provenance so deletion choices can be handled deliberately.

Reviewed July 19, 2026

01 / DISCONNECT

Disconnect an institution

In SIX, open the provider connection controls for the relevant institution and choose Disconnect Institution. After confirmation, SIX asks Plaid to remove access, removes the encrypted provider credential and connection-scoped provider caches, and stops future sync and webhook matching. If Plaid removal fails, SIX keeps the local credential so the owner can retry safely.

02 / STAGED DATA

Handle unapproved records

In the provider review area, Reject prevents an unapproved staged record from entering the canonical ledger. Rejected or other staged metadata may remain for review and audit until the connection is disconnected or a separately scoped deletion request is completed. SIX does not currently offer a general bulk-delete control for canonical financial history.

03 / PROVENANCE

Choose provenance handling

Provider provenance explains where an imported record originated and helps prevent duplicate or mismatched imports. A request can ask to remove provider-specific provenance where feasible or retain limited provenance needed for reconciliation, audit, or security. The effect will be clarified before completion.

04 / CANONICAL HISTORY

Request historical deletion

Approved canonical history is not silently deleted when a provider is disconnected. This protects ledger integrity. Historical deletion is a separate request, not an automated in-app action. Identify the institution, approximate date range, and desired scope without including sensitive account credentials.

Request by email

Email ricardo.suarez@outlook.com

State that the message is a SIX deletion request and describe the institution or data category and desired scope. Do not email passwords, access tokens, PINs, security answers, or complete account numbers. The request will be acknowledged, reasonable identity and scope verification may be requested, and the next steps or any constraints will be explained before any deletion occurs.

Some limited information may be retained when reasonably necessary for audit, security, reconciliation, fraud prevention, dispute handling, or legal obligations. Where applicable, retained information will be limited to that purpose and no longer used for ordinary analysis.