Confidentiality is the second thing a competition lawyer asks about. This page states what AEDILE® does and, just as importantly, where the boundaries are. It does not claim any certification.
Deployment models
AEDILE® can be deployed on-premises in the customer’s own infrastructure, as a managed hosted service, or white-labelled for law firms and consultancies. Customers can bring their own model provider keys (BYOK), and self-hosted models are available on request.
Tenant and data separation
One deployment serves one tenant: each deployment runs its own database, so separation between deployments is physical. Inside a deployment, research and document records are scoped to their owner by row-level security in the database, so a signed-in user reads their own rows. This covers the tables that hold research queries and answers and the tables that hold uploaded-document text. Details of the controls in force on your deployment are part of the security briefing.
Access control and sessions
- Users sign in with individual accounts through the platform’s authentication service.
- The browser session is a signed cookie, marked HTTP-only, valid for seven days.
- Conversation history is held in a separate cache with a default lifetime of one hour.
- Administrative functions require an administrator role held in the database. An ordinary signed-in user who calls an administrative route receives a refusal.
- Connections to the platform use HTTPS/TLS, and production servers send a restrictive content-security policy and HSTS.
Where processing happens
Two facts must be kept apart.
Data at rest stays inside the deployment. The database, uploaded files, extracted document text, credentials, cache and the legal library are held inside the deployment, and document extraction and indexing run locally.
Inference leaves it. The model prompt, which is the question text plus the source excerpts needed to answer it, is sent to the configured AI provider. Web-search query text is sent to the configured search provider. Prompts are sent whole: there is no prompt-level confidentiality filter, so the relevant text of an attached document reaches the provider. Under BYOK or BYOM, your own provider accounts and contracts govern what that provider does with it.
| What transits | Destination | Client content? |
|---|---|---|
| Model prompt | Configured AI provider | Yes: question and retrieved excerpts |
| Web-search query | Configured search provider | Yes: query text |
| Public URL fetch | Target public site | No: outbound request only |
| License validation | License server | No: license key only |
Data residency therefore applies to stored data. It does not extend to the prompt sent for inference, and AEDILE® does not describe a deployment as fully isolated from external services.
Logging and audit
Workflow executions and tool calls are recorded in audit tables. The “how this was researched” trail kept for follow-up questions is not exposed in the interface, exports or raw responses.
Output and request safeguards
Error messages shown to users are reduced to fixed, non-technical text. Answer markdown is sanitised in the browser. Server-side page fetches check the destination against private and internal addresses before and after redirects. Known limits of these safeguards are documented internally and can be discussed in a briefing.
What this page does not claim
AEDILE® makes no statements here about third-party certifications, encryption-at-rest, data retention periods or provider contract terms. Those depend on the deployment and the provider arrangements, and are covered in the briefing below.