Skip to content

Your media never leaves your control

Built for organisations that cannot compromise on privacy. You set how long anything is kept, the stack can run entirely inside your own network, and every access is on the record.

Encryption

TLS 1.2 or newer in transit

Data retention

Zero, or a window you set

Audit log

Every access recorded

Deployment

Self hosting available

Eight things we hold to

The answers a security review asks for, before it asks.

Retention you control

You choose how long media is kept. With zero retention, media is analysed and discarded once the verdict is returned and nothing is written to Raid AI storage. Otherwise media is kept for a window you set, 30 days by default, and then deleted. None of it is used to train a model, and enterprise tenants can keep their records inside their own database or infrastructure instead. Media goes only to the detection engines your tenant is configured to use, and only to produce the verdict.

Runs in your infrastructure

For air gapped and sovereign environments, the full detection stack runs inside your own network with no external connectivity.

Encryption in transit

All communication with the cloud API is encrypted using TLS 1.2 or newer, and older protocol versions are refused. Media is protected from the moment it leaves your network.

Scoped API keys

Every integration is gated by a scoped key with configurable rate limits and IP allowlisting. Keys can be rotated at any time.

SOC 2 principles

Built around the five SOC 2 trust service criteria: security, availability, processing integrity, confidentiality and privacy.

Where media is processed

The cloud service runs on Google Cloud in the United States. If that region cannot serve a request, detection fails over to a copy of the same models in the European Union. When media has to stay in one jurisdiction, the stack runs inside your own infrastructure.

Defence in depth

Infrastructure, application and model layers are each protected independently. A compromise at one layer does not expose customer data.

Audit logging

Every API call is written to a tamper evident audit trail, so you can reconstruct exactly what was processed, when, and by which key.

What we do not do

  • Train on your media, or use it to improve any model
  • Keep uploads, media or transcripts longer than the window you set
  • Share media with third parties beyond the engines you select

Report a vulnerability

If you have found a security problem in Raid AI, email info@raidxai.com with the subject Security report.

  • Tell us the page or endpoint affected and the steps to reproduce it
  • Do not access, change or delete data that belongs to other customers
  • Do not disrupt the service or slow it down for other people
  • Give us time to fix the problem before you publish it

Send us your questionnaire.

Email it to info@raidxai.com. We answer security reviews directly, and would rather do it before you have committed to anything than after.