Data Processing Addendum
The terms that apply when Limnn processes personal data for you: instructions, security measures, sub-processors, breach notification, deletion, audits and international transfers.
Formation and scope
This Data Processing Addendum (“DPA”) forms part of the Terms of Service between Limnn (Private) Limited (“Limnn”) and the customer (“Customer”) and applies whenever Limnn processes Customer Personal Data in providing the Services. It applies automatically when Customer accepts the Terms; customers that need a countersigned copy can request one from legal@limnn.com.
“Customer Personal Data” means personal data in Customer Data that Limnn processes on Customer's behalf. “Data Protection Laws” means laws that apply to that processing, including the EU GDPR, UK GDPR and Data Protection Act 2018, Swiss FADP and US state privacy laws, where applicable. Terms such as controller, processor, data subject and personal data breach have the meanings given in the GDPR.
Roles of the parties
Customer is the controller (or a processor acting for its own controller) and Limnn is a processor (or sub-processor) of Customer Personal Data. Where US state laws apply, Limnn is a “service provider” or “processor” and will not sell or share Customer Personal Data, retain, use or disclose it outside the direct business relationship, or combine it with other data except as those laws permit. Limnn is an independent controller for account, billing, security and website data described in the Privacy Policy.
Processing instructions
Limnn processes Customer Personal Data only on Customer's documented instructions, which are: the Terms and this DPA; Customer's configuration and use of the Services (including the modules, integrations, automations and AI features it enables); and any other written instructions agreed by the parties. Limnn will tell Customer if it believes an instruction breaks Data Protection Laws, and is not required to follow it. Customer is responsible for the lawfulness of its instructions and for having a lawful basis and giving notices for the data it puts into the Services.
Confidentiality of personnel
Limnn ensures that personnel authorised to process Customer Personal Data are bound by confidentiality obligations, and limits access to those who need it to provide, support or secure the Services.
Security
Limnn implements the technical and organisational measures in Annex II and may update them as long as the overall level of protection is not reduced. Customer is responsible for its own configuration: roles, MFA, SSO, IP allow-lists, sharing of file links, call-recording settings and the like.
Sub-processors
Customer authorises Limnn to use the sub-processors listed at Sub-processors & Data. Limnn imposes data protection terms on each sub-processor that protect Customer Personal Data to the standard of this DPA and remains responsible for their performance. Limnn will notify Customer by email at least 30 days before a new sub-processor begins processing Customer Personal Data. Customer may object on reasonable data-protection grounds within that period; the parties will discuss in good faith, and if they cannot resolve it Customer may terminate the affected Services and receive a refund of prepaid fees for the unused period.
Data subject requests and assistance
The Services include tools that let Customer respond to data subjects itself: record editing and deletion, CSV export, a data-subject access report and a data-subject erasure job (Settings → Data management), described at Sub-processors & Data. If Limnn receives a request directly from a data subject about Customer Personal Data, it will refer the person to Customer and not respond itself except to confirm the referral. Limnn will provide reasonable additional assistance with requests that the tools do not cover, with data protection impact assessments and with prior consultations, taking into account the nature of the processing and the information available to Limnn.
Personal data breach notification
Limnn will notify Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data. The notice will describe, as far as then known, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed. Limnn will update Customer as more information becomes available and take reasonable steps to contain and remedy the breach. Notification is not an admission of fault.
Return and deletion
During the subscription Customer can export and delete Customer Personal Data using the Services. After the Terms end, Customer may export its data while the workspace remains available and may ask Limnn to delete the workspace; Limnn will then delete Customer Personal Data from its live systems. Copies in encrypted database backups are deleted when those backups expire on their retention schedule. Limnn may keep data where law requires it, protected under this DPA.
Information and audits
Limnn will make available the information reasonably necessary to demonstrate compliance with this DPA, including by answering a reasonable written security questionnaire once a year. Limnn does not currently hold third-party certifications or audit reports. If the information provided is not sufficient to meet Customer's obligations, or a regulator requires it, Customer may conduct an audit at its own cost, on at least 30 days' notice, during business hours, limited to what is necessary and subject to confidentiality, and without access to other customers' data.
International transfers
Limnn operates globally, and Customer Personal Data may be stored and processed in countries other than the one where Customer or its users are located. Our sub-processors are listed at Sub-processors & Data. To the extent Customer Personal Data subject to EU, UK or Swiss law is transferred to a country without an adequacy decision, the parties agree that the European Commission's Standard Contractual Clauses (Decision 2021/914) are incorporated by reference, Module 2 where Customer is a controller and Module 3 where Customer is a processor, with Customer as data exporter and Limnn as data importer, the optional docking clause included, Clause 11 optional language omitted, the Clause 9(a) general-authorisation option with the notice period in this DPA, and Annexes I and II of this DPA completing the SCC annexes. For UK transfers the UK International Data Transfer Addendum applies, and for Swiss transfers the SCCs apply with the references adapted to the FADP. If the SCCs conflict with this DPA, the SCCs prevail.
Liability, precedence and governing law
Each party's liability under this DPA is subject to the limitations in the Terms, except where Data Protection Laws do not permit that. If this DPA conflicts with the Terms on data protection, this DPA prevails.
This DPA is governed by the law that governs the Terms (the laws of the State of Delaware, USA), except that the Standard Contractual Clauses are governed by the law of Ireland with disputes under them before the courts of Ireland (Clauses 17 and 18), and the UK Addendum by the law of England and Wales. Nothing in this DPA limits the rights of data subjects or supervisory authorities under Data Protection Laws.
Annex I: Details of processing
| Item | Details |
|---|---|
| Subject matter and duration | Provision of the Limnn Services for the term of the Terms and until deletion as described above |
| Nature and purpose | Hosting, storage, organisation, retrieval, transmission, analysis (including AI processing on Customer's request or configuration), and deletion of Customer Personal Data to provide the Services |
| Frequency | Continuous |
| Exporter / importer | Customer (exporter, controller or processor) / Limnn (Private) Limited (importer, processor). Contact: privacy@limnn.com |
Categories of data subjects and personal data, by module
| Module | Data subjects | Personal data |
|---|---|---|
| Account & administration | Customer's users | Name, email, profile details, role, team, manager, sign-in and session data, audit-log entries |
| Sales CRM | Customer's prospects, customers and contacts | Name, work/personal email, phone numbers, job title, company, deal and activity notes, do-not-contact flags, call notes and AI summaries |
| Support & help centre | End customers, website visitors | Name, email, ticket content, chat transcripts, satisfaction ratings |
| Limnn Mail & marketing email | Mailbox users, correspondents, email recipients | Addresses, names, message headers and content, attachments, spam-check results, opens, clicks, unsubscribes |
| Meetings & video | Hosts, invitees, guests, learners | Name, email, phone, time zone, booking answers, notes, audio/video streams, class recordings (if enabled) |
| People / HR & recruiting | Employees, contractors, dependants, candidates | Employment and job data, compensation and payslips, deductions, leave, attendance including clock-in IP address, benefits and dependant details, date of birth, nationality, address, emergency contact, performance reviews and goals, documents, e-signatures with IP address and browser, CVs, cover letters, interview notes, AI screening summaries |
| Learning | Learners, instructors | Progress, quiz and assessment results, certifications, gamification records, discussion posts |
| Limnn Active | Employees and contractors | Time-clock entries; application names, website domains, active/idle time and device details from enrolled devices; derived utilization, focus and workload insights |
| Beam, Workspace & Grid | Users, collaborators, form respondents | Messages, files, documents, sheets, decks, form responses, tasks and comments |
| Gate | Device users | Device name, hardware model and serial, OS, IP addresses, last signed-in user, security posture, remote-session records |
| Billing (Customer's own invoicing) | Customer's customers | Billing contact, invoice and payment records (card data is handled by the payment gateway, not Limnn) |
Special categories. Customer may choose to store special-category data (for example health information in leave records, or data revealing trade-union membership) in HR modules; Customer is responsible for the lawful basis and for restricting access with roles and field-level security.
Annex II: Technical and organisational measures
| Area | Measures |
|---|---|
| Hosting | Secure data centers in the United States for application, database and file hosting, operated by sub-processors listed on the Data page |
| Encryption | TLS for all traffic; database, files and backups encrypted at rest with managed keys; AES-256-GCM application-level encryption of stored third-party credentials (SMTP, telephony, payment-gateway keys) |
| Access control | Authentication with password, Google, Microsoft, magic link and SAML/OIDC SSO; workspace-enforced MFA (all users or admins), required SSO, allowed sign-in methods, IP allow-lists, maximum session age and idle timeout; minimum password length |
| Authorisation | Role-based access control, per-module tiers, field-level security; deactivated users refused at sign-in |
| Tenant isolation | Database-layer scoping of workspace data; AI actions refuse to run without a single workspace scope; AI tools derive workspace from the server session |
| Credentials & keys | API keys stored as SHA-256 hashes, scoped, expiring and revocable; agent device keys and enrollment tokens hashed; staff passwords scrypt-hashed |
| Private storage | Private bucket with short-lived signed links for HR, e-signature, recruiting, call-recording, email and class-recording files, after permission checks |
| Integrity of inputs | Signature verification on inbound webhooks; signed tokens for email tracking and unsubscribe links; CSV-injection protection on exports |
| Availability and resilience | Continuous encrypted backups with point-in-time recovery; web application firewall in front of the application; rate limiting on public endpoints; per-plan API quotas |
| Logging and audit | Infrastructure change logging and continuous threat detection; workspace audit log of administrative and data-export actions; Gate security-action audit; platform staff audit log; error tracking; developer request logs (metadata only, credentials and emails redacted, 30-day retention) |
| Data minimisation | Metadata-only API logging; Limnn Active collects app names and domains only, never screenshots, keystrokes, full URLs or content |
| AI governance | Workspace-scoped prompts with data-containment instruction; risk-tiered agent tools with mandatory human approval for customer-facing or irreversible actions; credit budgets and spend caps |
| Data subject rights | Export, access-report and erasure tooling; Do-Not-Contact suppression list |
| Personnel | Confidentiality obligations; separate authenticated staff console; least-privilege access |
| Incident management | Investigation, containment and customer notification process as set out in this DPA |
Annex III: Sub-processors
The current list of sub-processors, their purposes, data and locations is maintained at Sub-processors & Data and is incorporated into this DPA.
Limnn (Private) Limited. Privacy and data requests: privacy@limnn.com. Billing and account help: support@limnn.com. Security reports: security@limnn.com. Contracts and legal notices: legal@limnn.com.
