Your business data deserves a clear explanation. Here is how the product is designed, and what we review with you before connecting your systems.
01 / SOURCE ACCESS
Read-only analytics
The query path validates SQL before execution and authorises access to the selected sources. Source database accounts should be configured with read-only permissions. Deployment credentials and network access are reviewed during onboarding.
02 / TENANT BOUNDARIES
Scoped to the business
Tenant identities are restricted to their assigned data sources. Platform administration is a separate capability. Current role controls govern application capabilities; do not assume per-role column masking or custom data restrictions without a separate review.
03 / AI PROCESSING
Know what is processed
The product uses configured AI providers to interpret questions and build answers. Depending on configuration, prompts can contain business context and data. Provider processing, retention and hosting arrangements must be confirmed for your deployment.
04 / ANSWER CONTEXT
Review the evidence
Answers can include source scope and reporting context. The engine checks results and can ask for clarification. AI output should be reviewed for consequential decisions; the product does not promise perfect accuracy.
What we confirm before rollout
Supported source systems, read-only credentials and connectivity.
Business definitions, representative questions and expected answers.
User and administrative access, source scope and deployment configuration.
AI provider handling and any specific organisational requirements.
WhatsApp or voice dependencies when those capabilities are included.
This page describes product design, not an independent security certification or a contractual service-level agreement. Deployment-specific commitments belong in your agreed service documentation.