PHP download

Download the PHP package ginkelsoft/laravel-data-consent without Composer

On this page you can find all versions of the php package ginkelsoft/laravel-data-consent. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

Table of contents
Download ginkelsoft/laravel-data-consent
More information about ginkelsoft/laravel-data-consent
Files in ginkelsoft/laravel-data-consent

Vendor ginkelsoft
Package laravel-data-consent
Short Description A Laravel package that implements GDPR art. 6(1)(a) and art. 7 consent recording as a tamper-evident append-only event log, with grant/withdraw actions and a status helper for the current state.
License MIT

Keywords laravel consent avg gdpr compliance audit-log ginkelsoft toestemming

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:

If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.

Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
To use Composer is sometimes complicated. Especially for beginners.
Composer needs much resources. Sometimes they are not available on a simple webspace.
If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.

Please rate this library. Is it a good library?

Example code of ginkelsoft/laravel-data-consent

Informations about the package laravel-data-consent

Ginkelsoft Laravel Data Consent

Overview

Implements GDPR art. 6(1)(a) (consent as lawful basis) and art. 7 (conditions for consent — including the demonstrability requirement) for a Laravel application. Records every grant and every withdrawal as an append-only, hash-chained event in consent_log. The current state for a given (subject, purpose, version) is derived from the latest event.

This is the consent member of the GinkelSoft compliance family. The chain is built on the shared HashChain from ginkelsoft/laravel-compliance-core and the signing secret is shared with every other audit log in the family.

The family

Package	GDPR Article(s)	Role
`laravel-compliance-core`	art. 5(2)	Shared primitives
`laravel-data-retention`	art. 5(1)(e)	Storage limitation
`laravel-data-right-to-be-forgotten`	art. 17	Subject-driven erasure
`laravel-data-subject-access`	art. 15 + 20	Subject access
`laravel-data-consent`	art. 6(1)(a) + 7	Consent registry — this package
`laravel-data-breach-registry`	art. 33 + 34	Breach registry
`laravel-compliance-hub`	art. 5(2)	Umbrella

How it works

Record a grant or withdrawal

version lets you tie consent to a specific consent text or processing context. When you change your terms, prior consent does not automatically cover the new version — record a fresh grant against the new version string.

Query consent

activeFor returns only purposes whose latest event is granted — perfect for an account dashboard that lists "what you currently consent to".

CLI

For ops, backfills, and tests:

The command names keep the retention:consent: prefix for BC with the v1.x monolithic package. --consent-version rather than --version because Symfony already uses --version as a reserved option.

Verify the chain

Or run php artisan compliance:verify from the hub to verify every chain in the family in one shot.

What the log stores

consent_log is the only audit log in the family that stores the subject identifier directly. Consent inherently requires identification — you cannot prove "this person consented" without knowing who they are. Document that in your DPIA and apply your own retention policy to this table.

Per row: subject identifier, purpose, version, action (granted / withdrawn), source, optional metadata, occurred-at timestamp, plus the chain bookkeeping.

Compliance notes

GDPR art. 6(1)(a) — Consent as a lawful basis for processing.
GDPR art. 7 — Conditions for consent: demonstrability ("the controller shall be able to demonstrate that the data subject has consented"). The hash-chained log IS the demonstration.
GDPR art. 5(2) — Accountability. Idem.

This package is not legal advice. Whether consent is freely given, specific, informed and unambiguous is a question for your DPO.

Installation

Then add a secret to .env (shared with the rest of the family):

Gotchas

The log stores subject identifiers directly. That is necessary for art. 7 accountability — proof of consent has to be linkable to a real person. Mention this table in your DPIA.
No automatic deduplication. Two grant calls in a row produce two granted rows. Sometimes that is exactly what you want (re-affirming consent). When you want "only when not currently granted" semantics, check ConsentStatus::isGranted() first.
Withdrawal does not delete the prior grant. It records a new event that supersedes it. The grant stays in the log forever — that is what makes the chain a usable audit trail.
Forget does not automatically cascade to consent_log. A subject exercising their right to be forgotten (via laravel-data-right-to-be-forgotten) will not have their consent records removed unless you explicitly register ConsentEntry as Forgettable. The legal argument for keeping consent + withdrawal records even after forget is real (you may need them to defend the lawfulness of past processing), so this is opt-in rather than default.

Testing

Reporting bugs

Found a bug or unexpected behaviour? We want to hear about it.

Preferred — open a GitHub issue: https://github.com/ginkelsoft-development/laravel-data-consent/issues/new

When opening an issue, please include:

Versions — PHP, Laravel, and the package version (composer show ginkelsoft/laravel-data-consent).
What you did — the artisan command, code snippet, or steps that triggered the bug.
What you expected vs what actually happened — include full error output or a stack trace if there is one.
A minimal reproduction if you can — a failing test or a small code sample beats a long description.

Security-sensitive findings (anything that could expose personal data, break a hash-chain, or bypass an audit log) — please do not open a public issue. E-mail [email protected] directly with "SECURITY" in the subject line and we will respond privately.

Not on GitHub? You can also e-mail [email protected] with the same information.

Contact

For commercial support, integration questions, or anything that doesn't fit a GitHub issue: [email protected] — https://ginkelsoft.com.

License

All versions of laravel-data-consent with dependencies

PHP Build Version

Package Version

Version v1.0.0 Release 28. May 2026
create-project require 0 people chose require and
0 people chose create-project.

Download

Download latest version of laravel-data-consent from vendor ginkelsoft

Requires php Version ^8.2
illuminate/support Version ^10.0 || ^11.0 || ^12.0 || ^13.0
illuminate/database Version ^10.0 || ^11.0 || ^12.0 || ^13.0
illuminate/console Version ^10.0 || ^11.0 || ^12.0 || ^13.0
nesbot/carbon Version ^2.62 || ^3.0
ginkelsoft/laravel-compliance-core Version dev-development

Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package ginkelsoft/laravel-data-consent contains the following files

Loading the files please wait ...