EMF Map · Powered by ZapAtlas

Privacy policy

Last updated: October 11, 2026

Paul Warner operates EMF Map and its browser extension, map website at emfmap.org, and account and access-pass service at license.emfmap.org. This policy explains how these services handle information when you use the extension and its related features.

Information the extension handles

• Listing and page information. On supported pages, the extension reads the current page URL and relevant listing data, such as location coordinates, address, listing identifier, property type, bedrooms, bathrooms, floor area, year built, displayed price, and a listing photo URL. Availability varies by page. These details identify the listing, place the badge, display property context, and prepare a link to the full map.
• Locations. To request an estimate, the extension sends the listing latitude and longitude to EMF Map, together with an authentication token, supported-site identifier, and analysis request identifier. It does not send the entire listing page or the listing photo to the estimate endpoint.
• Account and authentication information. We receive the email address you enter, send a one-time verification code, and process that code to sign you in. The extension stores its sign-in email, account identifier, authentication token, and analysis receipts in local extension storage. It does not read your email inbox.
• Trial and access usage. Our account service maintains trial counters, supported-site categories, analysis receipts, access status, request times, and related records needed to provide access, avoid charging the trial twice for a replayed analysis, enforce rate limits, and prevent abuse. It does not log your keystrokes, mouse movements, or general scrolling activity.
• Purchase information. If you buy an access pass, we record its package, amount, currency, transaction identifiers, payment status, and access dates. The extension can retrieve this history for your account. Stripe processes checkout and payment details; the extension and EMF Map account service do not receive your full payment-card number or card security code.
• Technical request information. Our hosting and account services receive standard information associated with requests, such as your IP address, request time, requested URL, and browser or user-agent information. IP addresses and account identifiers may be used for rate limiting and security. Operational logs may retain request metadata.
• Support and privacy requests. When you submit our contact form, we store the email address you provide, your request type, message, reference identifier, and submission time in our private support database. We may record internal notes and handling status to respond to and manage your request. The email entered in the form is not automatically verified, and submitting a request does not automatically change or delete an account.

The extension does not request access to Chrome's history database or collect a general history of unrelated browsing. It handles the current supported-page URL and listing content because they are needed for the badge and map features. It does not collect medical records, symptoms, or diagnoses, and it does not read email inboxes or chat histories. Support messages are collected only when you voluntarily submit the contact form described above.

Opening the full map

When you choose “Open full EMF Map,” the link may carry the listing coordinates and available property details, including its address, price, listing identifier, source URL, and photo URL, to emfmap.org. These details let the map show the same property and its context. If a listing photo is displayed, your browser requests it from the original image host, which can receive normal request metadata such as your IP address.

The full map may also use locations, map bounds, or postal codes you select or enter to retrieve infrastructure and enforce map-access limits. Saved map-view preferences may be kept in browser storage. The browser extension does not automatically request your device's GPS location. The website's optional “Use My Location” feature requests a location only after you choose it and grant the browser permission.

Local storage and permissions

The extension keeps sign-in and analysis information locally so you can remain signed in and revisit results. Authentication storage is restricted to trusted extension contexts; listing scripts do not receive the account token. Local caches hold estimate responses and validated integration configuration to avoid unnecessary repeated requests. These records are not synchronized through Chrome storage sync.

The extension uses packaged content scripts on the specific listing domains declared in its manifest to read relevant page information and display its badge. It does not request all-websites access, optional wildcard host permissions, or the scripting permission. You can manage access to the declared sites through Chrome's extension controls. Remote responses provide data, not executable extension code.

How we use information

We use information to provide magnetic-field estimates and infrastructure context, show listing details, verify your account, deliver sign-in emails, manage trials and access passes, process purchases, restore access, answer support requests, and maintain the service's reliability and security. We do not use browsing or listing data to build advertising profiles, sell leads, or determine creditworthiness or eligibility for lending.

Our use of information handled through the extension complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. We limit access, use, and transfer to the disclosed features and related operational purposes. Human access to extension user data is limited to your explicit consent, permitted aggregated and anonymized operations, security investigations, or legal obligations.

Sharing and service providers

Information may be processed by the hosting and email-delivery providers needed to operate EMF Map and send account messages. For purchases, we send Stripe your account email and checkout information; Stripe handles the payment and returns transaction information used to activate your pass. We may disclose information when necessary to comply with law or protect the service from fraud or abuse. We do not sell or transfer information to advertising platforms or data brokers.

The listing websites, original image hosts, and payment checkout pages you visit are separate services with their own privacy policies. This policy describes EMF Map's handling of information; it does not replace those services' policies.

Retention and security

We retain information for the period needed to provide access, support purchases and account recovery, meet applicable recordkeeping obligations, and protect against abuse. Trial and transaction records may remain after a pass expires. Authentication codes, sessions, and analysis receipts have validity limits. Cached estimate responses are reused only while valid; expired local cache entries may remain until replaced, cleared, or removed by the browser.

The extension's service requests use HTTPS. Authentication tokens are restricted to trusted extension storage, and the account service hashes stored authentication tokens and verification codes. Access controls and bounded operational diagnostics help protect the service. No storage or transmission method can provide an absolute security guarantee.

Your choices and requests

You can disable or uninstall the extension, manage site access, and clear its locally stored information using browser controls. Removing local information or uninstalling the extension does not automatically delete account, trial, or payment records from our servers.

To ask a privacy question or request access to, correction of, or deletion of account information, use our contact form below. No account or sign-in is needed to submit it. We may need to verify control of your account email before acting on a request. Some records may need to be retained for legal obligations, transaction support, security, or fraud prevention. Do not include payment-card details, passwords, or authentication codes in your message.

Policy updates

We may update this policy when features or practices change. The date above identifies the latest revision. Material changes requiring further disclosure or consent will be addressed before the affected collection or use begins.