Data Processing Agreement
Last updated: July 2026
This Data Processing Agreement (the "Agreement") is entered into between the Customer (as identified in the main agreement) as data controller and Lexera AS, org. no. 937 286 554, as data processor, in accordance with the General Data Protection Regulation (GDPR) Article 28. The Agreement forms an integral part of the main agreement for the use of the Lexera platform.
1. Parties and Definitions
Data Controller ("Customer"): The organisation that has entered into the main agreement for use of the Lexera platform, and which determines the purposes and means of processing personal data.
Data Processor ("Lexera"): Lexera AS, org. no. 937 286 554, Tordenskiolds gate 2, 0160 Oslo, Norway, which processes personal data on behalf of the Customer.
"Personal data" means any information as defined in GDPR Article 4(1). "Processing" means any operation as defined in GDPR Article 4(2). "Applicable data protection legislation" means GDPR and the Norwegian Personal Data Act.
2. Instructions (Art. 28(3)(a))
2.1 Lexera processes personal data only on the Customer's documented instructions. Use of the service in accordance with this Agreement, the main agreement, the terms of service, and the Customer's configuration of the platform constitutes the Customer's documented instructions.
2.2 Lexera shall not process personal data for its own purposes or for third-party purposes, except as required by applicable law. If Lexera is legally required to process the data, the Customer shall be notified in advance, unless such notification is prohibited by law.
2.3 If Lexera receives an instruction that in our assessment conflicts with GDPR or other applicable data protection legislation, we will inform the Customer without undue delay and suspend the relevant processing until the Customer confirms or modifies the instruction.
2.4 The scope of processing, including categories of personal data, categories of data subjects, the nature and purpose of processing, and retention periods, is described in detail in Appendix 1.
3. Confidentiality (Art. 28(3)(b))
Lexera ensures that all persons authorised to process personal data on behalf of the Customer are subject to statutory or contractual confidentiality obligations. The confidentiality obligation survives termination of the employment or contract relationship.
All employees and contractors at Lexera who have access to personal data have completed training in data protection and information security, and have signed confidentiality agreements covering the processing of customer data.
4. Security Measures (Art. 28(3)(c) / Art. 32)
Lexera implements appropriate technical and organisational measures to ensure a level of protection appropriate to the risk of the processing, in accordance with GDPR Article 32. The measures shall, at minimum, cover:
- Encryption of data in transit (TLS 1.2+) and at rest (AES-256)
- Access control with OAuth 2.0, role-based access control (RBAC), and multi-factor authentication via the organisation's identity provider
- Firewall rules and strict access restriction in the Azure infrastructure
- Continuous monitoring, logging, and alerting for security anomalies
- Regular security testing, penetration testing, and vulnerability assessments
- Automated backup with geographic redundancy
A detailed description of security measures is available in Appendix 2 and on our security page (lexera.no/en/security). Lexera may update security measures over time, provided the overall level of security is not materially reduced. The Customer shall be notified of material changes.
5. Sub-processors (Art. 28(3)(d))
5.1 The Customer grants Lexera general written prior authorisation to use sub-processors. An up-to-date list of approved sub-processors is available in Appendix 3.
5.2 Lexera imposes on all sub-processors data processing agreements providing at least the same level of protection as this Agreement, in accordance with GDPR Article 28(4). Lexera remains fully liable to the Customer for the sub-processors' fulfillment of their obligations.
5.3 When adding or replacing a sub-processor, Lexera will notify the Customer at least 14 days in advance. The Customer may object to the change within 14 days of notification.
5.4 If the Customer objects, the parties will cooperate in good faith to find a solution, such as using an alternative sub-processor. If agreement cannot be reached within 30 days, the Customer may terminate the main agreement effective from the date the new sub-processor was planned to be deployed.
5.5 Lexera shall take appropriate measures to verify that sub-processors comply with their obligations, including review of security certifications, audit reports, and data processing agreements.
6. Data Subject Rights Assistance (Art. 28(3)(e))
6.1 Lexera assists the Customer in fulfilling its obligations to data subjects exercising their rights under GDPR Chapter III, including the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20), and objection (Art. 21).
6.2 If Lexera receives a request directly from a data subject, we will forward the request to the Customer within 5 business days and will not respond to it ourselves unless the Customer has instructed us otherwise.
6.3 The platform provides the Customer's administrators with applications for exporting user data and deleting users. For requests requiring manual assistance, Lexera will respond within 5 business days.
7. Breach Notification (Art. 28(3)(f))
7.1 In the event of a personal data breach, Lexera will notify the Customer without undue delay and no later than 24 hours after becoming aware of the breach, enabling the Customer to fulfil its notification obligation to the supervisory authority within 72 hours (GDPR Art. 33).
7.2 The notification will include: (a) a description of the breach, including categories and approximate number of affected data subjects and data records, (b) the name and contact details of Lexera's contact point, (c) a description of likely consequences, and (d) a description of measures taken or proposed to address the breach and mitigate potential adverse effects.
7.3 Lexera will document all personal data breaches, including the facts, consequences, and remedial actions, and make the documentation available to the Customer upon request.
8. DPIA and Prior Consultation Assistance (Art. 28(3)(f))
Lexera assists the Customer in carrying out data protection impact assessments (DPIAs) and any prior consultation with the supervisory authority (Art. 35–36), to the extent necessary based on the nature of the processing and available information.
The Lexera platform includes applications for conducting DPIAs as part of the application assessment process. Lexera will, upon request, provide the Customer with necessary information about processing activities to support the Customer's DPIA.
9. Deletion and Return (Art. 28(3)(g))
9.1 Upon termination of the main agreement, the Customer shall within 30 days choose between: (a) return of all personal data in a structured, machine-readable format (JSON/CSV), or (b) deletion of all personal data.
9.2 If the Customer does not provide instructions within 30 days of termination, Lexera will delete all personal data within 90 days of termination. Lexera will provide written confirmation that deletion has been completed.
9.3 Exceptions: Audit logs may be retained for up to 3 years after termination if required by applicable law (e.g., the Norwegian Bookkeeping Act). Automatic backups are retained for up to 7 days and then automatically deleted.
10. Audit and Inspection (Art. 28(3)(h))
10.1 Lexera makes available all information necessary to demonstrate compliance with the obligations in this Agreement and GDPR Article 28. The Customer has the right to conduct audits or inspections, either directly or through an independent third party, provided that: (a) the audit is agreed upon at least 30 days in advance, (b) it is conducted during normal business hours, and (c) the auditor is bound by a confidentiality agreement.
10.2 Lexera will provide reasonable assistance during audits. The Customer bears its own costs related to audits, unless the audit reveals a documented breach of this Agreement by Lexera. Audits may normally not be conducted more than once per 12 months, unless there are reasonable grounds to suspect non-compliance.
10.3 Lexera may alternatively present an independent audit report (e.g., SOC 2 Type II) as documentation of compliance, if the Customer accepts this as sufficient.
11. International Transfers
11.1 Lexera's primary data processing takes place in the EU/EEA (Microsoft Azure, Norway – the Norway East region). All storage of personal data takes place within the EU/EEA.
11.2 For AI assistance, Anthropic Ireland, Ltd (with processing in the USA) is used as a sub-processor. Transfers to the USA are based on EU Standard Contractual Clauses (SCCs) adopted by the European Commission on 4 June 2021, in accordance with GDPR Article 46(2)(c).
11.3 For email notifications, Resend Inc. (USA) is used as a sub-processor, also with SCCs as the transfer basis.
11.4 Lexera has conducted a Transfer Impact Assessment (TIA) for all transfers to third countries, and will upon request assist the Customer with information necessary for the Customer's own TIA.
12. Liability
12.1 Lexera is liable for damage caused by processing that violates GDPR or this Agreement, in accordance with GDPR Article 82. Lexera shall be exempted from liability if it is established that Lexera is in no way responsible for the event giving rise to the damage.
12.2 If a sub-processor causes damage, Lexera is liable to the Customer as if Lexera itself had performed the processing, cf. GDPR Article 28(4).
12.3 The liability amount under this Agreement is limited in accordance with the liability limitations in the main agreement, unless mandatory legislation dictates otherwise.
13. Governing Law and Jurisdiction
This Agreement is governed by Norwegian law. Disputes arising in connection with the Agreement shall be sought resolved through negotiations. If negotiations do not lead to resolution within 30 days, the dispute shall be decided by the Oslo District Court as the agreed venue.
14. Term and Termination
This Agreement applies for as long as Lexera processes personal data on behalf of the Customer. The Agreement terminates automatically when all processing of personal data has ceased and data has been deleted or returned in accordance with section 9.
The provisions on confidentiality (section 3), liability (section 12), governing law (section 13), and deletion (section 9) shall survive termination of this Agreement.
Appendix 1: Description of Processing
This overview describes the processing of personal data performed by Lexera on behalf of the Customer.
Purpose of processing
Delivery of the Lexera platform for AI governance, application assessment, and privacy/compliance management, including AI-assisted guidance.
Nature of processing
Storage, structuring, retrieval, use, disclosure by transmission, combination, and erasure of personal data in connection with the platform's functions.
Categories of data subjects
Employees and contact persons of the Customer, end users of the platform, and individuals mentioned in application assessments and processing activities.
Types of personal data
- Contact information (name, email address, phone number)
- Organisational affiliation and role
- Authentication data (OAuth tokens, session data)
- User activity and audit logs
- Content of application assessments and compliance documentation
Sensitive personal data
Lexera is not designed for processing special categories of personal data (Art. 9) or criminal conviction data (Art. 10). If the Customer nevertheless records such data in free-text fields, the Customer is the data controller for this, and Lexera processes the data in accordance with the Customer's instructions.
Duration of processing
For as long as the main agreement is in force, with deletion/return in accordance with section 9.
Storage location
Microsoft Azure, Norway (Norway East). AI processing at Anthropic (USA, with SCCs).
Appendix 2: Technical and Organisational Security Measures
The following measures have been implemented to protect personal data processed by Lexera, in accordance with GDPR Article 32.
A. Access Control
- Role-based access control (RBAC) with least privilege principles
- Multi-factor authentication (MFA) for all administrators
- Authentication via OAuth 2.0 (Microsoft Entra ID / Google Identity)
- Automated session management with timeout
- Tenant-based data isolation – Customers can never see other Customers' data
B. Encryption
- Data in transit: TLS 1.2 or higher for all communication
- Data at rest: AES-256 encryption for all databases and file stores
- Secrets stored in Azure Key Vault
C. Network Security
- All traffic over HTTPS with TLS 1.2 or higher; insecure protocols (FTP) disabled
- Security headers (CSP, HSTS, X-Frame-Options) and rate limiting on login
- Platform-level DDoS protection in the Azure infrastructure
- Database access restricted with firewall rules and enforced TLS
D. Logging and Monitoring
- Centralised logging of all access and change activity
- Real-time security monitoring and automated alerts
- Audit log with up to 3-year retention
E. Vulnerability Management
- Automated dependency and vulnerability scanning in CI (npm audit, Trivy)
- Regular penetration testing
- Responsible disclosure process for security vulnerabilities
F. Incident Response
- Documented incident response plan
- Customer notification within 24 hours of a security breach
- Post-mortem analysis and remedial actions after incidents
G. Personnel Measures
- Background checks for employees with access to customer data
- Mandatory training in information security and data protection
- Confidentiality agreements for all employees and contractors
H. Backup and Recovery
- Automated daily backup with geographic redundancy
- Point-in-time recovery (PITR) with up to 7 days of history
- Documented and tested recovery plan
Appendix 3: Approved Sub-processors
The following sub-processors are approved as of the agreement date:
| Sub-processor | Purpose | Processing location | Transfer basis |
|---|---|---|---|
| Anthropic Ireland, Ltd | AI assistance (application assessment, DPA analysis, Lea assistant) | USA | EU SCCs (2021) |
| Microsoft Ireland Operations Ltd | Cloud infrastructure, database, authentication (Azure, Entra ID) | EU/EEA (North Europe) | Not required (EU/EEA) |
| Resend Inc. | Transactional email (notifications, invitations) | USA | EU SCCs (2021) |
| Google Ireland Ltd | Authentication via Google account (only when using Google sign-in) | EU/EEA | Not required (EU/EEA) |
| PostHog, Inc. | Product analytics (aggregated usage statistics) | EU/EEA (Frankfurt) | EU data residency; EU SCCs (2021) |
| Functional Software, Inc. (Sentry) | Server-side error tracking | EU/EEA (Germany) | EU data residency; EU SCCs (2021) |
About Anthropic and AI Processing
Lexera's AI assistant (Lea) uses the Anthropic Claude API to provide contextual guidance in application assessments. The following guarantees apply:
- Anthropic does not use customer data to train or improve its models (zero data retention for API customers)
- Data is sent encrypted (TLS 1.3) and is not stored after the response is generated
- Lexera only sends context data necessary to generate guidance — never complete datasets
- The Customer can disable AI assistance per organisation or per assessment
Appendix 4: AI-Specific Provisions
These provisions supplement the main agreement and apply specifically to the processing of personal data in connection with AI features in the Lexera platform.
A. Core Principle
Lexera's AI assistant follows the principle of "AI suggests, humans approve". All AI-generated suggestions are presented as recommendations that require the user's active approval before being saved to the assessment.
B. Data Minimisation
Lexera practices data minimisation in AI processing. Only information directly relevant to the current guidance is sent to the AI service. Complete personal data is not transferred — only aggregated context and anonymised references where possible.
C. No Training on Customer Data
Neither Lexera nor Anthropic uses customer data to train, fine-tune, or improve AI models. Anthropic operates with zero data retention for API requests, and Lexera has a contractual guarantee to this effect.
D. Transparency
Users are clearly informed when interacting with AI-generated content. All AI suggestions are marked as machine-generated. The Customer can review and override all AI suggestions.
E. AI Processing Location
AI processing takes place via the Anthropic Claude API (USA). Lexera continuously evaluates the possibility of EU-based AI processing (e.g., via AWS Bedrock in eu-west-1) and will offer this as an alternative when available, at no additional cost to the Customer.
Questions about this agreement should be directed to: support@lexera.no