Aller au contenu
MapDove
    • Fréquentation Visites quotidiennes, visiteurs, durée de visite et profils horaires pour chaque lieu.
    • Sélection de sites Potentiel multicritère, prévisions Huff et cannibalisation avant de signer.
    • Zones de chalandise D’où viennent les visiteurs, qui ils sont et où ils font aussi leurs achats.
    • Intelligence de marché Tendances par catégorie, classements et benchmarks d’enseignes par ville.
    • Assistant IA Posez vos questions en langage courant ; les réponses viennent des analyses de MapDove, sur une carte.
    • API REST Chaque indicateur et chaque modèle derrière une clé API, avec sortie GeoJSON.
    • Retail Planification de réseau et performance des magasins pour les enseignes multisites.
    • Immobilier commercial Commercialisation, merchandising et acquisitions appuyés sur les données de visites.
    • Restauration Trouvez la prochaine zone de chalandise, protégez celles que vous avez.
    • Développement économique Montrez la vitalité d’un axe commerçant et attirez les bonnes enseignes.
  • Villes
  • Docs
  • Tarifs
  • Blog
  • English
  • Español
  • Deutsch
  • Français
  • Italiano
  • Português (Brasil)
  • العربية
Connexion Commencer gratuitement
  • English
  • Español
  • Deutsch
  • Français
  • Italiano
  • Português (Brasil)
  • العربية
Connexion Commencer gratuitement

Mentions légales

  • Conditions d’utilisation
  • Politique de confidentialité
  • Politique de remboursement
  • Politique relative aux cookies
  • Avenant relatif au traitement des données
  • Politique d’utilisation acceptable

Sur cette page

  • 1. Definitions
  • 2. Scope and roles
  • 3. Processing instructions
  • 4. Confidentiality
  • 5. Security
  • 6. Sub-processors
  • 7. Data subject requests
  • 8. Security Incidents
  • 9. Assistance
  • 10. Audits
  • 11. International transfers
  • 12. Return and deletion
  • 13. Liability and precedence
  • Annex 1 — Description of processing
  • Annex 2 — Technical and organizational measures
  • Contact
  1. Accueil
  2. Mentions légales
  3. Avenant relatif au traitement des données

Avenant relatif au traitement des données

Dernière mise à jour : 17 novembre 2026

Ce document est fourni en anglais ; la version anglaise fait foi.

This Data Processing Addendum (“DPA”) forms part of the Terms of Service or other written agreement (the “Agreement”) between MapDove (“Processor”) and the customer identified in the Agreement (“Customer”, “Controller”). It applies where MapDove processes Customer Personal Data in providing the Services. Capitalized terms not defined here have the meaning given in the Agreement.

1. Definitions

  • “Data Protection Laws” means all laws applicable to the processing of personal data under the Agreement, which may include the EU General Data Protection Regulation 2016/679 (“GDPR”), the UK GDPR and Data Protection Act 2018, the Swiss Federal Act on Data Protection, U.S. state privacy laws (such as the California Consumer Privacy Act as amended), and the UAE Federal Decree-Law No. 45 of 2021, each as applicable.
  • “Customer Personal Data” means personal data that MapDove processes on behalf of Customer under the Agreement.
  • “Sub-processor” means a third party engaged by MapDove to process Customer Personal Data.
  • “Security Incident” means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data.
  • “Controller”, “processor”, “data subject”, “personal data”, “processing” and “supervisory authority” have the meanings given in the GDPR; “business”, “service provider” and “sell”/“share” have the meanings given in applicable U.S. state laws.

2. Scope and roles

2.1 Customer is the controller (or business) and MapDove is the processor (or service provider) for Customer Personal Data.

2.2 MapDove is an independent controller for personal data it processes for its own purposes as described in the Privacy Policy — for example account administration, billing, security and fraud prevention — and this DPA does not apply to that processing.

2.3 Nature of the Services. The hosted MapDove analytics are built on open place data (OpenStreetMap and Overture Maps), aggregate public statistics and modeled visit estimates, none of which contain personal data. Customer Personal Data is therefore expected to be limited to the categories in Annex 1, unless Customer and MapDove agree in an Order to process customer-supplied data feeds.

3. Processing instructions

3.1 MapDove will process Customer Personal Data only on Customer’s documented instructions, which are the Agreement, this DPA, Customer’s configuration and use of the Services, and any other written instructions agreed by the parties. MapDove will inform Customer if, in its opinion, an instruction infringes Data Protection Laws.

3.2 Customer is responsible for the lawfulness of its instructions and for having a lawful basis, and any notices and consents required, for the processing of Customer Personal Data.

3.3 Service-provider commitments. MapDove will not sell or share Customer Personal Data; retain, use or disclose it for any purpose other than performing the Services or as permitted by Data Protection Laws; or combine it with personal data received from other sources except as permitted by law.

4. Confidentiality

MapDove ensures that personnel authorized to process Customer Personal Data are bound by confidentiality obligations and receive appropriate data protection training, and that access is limited to those who need it.

5. Security

