Skip to main content
Trust Center · Contact

Reach the Right Team for Trust, Security, Privacy & Procurement Questions.

Use this structured Trust Team route when your organisation needs focused information to evaluate risk, clarify responsibilities, submit due-diligence questions, request available assurance material, or raise a trust concern related to DataConsultant services.

Security, privacy and technical review
Procurement, compliance and contractual questions
Questionnaires and trust-document requests
Responsible AI and vendor-risk review

Do not submit passwords, credentials, confidential datasets, payment-card information, health records or sensitive project data through the initial web form.

Step 1

Define the question

State the decision, review or concern that needs to be supported.

Step 2

Choose the closest topic

Select the category that best describes your review, even when several areas overlap.

Step 3

Add useful context

Include the service, stakeholder role, stage of due diligence and information required.

Step 4

Route for review

Relevant stakeholders can then clarify scope, evidence boundaries and next steps.

01

When to Contact the Trust Team

This route is designed for enterprise review teams that need trust-specific information rather than a generic sales conversation. A concise, well-scoped question helps reduce unnecessary hand-offs.

Supplier & security review

Clarify service context, access, delivery responsibilities, technical questions or due-diligence requirements relevant to a proposed engagement.

Privacy & data handling

Ask about processing context, privacy roles, data-subject routing, retention considerations or documentation that may be relevant to the engagement.

Documents & questionnaires

Request available assurance information, describe a security questionnaire, or identify NDA, DPA and contract-review requirements.

Responsible AI & third parties

Raise questions about AI oversight, model use, limitations, governance, vendor dependencies or engagement-specific risk considerations.

02

Select the Route That Best Matches Your Review

Choose the closest category. If your question spans multiple trust areas, explain that in the requirement field rather than submitting duplicate enquiries.

Security Question

Architecture, access, delivery practices, technical controls or engagement-specific security requirements.

Privacy Request

Privacy practices, processing arrangements, retention, data handling or privacy documentation.

Data Subject Request

Personal-data rights, identity-verification routing or questions about an individual interaction.

Compliance Enquiry

Contractual, regulatory, policy, governance or client-specific due-diligence questions.

Responsible AI Enquiry

Human oversight, model use, data, evaluation, transparency, limitations or AI governance.

Vendor Assessment

Supplier onboarding, third-party review, access, dependency or procurement-risk questions.

Security Questionnaire

A structured questionnaire requiring coordinated security, privacy, technical or operational input.

NDA / DPA Request

Confidentiality or data-processing documentation requiring review by authorised stakeholders.

Trust Document Request

Available policies, summaries, process descriptions or engagement-specific supporting material.

Incident / Vulnerability

A suspected event, exposed information, vulnerability or urgent risk that requires careful routing.

03

Share Context, Not Confidential Data

The initial form is for routing and scoping. Provide enough information to understand the review without placing sensitive evidence, credentials or protected datasets into a general web form.

Useful information to include

  • Your organisation, role and the team conducting the review.
  • The relevant DataConsultant service or proposed engagement.
  • The review stage, decision or procurement activity being supported.
  • The specific questions, evidence category or document type required.
  • A target decision date where it materially affects coordination.

Do not include in the initial form

  • Passwords, one-time codes, API keys, access tokens or private keys.
  • Confidential datasets, health records or payment-card information.
  • Government identifiers or unnecessary personal information.
  • Source code containing secrets or sensitive internal architecture detail.
  • Exploit code or unnecessary details that could increase security risk.
Need to exchange sensitive evidence? Describe what your review requires and request an approved exchange method. Access conditions, confidentiality restrictions and authorised recipients should be confirmed before sensitive material is shared.
04

How a Trust Team Enquiry Moves Through Review

The route depends on subject, service, contractual context, urgency and evidence requirements. The process below explains the intended sequence without promising a fixed response time.

Trust enquiry lifecycleQuestion → Context → Triage → Specialist review → Clarification / response
01

Structured intake

We receive the category, stakeholder context, related service and concise enquiry details.

Outcome: a defined question rather than a generic contact request.
02

Initial triage

The enquiry is checked for scope, urgency, safe-handling needs and missing context.

Outcome: determine what must be clarified before deeper review.
03

Specialist routing

Relevant security, privacy, legal, technical, operational, procurement or other authorised stakeholders may be involved.

Outcome: route to the people best placed to address the subject.
04

Evidence boundary

The review identifies what can be answered publicly, what requires clarification and what may need controlled sharing.

Outcome: avoid over-disclosure and unsupported assurance statements.
05

Appropriate response

Available information, clarifying questions or a suitable document-exchange route is provided where applicable.

Outcome: support the decision without converting general information into an unintended commitment.
Trust Team enquiry

Contact the Trust Team

Complete the fields below. Required fields are marked with an asterisk. Keep the message focused on routing, review requirements and the decision your organisation is supporting.

