Privacy Policy

Controller for data processing in connection with the website exportmymap.com and the ExportMyMap browser extension is:

Elizaveta Akimova
Märkische Allee 390
12689 Berlin
Germany
Email: exportmymap@gmail.com

This Privacy Policy explains how we process personal data when you:

• visit exportmymap.com,
• use the ExportMyMap browser extension,
• check paid access with your email address,
• generate a PDF,
• create a share link, or
• purchase a paid plan through Stripe.

When you visit our website, our hosting provider Vercel may process technical request data such as IP address, date and time of access, browser and device information, operating system, and referrer URL. This is necessary to deliver the website, maintain security, and troubleshoot technical issues.

Legal basis: Art. 6 para. 1 lit. f GDPR (legitimate interests in operating a secure and reliable website).

We use Google Analytics and Vercel Web Analytics to understand how our website is used and to improve performance and usability.

• Google Analytics may process usage data, page views, browser information, approximate location derived from IP, and interactions with the website.
• Vercel Web Analytics may process aggregated or technical usage information about page visits and traffic patterns.

Where legally required, analytics are processed on the basis of consent under Art. 6 para. 1 lit. a GDPR. Otherwise, processing is based on Art. 6 para. 1 lit. f GDPR.

More information: Google Privacy Policy, Vercel Privacy Policy.

The ExportMyMap browser extension (Chrome, Edge, Opera, and Firefox) reads saved place data from Google Maps pages when you actively use the extension on those pages.

• Local exports: CSV, XLSX, JSON, GeoJSON, KML, and GPX files are generated locally in your browser.
• Print: when you choose Print, a hosted print page is opened.
• PDF generation: when you choose PDF, the selected place data is sent to our server so the PDF can be rendered and returned to you.
• Share links: when you choose to create a share link, selected place data may be stored on our server to make that link accessible later.
• Country lookup (paid plans): when you open a saved list, the extension sends the geographic coordinates of its places to our server so that each place can be matched to a country and you can filter by country before loading place details. Only coordinates and short numeric identifiers are transmitted — no place names, addresses, or notes. The lookup is answered from a static map dataset on our own server; coordinates are not stored or logged, and results are cached in your browser so the same coordinates are not sent again.

Selected place data can include, depending on the feature used, place name, address, coordinates, rating, phone number, website, opening hours, Google Maps link, and similar place details.

Legal basis: Art. 6 para. 1 lit. b GDPR (performance of the requested service) and Art. 6 para. 1 lit. f GDPR (technical operation and abuse prevention).

When you share a list or trip plan, recipients use its existing list link (/s/) or plan link (/p/). Search engines use the same page. We do not create a separate filtered copy for search: content shown on the shared page, including titles, place details and visible notes, may be indexed when indexing is allowed. This content may reveal personal information or private locations. Account email addresses and technical credentials are not displayed on the shared page.

New links first shared successfully on Free may appear in search engines. New links first shared with active paid access are marked not to be indexed, but anyone with the link can view them. Plans saved to your account remain unlisted, including after paid access expires. The indexing setting is fixed when the link is first shared successfully; a later purchase, expiry or repeated Share does not change it. Older links keep their previous setting. Opening a plan, saving, autosaving, printing or generating a PDF does not itself allow indexing.

The shared page is the live list or plan, not a separate publication snapshot. Changes visible at the same link can also become visible to search engines if that link allows indexing. The browser keeps a secret used to confirm the first Share, and our database stores its hash, the indexing decision and timestamps. Where available, an account or purchase email is used to check paid access independently of optional analytics; these checks do not publish the email.

Earlier publication copies and their private management links retain their existing behavior. For those legacy copies only, anyone with the management link can use its controls: free users may delete the copy, while active paid users may also make it public or unlisted. Deleting a legacy copy clears its snapshot content and associated owner email but retains a minimal record of its identifier, credential hash, type, policy and timestamps to prevent recreation by a retry. Those controls do not remove its original list or plan link and do not change the indexing setting of a new list or plan link.

Shared links have no automatic expiry. For a privacy, removal or content request, contact exportmymap@gmail.com with the page link and your concern. Search engines and other recipients may retain cached copies after removal or a restriction on indexing; we cannot guarantee their removal timing or whether a search engine includes a page. See Public Lists and Routes in our Terms.

If you want to unlock paid access, you can provide your email address in the extension or on the website. We use that email address to check whether a matching purchase exists and whether the relevant plan is active.

We may collect technical statistics about the device and browser used with the extension, together with basic information about how the extension is used. We use this information to improve the product, maintain compatibility, and find and fix bugs. This analytics does not include your browsing history, visited URLs, or page content.

The same category also covers error reports and diagnostics: when the extension fails to read a saved list, it can send us the failing response together with the extension version and a random installation identifier, so we can restore compatibility when Google changes its pages. The debug-data toggle on the extension's welcome page controls the raw response content: with the toggle off, a failure report may still be sent, but it contains only technical metadata (extension version, response size, error type) and no page content.

In Firefox this technical and interaction data is collected only if you accept it on the browser's own consent screen when installing the extension. Declining it, or turning it off later under Add-ons, leaves every export feature working and stops all analytics, error reports, and diagnostics.

The extension may also store your email address, plan type, and access status locally in your browser storage so you do not have to re-enter the same information every time.

Legal basis: Art. 6 para. 1 lit. b GDPR for paid-access verification and Art. 6 para. 1 lit. f GDPR for proportionate product analytics and the legitimate interests described above.

Paid plans are processed through Stripe. Payment card details are processed directly by Stripe and are not stored by us.

We receive only the data necessary to confirm and manage your purchase, such as your email address, plan, payment or subscription status, Stripe payment identifiers, and expiration dates for time-limited plans.

Legal basis: Art. 6 para. 1 lit. b GDPR.

More information: Stripe Privacy Policy.

If you submit feedback after uninstalling, we store your selected reasons and any details you provide in Supabase. You can optionally leave an email address when reporting a problem, requesting a missing feature, mentioning another tool, or choosing “Other” so we can contact you about your feedback and help resolve issues. This address is stored with your feedback for support follow-up; it is not added to a mailing list. You can send feedback without providing an email address.

We use the following service providers to operate the product:

• Vercel for website hosting and serverless functions
• Supabase for server-side data storage related to purchases, share links, and extension lifecycle analytics
• Stripe for payments and subscription management

These providers process data on our behalf or as independent controllers to the extent necessary for their services.

More information: Supabase Privacy Policy, Vercel Privacy Policy.

We do not sell personal data to third parties. We do not use the data processed through the extension or the website for advertising profiling, credit scoring, or unrelated third-party marketing purposes.

We retain personal data only for as long as necessary for the relevant purpose or as required by law.

• Purchase and access data may be retained as long as needed to manage paid access and meet tax or accounting obligations.
• Share-link data may remain stored while the share link is active.
• PDF payloads are processed to generate the requested file and are not intentionally stored by us as a separate long-term dataset.
• Technical extension analytics are retained only for as long as needed to understand product usage and improve compatibility and reliability or to meet legal requirements.
• Website logs and analytics data are retained according to the applicable provider settings and legal requirements.

You have the right to request access to your personal data, rectification, erasure, restriction of processing, objection to processing, and data portability, subject to the applicable legal requirements.

If you want to exercise your rights, please contact us at exportmymap@gmail.com.

You have the right to lodge a complaint with a competent data protection supervisory authority if you believe that the processing of your personal data violates applicable data protection law.

We may update this Privacy Policy from time to time to reflect changes in the product, legal requirements, or service providers. The latest version is published on this page.