Consent Archive
The consent archive is a key component to ensure compliance with GDPR (General Data Protection Regulation) regulations.
Its purpose is to record and securely store evidence of consent expressed by users for the processing of their personal data, collected through forms or through interaction with the cookie banner.
This feature allows you to:
- Obtain legally valid proof of consent
- Demonstrate transparency in data collection
- Maintain compliance with privacy regulations
The consent archive is protected by security measures to ensure the confidentiality and integrity of the personal data recorded. Only authorized users can access the archive and registration operations are tracked and recorded to ensure the audit trail.
Integration methods
The integration of the consent archive on your site can be done in two ways (see the technical documentation for details):
- WordPress Plugin: The Avacy plugin natively supports the following contact forms:
- Contact Form 7
- HTMLForms
- WooCommerce checkout forms
Simply activate the form and configure the available options.
- JavaScript + REST API You can automatically send consents to the registry via HTTP calls to our API every time a user fills out a custom form.
Note: This option is also recommended if you want to track consent for contact forms that are not yet natively supported by Avacy.
Archive structure
The archive is divided into two main sections:
Register of consents from forms: This section collects the consents provided by users when filling out forms on the site (contact form, registration, purchase, etc.).
Cookie banner consent register: This section collects the consents provided by users through interaction with the cookie banner installed on the site.
Consent Import/Export: Using the two buttons in the top-right corner, you can now import consents to populate your archive or export the current list, including any active filters.
Import/export of consents
It is possible at any time to export collected consents or import consents previously managed by other platforms.
The two buttons are located at the top right of the page.
Import consents
Importing consents requires a file in .tsv format. This file must follow the structure defined by the platform. A template is available for download directly from the interface to assist in filling it out and eliminate any risk of error.
The detailed data format is as follows:
| Column | Optional/Mandatory | Content |
|---|---|---|
| External ID | Optional | Free text. |
| Identifier | Mandatory | Free text. |
| Consent Type | Mandatory (Header) | Text (e.g., "banner", "form"). Default: form |
| Consent Features | Optional | Free string values separated by commas or JSON. |
| Optin | Optional | In case of a form, fallback to accepted. |
| IP Address | Mandatory | Text (e.g., 192.168.1.1). |
| Source | Optional | Text. |
| HTML Form | Optional | HTML text. |
| Consent Data | Optional | JSON string or free text key=value separated by commas. |
| Created At | Mandatory | Date/time (e.g., 2024-01-15 10:30:00). |
| Imported At | Optional | Date/time (e.g., 2024-01-15 10:30:00). Default: current date/time. |
If one or more mandatory columns are missing from the import file, the import will not be completed, and an error message will be displayed indicating the missing columns. If some consent rows in the import file are missing mandatory data, the import will load all consents that have all the necessary data, notifying the error for those with missing data.
Export consents
It is possible to export consents present on Avacy in .tsv format. Depending on your needs, you can choose from several export options:
- Export full archive: Exports all consents in the archive, from both forms and banners.
- Export filtered archive: Exports consents from the archive of the currently active tab (either form or banner). If additional filters have been used (e.g., start date), these are also taken into account in the export result.
- Export selection: If you select one or more consents using the side checkboxes, only the selected items will be exported.