Security

AES-256 encryption at rest. TLS 1.2+ in transit. Database backups encrypted to the same standard. Nothing leaves our systems in plaintext.

Juriton uses large language models as part of its intelligence layer. Every provider we use is contractually barred from training on your data. Content sent for processing is held by the provider only for a fixed abuse-monitoring window of 30 to 55 days depending on the provider, then deleted. We name each provider and its terms on request.

Your documents, matter data and backups are stored in Sydney on AWS infrastructure, and our application servers run in Sydney too. AI processing of document content happens with named providers outside Australia, under the no-training terms above, and is not stored there beyond the provider's monitoring window.

Dependency advisories are reviewed and patched, with high-severity fixes shipped within days. Internal security reviews in April, May and July 2026 tracked every finding to closure. An external penetration test is the next item on our security roadmap.

Juriton operates a multi-tenant architecture with strict tenant-level isolation. Every firm is a completely separate tenant. There is no cross-tenant data sharing of any kind.

Our hosting and database providers monitor the platform around the clock. On top of that we review dependency advisories, run database security checks after every schema change and route error telemetry and alerts to the team, with incident runbooks ready for each scenario.