Security is central to a tool that touches sensitive data. This page describes the controls the Service implements today. We make no claim to certifications we do not hold.
Data isolation & access
- Per-tenant isolation — each user's workspace, datasets and remembered rules are separated; users see only their own data.
- Role-based access control — admin, analyst and read-only roles gate sensitive actions.
- Authenticated sessions with server-side session verification.
AI safety
- Not used for training — your content is never used to train AI models.
- Bring your own key — you can route AI calls through your own provider account.
- Regulated-data mode — restricts AI routing to providers under a data-processing agreement.
- Prompt-injection boundary — untrusted data cannot override the system's instructions.
- Output filtering — model outputs are scanned and leaked secrets are redacted before display.
Integrity & monitoring
- Tamper-evident audit log — a hash-chained record of key actions that detects edits or deletions.
- AI health monitoring & drift evals — model calls are monitored and periodically evaluated for safety regressions.
- Dependency scanning in the build pipeline.
Transport & hosting
Traffic is encrypted in transit via TLS. The Service is hosted on [HOSTING PROVIDER]; [confirm data region and encryption at rest].
Responsible disclosure
Found a vulnerability? Please email ai-datavalidator@outlook.com and allow us reasonable time to remediate before any public disclosure. Thank you.