GPrivacy, explained
How to think about privacy when verifying identity
Short answer
Identity verification involves sensitive information, so the useful questions are: what is collected, who can see the result, what the requester receives, and how the person can ask for access or deletion. This is an educational explanation, not a policy. Review the policy pages and their approval status for the applicable disclosures.
Questions worth asking any provider
- What exactly is collected: ID images, face capture, contact details?
- Does the requester receive the ID images, or only an outcome?
- Who inside the provider can access the data, and why?
- How long is data kept, and where is that written down?
- How can the person request access, correction, or deletion?
- Is biometric consent requested separately and clearly?
Minimization habits for requesters
- Request an identity check only when you will actually use the answer.
- Do not ask the person to email you a copy of their ID as well.
- Keep the outcome in one place and limit who can see it.
- Do not screenshot records into group chats or shared drives.
Security is about limits, not slogans
No service can promise data will never be exposed. What you can look for is evidence of restraint: collecting less, limiting who sees what, private links instead of public pages, and clear routes to delete data. The Security page describes Truvee's approach in general terms; the Privacy Policy and Biometric Consent pages are the authoritative documents.
Limits to keep in mind
- This is an educational explanation, not a policy. The Privacy Policy governs.
- Retention and processing details are stated only in Truvee's published policies.