Leadspace Opt Out: Remove or Suppress Business Contact Data

To opt out of Leadspace selling or sharing your business-contact information, use its Do Not Sell My Personal Information form. Enter identifying details and choose your relationship to Leadspace. Use the request-details box if you also want deletion or correction.

The privacy team can also be reached at compliance_privacy@leadspace.com.

Leadspace opt out quick facts

Use Leadspace official privacy request instructions as the starting point. The instructions and public evidence were checked September 11, 2026. No consumer request was submitted, so this guide reports the documented process rather than a tested removal result.

How to submit your Leadspace request

1. Open the official form. Its introduction covers sale or sharing and also lists deletion, correction, access, disclosure information and sensitive-information limitations.
2. Enter your first name, last name and email. The visible email label has an asterisk, although its inspected HTML did not expose the same required attribute as the name fields; supply an accurate reachable address and follow actual form validation.
3. Add company and address details where they help identify the business record. The page also offers city, state and postal code. Do not add unrelated addresses simply because a field is present.
4. Select the relationship that accurately describes you. The visible options include Employee, Independent Contractor, Customer, Supplier, Job Applicant and Other. A person merely listed in a database should not pretend to be a paying customer.
5. Use the final text box to identify any right beyond the default sale/sharing opt-out. For example, request deletion of the matched business-contact record and ask which limited information will remain for suppression.
6. Submit only your own or properly authorized request. Save the response and monitor the supplied inbox. If the form fails or the record cannot be identified, contact compliance_privacy@leadspace.com with the case details.

Choose the scope before sending personal information

• Opt-out: stop sale or sharing of the matched personal information; this is the form’s primary purpose.
• Deletion: name deletion explicitly in the additional request field; it is not identical to unsubscribing from promotional email.
• Correction and access: identify the disputed field or the information you need, and be prepared for identity verification.

Write down the outcome you want before starting. A useful request identifies the relevant record and states whether you want a disclosure stopped, a field corrected, or stored information deleted. If several actions matter, list them separately and ask the provider to confirm the disposition of each one.

Use identifiers tied to the record rather than a large bundle of personal documents. A name alone may match another person, while an unrelated address can confuse the request. Supply the minimum accurate details needed for the particular workflow, then respond to any explained verification step.

What the provider controls

Leadspace distinguishes User Personal Information from Business Personal Information in its notice. Its description of not selling user-account data must not be read as a claim that it never sells business-contact data. Identify which relationship and record your request concerns.

The notice includes a ten-business-day statement in its mailing-list and affiliate/service-provider choice section. Its verifiable consumer-request section instead describes a 45-day response aim and a possible explained extension. These refer to different contexts; neither is a measured completion time for your submission.

The privacy notice says information may be processed in multiple locations worldwide. A business address or a particular office location does not by itself establish where all request data is stored. Ask the privacy team about handling if that affects what you are willing to submit.

Verification and processing: what to keep

Visible name and email fields plus a relationship selector; further identity checks may follow.

Policy aims to respond to verifiable requests within 45 days; a further 45-day extension may be explained.

Retain the submission date, the contact address or form URL, the identifiers used, and any case number. Keep the provider’s acknowledgement separate from its completion response. An automatic email that says a case was received does not establish that the record was removed or that every requested action was accepted.

When the provider asks for more information, check that the message belongs to the case you opened. Ask what is missing and how to supply it securely. Do not repeatedly send unrelated documents to multiple addresses. A precise reply in the existing thread usually makes the record easier to follow.

Reappearance and follow-up checks

A changed employer, email alias or independently supplied business record can require clarification; stopping Leadspace marketing messages does not remove records held by other sales databases.

Recheck the same record or environment first. Compare its identifying details with the request you submitted. A different email, employer, profile URL, or browser preference may explain why the later result is outside the original match. Ask the provider to clarify before describing the entire process as unsuccessful.

A practical privacy log can be brief: provider, relevant record, requested action, submission date, confirmation, and next check. Choose a reminder based on the response you receive. If no completion date is given, ask for one instead of treating a historical average or another provider’s deadline as a promise.

Connect this request to the next useful cleanup

Use the data broker opt-out list to track other providers and the opt-out topic hub to find current instructions. The broader manual data broker removal guide explains how to organize a multi-provider cleanup.

Relevant follow-up workflows are Apollo.io instructions, ZoomInfo instructions, and Cognism instructions. Use each only when it matches a separate exposure; one provider’s confirmation does not serve as proof about another database.

For wider exposure checks, run a free broker scan. If recurring follow-up would help, compare the scope and cadence of services in the data removal comparison hub. A scan is a starting point, not proof that every private database was searched.

Leadspace opt out FAQ

What should I select if I am only listed in the database?

Choose the accurate relationship, using Other if the listed categories do not fit. Explain that you are the subject of a business-contact record rather than inventing a customer account.

Can I request deletion in the opt-out form?

Yes. The form explicitly invites requests for other rights and provides a details field. State deletion separately so the requested outcome is clear.

Why might Leadspace ask for more information?

Its notice describes verification of identity, authority and the relevant personal information. A similar name or outdated employer may not be sufficient to match the correct record.

Is the published 45-day period a removal guarantee?

No. It is the provider’s stated response aim for verifiable requests, with possible extensions and exceptions. An acknowledgement or historical processing statistic does not prove your record has been deleted.

Will this stop every sales email?

Not necessarily. A sales sender may already hold its own copy or use a different source. Handle its unsubscribe separately and request clarification about any continuing Leadspace disclosure.

Sources and verification notes

Leadspace official privacy request instructions and the official privacy policy were checked on September 11, 2026. Screenshots document public instructions only. Request timing, eligibility, exceptions, and identity checks remain subject to the provider’s current process.

These are practical instructions based on the cited provider material, not an individual legal assessment. If a request is denied, keep the reason and consult the relevant regulator’s official guidance for your location. Do not assume that a request available in one jurisdiction has identical terms everywhere.