Private by default
Sensitive documents, personal identity records and internal evidence notes are not public profile content.
Privacy + data
Trust infrastructure requires careful boundaries.
Verification should make legitimate organizations easier to work with without making sensitive evidence public or collecting more than the decision requires.
Explicit consent
Organizations control public listing and authorize institutional access to verification results and approved summaries.
Purpose-limited access
A partner sees only what it needs for the stated verification purpose and approved level.
Accountable actions
Verification decisions, access changes and evidence reviews are recorded in an audit trail.
Time-bounded retention
Data retention is tied to legal, contractual and verification needs, with review and deletion rules defined by data class.
Human responsibility
Automated tools may assist reviewers, but they do not make final verification decisions.
Public information
What a public verification page may show
Organization name, country, organization type, issued status, verification date and basic organizational details—only when the organization consents.
Restricted information
What stays protected
Personal IDs, identity documents, bank details, private source documents, reviewer notes, confidential references and information outside the approved sharing purpose.
Data sources
Evidence may come from the organization, public registries, published filings, websites, domain records, structured references, approved local verifiers and direct confirmation. Each evidence record identifies its source and method; source presence does not guarantee sufficiency.
Important
TrustSana verification is evidence-based due diligence, not a guarantee of future performance, legal advice, a credit rating or a substitute for obligations specific to a regulated customer.