Rights Orchestration
Right to Delete anonymizes the applicant and removes their contact information. Right to Access returns any information associated with the applicant.
Ketch and Lever
Fulfill access and deletion requests against an ATS and CRM built around rich talent analytics, using a connection that requires the highest level of account permission Lever offers.
About Lever
Lever combines an applicant tracking system with CRM functionality, giving hiring teams sourcing, nurturing, and interview analytics in one place. That combination of ATS and CRM data means a deletion request needs to reach both, and Lever requires the highest level of account access, Super Admin, to establish an integration capable of doing so.
Ketch connects to Lever with exactly that level of access.
Capabilities
How Ketch works with Lever
The Ketch Lever integration covers Rights Orchestration: Right to Delete and Right to Access. Establishing the connection requires Super Admin permissions on the Lever account, Lever's own requirement for integrations with this level of access.
With Ketch, teams can
- Fulfill Right to Access and Right to Delete requests against Lever applicant data through the same workflow used for every other connected system
- Get both anonymization and contact information removal as part of a single deletion action
- Know upfront that Super Admin permissions are required, rather than discovering a permissions blocker mid-setup
The gap
The problem this integration solves
An ATS and CRM combination holds both structured applicant data and richer analytics-driving information, and connecting to reach all of it requires real, elevated access:
01. A deletion request that only anonymizes an applicant without removing their contact information leaves reachable personal data behind
02. Attempting to connect without Super Admin permissions fails, and it's better to know that upfront than discover it partway through setup
03. Manually locating and removing applicant data across an ATS and CRM combination doesn't scale to real request volume
Ketch resolves the first by removing both anonymization and contact information together in one action, and flags the Super Admin requirement so it's planned for rather than discovered as a blocker.
Why Ketch
Why teams choose Ketch for Lever privacy compliance
Permissioning infrastructure that governs Lever the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.
Deletion that reaches both anonymization and contact data
Right to Delete removes contact information alongside anonymizing the applicant record.
Upfront about the permission level required
The Super Admin requirement is stated plainly before setup begins.
Backed by enforcement precedent
The California Attorney General reached a $1.55 million settlement with Healthline Media over sharing sensitive data with advertisers without valid consent, a reminder that ATS and CRM platforms holding applicant data carry real exposure when deletion isn't genuinely complete.
Questions about the Lever integration
Related reading
Expert insights for teams connecting Lever
Integrations
Pre-built APIs with 1,000+ systems, apps, and models
Ketch ships connectors and SDKs so consent, rights, and policy flow into your CDPs, warehouses, ad platforms, and AI stack — without a custom data pipeline.
See Lever permissioning running end to end
Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Lever yourself.
Get Started Free
Get started in less than 5 min