Skip to content
Assess My Entity Operations
Security

Protect sensitive entity data with clear access, auditability and customer control.

Legal-entity records can contain sensitive corporate, ownership and governance information. Entiti is designed around controlled access, traceable change and customer data control.

View security principlesAssess My Entity Operations
Clear access boundariesReviewable audit historyCustomer control over sensitive data
How we approach it
  1. AccessLeast privilege by design
  2. EvidenceMake controls reviewable
  3. ControlKeep customers in charge

The controls behind each of these are listed below.

Trust architecture

Security should be clear before sensitive entity data enters the platform.

Entity data often moves across Legal, Tax, Finance, advisors and service teams. Clear access boundaries, auditability and customer control help each team work without exposing more information than necessary.

Access

Least privilege by design

Use role-, portfolio- and entity-level access patterns to support both enterprise teams and multi-client service providers.

Evidence

Make controls reviewable

Maintain clear audit history and security documentation so security and procurement teams can review how the service protects customer information.

Control

Keep customers in charge

Keep customer data portable, make retention and deletion processes clear, and support enterprise identity requirements as the service matures.

Our approach to security claims: certifications and service commitments are published only when they are achieved and supportable. Security information should remain specific, current and reviewable.

Security controls

How the platform protects entity data.

Access control
Role- and scope-based permissions define which users can see, change or export each class of information.
Auditability
Material actions create a traceable history of who changed what, when and from which prior value, so approved records are not silently overwritten without history.
Data protection
Encryption in transit and at rest, documented backup and recovery, clear tenant isolation and documented hosting / data-residency boundaries. Region-specific hosting is described only where it is technically and contractually supported.
Enterprise identity
Support SSO/SAML and enterprise identity requirements as larger deployments mature.
Customer control
Customers keep control of their data, with clear export, retention, deletion, subprocessor and applicable data-location information.
Security evidence
Provide reusable security and architecture information so diligence can start with clear evidence.

Security transparency

Certifications, data-residency options and service-level commitments will be shown only when they are independently true and supportable.