Security

Security is designed in, not added on

Lextree is compliance software built to hold the record that proves an organization met its obligations — the filing that went out, the resolution the board passed, the license that stayed current. A record like that is only worth keeping if it can be trusted, so security was never a later phase or a premium tier. It is the condition for the product working at all.

That shapes how the platform is built. Every request runs through the same permission and tenant boundaries. Every change to a record is written to its history in the same breath as the change itself. The result is a system where “who did what, and when” is not a feature you switch on — it is simply how the data behaves.

Certified facilities, honest claims

We’ll tell you plainly what we have and what we don’t. Lextree does not hold a SOC 2 report or an ISO certification of its own, and we won’t imply that it does. What we can show you is concrete and verifiable: the infrastructure we run on, the measures written into our Data Processing Agreement, and the controls described on this page.

The infrastructure is genuinely audited. Lextree runs on DigitalOcean, whose platform is certified to SOC 2 Type II and whose data centers carry ISO 27001, among other attestations. We inherit those physical and environmental controls, then build the application controls on top.

Fewer places to fail

Lextree is one focused platform, not a general-purpose toolkit you assemble yourself. The data model, the permissions, and the audit trail are built together, not bolted on separately — so there are fewer seams for a mistake to slip through, and fewer settings you have to get exactly right to stay secure.

How your data stays protected

Encrypted at every step

Everything moving between you and Lextree travels over TLS 1.2 or higher, and browsers are instructed to refuse anything less. Connections between the application and its database are encrypted the same way. Data at rest sits on managed, encrypted infrastructure using AES-256, and backups inherit that same protection. There is no point in the path where your records travel or rest in the clear.

Isolated by a tenant boundary

Every record in Lextree belongs to a subscriber, and every query that reads data is scoped to the subscriber making it. One customer cannot see another’s entities, documents, or people — the boundary is applied as data leaves the database, so unauthorized records are never returned in the first place. For organizations with regional requirements, Lextree offers data residency in the United States or the European Union.

Backed up and recoverable

Your data is backed up on managed infrastructure with point-in-time recovery, so a bad import or an accidental deletion can be rolled back to a moment before it happened rather than reconstructed from memory. Backups are encrypted and held apart from the live database, and retired copies are purged on a defined schedule after an account closes.

Access, permissions, and audit

Role-based, down to the record

Access in Lextree is layered. Users hold roles at the organization level, editor or viewer rights at the module level, and — on plans that include it — record-level access groups that wall off the most sensitive material, like ownership, trust, or employment data. These permissions are not advisory. They’re compiled into the database query itself, so a user never receives a record their role doesn’t permit.

An automatic change trail

Every create, update, and delete is logged automatically, in the same database transaction as the change, recording who made it, when, and exactly which fields moved. Because the logging happens at the database layer rather than in application code, nothing an ordinary user does can slip past it. Full audit-history access and extended retention are part of the Enterprise plan. Sign-in events are recorded separately, with device and IP address.

Built against the OWASP Top 10

The OWASP Top 10 is the industry’s consensus list of the ways web applications actually get breached. We treat it as a build standard, not a badge. Here is how Lextree’s engineering maps to the current 2025 list.

Secure by default

The safe path is the default path. Sign-in is passwordless — Lextree never stores a password that could be stolen — and multi-factor authentication is available on top. API keys are high-entropy, hashed, and revocable at any time. The application ships with security headers on, a strict host allowlist, and secrets supplied only through the environment, never checked into code.

Watched and kept current

Dependencies are pinned to exact, hash-verified versions and monitored for new advisories automatically, so a vulnerable library surfaces as a pull request rather than a surprise. The public API is rate-limited per account to blunt abuse, and production activity is written to dedicated application, access, and error logs.

Your data remains yours

Export and deletion

Your records are yours to take. Lextree provides export tools while your account is active, and when an agreement ends, we make your data available for export before removing it from production systems. Encrypted backup copies age out within ninety days. We process your data only to run the service — never to build a product of our own on top of it.

Breach notification in writing

If a security incident ever affects your data, our Data Processing Agreement commits us to notifying you within seventy-two hours — not as a courtesy, but as a contractual term. That same agreement lists the technical measures we maintain and the Standard Contractual Clauses that govern international transfers. Our sub-processor list names every third party that touches your data before we ever add another.