LidmeoDevelopers

Security and GDPR

How Lidmeo protects your access and your data, and what flows when you connect a tool.

Your access

  • API keys are never kept in clear: Lidmeo keeps only a fingerprint and shows them only once. A revoked key stops working right away.
  • OAuth tokens last one hour; their refresh token changes on every use, and a reused token brings the whole connection down. Revoking a token, access or refresh, also cuts the whole connection.
  • Scopes are chosen one by one. An API key never gets the right to send by default; when an application connects, each requested scope is shown and can be unticked. Contact details (e-mails, phone numbers) need a separate scope, contacts:read.
  • Webhook secrets are encrypted in the database, like the responses kept under an Idempotency-Key. Lidmeo only delivers to public HTTPS addresses, follows no redirect and checks the real address on every delivery.
  • Everything goes over HTTPS.

What is kept, and for how long

WhatDuration
The request log (who, when, which operation, which result; never the content)30 days
Events and their deliveries30 days
Idempotency keys and their response24 hours

Your data is hosted in the European Union.

When you connect a tool

Lidmeo transmits nothing on its own. When you connect an AI assistant (Claude, ChatGPT…), an automation (Zapier, Make, n8n) or your own program, you are the one who chooses it, and it receives the data you ask it to read, with the scopes you gave it. Some of these services are outside the European Union: their own terms apply. You withdraw an access at any time in Lidmeo, on the "Assistant IA et intégrations" (AI assistant and integrations) page.

The people you prospect

  • "Do not contact" applies everywhere, to the API as to the assistant: no more invitations, messages or e-mails. Add a person with POST /v1/suppressions.
  • An unsubscribe becomes the prospect.opted_out event: propagate it to your other tools.
  • An access or erasure request from a person: write to support, with their LinkedIn profile or e-mail.

See also your obligations.

Reporting a vulnerability

Write to contact@lidmeo.com with the details and a way to reproduce it. Please do not exploit the vulnerability beyond what demonstrates it, nor touch other accounts' data.

On this page