Contact us
Trust centre

AI, with your organisation in control.

AI in DarkRisk is set per tenant. Your organisation's configuration decides which models support your workflows, and our team manages preferences and opt-outs with you.

AI request Checked
  1. 01AI is enabled for this tenantPass
  2. 02The model is on the tenant's approved listPass
  3. 03Context is limited to what the task needsApplied
  4. 04Inputs are excluded from model trainingApplied
  5. 05The answer goes back for human reviewReview
Illustrative, for an example organisationUpdated 15 October 2026

Your inputs serve your DarkRisk experience.

DarkRisk does not sell your inputs, documents or customer data. We use them to provide and improve your experience within DarkRisk, including the AI-assisted tasks enabled for your organisation.
01

Relevant context

An AI task may process your prompt, selected documents, questionnaire answers or relevant vendor findings. Our policy is to limit that context to what the task needs.

02

No general-purpose training

DarkRisk does not use your inputs to train general-purpose AI models. Our policy requires provider terms or hosting safeguards that prevent that use of confidential tenant content.

03

Tenant-specific choices

Model selection is organisation-scoped. A model listed here is not automatically used for every tenant. Contact us to confirm your tenant's current models and processing arrangements.

How requests reach a model

Direct APIs, cloud model services and internal hosting.

DarkRisk integrates with provider APIs directly and uses managed model services from its cloud providers for supported deployments, such as Amazon Bedrock. The route depends on the region, the tenant configuration and model availability; not every listed model is available on every route.

Open-weight models may also be hosted on DarkRisk’s internal infrastructure, subject to their licences, the model’s availability and the tenant’s agreed configuration and restrictions.

For Amazon Bedrock, AWS documents separation from model providers. Retention and abuse monitoring depend on the model, feature and configured controls. A no-training policy does not mean that no data is retained.

The models behind the assistance.

DarkRisk can draw on several model families. Which ones run for your organisation, and where, depends on your configuration. We confirm the specifics for your tenant on request.
  • Claude
  • DeepSeek
  • Gemini
  • GLM
  • GPT
  • Grok
  • Hunyuan
  • Kimi
  • MiMo
  • Qwen

One standard for every model

Ask which models your tenant uses
  • 01No training on your inputs, under the service's terms or our hosting.
  • 02Retention that meets your tenant's agreed requirements.
  • 03An approved processing location.
  • 04Where a developer's own service falls short, an approved hosting route, or no use at all.

Clear rules for responsible use.

Our enterprise AI policy centres on purpose limitation, tenant control, provider assessment and human oversight. These are operating requirements, not a claim of external AI certification.
01Controlled model selection
AI work uses the tenant's configured models. New model availability does not automatically change a saved configuration, and fallback must stay within the tenant's permitted choices.
02Data protection before use
Our policy requires assessment of confidentiality, training use, retention, security and processing location before confidential content is sent to a service. Being listed here is not approval for every data type.
03Human review
AI can make mistakes. Teams should review generated answers, summaries and recommendations against the evidence before relying on them. AI assistance does not replace accountable vendor-risk decisions.
04Clear handling requirements
Tenant requirements should specify the permitted providers, models, routes and regions. Contact us for the applicable arrangement; this declaration does not promise universal zero retention or in-country processing.

Choose how AI works for your tenant.

An authorised contact at your organisation can request changes for the tenant. Sending a request does not itself change your configuration; we confirm the scope and when it takes effect.
01

Opt out of AI

Request that AI processing is disabled for your tenant. We will identify affected workflows and confirm which features remain available without AI assistance.

02

Exclude a provider

Request exclusion of a named provider and its model families. Tell us whether the restriction covers all hosting routes, including versions run by our cloud providers and models hosted on DarkRisk's own infrastructure.

03

Exclude specific models

Keep approved AI assistance while excluding particular model names, versions or IDs. We will confirm suitable alternatives and any effect on feature availability.

Manage your AI preferences

Include your organisation, workspace region and the providers or models you want to exclude. We will verify your authority, agree the change and confirm when it takes effect.

Changes apply from then on. They do not recall completed requests or automatically delete existing records; ask us separately about deletion and retention.

Contact our team

Or email compliance@darkrisk.io