This Cookie Policy explains how MapDove uses cookies and similar technologies on the MapDove marketing and documentation website (the “Site”) in the MapDove web application (the “App”), and in MapDove widgets that our customers embed on their own websites (“Widgets”). It supplements our Privacy Policy.
1. Summary
- The App uses one essential cookie,
ms_session, to keep you signed in. The Site and the App also remember your theme and language in local storage. - Analytics and session recordings on the Site and in the App. If you are in the EU/EEA, the UK or Switzerland, we ask first, and nothing is collected unless you accept. Elsewhere, analytics run without cookies. Session recordings always hide what you type into forms.
- Page speed measurement on the Site and in the App by our hosting provider, Cloudflare: no cookies or device storage, and not used for visitors in the EU.
- Widgets embedded on other websites set no cookies, use no device storage and load no analytics or third-party code. We count how often each widget is shown, without personal data.
- We use no advertising cookies, social-media trackers or fingerprinting.
2. What cookies and local storage are
A cookie is a small text file a website asks your browser to store and send back with later requests. Local storage is a similar browser feature that keeps data on your device; unlike cookies, it is not sent to the server automatically.
3. Marketing and documentation site
| Name | Type | Purpose | Duration | Sent to MapDove? |
|---|---|---|---|---|
| Theme preference | localStorage | remembers light, dark or other theme you chose | until you clear it | no |
| Locale preference | localStorage | remembers the language you picked | until you clear it | no |
Analytics and session recordings. The Site can send page views, clicks and error reports to our product analytics provider, and record sessions: a reconstruction of the page and your mouse movements, clicks and scrolling, so we can see where the Site is confusing. Recordings never contain what you type into forms (the waitlist and contact forms are always hidden), and they don’t include console logs or network contents. How it works depends on where you are, which we infer from your browser’s time zone:
- EU/EEA, UK and Switzerland: a banner asks for your consent. Until you accept, the analytics script is not loaded and nothing is sent. If you accept, it may set the
ph_*cookie and local storage described in section 4. Your choice is kept in local storage (ms.analyticsConsent), and you can change it at any time under Cookie preferences in the footer. Withdrawing consent deletes the analytics cookie and storage. - Elsewhere: no cookies are set. Analytics identifiers are kept in your browser’s session storage (
ph_*keys), so one visit across several pages counts as one session, and they are deleted when you close the tab.
Performance measurement (Cloudflare Web Analytics). Our hosting and network provider, Cloudflare, adds a small script to the Site’s and the App’s pages that measures how quickly they load and counts page views. It reports the page address, the referring page, your browser type and load timings. It sets no cookies, stores nothing on your device, doesn’t fingerprint you and isn’t linked to your account or to our product analytics. It is not added for visitors in the European Union.
The Site uses no advertising pixels, social-media trackers or fingerprinting. When you submit the waitlist or contact form, the information you enter is sent to us as described in the Privacy Policy.
4. Web application
| Name | Type | Purpose | Attributes | Duration |
|---|---|---|---|---|
ms_session |
first-party cookie | authenticates you after sign-in and protects your account | HttpOnly, SameSite=Lax, Secure (in production) |
up to 30 days, or until you sign out |
- HttpOnly means scripts in the page cannot read the cookie, which protects it from cross-site scripting.
- SameSite=Lax means the browser does not send it on most cross-site requests, which helps prevent cross-site request forgery.
- Secure means it is only sent over HTTPS.
The App may also keep interface preferences (such as theme or last-used panels) in local storage on your device. These are not used for tracking.
This cookie is strictly necessary: without it you cannot sign in. It is not used for advertising or to track you across other websites.
Product analytics. The App can send usage events (such as pages viewed and features used, with your user ID, role and organization) to our product analytics provider to help us improve it. The same provider receives error reports when something breaks in the App (the error message, stack trace, page address and browser), so we can fix it. It can also record sessions: a reconstruction of the screens you see and your clicks and scrolling, so we can find what is hard to use. Recordings hide everything you type, your AI assistant conversations, and your name and email in the account menu, and they don’t include console logs or network contents. Recording pauses entirely on settings pages, which show member details, API keys and two-factor setup, on the page where you approve a connected app, and while a PDF report is open for export, which shows your workspace name and logo. How it works depends on where you are, which we infer from your browser’s time zone:
- EU/EEA, UK and Switzerland: a banner asks for your consent. Until you accept, the analytics script is not loaded and nothing is sent. If you accept, it may set the cookie and local storage below. If you decline, nothing is collected. Your choice is kept in local storage (
ms.analyticsConsent) so we don’t ask again. You can change it at any time under Cookie preferences in the account menu, and withdrawing consent deletes the analytics cookie and storage. - Elsewhere: analytics run cookielessly. Their identifiers live only in the page’s memory and are discarded when you close or reload the tab, and nothing is written to cookies or local storage.
| Name | Type | Purpose | Duration | When |
|---|---|---|---|---|
ph_<project>_posthog |
first-party cookie | an anonymous analytics ID that links your visits | up to 1 year | only after you accept (EU/EEA, UK, CH) |
ph_* keys |
localStorage | analytics settings and queued events | until you withdraw consent or clear site data | only after you accept (EU/EEA, UK, CH) |
ms.analyticsConsent |
localStorage | remembers your analytics choice | until you clear it | after you choose |
Performance measurement. Cloudflare Web Analytics also runs in the App, exactly as described for the Site in section 3: no cookies or device storage, not linked to your account, and not added for visitors in the EU.
5. API
The MapDove API does not use cookies for programmatic access. Integrations authenticate with an API key sent in the Authorization header.
6. Embedded widgets
Customers can publish live MapDove charts and maps (for example a place’s visit trend or a city’s market snapshot) on their own websites. A Widget is a page served by api.mapdove.com inside a frame on the customer’s site.
- No cookies and no device storage. A Widget sets no cookies and writes nothing to local storage, session storage or any other storage on your device. It never reads the App’s
ms_sessioncookie, even if you are signed in to MapDove. - No analytics or third-party code. A Widget loads only its own script and stylesheet from
api.mapdove.com. It does not include our product analytics, session recordings, Cloudflare Web Analytics or any other third-party script, so the website you are on does not pass you to our trackers. - View counts without personal data. To enforce our customers’ plan limits, we count each time a Widget loads its data: one number per widget per month. We store no IP address, user agent, identifier or other information about you with that count. To protect the service from abuse, we use your IP address briefly, in server memory only, to limit how many requests one visitor can make per minute and to count repeated loads by the same visitor within 30 minutes only once; it is not written to a database. Like any web server, our servers and hosting provider may record technical request logs, which we keep as described in the Privacy Policy.
- The website that embeds a Widget is responsible for its own cookies and trackers, which this Policy does not cover.
7. Third parties
When you upgrade a plan, you may be redirected to a hosted checkout or billing page operated by our payment processor. That page is governed by the processor’s own cookie and privacy notices, which typically include cookies needed for payment security and fraud prevention.
Maps. The Site’s home and city pages and the App’s maps show a background map (streets, water, place names) from OpenFreeMap (tiles.openfreemap.org), a free map service built on OpenStreetMap data. On the Site the map is fetched only when a city map scrolls into view. Your browser requests the map images and fonts directly from OpenFreeMap, so OpenFreeMap receives your IP address, browser type and the address of our site (not the full page address), as with any web request. We send it no account or other information about you. These requests set no cookies and store nothing on your device. OpenFreeMap’s handling of that request data is governed by its own terms.
Sign in with Google. The App’s sign-in and sign-up pages show a “Continue with Google” button. It is a plain link: no Google script runs on our pages, and nothing is sent to Google unless you click it. When you do, you sign in on Google’s own page, which is governed by Google’s cookie and privacy notices, and Google then sends you back to the App. A short-lived value in your browser’s session storage (ms_google_signin), cleared when you return, protects that round trip.
8. Managing cookies and storage
- Sign out to end your session and invalidate the
ms_sessioncookie. - Use your browser settings to view, block or delete cookies and site data. Blocking the
ms_sessioncookie will prevent you from signing in to the App. - Clearing site data for the Site resets your theme and language to defaults.
9. Changes
If we introduce other non-essential cookies or device storage, we will update this Policy, change the “updated” date and request your consent where required before setting them.
10. Contact
MapDove · [email protected]