lemlist Opt Out: Remove Your People Database Profile

To complete a lemlist opt out from its People Database, email privacy@lempire.co and object to inclusion of your professional profile. The current policy says you do not need to give reasons for that objection. It says lempire will delete the profile, add an identifier to a suppression list and notify customers who received the data in previous months so they can act on the objection within 30 days.

That is different from unsubscribing from one sales email or closing a paid lemlist account. If a lemlist customer contacted you, direct a separate request to that sender for the customer's own campaign records. The guide below explains both routes and what a confirmation can establish.

Which lemlist privacy request do you need?

We reviewed the official lemlist privacy policy on November 12, 2026. It identifies lempire SAS as controller for the People Database and distinguishes customer campaigns, where lempire acts as a processor. We did not create a customer account, search a paid database or submit a consumer request.

1. Establish whether you mean the database or one sender

A sales message mentioning lemlist does not by itself show how the sender obtained your details. Save the sender's business name, your contacted address and any statement about the source. If the message says the People Database supplied the information, include that context in your request.

The People Database contains professional and company profiles used for business-to-business prospecting. The policy describes identification and professional information and enrichment that updates profiles. You should not expect the same workflow as removing a public residential listing from a people-search website.

The public versus non-public broker coverage guide explains this discovery gap. A profile can be available to customers without a public page that you can search by name. Ask the controller about the record rather than buying access just to test whether it exists.

2. Email the People Database objection

Write to privacy@lempire.co and make “People Database objection” clear in the subject or opening sentence. Identify yourself using the professional details relevant to the record, such as your name and the work email that received outreach. Add a company or profile reference if you already have one and it helps distinguish you from someone with a similar name.

A concise request could say: “I object to inclusion of my personal data in the lemlist People Database and its use for direct marketing. Please delete my profile, apply the suppression described in your policy and confirm the treatment of recipients who previously received my data.” Add only the matching information needed for your case.

This is suggested wording, not a required official form. The policy permits objections without reasons. You do not need to write a long account of why the outreach was unwelcome or make an unsupported legal allegation to ask for the documented action.

3. Understand deletion and the suppression identifier

The policy says the profile will be deleted and an identifier added to a suppression list. Those actions serve different purposes: deletion removes the profile from the described database, while a retained suppression identifier helps record your objection.

Ask the confirmation to distinguish the deleted profile from information retained to honor the objection or comply with another obligation. A minimal suppression record is not the same thing as leaving a prospecting profile available. Conversely, a generic “unsubscribed” reply does not establish that database deletion occurred.

For another professional-data workflow, see the Cognism opt-out guide. Each controller has its own matching and suppression process. A request to one company does not automatically remove data held independently by another.

4. Respond to identity questions carefully

The policy says rights requests can be sent through support chat or privacy@lempire.co. It gives a 30-day processing period and says proof of identity or authority may be requested where there are reasonable doubts about identity.

That does not mean everyone must attach an identity document to an initial email. Start with relevant matching details, then ask for a secure method and the reason if additional proof is needed. The policy says identity proof is retained only as long as necessary to verify identity and deleted once verification is complete.

Keep the request and follow-up together. Avoid sending passwords, unrelated identification or customer credentials. If you are acting for someone else, use an authorized process and be ready to show authority; knowing a colleague's email address does not itself authorize a deletion request for them.

5. Ask the sender about customer-controlled records

When a customer creates contact lists, campaigns or messages in lemlist, the policy says that customer determines the purpose and means of processing. Send the privacy or stop-contact request to that business directly. If you contact lempire instead, the policy says it will forward the request and assist the customer.

If your data is also in the People Database, lempire says it handles that part for its own account. Explicitly naming both issues can prevent a reply about one campaign from being mistaken for a complete database response.

The LeadIQ guide and Lead411 guide cover other professional-contact sources. Follow those routes only when your evidence points to them. Do not assume all sales tools exchange your particular record.

6. Interpret the recipient-notification promise correctly

The People Database section says lempire will inform customers who received your data in previous months so they can give effect to the objection within 30 days. This is a stated process for prior recipients, not our verification that every independent customer completed deletion.

Ask whether your request has triggered the described recipient notification. If a particular sender continues contacting you, bring that evidence to the sender and reference the earlier objection. A continued message may require a customer-level follow-up even after the database profile has been removed.

The policy also describes retaining information used to manage rights requests and direct-marketing objections for five years. Ask what is retained if that matters to your request. Do not equate every retained compliance entry with continued sale of the professional profile.

Check your result and future records

A useful final response states whether a profile was found, what was deleted, whether suppression was applied and how the recipient-notification process was handled. If the response is unclear, ask a focused question rather than starting multiple conflicting cases.

The opt-out guide hub organizes other removal workflows. A CrabClear privacy scan can help you review exposure in supported sources, but a scan result is not proof that this non-public database lacks your profile or that a particular customer deleted its campaign copy.

Request checklist

• Name the People Database when objecting to your professional profile.
• Use matching professional details and ask about suppression.
• Ask the sender separately about customer-controlled campaign records.
• Keep the database response and recipient-notification explanation for follow-up.

Frequently asked questions

Is lempire the correct contact for lemlist?

The current lemlist policy names lempire SAS as controller and privacy@lempire.co as its privacy contact. Verify the address against the official page before sending sensitive information.

Do I need to explain why I object?

The People Database section says you may object at any time without giving reasons. Still provide enough information to identify the record and clearly name the database.

Will deleting my account remove every professional profile?

Do not assume so. Account processing and the People Database have distinct descriptions in the policy. Ask explicitly about the database when that is your concern.

Does unsubscribing from a sales email solve this?

It can stop that sender's campaign, but it does not demonstrate removal from the People Database. Use the controller route for the database and the sender route for the campaign.

Is a passport required?

The policy allows additional identity proof when there are reasonable doubts. It does not say every initial request needs a passport. Ask for the necessity and secure submission method before providing extra evidence.

Can the record return after an update?

The policy's suppression process is intended to record your objection, but we did not test future imports. Retain the confirmation and follow up if new evidence shows the same profile being supplied again.