Privacy Policy
Version dated 8 November 2026
This English version is provided for convenience. The French version prevails.
Purpose and controller
This policy covers two sets of processing operations:
- the dexlo.fr website and Dexlo’s business prospecting, including demo requests sent through the website form;
- the service: the Dexlo software, which client establishments access by subscription.
The sections on retention, recipients, transfers, security and your rights apply to both.
Controller, except for the operating data processed on behalf of hoteliers (see The Dexlo service: two distinct roles): Adam Ben Hadj Ali, sole proprietor (entrepreneur individuel, EI), trade name Dexlo, 41 rue Ernest Renan, 92310 Sèvres, France, SIREN 109 281 824, RCS Nanterre. Contact: contact@dexlo.fr.
The dexlo.fr website
The website sets no cookies. It stores only one item in your browser’s local storage: the display theme (light or dark; key “dexlo-theme”), and only if you choose it, so that it is kept from one page and one visit to the next. This item stays in your browser, is never transmitted to Dexlo or to any third party, and is deleted when you clear the site’s data in your browser. It measures its traffic using its host’s audience measurement tool, Vercel (see Audience measurement below).
It is hosted by Vercel. Like any host, Vercel processes visitors’ IP addresses and the pages requested in order to serve the website; these technical logs are retained for Vercel’s own periods, which are provided on request. Pages may be served from servers located outside the European Union. Legal basis: Dexlo’s legitimate interest in ensuring the security and availability of the website (Art. 6(1)(f) GDPR).
The product screens shown on the website are reproductions: the hotel and the figures shown in them are fictitious.
The website has a single form, the demo request, described below.
Audience measurement
The website measures its traffic with Vercel Web Analytics, its host’s audience measurement tool. The measurement script is served by the website itself, from its own domain; each page viewed results in a measurement being sent to Vercel.
Data recorded. According to Vercel’s documentation, each measurement may include: the date and time of the visit, the address of the page viewed, with some of its parameters (filtered by Vercel), the referring page, an approximate location (country, region, city), the operating system and the browser, with their versions, the device type (desktop, mobile or tablet) and the version of the measurement script. Vercel states that these measurements are linked neither to a person nor to an IP address, and are used only to produce aggregated statistics.
Recognising visitors. To count visitors without cookies, Vercel computes, from the incoming request, a hash that is valid for a single day: it is then automatically reset. A visitor therefore cannot be tracked from one day to the next, or from one website to another.
Why your consent is not requested. The tool sets no cookies, writes no data to your browser’s local storage and reads no identifier from it: it relies on the information your browser transmits to display the page. For these reasons, Dexlo considers that this measurement does not require your consent under Article 82 of the French Data Protection Act (loi Informatique et Libertés); the website therefore does not display a consent banner.
Legal basis. Dexlo’s legitimate interest in measuring traffic to its website (Art. 6(1)(f) GDPR).
Retention. Vercel guarantees that the statistics are retained for a period that depends on the plan subscribed (one month on the Hobby plan, twelve months on the Pro plan, twenty-four months with the Web Analytics Plus add-on or on the Enterprise plan) and states that it may retain them for longer, so that the plan can be upgraded without losing data. The maximum retention period is not documented by Vercel; it is provided on request.
Location and transfer. The measurements are processed by Vercel Inc., a company established in the United States, whose primary processing facilities are located in the United States; the precise storage location of the statistics is not documented by Vercel and is provided on request. For this transfer outside the European Union, Dexlo relies on Vercel Inc.’s certification under the EU-U.S. Data Privacy Framework, which benefits from an adequacy decision of the European Commission; this certification is active as of the date of this version.
Objecting to the measurement. You may object to this measurement at any time by preventing the script from running: by disabling JavaScript for this website, or by using a blocking extension in your browser; the website remains viewable. As the measurements are not linked to any person, Dexlo cannot retrieve those that concern you. For any question, or to exercise your rights, write to contact@dexlo.fr (see Your rights).
Demo requests
This section describes what happens to a request sent through the website’s “Request a demo” form.
Data collected
The information you enter: name, business email address, hotel, city, number of rooms and PMS used. These six fields are required to process your request: without them, it cannot be sent. The form sets no cookies; neither its submission nor the information you enter in it is transmitted to the website’s audience measurement tool.
Calculator estimate
The gain calculator runs in your browser: the figures you enter in it are not sent anywhere. If you click “Get this estimate”, they are attached to the demo form in two ways: the number of rooms is copied into the “Rooms” field, which you can change, and the estimate is shown below the form. Only the six fields above are sent with your request; the estimate and the calculator’s other figures stay in your browser.
How your request is handled
Your browser sends the request to Dexlo’s CRM (crm.dexlo.fr), an application hosted by Vercel whose server functions run in the Paris region. The CRM records it in its database, hosted by Supabase in the European Union, in the Frankfurt region (Germany). This database is dedicated: it is separate from that of the Dexlo service. The CRM then, where applicable, sends an email notification to Dexlo by means of Resend, from its Ireland region, in the European Union. This notification is received in Dexlo’s email system.
Protection against abusive submissions
Your IP address is not retained: only a hash of it, computed with a secret key (HMAC), is retained, for 30 days, to limit abusive submissions. This anti-abuse log also retains, for 30 days, a hash of the email address entered, computed with the same key, as well as the date and outcome of the submission.
Purposes and legal bases
| Purpose | Legal basis |
|---|---|
| Responding to your request: contacting you, organising the demonstration, making you an offer | Pre-contractual measures taken at your request (Art. 6(1)(b) GDPR) |
| Subsequent business follow-up, between professionals | Dexlo’s legitimate interest in developing its business with hoteliers (Art. 6(1)(f) GDPR) |
| Anti-abuse log | Dexlo’s legitimate interest in protecting the form against automated or abusive submissions (Art. 6(1)(f) GDPR) |
Retention periods
The data in your request is retained for three years from the last contact, then deleted, including the copy received by email. If your establishment becomes a customer, the data is subject to the periods applicable to customers (see Retention periods). The anti-abuse log is retained for 30 days. The notification sent by Resend and its sending log are retained for 30 days by Resend. The CRM database is subject to no backup: deleted data is erased without any backup copy.
If you had objected to prospecting by Dexlo, your request is recorded in order to respond to it, without any subsequent sales follow-up: your objection remains in force.
Recipients
Your data is neither sold, rented out nor assigned. It is processed by Dexlo and by its technical service providers: Vercel, Supabase, Resend and Dexlo’s email service provider (see Recipients and processors).
Your rights
You have the rights of access, rectification, erasure, objection (including objection to prospecting, at any time and without giving reasons), restriction and, where applicable, portability. To exercise them, write to contact@dexlo.fr; you will receive a response within one month. You may also lodge a complaint with the CNIL (see Your rights).
Business prospecting
Purpose. Dexlo prospects hotel establishments: identifying hotels, reaching their decision-makers, and following exchanges and opportunities through to subscription. For this, it uses its CRM (crm.dexlo.fr), which is separate from the Dexlo service: the CRM has access to none of the service’s data.
Data. Identity and business contact details (surname, first name, email address, telephone number, job title, professional social network profile address), notes and follow-up of exchanges, and establishment data (name, city, number of rooms, PMS, website).
Source. Publicly accessible professional sources (establishments’ websites, professional directories, professional social networks, trade fairs), direct exchanges, and demo requests.
Legal basis. Dexlo’s legitimate interest (Art. 6(1)(f) GDPR): prospecting professionals at their business contact details, in connection with their job. For emails sent to business addresses, on a subject related to the recipient’s job, prospecting does not require prior consent: the persons concerned are informed of it at the first contact and may object to it at any time.
Retention. Three years from the last contact, then deletion; if the establishment becomes a customer, the data is subject to the periods applicable to customers. If you object, your email address is kept on an objection list, for the sole purpose of no longer contacting you, for as long as necessary to respect your objection.
Access. The CRM is accessible only to accounts authorised by Dexlo; there is no public sign-up.
The Dexlo service: two distinct roles
For the service, Dexlo acts in two different capacities, on two different sets of data.
| Set | Data concerned | Dexlo’s role | Applicable framework |
|---|---|---|---|
| A | User account, invoicing, support | Controller | This policy (see Service processing for which Dexlo is the controller) |
| B | Establishment operating data (bookings, rates, booking pace) and, when the B2B CRM is activated, data on its business relationship with its B2B partners (see The B2B CRM) | Processor for the hotelier | Data processing agreement, Article 28 GDPR |
For set B, the hotelier is the controller: it determines the purposes and means, and Dexlo acts only on its documented instructions.
Service processing for which Dexlo is the controller
| Purpose | Data | Legal basis | Retention |
|---|---|---|---|
| Creating and managing accounts, authentication | Business email address, password hash (bcrypt), role, linked establishment, active status, creation date | Performance of the contract (Art. 6(1)(b) GDPR) | Term of the contract, then see Retention periods |
| Service security, technical logging | Request identifier, method, path, status code, duration, timestamp | Legitimate interest (Art. 6(1)(f) GDPR): security and continuity of the service | See Retention periods |
| Invoicing and accounting obligations | Billing details, invoices | Legal obligation (Art. 6(1)(c) GDPR) | 10 years (Article L. 123-22 of the French Commercial Code) |
| Support and customer relations | Exchanges by email or telephone | Performance of the contract or legitimate interest | See Retention periods |
There is no public sign-up: accounts are created by the publisher at the customer’s request.
Data read from the customer’s systems
For set B, the software reads three families of data.
Bookings
When the customer connects its PMS, the connector reads only nine fields per booking. The list is closed: a technical booking identifier, its status, the source channel, the creation, cancellation and last-modification timestamps, the arrival and departure dates, and the requested room category.
None of these fields directly identifies a person.
B2B reading
When B2B reading is activated for the establishment (it is activated hotel by hotel, and only with the B2B CRM), the connector also reads, and only: the booking’s partner company (the one on whose behalf the booking is made) and the agency that acted as intermediary, with their names; the booking’s segment and rate, with their labels; the amount for the accommodation and the total amount of the booking, with the technical references these amounts need, which designate no one (link to the booking, line type, cancellation, currency). The list is closed.
In a company’s record, the PMS also provides a contact person, a telephone number, an invoicing email address, other contact details and notes: none of these fields is read. These data designate companies and agencies, not guests. A company’s name may, however, be that of a person (a sole trader): it is then treated as personal data.
Rates
The rates published by the establishment, as well as the public rates of its competitors collected from sources accessible to all. The latter are establishments’ prices, not personal data.
Booking pace
The pace (the number of bookings on the books by booking date and by night of stay) is derived from the timestamps above. It is not collected separately.
What else feeds the service
The establishment itself (name, type, city, geographical coordinates), its competitor panel, and public context data: weather, local events. These data do not relate to identified natural persons.
Sending a price to the PMS
When the sending feature is activated for the establishment during onboarding (it depends on the compatibility of the PMS), the customer can send to its PMS in one click, from a night’s file, the price it has chosen. No price is ever changed without the customer’s explicit action; by default, the decision is only recorded in the Dexlo software.
No directly identifying data of hotel guests
Apart from the case of exchanges described below, the service neither reads nor collects any directly identifying data of the hotel’s guests: no surname, first name, email address, telephone number, postal address, payment card number, identity document, stay preference or guest profile identifier.
This exclusion is structural:
- The connector cannot read what it does not request. The list of nine fields described above is an exhaustive allowlist. The fields that directly identify a person, or can be linked to one, which the PMS otherwise exposes (account, booker, profile or customer identifiers, payment method, number of guests, booking number, assigned room) are never accessed, not even transiently. Only B2B reading, when activated for the establishment, reads the agency and the partner company of a booking: businesses, not guests.
- The destination table has no column in which to write them. The data model that receives bookings contains no column that could receive directly identifying data.
The case of B2B CRM exchanges and documents. When the B2B CRM is activated, emails forwarded to a contract’s tracking address are filed in the contract’s thread as received, attachments included, and uploaded documents are kept as uploaded. Dexlo cannot prevent such a message or document from bearing a guest’s name, a rooming list for example. We therefore ask hoteliers not to send any list of guests’ names to it, and to inform their partners.
The B2B CRM
The B2B CRM is a feature of the service that helps the hotelier follow its B2B partners, agencies and companies: their contacts, their contracts, the documents and the exchanges, and what they bring to the hotel. It is activated establishment by establishment, at the customer’s request. It is separate from Dexlo’s prospecting CRM (crm.dexlo.fr), which has access to none of the service’s data.
For this data, the hotelier is the controller and Dexlo the processor (set B, see The Dexlo service: two distinct roles): it falls under the data processing agreement, and data subjects exercise their rights with the hotelier.
Partners’ contacts
- Purpose: business follow-up of the hotel’s partners and sending them their contracts. No prospecting of new accounts.
- Data: name, job title, business email address and telephone number, language.
- Source: entered by the customer’s users.
- Recipients: the customer’s authorised users; Dexlo and the service’s providers (see Recipients and processors); the user’s Google mailbox, for the messages the user sends.
- Retention: the hotel’s business relationship with the partner, then three years.
Contracts and documents
- Purpose: keeping and finding the hotel’s contracts with its partners, and sending them to the partners.
- Data: documents received from agencies, signed documents, corporate contracts generated by the service, summaries; the terms entered: commission, payment terms, period, notice, the agency’s booking procedure.
- Source: the customer’s users and the partners; the service, for the corporate contracts and summaries it generates.
- Where: documents are stored with Scaleway, in object storage, in the European Union.
- Recipients: the customer’s authorised users; the partners to whom a user sends them; Dexlo and the service’s providers.
- Retention: the end of the contract the document relates to, then five years.
Exchanges
- Purpose: keeping, in each contract’s thread, the messages exchanged with the partner.
- Data: for an email forwarded to a contract’s tracking address, the sender, recipients, subject, body and attachments; for a message sent from the B2B CRM, the copy kept by Dexlo (recipients, subject, body, attachment).
- Source: the partners and the customer’s users, who write or forward to the tracking address; Dexlo, for the copy of the messages it sends.
- Receipt: by Resend.
- The case of guests: an exchange may bear a guest’s name (see No directly identifying data of hotel guests).
- Recipients: the customer’s authorised users; Dexlo and the service’s providers.
- Retention: the end of the contract the exchange relates to, then five years.
Partners’ production
- Purpose: measuring, partner by partner, what agencies and companies bring to the hotel.
- Data: that of B2B reading (see Data read from the customer’s systems): companies, agencies, segments, rates and booking amounts. No guest data.
- Source: the customer’s PMS, when B2B reading is activated.
- Recipients: the customer’s authorised users; Dexlo and the service’s providers.
- Retention: that of the establishment’s operating data.
The weekly report
- Purpose: informing, every week, the sales director designated by the hotelier.
- Data: the recipient’s email address and the content of the report, drawn from the establishment’s B2B CRM data.
- Sending: by Resend, like the service’s other emails.
- Recipients: the designated recipient; Resend, which delivers the message.
- Retention: at Resend, provided on request.
Erasure. B2B CRM data is erased when its retention period expires, at the hotelier’s request, and at the end of the subscription in accordance with the data processing agreement. These periods are set out in the Retention periods section.
Google user data
When a B2B CRM user connects their Google Workspace mailbox to the service, Dexlo receives an authorisation from Google. Here is what it does with it.
- What Dexlo requests. Permission to send messages from your mailbox, and your account’s email address, to check that it belongs to a domain declared by your establishment or group: only those mailboxes can be connected. The sending permission allows Dexlo to send, never to read: Dexlo reads neither the messages in your mailbox, nor your contacts, nor your labels.
- What Dexlo receives and keeps. The refresh token for this authorisation, stored encrypted, which allows it to send the messages you ask it to send; and a copy of each message sent (recipients, subject, body, attachment), filed in the contract’s thread. This copy is that of the message Dexlo composes and hands over to Google; it is not read from your mailbox.
- Why. So that contracts and documents leave from your own address, and the exchange stays in the contract’s thread. No other use.
- Where. In the service, with its hosting providers (see Recipients and processors).
- Not passed on. Data received from Google is neither sold, nor assigned, nor transferred to any third party other than the service’s providers that host it, nor used for advertising, nor used to train an artificial intelligence model. No one at Dexlo reads it, except with your consent, for the security of the service or to comply with the law. Your messages go only to the recipients you choose.
- Revoking. You can withdraw the authorisation whenever you want, from your Google Account settings (third-party access): no further message then leaves your mailbox. The token is kept until the authorisation is revoked, or until your user account is removed, then erased.
Limited Use. Dexlo’s use of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements. Dexlo’s use of information received through Google Workspace authorisations also adheres to the Google Workspace user data and developer policy.
Retention periods
There is currently no automatic erasure mechanism on expiry in the service, and the prospecting CRM purge is triggered manually: the periods below are commitments that Dexlo carries out itself.
| Data | Retention period |
|---|---|
| Demo requests and prospecting data | Three years from the last contact, then deletion, including the copy received by email. If the establishment becomes a customer: for the duration of the contractual relationship, then according to the periods applicable to customers set out below. |
| Form anti-abuse log | 30 days |
| Email address on the objection list | As long as necessary to respect the objection |
| Technical logs of the website and the prospecting CRM | Periods specific to the providers concerned, provided on request |
| Demo request notifications sent by Resend (emails and sending logs) | 30 days at Resend (Resend free plan) |
| Website traffic statistics (audience measurement) | Period guaranteed by Vercel depending on the plan subscribed: one month (Hobby plan), twelve months (Pro plan), twenty-four months (Web Analytics Plus add-on or Enterprise plan). Vercel may retain them for longer; the maximum period is provided on request. The hash used to recognise a visitor is valid for a single day only. |
| User account and authentication | Term of the contract, then erasure within three months of its end |
| Establishment operating data (set B, B2B reading included) | Term of the contract, then return and erasure in accordance with the data processing agreement |
| B2B CRM partners’ contacts | The hotel’s business relationship with the partner, then three years |
| B2B CRM contracts and documents | The end of the contract the document relates to, then five years |
| B2B CRM exchanges, including the copy of messages sent | The end of the contract the exchange relates to, then five years |
| Google sending authorisation token | Until the authorisation is revoked, or until the user account is removed |
| Service emails sent and received by Resend (password, Daily, weekly report and emails received by the B2B CRM) | Retention period at Resend provided on request |
| Service application logs | Seven days; the host’s own logs are retained for its own periods, provided on request |
| Invoices and accounting records | Ten years (legal obligation) |
| Support exchanges | Three years from the last exchange |
| Backups of the service database | Deleted data may remain in the host’s backups until they expire; the backup retention period is provided on request. |
| Backups of the prospecting CRM database | None: the database is not backed up (Supabase free plan). Deleted data is erased without any backup copy. |
The B2B CRM retention periods apply unless the hotelier, the controller of this data, instructs otherwise, and run during the subscription; at its end, the data processing agreement applies to all its data.
Recipients and processors
Data is neither sold, rented out nor assigned. It is processed, solely for the purposes described in this policy, by the following providers.
Website, demo requests and prospecting
| Provider | Role | What it receives | Place of processing |
|---|---|---|---|
| Vercel | Hosting of the dexlo.fr website and of Dexlo’s CRM (crm.dexlo.fr); audience measurement for the website | IP address and pages requested; for audience measurement, the data described in the Audience measurement section; for the CRM, the demo requests and prospecting data processed by its server functions | Website: pages may be served from servers located outside the European Union. Audience measurement: United States. CRM: server functions run in the Paris region. Company governed by U.S. law. |
| Supabase | CRM database and authentication | Demo requests, prospecting data, anti-abuse log, CRM access accounts | European Union, Frankfurt region (Germany). Company governed by U.S. law. |
| Resend | Sending of demo request notifications | The fields entered in the form | European Union, Ireland. Company governed by U.S. law. |
| Dexlo’s email service provider | Receipt of emails sent to contact@dexlo.fr and support@dexlo.fr, including demo request notifications | Content of the emails received | Provided on request |
Service
| Provider | Role | What it receives | Place of processing |
|---|---|---|---|
| Render | Hosting of the application, the database and the cache | All service data | European Union, Frankfurt region (Germany). Company governed by U.S. law. |
| Vercel | Hosting of the service’s authenticated interface (app.dexlo.fr) | Users’ requests (IP address, pages requested) and, on protected pages, the session token (user identifier and role, signed), read by the access control. Service data (bookings, rates, recommendations) is exchanged directly between the browser and the application hosted by Render, without passing through Vercel. | Execution region not fixed: the interface may run outside the European Union. Company governed by U.S. law. |
| Sentry | Monitoring of technical errors | Technical error reports, which may include technical elements of the request concerned | European Union |
| Resend | Sending of the service’s emails (password reset and change, Daily and, when the B2B CRM is activated, weekly report); receipt of emails forwarded to a contract’s tracking address (B2B CRM) | The recipient’s email address and the content of the message; for receipt, the email as received: sender, recipients, subject, body, attachments | Location and retention period provided on request. Company governed by U.S. law. |
| Scaleway | Storage of B2B CRM documents, when it is activated | B2B CRM contracts and documents | European Union. Company governed by French law. |
| DataForSEO | Collection of competitors’ public rates | Search subjects: establishments, locations, dates. No customer data. | Not applicable: no personal data is transmitted to it. |
The customer’s PMS
The customer’s PMS is not a processor of Dexlo: it is the customer’s tool, under its own contract. Dexlo connects to it with the access credentials the customer grants it: it receives data from it and, when the sending feature is activated, transmits to it the prices the customer decides to send. Dexlo is not its principal. The customer remains in control of this connection and may revoke it at any time.
The user’s Google mailbox
When a B2B CRM user authorises sending, their messages leave from their Google Workspace mailbox, which is the hotelier’s: only mailboxes on a domain declared by the hotelier or its group can be connected (see Google user data). Google is the hotelier’s email provider, not a processor of Dexlo. Dexlo does not read this mailbox.
Public sources queried
The service queries public sources to which it transmits an establishment location or a search subject, and no personal data: weather services, local event services, a public geocoding service.
Transfers outside the European Union
The service’s application, its database and its cache are hosted in the European Union (Frankfurt region, Germany). The prospecting CRM database is hosted in the European Union (Frankfurt region, Germany) and its server functions run in Paris; demo request notifications are sent from Resend’s Ireland region, in the European Union. B2B CRM documents are stored with Scaleway, in the European Union.
The following may, however, take place outside the European Union: the running of the service’s authenticated interface by Vercel, whose execution region is not fixed (operating data does not pass through it, but the session token is read there), the delivery of the website’s pages by Vercel’s network, as well as the sending and receipt of the service’s emails by Resend, whose location is provided on request.
Messages sent from the Google mailbox of a B2B CRM user are carried by Google, the hotelier’s email provider.
Audience measurement for the website is processed by Vercel Inc. in the United States, where its primary processing facilities are located; for this transfer, Dexlo relies on Vercel Inc.’s certification under the EU-U.S. Data Privacy Framework, described in the Audience measurement section.
In addition, several providers, including Render, Vercel, Supabase and Resend, are companies governed by U.S. law: even where data is hosted in the European Union, access from the United States, in particular for administration or support purposes, cannot be ruled out and constitutes a transfer. The processing entrusted to Sentry is located in the European Union.
These transfers are subject to the conditions of Chapter V GDPR. The information Dexlo has on the safeguards governing them, provider by provider, is provided on request at contact@dexlo.fr.
Security
For the service, the following measures are in place; they are detailed in Annex 2 to the data processing agreement.
- Encryption in transit: access to the service over HTTPS only.
- Passwords: never stored in plain text (bcrypt hash, 12 rounds).
- Sessions: signed authentication token, set in an httpOnly cookie, marked secure (transmitted over HTTPS only) and SameSite=Strict in production; CSRF protection by double submission, mandatory in production.
- PMS access secrets: each establishment’s access token is encrypted at rest (Fernet, dedicated key) and is decrypted only when it is used. It never appears in a log.
- Start-up guard: the application refuses to start in production if the configuration is dangerous (authentication bypass enabled, a secret left at its default value, missing encryption key, development database, or SQL query echo enabled).
- Access partitioning: access restricted to the establishment linked to the account; allowed origins limited to the official interface; public sign-up closed.
- Logs: application logging excludes the query string, request bodies and authentication headers.
- Sending prices to the PMS: only when the feature is activated for the establishment, and only on explicit action by a user of the customer.
- Hosting of the application and its database in the European Union (see Transfers outside the European Union).
For the prospecting CRM: access restricted to accounts authorised by Dexlo, with no public sign-up; the IP address of the persons who submit the form is not retained.
For the B2B CRM: its own measures, including the encryption of the Google authorisation token, are put in place before it is first activated for a hotel.
What is not promised: no multi-factor authentication at this stage; no quantified availability commitment; no measures other than those described above.
Your rights
Every data subject has the rights of access, rectification, erasure, restriction, objection and portability provided for in Articles 15 to 22 GDPR, under the conditions laid down therein. Objection to prospecting may be exercised at any time, without giving reasons.
- Website, demo requests, prospecting, accounts, invoicing and support: requests are made to Dexlo, at contact@dexlo.fr. A response is given within one month.
- Establishments’ operating data (set B), including B2B CRM data: requests are addressed to the hotelier, as controller. Dexlo assists the hotelier under the conditions of the data processing agreement and does not respond directly to the data subject.
Anyone may lodge a complaint with the CNIL: 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07 (www.cnil.fr).
No decision based solely on automated processing is taken with regard to the persons whose data is processed.
Data protection officer: Dexlo has not appointed a data protection officer, as the appointment is not mandatory given its activity and the volume of its processing; none of the three cases in Article 37(1) GDPR applies.
Changes to this policy
Any substantial change is brought to the attention of customers in writing. The version in force is dated at the top of this page.
A change in the use of Google user data is applied only after the users concerned have been informed and have given their consent again.