Understanding how your data is used.

The controller for the processing described on this page is Steven Poivre, who leads the Enskel project.

For any question about your data, write to hello@enskel.com.

This page covers the enskel.com website. Processing carried out in the Enskel software for client sites is subject to information and commitments specific to that service.

The demo request form collects your first name, last name, work email address, brand or company, number of locations, the subject of your enquiry and your message. Phone number, role and how you heard about Enskel are optional.

This information is used to prepare the demo and to reply to your request, including a partnership proposal. Sending the form does not sign you up to any newsletter.

The language of the form and, when known, the address of the previous page on this site may accompany your request. URL parameters are excluded. These details are used to place your message in context, not to establish your acquisition source.

Your request is sent by email to the Enskel team via the Resend service, after technical processing by Cloudflare. Its content is added neither to analytics events nor to application logs. Resend’s commitments are described in its data protection agreement (Resend).

Your request is also recorded in HubSpot, the customer relationship management tool Enskel uses, whose account belongs to HubSpot’s European data region: your contact record, the details of your request and, for a demo or equipment request, a sales opportunity to be qualified. This does not subscribe you to any campaign or newsletter. If HubSpot is unavailable, Cloudflare keeps the request within the European Union only until it can be passed on, for seven days at most. HubSpot may use sub-processors located outside the European Union; its commitments are described in its data processing agreement (HubSpot).

If you book the demo in the calendar on the contact page, your first name, last name and email address, plus your site or group if you give it, are collected by Google Calendar, the Google Workspace tool Enskel uses. Google creates the appointment and sends you the invitation. The calendar only loads when you ask for it; Google may then set its own cookies. Google may process this data outside the European Union, notably in the United States; its commitments are described in its Cloud Data Processing Addendum (Google).

Retention period: [3 years after the last exchange]. You can ask for your correspondence to be deleted at any time by writing to hello@enskel.com.

Analytics is not currently enabled. No Google Analytics script is loaded. Enabling it will require updated information and your prior consent.

Delivering pages and securing the site involve technical exchanges with our provider Cloudflare: IP address, requested resource, request date and browser information. This technical processing is separate from optional analytics and is based on our legitimate interest in providing and protecting the site.

Worker logs and traces used for diagnostics are kept by Cloudflare for no more than 7 days, depending on its plan. Cloudflare operates a global network; its processing and transfer commitments are set out in its data protection agreement (Cloudflare).

The cookie that stores your choice is only used to remember your acceptance or refusal for 180 days. It is not sent to Google in the events we configure.

Under the conditions laid down by the GDPR, you have the rights of access, rectification, erasure, restriction of processing, objection and portability. You can withdraw your consent at any time, without affecting the processing carried out before the withdrawal.

Send your request to hello@enskel.com. We reply within the time limits set by the GDPR, normally within one month, and may ask you only for the information needed to verify your identity or find the data concerned.

You can also lodge a complaint with the French data protection authority, the Commission nationale de l’informatique et des libertés (CNIL).

Cookie names and durations, and how preferences work, are detailed in the cookie policy.