Security at Limnn

Limnn runs your CRM, support, HR, finance and team chat on one shared record, which makes it some of the most important data your company holds. We protect it accordingly. Because every product sits on the same platform, each safeguard is built once and applies everywhere: one identity layer, one permission model, one audit trail.

Our principles are simple: least privilege by default, defense in depth, and controls your admins can see and configure for themselves.

• Encryption in transit. All traffic to Limnn, including the web app, mobile apps and API, is encrypted with TLS.
• Encryption at rest. Customer data, files and backups are encrypted at rest with industry-standard AES-256.
• Key management. Encryption keys are held in a dedicated managed key service, separate from the data they protect, with access tightly restricted and logged.
• Sensitive credentials. Secrets you connect to Limnn, such as mail server passwords and payment API keys, get an additional layer of application-level encryption and are never sent back to the browser. API keys are stored only as one-way hashes.
• Private files. HR, e-signature, recruiting and recording files are served only through short-lived, permission-checked links.
• Tenant isolation. Every request is scoped to a single workspace at the data layer, so one customer's data is never reachable from another's.

• Single sign-on with SAML and OIDC, plus Google and Microsoft sign-in.
• Multi-factor authentication, which admins can require for everyone or for administrators only.
• Workspace security policies: IP allow-lists, required SSO by domain, allowed sign-in methods, session age limits and idle timeouts.
• Roles and permissions: system and custom roles with per-product access levels, plus field-level permissions that hide or lock individual fields by role.
• Admin controls: deactivate users instantly, scope and expire API keys, and revoke devices at any time.
• Limnn personnel reach customer environments only when needed to operate the service, through separate, audited administrative tooling. Staff cannot sign in as your users.

• US data centers. Limnn is hosted with leading cloud providers in secure data centers in the United States, with physical security, power and network redundancy managed to their standards.
• Redundancy. Services are built to recover quickly, and continuous backups with point-in-time recovery protect against data loss.
• Monitoring. Infrastructure and application activity are monitored continuously for errors, anomalies and suspicious behavior, with automated alerts to our team.
• Backups. Your data is backed up continuously and automatically, encrypted, and protected by point-in-time recovery, so the service can be restored to a known-good state after an infrastructure failure.
• Edge protection. A web application firewall and layered rate limiting sit in front of the service to absorb abusive traffic.

• Secure development lifecycle. Every change passes automated tests, type checks and security checks before it reaches production.
• Dependency scanning. Third-party packages are monitored for known vulnerabilities and patched promptly.
• Rate limiting and quotas on public endpoints and the API protect against abuse and brute-force attempts.
• Browser protections, including a Content Security Policy and secure cookie settings.
• Verified integrations. Inbound webhooks are signature-checked before they are processed, and exports are sanitized against spreadsheet injection.
• Secrets management. Credentials and keys live in the hosting environment, never in source code.

• The workspace audit log records administrative activity: invitations and removals, role and permission changes, setting changes, integrations, exports and data-subject requests.
• Limnn Gate keeps its own trail of device security actions such as remote sessions, isolation, lock and wipe.
• API request logs with trace IDs help your developers investigate integrations.
• Configuration restore points let admins roll back changes to settings, pipelines and rules.

Cortex works only inside your workspace and respects each user's permissions. Customer-facing or irreversible AI actions always wait for human approval, and AI spend is capped by workspace budgets. Details are in AI & Cortex Data Use.

We follow a documented incident response process to detect, triage, contain and resolve security events. If an incident affects your data, we will notify you without undue delay with the information you need to meet your own obligations, as set out in our DPA.

• Standard plans retain workspace history for up to 6 months.
• Enterprise retains history for up to 1 year, with the option to keep it forever.
• Retention is controlled by your admins, and data can be exported at any time.
• Permitted users can delete records, admins can erase a person for data-subject requests, and a workspace owner can request permanent deletion of the whole workspace. See Sub-processors & Data.

Our security program is built around the controls in SOC 2 and the requirements of GDPR, and every customer can sign our Data Processing Addendum. Formal third-party audits are planned. Limnn does not hold a security certification today; we will publish any we obtain on this page.

Security is a partnership. We recommend turning on SSO and MFA, reviewing roles and field permissions regularly, using IP allow-lists for sensitive teams, protecting API keys and shared links, and removing users promptly when they leave.

If you believe you have found a vulnerability, email security@limnn.com with steps to reproduce. Please give us reasonable time to fix it before disclosing publicly, and do not access other customers' data or disrupt the service. We will acknowledge your report, keep you updated, and will not pursue action against good-faith research.