What is the first pass costing your firm? Run your numbers
Trust centre Trust

Security overview

Version 1.1 · October 2026

What Solicia is

Solicia is an AI paralegal your lawyers instruct by email. Staff send documents and instructions from their existing corporate mailboxes to a Solicia address, and the finished work product comes back by reply in the same thread. A web dashboard provides visibility and administration. Connectors to Microsoft 365 and Google Workspace are optional and enabled with your administrator's consent.

Because the primary interface is your own email, day-to-day identity and access remain governed by your existing identity platform and mail security controls. Only senders your firm has authorised are served. Mail from any other address receives no work and no acknowledgement.

Architecture and data flow

Three tiers, with no traditional corporate network and no on-premises equipment:

  1. Edge: Cloudflare provides DNS, TLS reverse proxy, and always-on network- and application-layer DDoS mitigation for the dashboard and API hostnames. Traffic is encrypted end-to-end to origin, and origins are locked so requests cannot bypass the edge. The email pipeline does not traverse the edge.
  2. Application: Isolated container workloads (Microsoft Azure Container Apps, Australia East / Sydney): API, background workers, dashboard and connector service, deployed as immutable versioned images with revision-based rollback.
  3. Data: Managed PostgreSQL, Redis and blob storage in Azure Australia East, reachable only over the private network. Inbound email is received by AWS SES in Sydney (ap-southeast-2); encrypted database backups are stored in AWS S3 Sydney.

AI inference runs on the Azure OpenAI Service from a resource in Australia East, using Data Zone deployments: processing is confined to Microsoft's Asia-Pacific data zone and is never routed to US endpoints or to OpenAI, Inc. Every model call is made with storage disabled (`store: false`). Customer content is never used to train any model, and that commitment is in your agreement.

Data residency

  • Stored: exclusively Australia (Azure Australia East; AWS Sydney)
  • Processed: Australia; transient AI inference within the APAC data zone (Australia, Japan, South Korea, Singapore, India). Australia-only inference is available on a dedicated provisioned deployment on request, at additional cost.
  • Never: stored in, or persistently processed in, the US, UK or EU
  • Network edge: dashboard and API traffic is proxied through Cloudflare's anycast edge, where TLS is terminated, ordinarily at an Australian point of presence, for transient inspection and DDoS mitigation before re-encryption to origin. Nothing is retained at the edge. Full detail is in the Data Residency & Subprocessor Register.
  • Web research: before a search query is sent to a search provider outside Australia, a sanitiser removes party names, matter identifiers, email addresses, phone numbers, ABN/ACN and street addresses from it. No document is ever sent. See the register.
  • Residency is fixed at the platform level and cannot be changed by any user or configuration.

Backups, recovery and retention

  • PostgreSQL: continuous automated backup with point-in-time recovery for 7 days, held in Australia East.
  • A nightly encrypted logical backup is written to AWS S3 Sydney under a 35-day object lock and expires at 90 days.
  • Blob storage keeps prior file versions for up to 30 days after deletion or overwrite.
  • Raw inbound email held by the mail receiver expires after 7 days. Platform logs are retained for 30 days in Australia East and hold process data only: identifiers, stages, tools, models, timings, token counts, error classes and sizes. No email, instruction, document, filename, address, search query, prompt or model output appears in a log line. A redaction filter enforces this on every record, and a test fails the build if a log statement names a content field.
  • Restore has been verified in practice: on 25 July 2026 the complete production database was restored into new infrastructure with automated verification of schema and record counts, followed by a confirmed live transaction. Restore tests run at least twice a year.
  • Retention of your content is set by your firm (purge on delivery, or any period from 7 days to 10 years); every purge is logged. After a purge, the last copy of deleted content leaves point-in-time recovery within 7 days and the offsite backup within 90 days. On termination, you may export your data during the term and for 30 days after; we delete it from production within 30 days.

Subprocessors

Three cloud infrastructure providers hold infrastructure-level access only, under their standard data protection terms: Microsoft (Azure, including Azure OpenAI), Amazon Web Services and Cloudflare. Two web-research providers (Exa Labs and Microsoft's hosted web search) receive sanitised search queries only. The register lists each provider's head office, delivery region and data-access scope.

Who can see your work

No path in the application lets Solicia staff read customer content. Email bodies, instructions, attachments, documents, generated work product, model prompts and outputs, transcripts and review drafts are bound to the firm's own tenant for every role, including Solicia's administrators. The staff console sees metadata only: task type, status, timings, token and artefact counts and a structured error class. That is what we need to diagnose a failed job. Every staff read of a firm's metadata is written to that firm's own audit log. Where a fix genuinely needs the words, your user sends them to us.

Solicia staff do not access customer content. Access to the production infrastructure is restricted to operating and recovering the service, and every access to Key Vault, storage and the database is logged in Log Analytics.

Security controls

  • Encryption: TLS 1.2+ in transit; AES-256 encryption at rest on every store, including backups, under platform-managed keys. Connector OAuth tokens and MFA secrets are additionally encrypted at the application layer (AES-256-GCM) with a key held in Azure Key Vault (RBAC, soft delete and purge protection). Customer-managed keys are not currently offered.
  • Identity: named accounts only; MFA on all administrative access; quarterly access reviews. Dashboard sign-in supports Microsoft Entra ID single sign-on; a firm can require SSO and disable password sign-in for its users, and pin sign-in to its own Entra directory. Password accounts use bcrypt, breached-password screening and TOTP MFA, which a firm can make mandatory.
  • Tenant isolation: tenant-scoped storage and database access enforced programmatically on every request; cross-tenant requests are refused and audited.
  • Network: data tier has public network access disabled and is reachable only over the private network; Azure OpenAI is reached over a private endpoint with public access disabled; always-on DDoS mitigation at the edge with platform protection beneath it on Azure; origins locked against edge bypass.
  • Email authentication: inbound mail must pass DMARC (or aligned DKIM where no DMARC policy exists) and come from a sender the firm has authorised; the sending domain is DKIM-signed with a custom MAIL FROM; automatic bounce and complaint suppression.
  • AI safety: inbound content is stripped of hidden text and wrapped as untrusted before any model sees it; the model cannot send email. Every result returns to the instructing lawyer's own address, and drafts are staged in the user's own mailbox for a human to send; Azure content filters and prompt shields are applied to every call.
  • Monitoring: AWS GuardDuty (Sydney) and Microsoft Defender for Cloud; centralised logging in Azure Log Analytics with automated alerting on security-relevant events; application-layer audit trail across 60+ event types, tenant-scoped and exportable by your administrators.
  • Development: every change ships via pull request through CI with branch protection: the full automated test suite (16,000+ tests), golden-regression checks, secrets scanning on every commit (gitleaks), a dependency vulnerability gate that blocks on high and critical advisories, static analysis (Semgrep), container image scanning (Trivy), and weekly Dependabot updates. Remediation targets: critical 7 days, high 30, moderate 90.

We have never received a government request for customer information. We disclose only under valid legal compulsion, verify and narrow every request, and notify affected customers unless legally prohibited, in which case we notify as soon as the restriction lapses.

Insurance

Solicia maintains professional indemnity and cyber insurance.