A lead's Social Security number - stored encrypted, shown as the last four, written to history encrypted

Shipped

November 12, 2026 at 6:21 PM UTC

Author

Kamo

Commit

a85ea70

AES-256-GCM through a dedicated key (lead.pii-enc-key), SSN_ENCRYPTED + SSN_LAST4 on LEADS. Responses carry only the last four; the history token keeps the last four in the clear beside the ciphertext so any reader can mask it without the key. A same-number resubmit changes nothing. An inbound lead is never lost to its number; a member's update that cannot store one fails loudly. New right VIEW_FULL_SSN (710), a child of View Leads. The mapper reads an 'ssn' target.