AI & Compliance

AI that respects your data and your regulators

Agents and AI features are now in demand everywhere, and so are the rules around them. Here's how we build AI responsibly, and the frameworks we design for.

Agentic engineering

Domain-specific agents, built to be trusted

An agent is only useful if people can rely on it. We engineer agents like any critical system: scoped, measured, guarded and auditable.

Scoped

Every agent has a written scope: the tasks it does, the tools it may call, the data it may see, and what it must never do.

Measured

Evaluation sets built from your real cases. Accuracy, refusal and safety are measured before each release, not guessed.

Guarded

Defences against prompt injection, data leakage and tool misuse, following the OWASP Top 10 for LLM applications.

Supervised

A person approves anything consequential: payments, record changes, messages to customers or citizens.

Auditable

Every step an agent takes is recorded: what it saw, what it decided and which tools it used.

Right-sized models

Hosted, open-weight or a mix, chosen for the task, the sensitivity of the data and the budget.

Private AI

No prompt logging, data residency, your infrastructure

Some prompts contain patient records, case files or trade secrets. For that work we keep the whole AI pipeline inside your control.

Discuss private AI
  • Open-weight and open-source models run in your cloud account or on your own hardware.
  • No prompt or response logging: AI traffic can run with prompt and response content kept out of logs; only operational metrics are recorded.
  • Data residency: processing and storage kept in Canada, the US, the EU or the UAE, as your rules require.
  • In-region or air-gapped deployments where data must not leave a jurisdiction or a network.
  • No training on your data: your prompts, files and outputs are not used to train models.
  • Hosted models when they are the better fit, through providers that offer no-retention and no-training terms.
Reference

Compliance frameworks we design for

The frameworks that most often shape AI and software projects in government, healthcare and business. Each links to its official source.

We help you build solutions that support these frameworks. Whether a system complies, and any certification, is determined by your organization, your legal advisers and your auditors.

Global

International

ISO/IEC 27001

Information security management systems.

iso.org →
International

ISO/IEC 42001

AI management systems: governance of how AI is built and used.

iso.org →
Industry

OWASP Top 10 for LLM applications

The main security risks for applications built on language models.

owasp.org →
Industry

PCI DSS

Security standard for systems that handle payment card data.

pcisecuritystandards.org →
Industry

WCAG 2.2

Web accessibility guidelines, required by most public bodies.

w3.org →

United States

Health

HIPAA Security Rule

Safeguards for electronic protected health information.

hhs.gov →
AI risk

NIST AI Risk Management Framework

Voluntary framework for managing AI risks across the life cycle.

nist.gov →
Government

NIST SP 800-53

Security and privacy controls for information systems.

nist.gov →
Government

FedRAMP

Security authorization for cloud services used by US federal agencies.

fedramp.gov →
Business

SOC 2

Trust services criteria for service organizations (security, availability, confidentiality).

aicpa-cima.com →

Canada

Privacy

PIPEDA

Federal privacy law for personal information in commercial activity.

priv.gc.ca →
Government

ITSG-33

IT security risk management for Government of Canada systems.

cyber.gc.ca →
Quebec

Law 25

Quebec's modernized private-sector privacy law.

cai.gouv.qc.ca →
Government

Directive on Automated Decision-Making

Government of Canada rules for systems that support administrative decisions.

canada.ca →

European Union

Privacy

GDPR

General Data Protection Regulation (EU) 2016/679.

eur-lex.europa.eu →
AI

EU AI Act

Regulation (EU) 2024/1689 on artificial intelligence, with duties by risk level.

eur-lex.europa.eu →
Security

NIS2 Directive

Cybersecurity duties for essential and important entities.

eur-lex.europa.eu →

United Arab Emirates

Privacy

UAE Personal Data Protection Law

Federal Decree-Law No. 45 of 2021 on the protection of personal data.

u.ae →
FAQ

Common questions

Can you build AI features that never store our prompts or responses?

Yes. We deploy open-weight or open-source models in your cloud account or on your hardware, configured with no prompt or response logging and with data kept in your region. Where a hosted model is a better fit, we use providers that offer no-retention and no-training terms.

Is D9010 certified for HIPAA, ISO 27001 or SOC 2?

We help you design and build software that supports your compliance program for frameworks such as HIPAA, ISO/IEC 27001 and SOC 2. Certification and attestation are issued to your organization by its auditors.

Can our data stay in Canada, the EU or the UAE?

Yes. We deploy in the region your rules require, including Canada, the United States, the European Union and the United Arab Emirates, or in your own data centre.

How do you keep AI agents safe?

Each agent has a defined scope of tools and data, is measured against evaluation sets built from real cases before every release, is protected against prompt injection and data leakage following the OWASP Top 10 for LLM applications, asks a person to approve consequential actions, and records an audit trail of everything it does.

Do you work with open-weight and open-source models?

Yes. We choose the model that fits the task, data sensitivity and budget, including open-weight and open-source models that you can run privately.

Building AI under strict rules?

Tell us which frameworks apply. We'll show you how we'd design for them.

Talk to us