Security and compliance
What an integration can rely on, and what it must leave to the professional: where LexOpti keeps the data, how access through the API is protected and traced, and how the obligations divide between the professional’s organization, your software and LexOpti.
- Hosting: LexOpti runs in the European Union, on servers it operates; data stays in the EU.
- Access: OAuth 2.1 with PKCE, 15-minute access tokens, rotating refresh tokens, per-request checks of membership, block and consent. Every action through the API is recorded in the organization’s audit trail with the application that made it. Installing an application for a whole organization, revoking or blocking it there is decided by LexOpti at the organization’s request, with a recorded motive and a strong authentication of the LexOpti administrator; an organization’s settings only list its connected applications.
- Minimisation: webhooks carry ids only; read the details through the API, with the member’s rights.
- Responsibilities: the professional stays responsible for their vigilance obligations (CMF L561-7; AMLR article 18 from 10 July 2027). Risk levels and acceptance decisions are validated by a member in LexOpti. LexOpti remains the record (CMF L561-12): keep references, not copies.
- GDPR: your software acts on the professional’s instructions: the data reaches it only once the professional has authorised your application, and stops when the access is withdrawn: the member unlinks LexOpti in your software, or the organization asks LexOpti to revoke it. Contact us for the list of sub-processors and the terms that apply to these flows.
- Report a vulnerability: contact@lexopti.com.