5.1 MapDove implements appropriate technical and organizational measures to protect Customer Personal Data, taking into account the state of the art, costs, and the nature, scope, context and purposes of processing. Current measures are described in Annex 2.

5.2 MapDove may update its measures, provided that updates do not materially decrease the overall level of protection.

6. Sub-processors

6.1 General authorization. Customer gives MapDove general authorization to engage Sub-processors. MapDove currently uses Sub-processors in the following categories:

Category Purpose Data involved Location
Cloud hosting and infrastructure compute, databases, storage, backups, network delivery all Customer Personal Data held in the Services United States
Transactional email delivery sign-up, security and service notifications name, email address, message content Available on request from [email protected]
Payment processing (Paddle.com, our reseller and merchant of record) checkout, subscriptions, invoices, sales tax billing contact, organization ID, payment details (collected directly by Paddle) United Kingdom, United States
Error tracking and monitoring diagnosing faults and performance issues technical data, which may include user ID, IP address and request metadata United States
Website performance measurement (Cloudflare Web Analytics) measuring page load speed and counting page views in the web app page address, referrer, browser user agent, load timings; no cookies, not linked to user IDs; not collected for visitors in the European Union United States
Product analytics, session recordings and error tracking understanding how the web app is used and finding errors in it, to improve it user ID, role, organization ID and plan, pages viewed, features used, session recordings (screens and interactions, with all typed input and AI assistant conversations masked and settings pages, connected-app approval pages and PDF report previews excluded), error reports (message, stack trace, page address), IP address, browser user agent United States

| AI model provider: DeepSeek (Hangzhou DeepSeek Artificial Intelligence Co., Ltd.) | generating the AI assistant’s answers, only when a User uses the assistant (Customer’s owners and admins can turn it off for the workspace) | the User’s questions and the earlier messages of that conversation, and the MapDove data the assistant looks up to answer them; no name, email or user ID is sent. DeepSeek’s terms do not state whether API inputs are used for model training or for how long they are kept | People’s Republic of China |

A current list naming each Sub-processor is available on request to [email protected] [or at: link].

6.2 Obligations. MapDove will impose on each Sub-processor data protection obligations no less protective than this DPA and remains responsible for its Sub-processors’ performance.

6.4 AI assistants connected by Users. Users may connect third-party AI assistants (for example Claude, ChatGPT, Groq or coding tools) to the Services through MapDove’s MCP server, and Customer’s owners and admins can turn this off for the Workspace. When a User does so, MapDove discloses the data the assistant requests to that assistant’s provider at the User’s and Customer’s direction, as part of Customer’s instructions under section 3.1. The provider is not a Sub-processor of MapDove: it receives and processes that data under Customer’s or the User’s own agreement with it, and MapDove is not responsible for its processing. MapDove keeps a record of each connection (the app’s registered name and return address, the User and Workspace, approval and last-use times), the connection’s tokens as hashes only, and audit-log entries for approvals, revocations and detected token reuse.

6.3 Changes. MapDove will notify Customer at least 30 days before authorizing a new Sub-processor (by email to the account owner or a subscription mechanism). Customer may object on reasonable data-protection grounds within that period. The parties will discuss the objection in good faith; if no resolution is reached, Customer may terminate the affected Services and receive a refund of prepaid fees for the remaining term.

7. Data subject requests

Taking into account the nature of processing, MapDove will assist Customer by appropriate technical and organizational measures in responding to requests from data subjects to exercise their rights. If MapDove receives a request directly, it will redirect the data subject to Customer where the request relates to Customer Personal Data, unless legally required to respond. Many requests can be handled by Customer directly in the Services (for example, editing or removing members).

8. Security Incidents

8.1 MapDove will notify Customer without undue delay, and in any event within 72 hours, after becoming aware of a Security Incident affecting Customer Personal Data.

8.2 The notification will describe, to the extent known, the nature of the incident, the categories and approximate number of data subjects and records concerned, likely consequences, and measures taken or proposed. MapDove will provide updates as information becomes available and take reasonable steps to contain and remediate the incident.

8.3 Notification is not an acknowledgment of fault or liability.

9. Assistance

MapDove will provide reasonable assistance to Customer with data protection impact assessments and prior consultations with supervisory authorities, to the extent required by Data Protection Laws and relating to the Services.

10. Audits

10.1 MapDove will make available information reasonably necessary to demonstrate compliance with this DPA, including summaries of [third-party audit reports or security assessments], and answers to reasonable security questionnaires, no more than once per year.

10.2 If this information is insufficient to demonstrate compliance, or where required by a supervisory authority, Customer may conduct an audit with at least 30 days’ notice, during business hours, subject to confidentiality and at Customer’s cost, in a manner that does not compromise the security of other customers.

11. International transfers

Where Customer Personal Data is transferred to a country that does not provide an adequate level of protection under Data Protection Laws, the parties agree that the applicable Standard Contractual Clauses (Module Two, controller to processor, and where applicable the UK Addendum or Swiss amendments) are incorporated by reference, with Annexes completed by Annex 1 and Annex 2 of this DPA. MapDove will ensure equivalent safeguards for onward transfers to Sub-processors. Customer Personal Data sent to the AI model provider is transferred to the People’s Republic of China, which has no adequacy decision.

