Ketch
Get a Demo

Ketch and Ashby

Anonymize a candidate's record without risking an application that's still actively being considered.

Get a DemoGet Started Free
Ashby Integration Documentation
Ashby

About Ashby

Ashby helps high-growth companies run recruiting end to end, which means a candidate's data often spans multiple applications to different roles at once. Deleting a candidate mid-process, while a hiring manager is still actively reviewing their application, risks disrupting a decision in progress. Ashby's own API reflects that concern directly in how it handles anonymization.

Ketch connects to Ashby with that safeguard built in.

Capabilities

How Ketch works with Ashby

The Ketch Ashby integration covers Rights Orchestration: Right to Deletion and Right to Access. If any application is still active, deletion won't proceed for that candidate.

Rights Orchestration

Right to Delete anonymizes the candidate, an action that cannot be reversed, but only once every one of that candidate's applications is in archived or hired status. Right to Access returns the information associated with the candidate.

With Ketch, teams can

  • Fulfill Right to Access and Right to Delete requests against Ashby candidate data through the same workflow used for every other connected system
  • Rely on a built-in safeguard that blocks anonymization while any application remains active, rather than risking disruption to an in-progress hiring decision
  • Know upfront that anonymization is permanent, since it cannot be reversed

The gap

The problem this integration solves

Recruiting platforms holding multiple concurrent applications per candidate create a real risk of deleting someone mid-process:

01. A deletion request that doesn't check application status could anonymize a candidate while a hiring manager is still actively reviewing their application

02. Assuming anonymization is reversible, when it isn't, risks a serious misunderstanding if a deletion happens by mistake

03. Manually checking every application's status before deleting a candidate doesn't scale to real request volume

Ketch resolves this by relying on Ashby's own application-status safeguard, so deletion only proceeds once every application has actually reached a resolved state, and by stating the permanence of anonymization plainly.

Why Ketch

Why teams choose Ketch for Ashby privacy compliance

Permissioning infrastructure that governs Ashby the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.

  • Built-in protection for active applications

    Deletion only proceeds once every one of a candidate's applications is archived or hired, protecting decisions still in progress.

  • Honest about permanence

    Anonymization cannot be reversed, and this integration states that plainly rather than leaving it ambiguous.

  • 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 recruiting platforms holding candidate data carry real exposure when deletion isn't handled with real safeguards behind it.

Questions about the Ashby integration

Related reading

Expert insights for teams connecting Ashby

Browse the Blog

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.

Browse All Integrations

See Ashby permissioning running end to end

Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Ashby yourself.

Get Started Free

Get started in less than 5 min

Get a Demo