Lexnavi Trust Centre

Security, privacy and architecture you can rely on

Compliance and risk teams, and independent law firms, handle sensitive information. The Lexnavi platform is designed around three principles: data hosted in Turkey, professional secrecy, and strict separation of customer data.

Hosting in Turkey

The platform runs in data centres located in Turkey, with data residency in line with Turkish regulation.

Full compliance with KVKK Article 9 (cross-border data transfers)

A dedicated database for each customer

Each company has its own physically separate, file-based database, kept apart from other customers' data. There are no shared tables.

Physical file locks

Attorney-client confidentiality

Built around Article 36 of the Turkish Attorneyship Law (No. 1136), which sets out the lawyer's duty of professional secrecy. Different law firms are kept apart, and a previous law firm's confidential material stays protected when a company changes its law firm.

Privacy by design

No AI training on your data

Customer and company data is never used to train or fine-tune any AI model.

Human review of every legal assessment

1. Data residency and infrastructure

Lexnavi is designed for organisations with demanding regulatory requirements. The servers running the Lexnavi platform are located in Turkey.

  • Hosting in Turkey: The platform infrastructure runs within Turkey, with data residency in line with Turkish regulation.
  • No advertising or behavioural tracking: The Lexnavi platform does not use third-party analytics or advertising cookies that track user behaviour.
  • Separated environments: Production systems and the regulatory data feed run in separate environments, isolated from each other.

Deployment models: cloud and on-premises

Lexnavi offers two flexible models for companies:

Cloud (SaaS):
Your data is stored in isolated databases in Turkey, with 256-bit encryption and regular backups.
On-premises:
Company operational data stays on your own servers. Lexnavi servers hold only what is needed for sign-in (authentication).

2. Attorney-client confidentiality and professional secrecy

Under Article 36 of the Turkish Attorneyship Law (No. 1136), lawyers in Turkey have an absolute duty to keep their clients' affairs confidential. Lexnavi is built to support that duty with technical safeguards:

Separate access for each law firm

If your company works with several law firms, each firm sees only the departments, data and tasks it has been authorised to see. Firms cannot see that the other firms exist, or read their correspondence.

Protection when you change law firm

If you stop working with a law firm, that firm's legal opinions and internal messages in the Legal Desk (Hukuk Masası) are not opened to the new law firm. Not even company users can pass them on by copying them within the system.

No administrative access by Lexnavi staff

Lexnavi technical and operational staff cannot access the content of customers' Legal Desk opinions, confidential company profile data, or the case and contract attachments customers upload.

3. AI assurance and data protection

No training on customer data: Company correspondence, audit findings, task notes and client documents uploaded to the platform are never used to train or fine-tune any public or private AI model.

AI is limited to scanning regulatory announcements, summarising legal provisions and drafting general checklist templates. Company-specific identifiers and profile data are not sent to AI services.

Human review before publication (human-in-the-loop)

Our AI agents monitor the Official Gazette and announcements from regulators around the clock. But every impact analysis, penalty risk and legal risk alert must be approved by Lexnavi's team of lawyers and legislation analysts before it goes live on the platform.

Fixed-rule calculations: Legal risk is calculated from the text of the law using fixed, objective formulas, not predicted by a general-purpose AI model. The same inputs always give the same result.

4. Cryptographic integrity and audit trail

TLS 1.3 and HTTPS

All traffic between your browser and our servers is encrypted with TLS 1.3.

AES-256 encryption at rest

Customer databases and system backups are encrypted with AES-256.

SHA-256 proof records

Contract approvals, KVKK consents and user commitments are recorded with a timestamp and a SHA-256 cryptographic digest, so any later change can be detected.

Backups and disaster recovery

A snapshot is taken before every release, and isolated disaster-recovery backups are made regularly.

Legal policies and e-contracts

Our policies, user agreements and privacy notices are publicly available: