Public
Verified live document
Open directly when a current approved public URL has been verified.
Trust Center · Trust Documents
Trust documents for structured data and AI due diligence
Use this page to find verified public DataConsultant documents, understand how controlled assurance information may be handled, and submit a context-rich request for security, privacy, legal, procurement, risk or responsible AI review.
Only verified public documents are linked as current evidence
Access conditions are separated from document existence
Security-sensitive material is not exposed through public pages
Engagement-specific requirements remain subject to scope and contract
This page does not imply certification, audit status, regulatory approval, guaranteed security, universal compliance, or the existence of any document that has not been verified.
✓ PublicVerified live information that can be opened directly.
↗ On RequestA generic access category subject to relevance and approval.
! RestrictedPotentially sensitive information requiring controlled disclosure.
C Client-SpecificQuestionnaires, contract terms and engagement evidence.
Trust Documents
Evidence should be current, approved, relevant and disclosed through the right channel.
Available on request
Context first
A generic access category for material that may require relevance and disclosure review.
Restricted
Controlled disclosure
Potentially sensitive assurance information may require confidentiality and need-to-know controls.
Client-specific
Engagement evidence
Questionnaires, contract terms and project evidence depend on the actual service and responsibilities.
Evidence architecture
A controlled path from public information to client-specific due diligence
Trust information should become more specific only as the review purpose, confidentiality needs and engagement context become clearer. The levels below describe an evidence model, not a claim that a document exists at every level.
What this page can confirm
Enterprise review teams need to distinguish current public information from deeper evidence that may be controlled or specific to an engagement. This page is designed to make that boundary visible before a request is submitted.
- Public links are shown only for documents with a verified live DataConsultant URL.
- Access categories explain disclosure conditions without manufacturing a document repository.
- Questions can be routed by trust topic, review stage and intended decision.
- Client-specific controls and commitments remain subject to the agreed scope and contract.
A document title, certification, audit report or assurance status should never be inferred merely because that type of material is common in enterprise procurement.
Public information
Verified pages and documents suitable for unrestricted access.
Trust Center detail
Expanded explanations of governance, processes, responsibilities and limitations.
Control or process evidence
Supporting material that may require context and approval before disclosure.
Restricted assurance material
Security-sensitive or confidential information shared only through an appropriate controlled route.
Client-specific due diligence
Questionnaires, contractual evidence and engagement-specific reviews connected to the proposed service.
Verified public documents
Current public information with live DataConsultant URLs
The items below are limited to public documents whose live destination has been verified for this page. No unverified policy, certificate, report, assessment or audit is presented as an existing DataConsultant document.
● Public
Privacy Policy
Privacy
Public information about how DataConsultant handles personal information in connection with the website, enquiries, business relationships and relevant service activities.
Open Privacy Policy
● Public
Terms of Use
Legal
Public website terms covering use of DataConsultant online resources and general conditions relevant to enquiries and consulting-service interactions.
Open Terms of UseWhy the public library is intentionally small: this page prioritises evidence integrity over appearance. Additional material should only be named when its title, status, version, owner or access route is supportable.
Assurance topics
Route the document request to the subject your reviewers actually need
Many due-diligence questions are better answered by combining public Trust Center context with a focused request rather than asking for a generic “security pack”. Select the relevant topic before requesting evidence.
Information Security
Security governance, access, delivery controls, monitoring and incident-related responsibilities.
Review topicData Privacy
Personal-data roles, handling expectations, privacy-by-design considerations and client responsibilities.
Review topicBusiness Continuity
Continuity planning, dependencies, communication, recovery considerations and scope limitations.
Review topicCompliance
Requirement interpretation, responsibility allocation, control mapping and evidence discussions.
Review topicResponsible AI
AI governance, data, evaluation, human oversight, reliability and monitoring considerations.
Review topicVendor Management
Third-party due diligence, information access, risk review, monitoring and offboarding context.
Review topicQuality Assurance
Requirements, review, testing, defect handling, acceptance and transparent delivery limitations.
Review topicSecure Delivery
Project setup, access, environments, data handling, review gates, handover and closure.
Review topicRequest workflow
From due-diligence question to an appropriate evidence route
The request process is designed to provide relevant approved information while avoiding unnecessary disclosure of sensitive, outdated or engagement-irrelevant material.
Define the review
Identify the service, stakeholder group, decision, questionnaire and target date.
Classify the request
Separate public information, controlled assurance needs, restricted detail and client-specific questions.
Agree access conditions
Where needed, clarify recipient, confidentiality, purpose, scope and a suitable delivery route.
Provide the right response
Share approved information where available or explain the appropriate questionnaire, meeting or contractual route.
Document governance
Evidence should be owned, reviewed, approved and kept current
A document is useful for enterprise assurance only when its status is understandable. The governance model below describes the information that should support publication or controlled sharing.
Draft
Prepare or revise content from accountable source material.
Review
Check legal, privacy, security, technical and business accuracy as relevant.
Approved
Record the authorised version, audience and access classification.
Published or controlled
Use the verified public URL or approved restricted delivery route.
Superseded
Prevent obsolete material from being represented as current evidence.
| Publication check | What should be confirmed | Why it matters |
|---|---|---|
| Ownership | Accountable owner or approving function is identifiable. | Questions and updates can be routed to the right authority. |
| Approval state | The material is approved for its intended audience and use. | Draft or unreviewed material is not mistaken for official assurance. |
| Version / date | Current version, effective date or review date is supportable where applicable. | Review teams can distinguish current evidence from superseded content. |
| Access classification | Public, request-based, restricted or client-specific handling is clear. | Sensitive information is not exposed through an inappropriate channel. |
| Delivery route | A verified URL or controlled disclosure method is available. | Recipients receive the intended approved version rather than an informal copy. |
Disclosure guardrails
Transparency should support assurance without exposing sensitive detail
Trust Center content is intended to explain governance, process, responsibilities and evidence boundaries. It should not publish operational detail that creates unnecessary security, privacy or confidentiality risk.
Appropriate for public assurance
Public content can explain the principles and decision process that reviewers need in order to determine whether deeper evidence is required.
- Governance and accountability models
- High-level lifecycle and control concepts
- Shared-responsibility boundaries
- Public legal information with verified URLs
- How to request deeper due-diligence information
Not appropriate for a public form or page
Security-sensitive or confidential information should use an approved controlled channel rather than a general public page or initial web form.
- Passwords, credentials, secrets, private keys or tokens
- Detailed vulnerability or penetration-test findings
- Internal hostnames, IP addresses or admin endpoints
- Confidential client architecture, datasets or personal records
- Restricted documents not approved for public disclosure
Need a specific document, questionnaire response or evidence discussion?
Tell us what your security, privacy, legal, procurement, risk or AI-governance review is trying to establish. The request can then be routed to the most appropriate information or controlled discussion.
Frequently asked questions
Trust-document questions from procurement and review teams
These answers explain access, evidence boundaries, requests, shared responsibility and the limits of what should be inferred from a public Trust Center page.
What are DataConsultant trust documents?
Trust documents are approved public or controlled materials that can support security, privacy, legal, procurement, operational, responsible AI and other due-diligence reviews. This page only names a document as available when its current status can be supported.
Can I download every assurance document directly from this page?
No. Public documents can be linked when an approved live URL is available. Other assurance information may require a request, confidentiality conditions, a defined review purpose or engagement-specific discussion. A request does not guarantee that a particular document exists or can be disclosed.
What does “available on request” mean?
It is an access category used for material that may be shared after the review context, recipient, relevance and disclosure conditions are understood. The category does not by itself assert that a specific named document exists.
Why might assurance material be restricted?
Some information may contain security-sensitive, confidential, supplier, contractual or client-specific detail. Access may therefore depend on confidentiality terms, need-to-know, review purpose and the scope of the proposed or active engagement.
Can procurement submit a security or supplier questionnaire?
Yes. Use the documentation request form to describe the questionnaire, the service being reviewed, the stakeholder group, the decision or onboarding stage, and any target date. Do not paste credentials, confidential datasets or other highly sensitive information into the form.
Do trust documents prove that every control applies to every engagement?
No. Applicability depends on the agreed service, systems, data, access, delivery model, technology providers, client requirements and contract. Public material supports due diligence but does not replace engagement-specific scope and responsibility decisions.
Does this page confirm any DataConsultant certification or audit status?
No certification, audit, regulatory approval or universal compliance status should be inferred from this page. Such claims should only be made where current, approved DataConsultant evidence explicitly supports them.
What information should I include in a trust-document request?
Provide your organisation, role, the service or engagement under review, the purpose of the review, the information or questionnaire required, and any target decision date. This context helps route the request without requiring unnecessary sensitive information.
How are outdated or superseded documents handled?
A sound document-governance process should distinguish draft, reviewed, approved, published or controlled, and superseded material. Public or shared information should be checked for the correct owner, approval state, access classification and current version before use.
How can I ask a question that is not covered by an available document?
Use the Contact Trust Team page or the documentation request form on this page. DataConsultant can route the question to the appropriate trust, legal, privacy, security, technical or operational context where applicable.
Trust documentation request
Request assurance information
Use this form for trust-document, security-questionnaire, privacy, compliance, continuity, responsible AI, vendor-risk or related procurement requests. Do not include passwords, credentials, confidential datasets or highly sensitive security detail.