How VYAX Protects Client SSNs

    Last verified: October 1, 2026

    Of everything a tax practice collects, a Social Security Number carries the most consequence if it ends up in the wrong place. It's also one of the least visible parts of any software — a client never sees how it's stored, only whether the firm handling it takes that seriously.

    Encrypted at the database level, not just access-controlled

    An SSN isn't kept as plain text with a permissions check in front of it. It's encrypted in the database itself, with the encryption key held in Supabase Vault rather than sitting in the same table as the data it protects — so a database read alone doesn't reveal anything usable.

    Day-to-day, only the last four digits are ever shown

    Confirming a client's identity or matching a document doesn't require displaying the full number — the interface a preparer actually works in shows only the last four digits, the same convention used on a pay stub or a bank statement.

    Viewing the full number is gated, not a standing permission

    Retrieving the decrypted value is restricted to the specific client it belongs to and their assigned preparer — not any preparer at the firm, and never another client. It isn't a setting a preparer can grant themselves broader access to; it's checked against who the record actually belongs to, every time.

    Every access leaves a record — without logging the number itself

    Each time an SSN is viewed or updated, that event is recorded — who, when, which record — in a dedicated access log. The log captures that an access happened, never the number itself; system logs are built to mask it rather than print it.

    See how VYAX handles sensitive data, free →

    This is server-side encryption with a controlled, audited decryption path — not end-to-end or "zero-knowledge" encryption where VYAX itself could never access the value. A service-role process can decrypt an SSN when a legitimate request calls for it; what this design prevents is casual, unlogged, or cross-client exposure.