Back to Deenez

GDPR Compliance

The European Union General Data Protection Regulation (GDPR) is a regulation that aims at unifying EU member state data privacy regulations into a single regulation, enforced on the EU single market. This article describes the GDPR compliance status of Deenez.

If your company needs to ensure it is GDPR-compliant, it also needs to ensure its providers (ie. Deenez) are also GDPR compliant. Deenez is GDPR-compliant, and strictly enforces the regulation as to protect the user data we store.

Deenez and GDPR

The GDPR regulation can be reduced to 10 important points. For each point, we explain how Deenez handles its compliance. If we did not answer your questions in this article, you can still drop us a chat or email.

Also, please note that all Deenez data processor providers have been checked to be all GDPR-compliant (Stripe).

1. Awareness

All employees responsible for software development & infrastructure maintenance of Deenez are fully aware of the GDPR requirements.

Also, code reviews are performed by the Data Protection Officers (as listed in this article), before any code deployment to the platform. This ensures security breaches and bad practices are not implemented by eg. a third party temporary contractor or a Deenez employee, even if aware of GDPR requirements (this plays as a double human safety check).

2. Information we hold

Deenez stores data on 2 kinds of parties:

2.1. Information held on our users

Deenez collects account information for each user (we refer to them as customers in this article), including:

2.2. Information held on our users’ end-users

Information held on our users’ end-users include:

Deenez resolves end-user identity information (first and last name, avatar, company) from external APIs. Those external APIs sources from public information that the end-user consented to share on a third-party service (eg. on social networks such as LinkedIn or Twitter). This end-user identity information is stored on Deenez services, for as long as the Deenez customer wishes them to be stored in their Deenez CRM database.

The information held on our users’ end-users is solely the responsibility of our users (ie. the individual websites using Deenez). It is the responsibility of our users to manage the data they hold in the Deenez platform, ie. to remove sensitive data if someone may happen to share it with them (eg. Social Security Numbers, etc.). It is our responsibility to secure access to this data (ie. only website operators can access it and have a right to rectification and deletion).

3. Communicating privacy information

Deenez customers end-users privacy terms are the sole responsibility of Deenez customers. They should be announced on Deenez customers website.

4. Individuals right

5. Subject access requests

Deenez responds to all access requests (whether granted or denied) within one month. Where possible, we aim to respond within one week.

We offer this free of charge for our customers (paid and free).

6. Lawful basis for processing personal data

Deenez stores user data involving a consent (ie. a conversation both parties entered by will, and exchanged eg. emails).

It is the customer’s responsibility to ensure that any personal data submitted to or processed through Deenez is collected and used lawfully. For example, if a customer collects email addresses through Deenez and later uses them for marketing purposes (whether within Deenez or via an external system), the customer must have a valid legal basis to do so, such as obtaining the user’s consent where required.

7. Consent

Consent is provided by our users explicitly when proceeding an action or task (eg. when they provide user data).

Deenez allows its customers to submit user data in an automated way, via a frontend JavaScript API and backend REST API. This data must have been provided by the customer user in a consensual way, as it will get propagated to Deenez in an automatic way (if the customer implemented such API in their source code).

8. Children

Deenez does not offer online services to children, due to the nature of the service provided (business-to-business). Thus, we did not identified it as relevant to control the age of users signing up for services.

Children might still be able to use the Deenez services, from the website or apps of a customer. To this extent, the Deenez customer is responsible for checking against their own users and activities regarding children regulations.

9. Data breaches

Our team closely monitors any unauthorized system access, and has put in place multiple preventive measures to reduce the attack surface on our systems and services. From the start in 2026, Deenez has had 0 major security issues.

Here are a few measures we took to reduce any attack surface:

The points listed above help reduce the probability of a major data breach occurring.

10. Data Protection by Design and Data Protection Impact Assessments

Whenever Deenez develops a new system, security comes as a first when designing the architecture of such a system. Our first goal is to protect the integrity of the new production system, and the second goal to protect the user data that’s being stored and used by that system.

Changes to this GDPR Notice

We may update this GDPR notice from time to time to reflect changes in our practices, technology, legal requirements, or other factors. If we make material changes, we will notify customers at least 30 days before the changes take effect (for example via email and/or an in-app notice). What constitutes a material change will be determined at our sole discretion.

By continuing to access or use the Service after the changes become effective, you acknowledge the updated GDPR notice. If you do not agree with the updated notice, you should stop using the Service.

Contact Us

If you have any questions about this GDPR notice, please contact us at support@deenez.com.

This notice was last updated on 03.03.2026.