Demos & calls
You share a tab to walk a colleague through a ticket — and everyone on the call sees the customer's full IBAN.
You're screen-sharing, presenting, or just working in an open office — and a ticket, a CRM record, an email shows a client's IBAN, a card number, an API token in plain sight. Proxia masks sensitive values right on the page. One click on the eye reveals a value when you actually need it.
Flip the switch on the record — watch the sensitive fields veil over.
Proxia guards both ways. The checkpoint stops sensitive data from leaving in a prompt. Display masking stops sensitive data already on your screen from leaking through your eyes and your camera — the screenshot, the recording, the person behind you.
You share a tab to walk a colleague through a ticket — and everyone on the call sees the customer's full IBAN.
A screenshot for a bug report, a recorded walkthrough — the secret is now saved in a file you'll forget about.
The person beside you doesn't need access to your systems to read a card number off your screen.
Format is preserved and the last characters stay visible, so you keep your bearings while the value itself is hidden.
Turn on masking for the apps where sensitive data is displayed — Jira, Confluence, Outlook, Teams, or any internal tool you add yourself.
On-device, it scans the page's text and masks IBANs, cards, national numbers, secrets and other PII — format preserved, last characters kept for reference.
Need the real value? Click the eye. It reveals just that field, just for you — the page and the server are untouched.
Masking hides the value from view — screen shares, screenshots, shoulder-surfers. The real value still lives in the page and is revealable (that's the point of the eye). It is display protection, not encryption or access control. For stopping data from leaving your device, that's the outbound checkpoint.
The same on-device core that stops leaks on the way out veils sensitive data on the way in. Nothing is transmitted, either way.