Your review context * Required fields
Enquiry routing
Your requirement
Describe the review stage, decision being supported and information required. Do not paste confidential or sensitive material.
Preferred Response Method
Security check
Numeric security check Loading question…

Submission is an enquiry only. It does not create or amend a contract, accept customer terms, confirm compliance, or establish a response-time commitment. Information submitted through this form is subject to the DataConsultant Privacy Policy.

Form unavailable? Use the verified company contact email: support@dataconsultant.in.
05

What a Trust Team Response Can Clarify

Assurance information has different disclosure and applicability boundaries. The purpose of the enquiry route is to connect your decision with the appropriate level of information without treating every document, control or contract term as universally applicable.

Public information

Trust Center guidance

General information suitable for public review, including topic explanations, responsibility boundaries and due-diligence guidance.

Use this first when the answer is already available publicly.
Clarification

Context-specific explanation

Questions about how a general practice, responsibility or review point may relate to the service and engagement under consideration.

Applicability still depends on scope, architecture, contract and client requirements.
Controlled evidence

Request-based material

Supporting information that may require relevance review, confidentiality controls, authorised recipients or a defined exchange route.

No restricted document is represented as available unless it has been verified and authorised.
Client-specific

Deeper due diligence

Questionnaires, contractual requirements and engagement-specific review where parties need to agree roles, controls, evidence or responsibilities.

Formal commitments require authorised written agreement.

Important: Asking for a certification, audit report, policy or control description does not mean that DataConsultant claims to hold that certification, possess that report, or apply that control universally. Availability and applicability must be verified.

07

Trust Team Contact & Enquiry FAQs

These answers explain appropriate use of the contact route, information-sharing boundaries, evidence requests and the limits of a web-form submission.

What types of enquiries should be sent to the Trust Team?
Use this route for security, privacy, data-subject, compliance, responsible AI, vendor-assessment, procurement due-diligence, security-questionnaire, NDA or DPA, trust-document, contractual-security, suspected-incident or vulnerability questions. General sales or project-scoping requests should use the normal commercial contact route instead.
What information should I include in a security or procurement enquiry?
Provide your organisation, role, the relevant service or proposed engagement, the review stage or decision being supported, and the specific questions or information required. Keep the initial message concise and avoid submitting confidential datasets, credentials or other unnecessary sensitive material.
Can I submit a security questionnaire through this form?
Yes. Select Security Questionnaire and describe the review stage, relevant service, expected scope, preferred exchange method and any target date your team is working toward. Do not paste confidential questionnaire content into the initial web form; an appropriate exchange route can be discussed after triage.
How are Trust Team enquiries routed?
The enquiry category, service context, decision being supported and information requested are used to identify which security, privacy, legal, technical, operational, procurement or other authorised stakeholders may need to review the question. Routing depends on the subject and engagement context.
Do you guarantee a Trust Team response time?
No response-time commitment is stated on this page. Timing can vary with urgency, complexity, identity-verification needs, evidence availability, contractual context and the involvement of specialist reviewers.
Can I use this form for a data-subject or privacy request?
Yes. Select the relevant privacy or data-subject category and provide only enough information to identify the interaction and nature of the request. Additional information may be requested through an appropriate channel when identity or scope needs to be verified.
Can I request an NDA, DPA or other trust documentation?
You can request review of confidentiality, data-processing or trust documentation. Availability, applicability, access conditions, amendments and approval depend on the proposed engagement, authorised records, confidentiality restrictions and review by the appropriate stakeholders. Submission does not mean a document or term has been accepted.
Can I request certification or audit evidence?
You can identify the specific evidence your review requires. Any response depends on verified company records, relevance, confidentiality restrictions and engagement context. This page does not claim that DataConsultant holds a particular certification, audit report or regulatory approval.
What responsible AI topics can I ask about?
Relevant topics may include model selection, intended use, human oversight, data use, evaluation, transparency, limitations, output review, risk ownership, acceptable use and engagement-specific governance. The applicable controls and responsibilities depend on the actual solution and service scope.
Should I report a suspected vulnerability or incident here?
You may use the suspected incident or vulnerability category, but share only the minimum information needed to identify and route the concern. Do not exploit a suspected weakness, access data that is not yours, disrupt services or publish sensitive details. For an active matter, use the fastest verified company contact route available to you.
What should I never submit through the general Trust Team form?
Do not submit passwords, one-time codes, API keys, access tokens, private keys, confidential datasets, payment-card information, health records, government identifiers, source code containing secrets or sensitive project data. Request an approved exchange method after the enquiry has been routed.
Does contacting the Trust Team create a contract or confirm compliance?
No. A form submission is an enquiry. It does not create or amend a contract, accept customer terms, confirm universal compliance, establish a service-level commitment or override an authorised written agreement.

Use the Trust Team Route to Keep Due Diligence Focused and Controlled.

Start with the review decision, choose the closest trust topic, share only the context needed for routing, and request a controlled exchange method if sensitive evidence is required.