Security and trust at AILeakShield

AILeakShield exists to keep sensitive data out of AI, so we hold ourselves to the same standard. This page explains where AILeakShield runs, how we protect your data, what we store and what we do not, and how we prove it every year.

At a glance
  • Hosted on Microsoft Azure, whose data centers are independently audited for SOC 1, SOC 2 and SOC 3, ISO 27001 and more.
  • Encrypted in transit with TLS 1.2 or newer and encrypted at rest.
  • Blocked prompt content is never stored, and the browser extension does not store prompt text at all.
  • We assess our own controls against the SOC 2 Trust Services Criteria every year and share an annual security attestation with customers.
  • We sign HIPAA Business Associate Agreements.

Infrastructure and hosting

The AILeakShield platform runs on Microsoft Azure in North America: the application, the database, secret storage and logging. Microsoft maintains independent SOC 1, SOC 2 and SOC 3 reports, ISO/IEC 27001 certification and a HIPAA Business Associate Agreement for the Azure services we use, so the physical data center, hardware and network layers are covered by Microsoft's audited controls.

Encryption in transit

Every connection to AILeakShield uses HTTPS with TLS 1.2 or newer, and browsers are told to use HTTPS only (HSTS). Connections between the application and its database also require TLS.

Encryption at rest

Our database storage and backups are encrypted at rest by Azure. Integration credentials that partners connect, such as RMM API secrets, are encrypted again at the application layer.

Secrets management

Application secrets live in Azure Key Vault and are read by the application through a managed identity, not stored in code. Access tokens we issue, such as enrollment and feed tokens, are stored only as one-way hashes.

Backups

The database is backed up automatically every day, with point-in-time restore for the last seven days.

Logging and monitoring

Application and platform logs are centralized in Azure Log Analytics, where they are retained, searched and monitored for security events, with alerting and reporting. Credentials and tokens are redacted from request logs.

Application security

Rate limiting, request size limits, protection against server-side request forgery, strict security headers and automated tests on every deployment.

What we store, and what we do not

The less sensitive data we keep, the less there is to protect. AILeakShield is designed so that the data it is protecting does not end up stored with us.

We do not store

  • The content of prompts that were blocked. A blocked prompt is recorded only as a decision and a category, such as "credentials".
  • Prompt text from the browser extension. It is inspected in memory and discarded; only the decision, category and site are logged.
  • Your prospects' raw DNS or proxy logs from a shadow AI assessment. Rows are processed in memory and only the summary report is kept.

We do store

  • Event records for your admins: the decision, category, AI site or model, user and time.
  • Short previews of prompts sent in the optional AILeakShield secure AI workspace, which are automatically deleted after 24 hours. Admin views show masked previews.
  • A justification when someone chooses to send a warned prompt anyway, deleted after 24 hours with the previews.
  • Account and configuration data such as users, policies and settings.

Access control and tenant isolation

  • Single sign-on with Microsoft Entra ID, so your own MFA and conditional access policies apply. Email sign-in links are limited to work email domains.
  • Role-based access for end users, organization administrators and partners, with short-lived sessions that are revoked at sign-out.
  • Tenant isolation on every request: each organization's data is scoped to the signed-in user's own organization.
  • Partners manage configuration, not content. An MSP can deploy and configure AILeakShield for a client but cannot read that client's prompts, events or audit records. This boundary is covered by automated tests that run on every release.
  • Audit logging of administrative actions, such as sign-ins, role changes, policy changes and connected integrations, visible to your administrators.

The browser extension

The AILeakShield extension runs only on the AI sites it protects, such as ChatGPT, Claude, Gemini, Microsoft Copilot and Perplexity, and on AILeakShield's own sites. It does not run on the rest of the web, does not execute remote code, and asks for only the permissions it needs. If it cannot reach AILeakShield, an on-device copy of your block rules keeps blocking high-risk data such as credentials and payment card numbers.

Compliance and assurance

Annual SOC 2-based assessment

Every year we assess our own controls against the AICPA SOC 2 Trust Services Criteria for security, availability and confidentiality, and track remediation of anything we find.

Annual security attestation

Customers and partners can request our annual security attestation package under NDA. It includes our latest penetration test results, vulnerability scan results and our security policies.

HIPAA

We sign Business Associate Agreements with covered entities and business associates, and AILeakShield helps you keep protected health information out of AI tools.

Subprocessors

We use a small number of providers to run AILeakShield:

ProviderPurpose
Microsoft AzureHosting, database, secret storage, logging and transactional email
Microsoft Entra IDSingle sign-on
SupabaseEmail sign-in links (stores the email address used to sign in)
OpenAI and AnthropicAI models for the optional secure AI workspace only. Prompts are inspected and filtered by your policy before they are sent.

Report a security issue

If you believe you have found a security vulnerability in AILeakShield, email security@aileakshield.com. We review every report and will work with you on responsible disclosure.

Frequently Asked Questions

Where is AILeakShield hosted?

On Microsoft Azure in North America. The application, database, secret storage and logs all run in Azure.

AILeakShield runs on Microsoft Azure, which is independently audited for SOC 2. We also assess our own controls against the SOC 2 Trust Services Criteria every year and share an annual security attestation, including penetration test and vulnerability scan results, with customers under NDA.

Yes. Data is encrypted in transit with TLS 1.2 or newer and encrypted at rest in Azure, and integration credentials are encrypted again at the application layer.

Blocked prompt content is never stored, and the browser extension does not store prompt text at all. In the optional secure AI workspace, short previews are kept for 24 hours and then deleted automatically.

Yes. We sign Business Associate Agreements with covered entities and business associates.

Contact us to request our annual security attestation package. It includes our latest penetration test results, vulnerability scan results and security policies, shared under NDA.

Say yes to AI, safely.

AILeakShield discovers all the AI in your environment, blocks the AI tools you have not approved, and keeps sensitive data out of the prompts sent to the ones you have.