Define the question
State the decision, review or concern that needs to be supported.
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.
Do not submit passwords, credentials, confidential datasets, payment-card information, health records or sensitive project data through the initial web form.
State the decision, review or concern that needs to be supported.
Select the category that best describes your review, even when several areas overlap.
Include the service, stakeholder role, stage of due diligence and information required.
Relevant stakeholders can then clarify scope, evidence boundaries and next steps.
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.
Clarify service context, access, delivery responsibilities, technical questions or due-diligence requirements relevant to a proposed engagement.
Ask about processing context, privacy roles, data-subject routing, retention considerations or documentation that may be relevant to the engagement.
Request available assurance information, describe a security questionnaire, or identify NDA, DPA and contract-review requirements.
Raise questions about AI oversight, model use, limitations, governance, vendor dependencies or engagement-specific risk considerations.
Choose the closest category. If your question spans multiple trust areas, explain that in the requirement field rather than submitting duplicate enquiries.
Architecture, access, delivery practices, technical controls or engagement-specific security requirements.
Privacy practices, processing arrangements, retention, data handling or privacy documentation.
Personal-data rights, identity-verification routing or questions about an individual interaction.
Contractual, regulatory, policy, governance or client-specific due-diligence questions.
Human oversight, model use, data, evaluation, transparency, limitations or AI governance.
Supplier onboarding, third-party review, access, dependency or procurement-risk questions.
A structured questionnaire requiring coordinated security, privacy, technical or operational input.
Confidentiality or data-processing documentation requiring review by authorised stakeholders.
Available policies, summaries, process descriptions or engagement-specific supporting material.
A suspected event, exposed information, vulnerability or urgent risk that requires careful routing.
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.
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.
We receive the category, stakeholder context, related service and concise enquiry details.
Outcome: a defined question rather than a generic contact request.The enquiry is checked for scope, urgency, safe-handling needs and missing context.
Outcome: determine what must be clarified before deeper review.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.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.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.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.
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.
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.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.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.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.
These answers explain appropriate use of the contact route, information-sharing boundaries, evidence requests and the limits of a web-form submission.
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.