Organization-owned AI controls
AI availability, provider configuration and secret references belong to the organization. Each reporting cycle has a separate switch within that ceiling.
Security & AI
AI can assist the review. It cannot hold the pen.
Repdate keeps professional decisions with named users and places outbound AI behind organization controls, typed tasks, figure masking and an evidence ledger.
Important boundary
Figure masking is not a claim that arbitrary prose can be proven free of financial meaning. New languages and formats require a separately tested policy. Deployment, retention, encryption, subprocessors and certifications must be confirmed for the actual production environment.
Figures stay out of AI requests
The documented english-figures-v1 policy masks numeric figures and supported written-number expressions before outbound AI requests. Unsupported or ambiguous formats are blocked.
Typed, bounded actions
The gateway accepts only approved mapping, statement-review and wording tasks, reconstructs the allowed request and rejects added tools, messages or endpoint changes.
Advisory output only
AI can propose or question. It cannot calculate, approve, change review status or alter a report without a named user decision.
Evidence before transmission
The evidence ledger records the sanitized request, policy version, validation state, provider outcome, latency and token usage before transport.
Managed credential boundary
Production AI credentials must use an organization-scoped managed secret reference. Development fallbacks are not accepted in production.
Access and evidence
Controls must be inspectable.
Authentication, organization membership, team access, reporting roles and server-side authorization protect the working boundary. Immutable artifact versions and audit events preserve what the application saw and what people decided.
What the evidence shows
Application-visible requests, attempts, responses, validation outcomes, review decisions and reporting events.
What it does not claim
Database-only evidence is not tamper-proof against database administrators, and a transmission attempt does not prove a provider received it.
Start with one recurring report
See how Repdate would handle your reporting cycle.
Bring the shape of one Word report, its approved workbook output, and the review steps your team follows today. No sensitive files are needed for the first conversation.