Beyond Gate, the platform itself provides the controls administrators use to keep workspace data safe and prove it. This article maps those controls to where you configure them.
Audit logs
Open /settings/audit to review a chronological record of sensitive actions: role and permission changes, user invitations and deactivations, integration and API key changes, exports and administrative setting edits. Filter by actor, action type and date range.
- 1Go to /settings/audit.
- 2Filter by the actor or action you are investigating.
- 3Open an entry to see the target record and the time.
- 4Export the filtered view when you need to hand evidence to an auditor.
Encryption and hosting
- Data in transit is protected with TLS on all app and API traffic.
- Data at rest is encrypted in the managed database and object storage that hold your records and files.
- Secrets such as integration credentials are stored server-side and not exposed to the browser.
- API keys are stored hashed, so a key is shown once when created and cannot be recovered later.
Access hardening
- /settings/security - idle timeout, maximum session age, enforced two-factor, allowed sign-in methods, required SSO and IP allow-list (see Workspace security policies).
- /settings/developer/api-keys - create scoped service keys with an expiry, rotate and revoke; rotate on staff changes.
- /settings/roles and /settings/field-access - least privilege and field-level protection.
- /settings/retention - record a retention period and legal-hold flag per object for your records policy.
- /settings/data-management - CSV exports, data-subject access reports and data-subject erasure.
Data-subject requests
Under /settings/data-management an admin can produce a data-subject access report (JSON) for an email address, or erase a person. Erasure anonymises their contacts and leads in place and redacts related ticket and activity text, so linked deals and tickets keep their history without the personal data.
AI and your data
Cortex runs on Anthropic's Claude through Anthropic's commercial API. Google Gemini handles embeddings, some media generation and some lighter tasks. Neither provider trains its models on this data. Anthropic keeps API inputs and outputs for up to 30 days for trust and safety review. Limnn does not have a zero-data-retention agreement with Anthropic. Cortex only reads data the current user is permitted to see, including field-level rules. See AI data protection & guardrails for detail.
Log retention
- Developer API request and webhook delivery logs are kept for 30 days.
- Daily API usage counters are kept for 90 days.
- Removed users are deactivated, never deleted, so the audit trail stays intact.