"Delete this client" sounds like a single action. Underneath, a client's data usually touches dozens of tables — documents, messages, invoices, signatures, logs — and a deletion that only handles some of them leaves a trail of orphaned rows nobody is tracking. VYAX treats deletion as one coordinated action, not a cleanup job left to chance.
Deleting a client runs through a single database function that discovers every table referencing that client's record and handles each one by rule — rather than a preparer, an admin, and a script each clearing out a different piece by hand.
An audit entry — who deleted the account and when — is written first, and that entry is never itself deleted. If a question ever comes up about when and why an account was removed, there's a permanent answer, independent of everything else the deletion touched.
In-app messages and the client's own working data are removed — there's no retention requirement for those. Compliance-relevant records (billing and security logs, for example) are kept with the personal identity scrubbed from them, because recordkeeping rules for tax practices (IRS Publication 4557, GLBA safeguarding requirements) exist independently of whether a specific client account still exists. It's not VYAX choosing to hold onto data it doesn't need — it's the difference between a client's day-to-day data and a firm's compliance obligations.
Deleting a client's portal account isn't the same as a firm's own recordkeeping duty. Preparers are still responsible for retaining their own copies of filed returns for the period required under IRS §6107(b) — generally three years — independent of whether that client's portal account still exists.