Discovery
Scans databases, tables, and columns using read-only `SELECT` access.
Ketch and MariaDB
Find where personal data lives inside a MariaDB deployment, and fulfill deletion requests against it directly, using a dedicated database user created specifically for this purpose.
About MariaDB
MariaDB runs relational workloads as a MySQL-compatible open-source database, often behind applications that have grown their schema organically over time. Knowing exactly which tables and columns hold personal data, and being able to act on that directly, matters more the longer a schema has grown without a centralized privacy review.
Ketch connects to MariaDB through a Ketch Transponder to support both discovery and, where authorized, direct execution.
Capabilities
How Ketch works with MariaDB
The Ketch MariaDB integration covers Discovery and Rights Orchestration for both Right to Access and Right to Delete.
Rights Orchestration
Requires `UPDATE` and `DELETE` access granted on top of that, scoped to specific databases, tables, and columns.
With Ketch, teams can
- Discover which MariaDB tables hold personal data using read-only access
- Grant rights-execution privileges separately from Discovery, deciding independently whether and when to authorize direct deletion and update
- Connect through a dedicated database user created specifically for this integration
The gap
The problem this integration solves
A schema that's grown organically over time creates real risk that personal data ends up in places nobody's specifically reviewing:
01. Manually reviewing tables and columns for personal data doesn't scale and misses schema changes made without a privacy review
02. Fulfilling a deletion request against a database has historically meant a manually written query, slow and hard to prove complete
03. Granting broad write access to any tool touching production data is a real risk independent of the privacy use case
Ketch resolves this by connecting continuously with scoped Discovery and rights-execution privileges, using a dedicated user rather than shared credentials.
Why Ketch
Why teams choose Ketch for MariaDB privacy compliance
Permissioning infrastructure that governs MariaDB the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.
Least-privilege by design
Discovery requires only `SELECT`; rights execution is a separate, explicit grant.
A dedicated database user
Ketch connects through a user created specifically for this integration, not a shared or general-purpose credential.
Backed by enforcement precedent
Regulators increasingly expect businesses to prove technical enforcement, not just describe it on paper, the same underlying expectation that applies to knowing what personal data a database holds.
Questions about the MariaDB integration
Related reading
Expert insights for teams connecting MariaDB
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 MariaDB permissioning running end to end
Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect MariaDB yourself.
Get Started Free
Get started in less than 5 min