Ember.Ember

Translation provided for information only. The French version prevails. Read the French version

Lead Intelligence legal framework

Effective October 26, 2026EMBER Origin SAS

Article 1

Prospect data & rights

Ember Lead Intelligence helps its professional users identify, prioritize and contact B2B prospects. This page informs the people whose data is processed in this context, under Articles 13 and 14 of the GDPR, including where the data is not collected directly from them.

Who is responsible for this processing?

Prospecting missions are configured and managed by our client users, who determine their targets, channels and messages: they are the data controllers for their prospecting. EMBER ORIGIN SAS, 16 place des Quinconces, 33000 Bordeaux (support@ember.do), which publishes the Ember platform, acts as a data processor on behalf of its clients, and as a data controller for the operation, security and improvement of the Platform.

What categories of data are processed?

Name, job title, seniority and department, company, city and country, business email address and phone number, LinkedIn profile (identifiers, career history, posts, degree of connection with the user), company activity signals (fundraising, hiring, press, job changes, etc.), messages exchanged with the user and their read status. To help the user write their messages, our artificial intelligence models also produce an analysis of the prospect’s communication style (DISC-type profile) from their public information. No sensitive data within the meaning of the GDPR is sought; our agents are instructed never to collect or guess a personal mobile number or email address.

Legal basis and purposes

The processing relies on the legitimate interest of business-to-business commercial prospecting (Article 6(1)(f) of the GDPR): identifying relevant companies and contacts, enriching their business contact details, prioritizing them, following their public signals, preparing and sending messages, measuring results.

Data sources

The data comes from: LinkedIn, read with the LinkedIn account of the user connected through our provider Unipile; web searches and public pages read by our agents through the Serper service (company websites, press, public posts on LinkedIn, Reddit or X); files imported by the user (for example exports from Apollo, lemlist, Clay, HubSpot, Salesforce or Pipedrive); the user’s entries; and, where this service is enabled, business contact enrichment by FullEnrich.

How is the prospect contacted and informed?

When the user approves or schedules it, Ember sends LinkedIn invitations and messages on their behalf, and emails from the Gmail or Outlook mailbox they connected. Ember receives LinkedIn replies and their read receipts; email replies are added by the user. Every email sent with Ember, and the first LinkedIn message or InMail of a conversation, automatically ends with a mention in the language of the mission: the sender’s name, the origin of the contact details (public sources and enrichment service, public LinkedIn profile, file provided by the sender or the sender’s own entry) and a link to stop being contacted. LinkedIn invitations (300 characters) and messages that the user copies and sends themselves do not include it: it is up to the user to inform these prospects no later than the first contact and to respect their objection.

Objection and do-not-contact list

When the user adds a prospect to their do-not-contact list, Ember cancels pending actions and follow-ups, pauses monitoring and enrichment, and refuses any new sending to that email address, domain or LinkedIn profile. The link in the mention opens a page accessible without an account: its button adds the person to the do-not-contact list of the sender and their organization, and stops the planned sendings. This list is specific to the user or their organization; it does not apply to other Ember clients. A reply from the prospect stops automatic follow-ups. A prospect who objects to Ember (support@ember.do) has their request passed on to the user concerned, whom We help to respond.

Access, rectification, deletion

You have the rights of access, rectification, erasure, restriction and objection, and You may object at any time, without justification, to prospecting (Article 21 of the GDPR). Requests sent to support@ember.do are handled manually by our team, within one month, after verification of the requester’s identity: there is no automatic deletion or export from a prospect’s record. You may also lodge a complaint with the CNIL (www.cnil.fr).

How long is the data retained?

Company records, people and their messages are deleted automatically 3 years after their collection or after the prospect’s last reply: a message sent or a signal observed does not extend this period. They are deleted earlier with the mission, when the account of the user who created it is deleted, or by our team at the request of the data subject. Archiving a mission does not delete them. Entries on the do-not-contact list are kept for as long as the user does not remove them, in order to keep respecting the objection.

Recipients and subcontractors

Prospect data is accessible to the user who manages the mission, to the members of their team with whom they share it, and to authorized Ember teams. It is processed by: Unipile (LinkedIn and email connection, France); Serper (web search, United States); Supabase (database hosted in the European Union, in Paris and Ireland); Railway (hosting of the prospecting engine, United States); FullEnrich (enrichment, France), where this service is enabled; OpenRouter (United States) and, through it, the artificial intelligence models of Anthropic (United States), Google and OpenAI (United States), DeepSeek and MiniMax (China, or United States depending on the host); LangSmith (technical traces, United States); Resend (summary emails to the user, United States); Slack, if the user receives their daily summary there; Google or Microsoft, for emails sent from the user’s mailbox. The safeguards governing these transfers are detailed in our privacy policy.

Article 2

Product safeguards

  • Sending checks the user’s do-not-contact list before every invitation, message or email.
  • No message is sent without the user’s approval or scheduling.
  • Paid contact enrichment is used only when the contract with the provider is in place and the service is enabled.
  • Rights requests are logged and handled manually by our team; there is no automatic deletion or export from a prospect’s record.
  • Each prospect keeps a record of its origin (Ember recommendation, LinkedIn search, import, manual entry) and of the main decisions made about it.

Article 3

Contact

To exercise a right or object to prospecting, write to support@ember.do. Ember may ask for additional information to verify the requester’s identity or the validity of the mandate presented.

Need help?

For questions about prospect data or a rights request, contact us:

support@ember.do

06 20 82 52 88

EMBER Origin SAS16 Place des Quinconces33000 BordeauxFrance

Your next decision can start here.

Describe your priority. Ember helps you move forward.