Privacy + data

Trust infrastructure requires careful boundaries.

Verification makes legitimate organizations easier to work with, keeps sensitive evidence private and collects only what each decision requires.

01

Private by default

Sensitive documents, personal identity records and internal evidence notes stay out of public profiles.

02

Explicit consent

Organizations control public listing and authorize institutional access to verification results and approved summaries.

03

Purpose-limited access

A partner sees only what it needs for the stated verification purpose and approved level.

04

Accountable actions

Verification decisions, access changes and evidence reviews are recorded in an audit trail.

05

Time-bounded retention

Data retention is tied to legal, contractual and verification needs, with review and deletion rules defined by data class.

06

Human responsibility

Automated tools assist reviewers. Accountable people make the 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, shown only with the organization’s consent.

Restricted information

What stays protected

Personal IDs, identity documents, bank details, private source documents, reviewer notes, confidential references and information beyond 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. Each source is weighed for what it actually establishes.

Important

TrustSana verification is evidence-based due diligence. It is a verification record, separate from legal advice, credit ratings and the obligations specific to a regulated customer.

Have a privacy or data-source question?

Contact TrustSana