12. Return and deletion

On termination of the Services, MapDove will, at Customer’s choice, return Customer Personal Data (by self-service export or on request within 30 days) and then delete it within [90] days, including from backups on their normal rotation, unless retention is required by law. MapDove will certify deletion on request.

13. Liability and precedence

Each party’s liability under this DPA is subject to the limitations in the Agreement. If this DPA conflicts with the Agreement regarding the processing of Customer Personal Data, this DPA prevails. The Standard Contractual Clauses, where applicable, prevail over both.

Annex 1 — Description of processing

Item Description
Subject matter Provision of the MapDove location-intelligence and site-selection Services
Duration The term of the Agreement plus the return/deletion period
Nature and purpose Hosting, storage, retrieval, display and transmission of data necessary to provide, secure and support the Services
Data subjects Customer’s Users (employees and contractors); individuals mentioned by Customer in Customer Content
Categories of data Name, work email, role, organization, language and interface preferences, authentication and security events, the Google account ID of Users who choose Sign in with Google, IP address, audit-log entries, project names and notes, AI assistant conversations, records of the AI assistants Users connect (app name and return address, approval and last-use times; tokens as hashes), and any personal data included in Customer Content
Special categories None intended. Customer will not submit special-category data or data revealing the precise location or movements of identifiable individuals
Frequency Continuous for the duration of the Services
Customer data feeds (Enterprise) Only data aggregated to place and day (or hour) level, which should not constitute personal data; any exception must be agreed in an Order

Annex 2 — Technical and organizational measures

  • Encryption of data in transit (TLS) and of storage volumes and backups at rest at the infrastructure level.
  • Credential protection: passwords hashed with a modern, salted algorithm; API keys stored only as hashes and shown once at creation; OAuth tokens of connected AI assistants stored only as hashes, short-lived, bound to one User, Workspace and resource, with single-use authorization codes, PKCE and rotating refresh tokens whose reuse revokes the connection; session cookies HttpOnly, SameSite=Lax and Secure; sessions invalidated on password change.
  • Access control: role-based access within organizations (owner, admin, member); API keys cannot manage keys, members or billing; least-privilege staff access, with two-factor authentication required for platform administrators; logged administrative actions.
  • Account security: optional two-factor authentication for all users; throttling of repeated sign-in attempts.
  • Logging and monitoring: audit log of security-relevant events (sign-ins, failures, key creation and revocation, connecting and disconnecting AI assistants, plan and member changes, exports); error tracking and service monitoring.
  • Tenant isolation: all customer records scoped to the organization at the application and query level.
  • Resilience: regular backups, tested restoration, infrastructure redundancy as provided by the hosting provider.
  • Secure development: code review, dependency updates, automated testing, separation of development and production environments.
  • Vendor management: due diligence and written data protection terms with Sub-processors.
  • Incident response: documented procedure, on-call responsibility and post-incident review.
  • Data minimization: the analytics dataset consists of open place data, aggregate statistics and modeled estimates; no personal location data is collected or processed.
  • Embedded widgets: widgets Customer publishes on its websites show only the data of that widget, can be framed only by the domains Customer allows, set no cookies or device storage, load no analytics or third-party code, and record only a monthly view count per widget; visitors’ IP addresses are used transiently in memory for rate limiting and are not stored with view counts.

Contact

Privacy inquiries: [email protected] · Legal notices: [email protected] · MapDove

MapDove

Analyse de fréquentation, zones de chalandise et sélection de sites pour les équipes qui ouvrent des portes.

  • English
  • Español
  • Deutsch
  • Français
  • Italiano
  • Português (Brasil)
  • العربية

Produit

  • Fréquentation
  • Sélection de sites
  • Zones de chalandise
  • Intelligence de marché
  • Assistant IA
  • API REST
  • Tarifs

Solutions

  • Retail
  • Immobilier commercial
  • Restauration
  • Développement économique
  • Villes

Ressources

  • Docs
  • API REST
  • Méthodologie
  • Blog
  • Nouveautés

Entreprise

  • À propos
  • Carrières
  • Contact
  • Sécurité

© 2026 MapDove. Tous droits réservés. Les chiffres de visites sont des estimations modélisées. Lieux © contributeurs OpenStreetMap · © Overture Maps Foundation

  • Conditions d’utilisation
  • Politique de confidentialité
  • Politique de remboursement
  • Politique relative aux cookies
  • Avenant relatif au traitement des données
  • Politique d’utilisation acceptable
  • LinkedIn
  • RSS

Cookies et mesure d’audience

Nous souhaitons utiliser des cookies de mesure d’audience et des enregistrements de session (les champs de formulaire sont toujours masqués) pour comprendre comment les visiteurs utilisent ce site et l’améliorer. Rien n’est collecté sans votre accord, et vous pouvez modifier ce choix à tout moment via Préférences cookies en bas de page. Politique relative aux cookies