Ketch and Pingboard

Fulfill access and deletion requests against the employee directory and org chart data a whole company sees, not just what HR has on file.

Pingboard

About Pingboard

Pingboard gives employees visibility into who's who across a company: org charts, availability, and team information visible broadly across an organization, not locked away in an HR system only a few people can access. That visibility is the whole point of the product, but it also means personal data here is seen by more people day to day than a typical HR record.

Ketch connects to Pingboard to fulfill access and deletion requests against that data.

Capabilities

How Ketch works with Pingboard

The Ketch Pingboard integration covers Rights Orchestration: Right to Delete and Right to Access.

Rights Orchestration

Fulfills Right to Access and Right to Delete against Pingboard through the same workflow used for every other connected system. The connection requires admin permissions in the Pingboard account; on a Company plan, API access is already included by default.

With Ketch, teams can

  • Fulfill Right to Access and Right to Delete requests against Pingboard directory and org chart data through the same workflow used for every other connected system
  • Match requests using email address as the identifier
  • Connect without needing separate API access provisioning if already on a Company plan

The gap

The problem this integration solves

An internally visible employee directory carries different stakes than a typical back-office HR system, since the data is seen broadly across an organization by design:

01. Manually locating and removing a specific employee's directory data doesn't scale to real request volume

02. Assuming an internally facing tool like an org chart platform is lower-risk than customer-facing systems misses that its data is actually seen by more people day to day

03. HR and internal-directory systems are sometimes deprioritized in privacy programs focused on customer data, even though the same underlying obligations apply

Ketch resolves the first by giving Pingboard a structured, repeatable rights workflow, and addresses the second and third by treating internal directory data with the same rigor as any other personal data source.

Why Ketch

Why teams choose Ketch for Pingboard privacy compliance

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

  • Closes a coverage gap many privacy programs miss

    Internal, broadly visible directory data gets the same rights treatment as customer-facing systems.

  • Simple setup for Company plan accounts

    API access needed for this integration comes included by default rather than requiring separate provisioning.

  • 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 any system holding personal data, internally visible directories included, carries real exposure when rights requests aren't fulfilled completely.

Questions about the Pingboard integration

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 Pingboard permissioning running end to end

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

Get Started Free

Get started in less than 5 min