Rights Orchestration
Right to Access returns the information associated with a client. Right to Delete removes both the client record and the appointments associated with them, rather than deleting one without the other.
Ketch and Acuity Scheduling
Fulfill access and deletion requests against a scheduling platform, reaching both the client record and every appointment tied to it.
About Acuity Scheduling
Acuity Scheduling lets clients book appointments, fill out custom forms, and pay online around the clock. A client's booking history, including custom form responses collected at scheduling time, often holds more personal detail than a typical CRM record, since intake forms can capture specifics tailored to whatever a business actually needs to know before an appointment.
Ketch connects to Acuity Scheduling to fulfill both access and deletion requests against that data.
Capabilities
How Ketch works with Acuity Scheduling
The Ketch Acuity Scheduling integration covers Rights Orchestration: Right to Access and Right to Delete.One setup requirement worth knowing upfront: this integration requires an Acuity account on the Powerhouse Package subscription tier specifically; the connection won't succeed on a lower tier.
With Ketch, teams can
- Fulfill Right to Access and Right to Delete requests that reach both a client record and their associated appointments
- Match requests using email address as the identifier
- Know upfront whether an existing Acuity subscription tier supports this integration, rather than discovering a blocker mid-setup
The gap
The problem this integration solves
A scheduling platform holding custom intake-form responses alongside appointment history creates real stakes for a rights request:
01. A deletion that removes a client record but leaves their appointment history intact (or vice versa) doesn't actually fulfill the request completely
02. Custom form responses collected at booking time can hold more specific personal detail than a typical contact record, and a rights process needs to account for that
03. Subscription tier requirements that aren't checked upfront can block an integration partway through setup
Ketch resolves the first two by covering both the client record and appointment data together in one deletion action, and flags the tier requirement so it's known before setup begins rather than discovered mid-process.
Why Ketch
Why teams choose Ketch for Acuity Scheduling privacy compliance
Permissioning infrastructure that governs Acuity Scheduling the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.
Deletion that covers the whole booking relationship
Both the client record and their associated appointments are removed together, not as two separate, easy-to-miss steps.
Upfront about setup requirements
The Powerhouse Package subscription requirement is stated plainly before installation, rather than discovered as a failed connection attempt.
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 appointment and intake data, often more detailed than standard contact records, carries real exposure when rights requests aren't fulfilled completely.
Questions about the Acuity Scheduling integration
Related reading
Expert insights for teams connecting Acuity Scheduling
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 Acuity Scheduling permissioning running end to end
Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Acuity Scheduling yourself.
Get Started Free
Get started in less than 5 min