Remove your data from Kaspr
Delist pursues supported removal requests and tracks their status. Before requesting help with Kaspr, check the current request scope and any steps that require you. A request receipt does not establish that a listing is no longer visible.
Prefer to handle the request yourself? Read the Kaspr request guide and its current limits.
Review possible exposure
A free scan is separate from paid removal work. Review the supported request scope before proceeding.
Run a free scan- What Kaspr is
- B2B contact database
- Parent company
- Cognism Limited
- Opt-out difficulty
- easy
- Opt-out page
- https://kaspr.privacy.saymine.io/kaspr
- Verification required
- Time to removal
- as soon as possible after verification
- Does your data come back?
- After opt-out, all Kaspr users who saved your data are notified and asked to remove it; your data won't show in the extension/dashboard.
What is Kaspr?
Kaspr is a LinkedIn-prospecting Chrome extension (owned by Cognism) that reveals phone numbers and email addresses from LinkedIn profiles, building a crowdsourced B2B contact database.
Data categories Delist has recorded for Kaspr
- full name
- work email
- personal email
- mobile/direct dial phone
- job title
- employer
- LinkedIn URL
- location
Removal and reappearance limits
After opt-out, all Kaspr users who saved your data are notified and asked to remove it; your data won't show in the extension/dashboard. Because Kaspr is crowdsourced from extension users enriching LinkedIn profiles, re-collection is possible. Data may also reside in parent Cognism systems.
Where Delist fits
Review the current supported removal work and any steps that require you. Submission, a provider response and direct visibility establish different things; blocked access is inconclusive.
Beyond Kaspr: see your state's data privacy rights for laws that may give you stronger tools than opting out site-by-site.
Find out what data brokers know about you
Start with a free scan to review possible exposure. Review service scope and any required authorization separately.