Data subject request
A request concerning personal data rights, identity verification, or request-routing guidance.
Trust Center contact
Reach the right team for trust, security, privacy, and procurement questions.
Use this structured route to help us understand your review, route it to appropriate stakeholders, and respond with information that is relevant to your organisation, proposed service, and stage of due diligence.
Do not submit passwords, credentials, confidential datasets, payment-card information, health records, or sensitive project data through this form.
Executive summary
A practical contact route for due diligence and trust-related decisions.
This page is designed for enterprise buyers, procurement teams, security reviewers, privacy teams, legal stakeholders, executives, and technical leaders evaluating our data, analytics, AI, cloud, and managed-service capabilities.
What this route is intended to support
Use the form when your organisation needs focused information to evaluate risk, clarify responsibilities, request available documents, or route a potentially urgent trust concern.
- Supplier evaluation, security review, and technical due diligence.
- Privacy assessment, data-processing questions, and data-subject requests.
- Procurement, contractual, compliance, NDA, DPA, and questionnaire coordination.
- Responsible AI, human oversight, model use, limitations, and governance questions.
Enquiry categories
Select the route that best matches your review.
Choosing a category helps reduce unnecessary hand-offs. Select the closest option even when your enquiry spans more than one area.
Security question
Architecture, access, delivery practices, technical controls, or engagement-specific security requirements.
Privacy request
Privacy practices, processing arrangements, retention, subprocessors, or privacy documentation.
Compliance enquiry
Contractual, regulatory, policy, governance, or due-diligence questions relevant to an engagement.
Responsible AI enquiry
Human oversight, model use, AI risk, transparency, evaluation, or engagement-specific AI governance.
Vendor assessment
Supplier onboarding, procurement review, risk assessment, or third-party evaluation.
Security questionnaire
A structured questionnaire requiring coordinated security, privacy, technical, or operational input.
NDA or DPA request
Confidentiality or data-processing documentation for review by authorised stakeholders.
Trust document request
Available policies, summaries, process descriptions, or engagement-specific supporting material.
Suspected incident or vulnerability
A suspected active security event, exposed information, vulnerability, or urgent risk requiring careful routing.
Safe submission
Share context, not confidential data.
The initial form is for routing and scoping. Sensitive material should be exchanged only through a method approved for the specific enquiry.
Useful information to include
Your organisation, role, enquiry category, relevant service, review stage, decision being supported, and a concise description of the information or document required.
Do not include sensitive material
Never submit passwords, API keys, access tokens, confidential datasets, payment-card data, health records, private keys, or source code containing secrets.
Handling and routing
How a Trust Team enquiry is expected to move.
The exact route depends on the subject, service, contractual context, urgency, and evidence required. No unverified response-time promise is made.
Structured intake
We receive the category, stakeholder context, related service, and concise enquiry details.
Initial triage
The request is checked for scope, urgency, safe handling needs, and missing context.
Specialist routing
Relevant privacy, security, legal, technical, operational, or executive stakeholders may be involved.
Appropriate response
Available information, clarifying questions, or a suitable document-exchange route is provided where applicable.
Contact the Trust Team
Complete the fields below. Required fields are marked with an asterisk. Keep the message focused on routing and review requirements.
Describe the review stage, decision being supported, and information required. Do not paste confidential or sensitive material.
Submission does not create a contract, accept customer terms, confirm compliance, or establish a response-time commitment.
What this means for clients
Clearer review, fewer unnecessary hand-offs.
A well-scoped enquiry helps each stakeholder focus on the information that matters to the decision being made.
Context-aware routing
The category and service context help identify which functions may need to review the request.
Relevant documentation
Requests can be narrowed to available information that is appropriate to the engagement and review stage.
Safer information exchange
Sensitive material can be withheld until an approved exchange route and authorised recipients are confirmed.
Important considerations
Scope, limitations, and shared responsibilities.
Trust information must be interpreted in the context of a defined service, architecture, contract, and division of responsibilities.
Engagement-specific applicability
Controls, roles, data flows, platforms, and contractual terms can vary by service and client requirements.
Evidence requires verification
Only verified and authorised documents or statements should be relied on during procurement or legal review.
Shared responsibility
Clients remain responsible for their users, instructions, access decisions, configurations, source data, and legal obligations within their control.
Frequently asked questions
Trust Team contact and enquiry guidance.
These answers explain appropriate use of the form, expected routing, important limitations, and safer information-sharing practices.
What types of enquiries should be sent to the Trust Team?
Use this page for security, privacy, data-subject, compliance, responsible AI, vendor-assessment, questionnaire, NDA, DPA, trust-document, suspected-incident, or vulnerability enquiries. General sales and project-scoping questions should use the main contact route.
What information should I include in a security or procurement enquiry?
Provide your organisation, role, the relevant service or proposed engagement, the decision you are supporting, and the specific questions or documents required. Do not include credentials, confidential datasets, payment-card data, health records, or unnecessary sensitive information.
Can I send a security questionnaire through this form?
Yes. Select “Security questionnaire” and describe the questionnaire, due-diligence stage, relevant service, preferred exchange method, and any deadline that your team is working toward. Do not paste confidential questionnaire content into the form.
How are enquiries routed internally?
Enquiries are reviewed by category and may be routed to appropriate privacy, security, legal, technical, operational, procurement, or executive stakeholders. Routing depends on the subject, engagement context, and information needed to provide an accurate response.
Do you guarantee a response time?
No unverified response-time commitment is stated on this page. Timing can depend on the nature, urgency, complexity, identity-verification needs, and involvement of specialist reviewers.
Can I use this form to make a data-subject request?
Yes. Select “Data subject request” and provide enough information to identify the relevant interaction without adding sensitive data. We may need to request additional information through an appropriate channel to verify identity and scope.
Will you sign our NDA or data processing agreement?
You may request review of an NDA or DPA. Acceptance, amendments, and signing authority depend on the engagement, applicable roles, risk allocation, legal review, and authorised approval. Submission does not mean a document has been accepted.
Can you provide certifications or audit reports?
Request the specific evidence your review requires. Available documentation depends on verified company records, relevance, confidentiality restrictions, and the proposed engagement. This page does not claim any certification or audit status.
What responsible AI topics can I ask about?
Relevant topics may include model selection, human oversight, data use, evaluation, transparency, limitations, output review, risk ownership, acceptable use, and engagement-specific governance. Applicability depends on the service and solution design.
Should I report a suspected vulnerability here?
Yes, but share only the minimum information needed to identify and assess the issue. Do not exploit a suspected weakness, access data that is not yours, disrupt services, or publish sensitive details. For an active incident, also follow the emergency guidance on this page.
What should I avoid submitting?
Do not submit passwords, access keys, authentication tokens, confidential datasets, payment-card information, health records, government identifiers, source code containing secrets, or sensitive project data. Use an approved secure exchange method after routing is confirmed.
Does contacting the Trust Team create a contract or legal commitment?
No. A form submission is an enquiry and does not create a contract, amend an agreement, accept customer terms, confirm compliance, or establish a service-level commitment. Formal commitments require authorised written agreement.
Guidance for a suspected active incident
When you believe an incident is active, information is exposed, or immediate harm may be occurring, use the fastest verified company contact route available to your organisation and clearly mark the message as urgent.
- Stop actions that may expand the impact; do not test, exploit, or access data beyond what is necessary to identify the concern.
- Preserve relevant timestamps, URLs, screenshots, and non-sensitive observations without sharing credentials or confidential datasets through this form.
- Contact your own security, privacy, legal, or incident-response personnel as required by your organisation’s procedures.
- Where personal safety, criminal activity, or critical public infrastructure may be at risk, contact the appropriate local emergency or law-enforcement authority.