LidmeoDevelopers

Privacy policy

The data Lidmeo's AI connector, API and webhooks process: which data, why, for how long, and your rights.

This policy covers Lidmeo's AI connector (Claude, ChatGPT…), API and webhooks. It complements the privacy policy published on lidmeo.com, which still applies to the rest of the service.

Who processes your data

MINDLINK, a French SAS with a share capital of €1,000, registered with the Paris Trade and Companies Register under number 992 801 357, whose registered office is at 60 rue François Ier, 75008 Paris, France, publisher of Lidmeo.

Contact: contact@lidmeo.com.

What you authorize

When you connect your Lidmeo account to an AI assistant or an application, or create an API key, you allow it to read and, depending on the permissions you grant, change data in your account: your prospects and their cards, your LinkedIn and e-mail conversations, your campaigns, your CRM (stages, lists, reminders, notes) and your statistics. Contact details (e-mails, phone numbers) need a separate permission.

You choose these permissions one by one when you connect, and you can revoke an access at any time in Lidmeo, on the "Assistant IA et intégrations" (AI assistant and integrations) page.

From an AI assistant, no invitation or message is sent without your explicit confirmation. An application can send only if you gave it that permission. In every case, your account's daily limits, sending hours and do-not-contact list apply.

The data we process

  • The account data each request needs. Lidmeo reads it and returns it to the tool you connected. We never read your conversation history with the assistant or its memory.
  • Your accesses. API keys and connection tokens are never stored in clear: Lidmeo only keeps a fingerprint of them.
  • A technical request log: the date, the operation, the result, the duration, the IP address and the calling software. Never the content of your data.
  • The events sent to your webhooks and the history of their deliveries. Webhook secrets are encrypted.
  • Providing the service you ask for (performance of the contract, Article 6(1)(b) GDPR): answering the requests of the connected tool, applying the actions you authorize, delivering events to your webhooks.
  • Securing accesses and helping you when something goes wrong (legitimate interest, Article 6(1)(f) GDPR): the request log is used to detect abuse and to find a request when you contact support.

Lidmeo does not sell your data.

Who receives it

  • The tool you connect (for example Claude, by Anthropic, or ChatGPT, by OpenAI, an automation or your own program) receives the data you ask it to read. Its provider processes it under its own terms; some are located outside the European Union.
  • A search for e-mails or phone numbers started from a connected tool works exactly as it does from Lidmeo, with the same contact-data provider.
  • Our hosting providers, who act on our instructions. The application and the database are hosted in the European Union.

No other third party receives this data.

For how long

WhatRetention
The request log30 days
Webhook events and their deliveries30 days
An access tokenone hour
A refresh token60 days, renewed on each use

An API key works until you revoke it. Revoking an access in "Assistant IA et intégrations" cuts the connection immediately. Your account data follows the retention periods of the policy published on lidmeo.com.

The people you prospect

The do-not-contact list applies everywhere, to the API and to the assistant. For an access or erasure request from a person you prospect, write to contact@lidmeo.com with their LinkedIn profile or e-mail. See also your obligations.

Your rights

You can ask for access to your data, its rectification, its erasure, the restriction of its processing or its portability, and object to processing based on legitimate interest: write to contact@lidmeo.com. You can also lodge a complaint with the French data protection authority, the CNIL (cnil.fr).

Security

Everything goes over HTTPS, accesses are never stored in clear and each permission is granted separately. The details: security and GDPR.

Changes

Any change to this policy is published on this page.

Last updated: October 3, 2026.

On this page