A privacy-first, open-source consent management platform.

• Live Demo (Frontend)
• Live Demo (Back-office)

• User-friendly interface for managing consent preferences
• Light and fast dialog script (~8KB compressed, ~50req/s on a single Scaleway Stardust instance)
• Referer Based (no need for script configuration. Include anywhere, and activate on demand via back-office)
• Saas-Like (multi-site, multi-client and multi-tenant)
• Highly configurable, customizable and extensible
• DNT support (optional)
• Consent logging and reporting
• Page view tracking
• Multiple RDBMS support (PostgreSQL, MariaDB and SQLite tested, MySQL, Oracle and SQLServer should work)
• Configurable cache layer (Redis, Memcached, APCu)
• GDPR Registry Auto-generation

 $ docker run -it --rm -p 80:80 -p 443:443 --name 1z1-consent \
       -e SERVER_NAME="localhost, www.localhost" \
       -e MAIN_DOMAIN="localhost" \
       -e APP_SECRET="$(shell openssl rand -hex 32)" \
       ghcr.io/un-zero-un/1z1-consent:latest

This will start a single container with both the web server and the database (SQLite) running. Data will be stored in the container, so if you remove the container, you will lose all your data. You can also use a volume to persist the data:

 $ docker run -it --rm -p 80:80 -p 443:443 --name 1z1-consent \
       -e SERVER_NAME="localhost, www.localhost" \
       -e MAIN_DOMAIN="localhost" \
       -e APP_SECRET="$(shell openssl rand -hex 32)" \
       -v 1z1-consent-data:/app/var/data \
       ghcr.io/un-zero-un/1z1-consent:latest

You can use an external database by providing the DATABASE_URL environment variable: mysql://user:password@host:port/dbname?serverVersion=8&charset=utf8mb4 or postgres://user:password@host:port/dbname?serverVersion=17&charset=utf8

A complete docker compose config is provided. The simplest way to use it is via Makefile:

 $ make run

If you have docker compose and mkcert available, it'll run the stack with a local CA signed certificate for localhost and www.localhost, a postgres database and a APCu cache in development mode.

The application is configured via environment variables. Available variables are :

Once the application is running, you can access the back-office at https://<MAIN_DOMAIN>/admin.

If you load the data fixtures, the admin user is [email protected] and the password is admin.

The front-end script can be included in any website by adding the following script tag:

<script src="//<MAIN_DOMAIN>/api.js" async></script>

document.dispatchEvent(new CustomEvent('1z1-content:show-dialog'));