Trust6 does not ask you to believe your data is protected: every protection leaves inspectable proof.
The badge under every exchange
Every sent message carries a “Pseudonymized before sending” badge, with the number of masked entities. Your message stays displayed as tokens by default: it is the proof of what went out, not a decoration. The button under the bubble toggles between the two versions:
- View original: the real text, rehydrated for you.
- As sent: the tokens, exactly as the provider received them.
Both versions remain available at all times: nothing is cosmetic after the fact.
The network payload, byte for byte
“View network payload” opens the inspector: the provider’s real endpoint and the exact JSON that left. You can check that no clear-text name, email or amount is in there, and that attached documents appear as masked, numbered blocks. Authentication headers are never displayed.
The audit log
The Audit log button in the vault header opens the full history, filterable by family:
- Detection: every analysis, with the engine used and counts by type; never the values.
- Files: attachment added, extracted, removed.
- Sends: every send, failure or block, with its reason.
The CSV export follows the current filter: what you see is what you export. Handy for documenting compliance.
The token probe: proof of isolation
In the Audit view, the “Resolve a token” box lets you paste any token (say, PERSON_001 seen in an exchange):
- In the right vault: “Resolved in this vault”, with the real value.
- In any other vault: “Unknown token in this vault”.
That is the in-app demonstration that each client lives in a separate encrypted database.