Compliance Guidelines

Built for DPA 2024 from day one.

Tiro Motlhofo is designed so that compliance with Botswana's Data Protection Act 2024 is a property of the platform, not a checklist your team has to remember.

Tenant isolation by default

Row-level security is enforced at the database, not just the app. A tenant can never read or write another tenant's rows — even if application code has a bug.

PII redaction at the edge

Omang national IDs, +267 phone numbers, card numbers and emails are stripped from every prompt before it leaves our servers to an AI provider.

DPA 2024 audit log

Every AI call is recorded with the tool used, the model, token counts and a SHA-256 hash of the prompt — enough to prove processing without storing the plaintext.

72-hour breach register

A dedicated breach register keeps you audit-ready under DPA s.74. If we detect an incident, it is logged immediately and the IDPC notification window is tracked.

Least-privilege access

Roles are stored in a separate table checked by a SECURITY DEFINER function. There is no client-side privilege check — the database is the source of truth.

Prompt-injection defence

System prompts are server-only and cannot be overridden by user input. Tool identifiers are validated against an allow-list before any model call.

Data residency & sub-processors

Tenant data is stored in a managed PostgreSQL instance. AI inference is routed via the Lovable AI Gateway to model providers under contract. A current sub-processor list is available to Enterprise customers on request.

Your responsibilities

  • • Appoint a Data Protection Officer and record their email in your workspace settings.
  • • Sign the Data Processing Agreement before enabling production workloads.
  • • Review the audit log at least quarterly and export it for your internal records.
  • • Notify us within 24 hours of any suspected breach on your side.