Privacy Policy
Effective date: October 2, 2026
This policy describes how Exploration Maps ("we", "us") collects and uses information when you use explorationmaps.com.
What we collect
How much we hold depends on whether you create an account.
Without an account, your map stays in your browser. We collect:
- Usage data — standard server logs (IP address, browser type, pages visited, timestamps) from our hosting provider (Vercel), plus first-party product analytics: pages viewed, searches run, features used, exports completed, and an anonymous session identifier. We use these to understand usage and diagnose issues.
- Email address — if you enter one to remove the large export watermark. It is also used to email you a sign-in link.
- Map data you import — files you upload are processed in your browser and are not sent to our servers unless you save a project, publish a share link, or sign in.
With an account, we additionally store, on our infrastructure:
- Account records — your email address, authentication credentials, and sign-in timestamps.
- Saved projects — the full map you save to the cloud, including imported geodata, styling, any logo or images you add, and a preview thumbnail.
- Account settings and brand kits — such as company name, Qualified Person name and credentials, projection defaults, and reusable styling.
- Product activity — which features you use, projects created, exports produced (and whether the file was branded or clean), all linked to your account.
If you publish a share link, a snapshot of that project — its geodata, styling, titles, company/QP metadata, and any embedded images — is stored on our servers and is readable by anyone who has the link. Share links are public and unlisted, not private. Do not publish material you cannot disclose.
If you connect an AI agent or use the Agent API, we store the connection name, a one-way hash of the API key, its scopes, creation and last-used timestamps, and technical records of map-generation requests (such as status, timing, map type, project/share identifiers, and error codes). We do not store the plaintext API key after it is created. Map requests can include mineral-registry search terms or, for connected accounts, geospatial data you intentionally send through the agent. Anonymous Agent API previews are rate limited and create expiring public share links; they do not save a project to an account.
If you subscribe or are invoiced, our payment processor (Stripe) handles your payment details; we never receive or store full card numbers. We store your Stripe customer and subscription identifiers, plan status, and — for invoiced work — invoice identifiers, amounts, status, and the hosted invoice link.
What we don't do
- We don't require an account to build and export a map — the editor works without signing in.
- We don't sell your personal information, or share it with third parties for their own marketing.
- We don't receive or store your full payment card details.
Cookies, local storage, and advertising
If you sign in, your browser stores a session token so you stay signed in. Your browser also stores local data (localStorage) to preserve your map between sessions and to remember your plan status briefly while offline. We keep the first referral page and campaign identifiers in your browser for up to 90 days, and attach that context to a new account so an email sign-in or a new tab does not lose the original referral.
We use Google Ads to measure whether our ads lead to a subscription. Google's tag runs on every page and, separately, records a conversion when a paid upgrade is verified. This involves cookies and shares limited data (such as the page you're on and, for a conversion, the plan value and currency) with Google. It does not include your name, email, or payment details. You can opt out using Google's Ads Settings or a browser extension that blocks advertising cookies.
Third-party services
We rely on the following providers, who process data on our behalf or as independent controllers:
- Vercel — hosting, server logs, and site analytics.
- Supabase — authentication, database, and storage for accounts, projects, settings, and share links.
- Stripe — subscription and invoice payment processing.
- Google Ads — conversion tracking for our advertising, as described above.
- Ahrefs — website traffic analytics (pages visited, referring site, approximate location and device type). It does not use cookies.
- Basemap tile providers (CartoCDN, Esri, OpenStreetMap contributors, OpenTopoMap, OpenRailwayMap, USGS) — your browser requests map tiles directly from them.
- Mineral claim registries — public registry services we query on your behalf when you search for claims.
- AI agents and connector platforms you choose to connect — such as Meta Muse or another agent client. Those services receive the API responses needed to complete your request and operate under their own privacy terms. Exploration Maps does not provide them broader access than the API key or anonymous preview endpoint permits.
- Google Fonts — typography; loading fonts involves a request to Google's servers.
Data retention
Account records, saved projects, settings, and brand kits are retained until you delete them or ask us to delete your account. Share-link snapshots are retained until the share is removed. Billing and invoice records are retained as long as required for tax and accounting purposes. Product analytics and server logs are retained on a rolling basis for operational analysis.
Your rights
You can request access to, correction of, export of, or deletion of the personal information we hold about you, including deletion of your account and its associated projects and shares. Email privacy@explorationmaps.com and we will respond within 30 days.
Changes to this policy
If we make material changes to this policy, we'll update the effective date at the top of this page. Continued use of the site after changes constitutes acceptance.
Contact
Questions about this policy: privacy@explorationmaps.com