MariaDB

What Is MariaDB?

MariaDB is an open source relational database management system (RDBMS), originally created as a community developed fork of MySQL by Michael Widenius, one of the original MySQL founders. It is maintained by the MariaDB Foundation, a Finnish non profit organisation based in Espoo, Finland. MariaDB offers drop in compatibility with MySQL and is used by major organisations worldwide as a backend database for web applications, enterprise systems, data warehousing, and embedded applications. It is available as self hosted open source software or via SkySQL, MariaDB's cloud managed database service running on AWS and GCP.

Data Collected and Storage Approach

MariaDB operates at the infrastructure layer and does not interact with end users directly or set browser cookies. The personal data it processes is entirely determined by the application layer. Common data stored includes user accounts, contact information, transaction records, and application logs. MariaDB supports the Audit Plugin for logging database access and queries, binary logging for replication and point in time recovery, and general query logging. SkySQL collects operational metadata including connection logs, performance metrics, and user account information for the management console.

GDPR and ePrivacy Implications

For self hosted MariaDB deployments, no third party data processing is involved, and the organisation bears full responsibility for GDPR compliance at the infrastructure level. The EU base of MariaDB Foundation (Finland) is a privacy advantage as the open source project is maintained within the EEA. For SkySQL cloud deployments, MariaDB acts as a data processor and provides service agreements addressing GDPR requirements. MariaDB supports encryption at rest (using file key management or AWS Key Management), encryption in transit (TLS/SSL), role based access control, and comprehensive audit logging via the Audit Plugin. These features enable organisations to implement strong data protection measures at the database level.

Consent and Legal Basis Requirements

As a database engine, MariaDB does not require consent from end users. The legal basis for data storage depends on the application: typically contract performance (Art. 6(1)(b)) or legitimate interest (Art. 6(1)(f)). Organisations must implement consent mechanisms at the application layer for any personal data collection requiring consent. The mariadb.org and SkySQL websites set analytics cookies requiring ePrivacy consent, but this applies only to visitors of those sites, not to end users of applications built on MariaDB.

International Data Transfers

Self hosted MariaDB keeps data entirely under the organisation's control with no international transfers unless the organisation configures cross region replication. For SkySQL, EU deployment regions are available on AWS and GCP. MariaDB Foundation is based in Finland, providing an EU base for the open source project governance. MariaDB Corporation (now part of the restructured entity) has operations in multiple countries. Organisations using SkySQL should confirm their chosen deployment region and review the service agreement for transfer safeguards.

Practical Compliance Steps

For self hosted deployments: enable TLS for all connections, configure encryption at rest using the file key management plugin, implement role based access control with least privilege principles, enable the Audit Plugin for comprehensive query logging, configure binary logging for data recovery, secure network access with firewall rules, and implement automated backup with tested restoration procedures. For SkySQL: review the service agreement, select an EU deployment region, configure access controls, and enable audit logging. For all deployments: design your database schema to support GDPR data subject rights, implement data retention policies using scheduled purge procedures or event scheduler jobs, conduct a DPIA if storing sensitive personal data, and document MariaDB in your Records of Processing Activities.