BelongMapsOpen the map

Disclosures & Policies

Last checked

Data Sources & Attributions

BelongMaps integrates data from multiple government agencies, open data initiatives, and third-party services. We are committed to transparency about our data sources and compliance with their terms of use.

U.S. Government Data Sources

The following data is sourced from U.S. federal government agencies and is in the public domain:

U.S. Census Bureau

Data Used: American Community Survey (ACS) demographic and economic data, TIGER/Line geographic boundary files, TIGERweb mapping services

Required Disclosure:

"This product uses the Census Bureau Data API but is not endorsed or certified by the Census Bureau."

Source: census.gov/data/developers

Federal Bureau of Investigation (FBI)

Data Used: Uniform Crime Reporting (UCR) Program data, National Incident-Based Reporting System (NIBRS) crime statistics

Crime data is sourced from the FBI Crime Data Explorer API, which provides aggregated crime statistics reported by law enforcement agencies nationwide.

Source: Crime Data Explorer (cde.ucr.cjis.gov)

Federal Emergency Management Agency (FEMA)

Data Used: National Flood Hazard Layer (NFHL), flood zone designations, Special Flood Hazard Areas (SFHA); National Risk Index (NRI) v1.20.0; OpenFEMA Disaster Declarations Summaries (v2)

Flood zone data is provided by FEMA through the National Flood Hazard Layer. We show it over our own base map, so it is for general reference only. It is not an official FEMA flood map, and it is not for official National Flood Insurance Program (NFIP) purposes or insurance determinations.

Required Disclosures:

"This product uses the Federal Emergency Management Agency’s National Risk Index dataset API or downloadable datasets but is not endorsed by FEMA. The Federal Government or FEMA cannot vouch for the data or analyses derived from these data after the data have been retrieved from the Agency's website(s)."
"This product uses the FEMA OpenFEMA API, but is not endorsed by FEMA. The Federal Government or FEMA cannot vouch for the data or analyses derived from these data after the data have been retrieved from the Agency's website(s)."

The National Risk Index is meant for broad nationwide comparisons and is not a substitute for a local risk assessment.

Sources: FEMA National Flood Hazard Layer | FEMA National Risk Index Data v1.20.0 | OpenFEMA Dataset: Disaster Declarations Summaries - v2

Federal Highway Administration (FHWA)

Data Used: Highway Performance Monitoring System (HPMS): traffic counts, lanes and road types for every Federal-aid road, as reported by each state

Our traffic congestion layer is an estimate we compute from this data: how full each road gets at a typical weekday peak hour, extended into the surrounding neighborhood. It is not observed traffic, and it is not an FHWA product. How we estimate it.

Citation: U.S. Department of Transportation, Federal Highway Administration, Office of Highway Policy Information. Highway Performance Monitoring System (HPMS). National Transportation Atlas Database, Bureau of Transportation Statistics. https://doi.org/10.21949/91q8-zb78

USDA Forest Service

Data Used: Wildfire Risk to Communities, Risk to Potential Structures (2nd Edition)

Our wildfire layer is derived from this dataset. It is not the original Forest Service data publication, and it is not a substitute for a state, regional or local wildfire risk assessment.

Citation: Scott, Joe H.; Dillon, Gregory K.; Jaffe, Melissa R.; Vogler, Kevin C.; Olszewski, Julia H.; Callahan, Michael N.; Karau, Eva C.; Lazarz, Mitchell T.; Short, Karen C.; Riley, Karin L.; Finney, Mark A.; Grenfell, Isaac C. 2024. Wildfire Risk to Communities: Spatial datasets of landscape-wide wildfire risk components for the United States. 2nd Edition. Fort Collins, CO: Forest Service Research Data Archive. https://doi.org/10.2737/RDS-2020-0016-2

National Oceanic and Atmospheric Administration (NOAA)

Data Used: Office for Coastal Management Sea Level Rise data, NCEI U.S. Climate Normals (1991-2020), NOHRSC National Snowfall Analysis

The sea level rise layer shows the scale of potential flooding, not the exact location. It is a planning reference only and should not be used for navigation, permitting, or other legal purposes. Our climate layers are derived from NOAA data and are not official NOAA or National Weather Service products.

Source: NOAA Sea Level Rise Viewer

School Data

Data Used: NCES Common Core of Data and Private School Universe Survey, via the Urban Institute Education Data Portal; the U.S. Department of Education Office for Civil Rights Civil Rights Data Collection (CRDC); state education department report cards

Required Attributions:

Contains information from NCES Common Core of Data and Private School Universe Survey, via the Education Data Portal, Urban Institute, which is made available under the ODC Attribution License.
Contains data from the Civil Rights Data Collection, U.S. Department of Education Office for Civil Rights, licensed under the Creative Commons Attribution License. Contains data from the Washington Office of Superintendent of Public Instruction (OSPI), licensed under CC BY 4.0. Both have been modified: combined with other data into a school score.
"The data made available here has been modified for use from its original source, which is the State of Missouri. THE STATE OF MISSOURI MAKES NO REPRESENTATIONS OR WARRANTY AS TO THE COMPLETENESS, ACCURACY, TIMELINESS, OR CONTENT OF ANY DATA MADE AVAILABLE THROUGH THIS SITE. THE STATE OF MISSOURI EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the Web feed is being used at one’s own risk."

National Renewable Energy Laboratory (NREL) and U.S. Energy Information Administration (EIA)

Data Used: U.S. Electric Utility Companies and Rates: Look-up by Zip Code (2024), compiled by NREL from EIA Form 861 and other sources

Huggins, Jay. U.S. Electric Utility Companies and Rates: Look-up by Zip Code (2024). National Renewable Energy Laboratory (NREL), Open Energy Data Initiative (OEDI), data.openei.org/submissions/8563. Licensed under CC BY 4.0. Modified: where several utilities serve a ZIP code, the lowest rate is used; ZIP codes the dataset lists no utility for take a county average computed from Form EIA-861; rates are grouped into price tiers. Source: U.S. Energy Information Administration, Form EIA-861 (2024 data for the ZIP-code rates, 2025 data for the county averages).

Environmental Protection Agency (EPA) — Water Quality

Data Used: Three EPA data sources are combined for the Water Quality filter:

  • EPA ATTAINS — Impaired surface waters assessed under Clean Water Act Section 303(d). 500-foot buffer applied around impaired rivers, streams, lakes, ponds, estuaries, and coastal waters.
  • EPA Superfund/NPL — National Priorities List contaminated site boundaries. 1-mile buffer applied around site boundaries to account for contaminant plume migration.
  • EPA SDWIS — Safe Drinking Water Information System. Community water system service area boundaries for systems with active health-based violations (MCL/MRDL/treatment technique). No additional buffer — the service area polygon represents the affected area.

If any source flags a location, it is excluded from the overlay. Waters that states have not assessed are included. They are not on EPA’s impaired-waters list, but no measurements are available.

Areas outside a drinking-water violation or more than 1 mile from a Superfund site are not confirmed safe. Private wells are not covered by the drinking-water data. Brownfields, leaking fuel tanks and other smaller contaminated sites are in the Soil Contamination filter, not this one.

Sources: EPA ATTAINS | EPA Superfund | EPA ECHO/SDWIS

State Government Data Sources

California Geological Survey

Data Used: Official Map of Seismic Hazard Zones, in the Ground Movement layer for California

Modified from California Geological Survey, Webservice of Official Map of Seismic Hazard Zones(2017)

Open Data Sources

OpenStreetMap

Data Used: Points of interest (hospitals, schools, transit stations, restaurants, warehouse clubs), geographic features, road networks, water areas and airports. Every map overlay uses OpenStreetMap water and airport data, so every overlay contains OpenStreetMap data.

License: Open Database License (ODbL) 1.0

Required Attribution:

"Map data © OpenStreetMap contributors"
Contains information from OpenStreetMap, which is made available here under the Open Database License (ODbL).

The OpenStreetMap-derived layers (water, airports, warehouse-club locations, transit stops, roads) are available in machine-readable form under the ODbL on request: support@belongmaps.com.

Source: openstreetmap.org/copyright

Residential land (applies to every overlay)

Data Used: Every highlighted area is limited to land where homes are or may be: land that had at least one housing unit in the 2020 Census, land within 100 m of a mapped building, or land within 50 m of construction that satellite imagery shows since 2020. In Census blocks larger than 4 km² (about 1.5 square miles), only the land near the block’s homes is shown: within 250 m of a building or new construction, or within 100 m of where LandScan USA places residents.

  • USA Structures, Oak Ridge National Laboratory (ORNL); Federal Emergency Management Agency (FEMA) Geospatial Response Office. Licensed CC BY 4.0; modified by BelongMaps.
  • 10 m Annual Land Use Land Cover, Esri, Impact Observatory. Licensed CC BY 4.0; modified by BelongMaps.
  • LandScan USA 2021, Oak Ridge National Laboratory, doi.org/10.48690/1527701. Licensed CC BY 4.0; modified by BelongMaps.
  • Global ML Building Footprints, Microsoft, made available under the Community Data License Agreement – Permissive, Version 2.0.
  • 2020 Census block housing units and population, U.S. Census Bureau (public domain).
  • Annual National Land Cover Database, U.S. Geological Survey (public domain).

Database on Ideology, Money in Politics, and Elections (DIME)

Data Used: Ideology scores for elected officials, in the Local Politics layer

Contains information from DIME (Bonica, Adam. 2024. Database on Ideology, Money in Politics, and Elections: Public version 4.0. Stanford University Libraries), which is made available under the ODC Attribution License.

MIT Election Data and Science Lab

Data Used: 2024 presidential election returns, in the Political Leaning layer

Both datasets are dedicated to the public domain under CC0 1.0.

PRISM Group, Oregon State University

Data Used: 2023 USDA Plant Hardiness Zone GIS datasets

Our planting zone layer is derived from these datasets. It is not the official USDA Plant Hardiness Zone Map.

Source: PRISM Group, Oregon State University, https://prism.oregonstate.edu, accessed 2026-08-02

Home Prices

Data Used: Typical home prices, in the Housing Cost layer

Data Provided by Zillow Group.

Home-price medians: Redfin Data Center.

Starred Restaurants

Starred restaurants: locations of restaurants recognised with stars in the MICHELIN Guide, taken from the open-source michelin-my-maps compilation (MIT licence). Belong Maps is not affiliated with or endorsed by Michelin.

Other Sources

  • U.S. Geological Survey: landslide susceptibility, National Seismic Hazard Model, sinkhole susceptibility, Protected Areas Database (PAD-US), National Hydrography Dataset, National Land Cover Database
  • U.S. Environmental Protection Agency: Air Quality System, National Walkability Index, Facility Registry Service, Toxics Release Inventory
  • U.S. Bureau of Economic Analysis: Regional Price Parities
  • Bureau of Transportation Statistics: National Transportation Noise Map
  • Centers for Medicare & Medicaid Services: Provider Data Catalog, hospitals
  • U.S. Customs and Border Protection: airports with Global Entry
  • USDA Economic Research Service: Food Access Research Atlas
  • National Center for Education Statistics: IPEDS
  • National Radon Exposure Model: Li, Coull, Zilli Vieira and Koutrakis, 2025, Proceedings of the National Academy of Sciences
  • OurAirports, Open States, Wikidata
  • Ballotpedia: local elected officials, in the Local Politics layer

None of these agencies or organizations endorses BelongMaps. Their names are used only to identify the source of the data.

Local law-enforcement data notices

Our crime layer also uses crime data published by the cities, counties and agencies below. Their terms ask us to show these notices. Where a publisher gives the wording, it is quoted exactly.

Required disclaimers

City of Chicago

“This site provides applications using data that has been modified for use from its original source, www.cityofchicago.org, the official website of the City of Chicago. The City of Chicago makes no claims as to the content, accuracy, timeliness, or completeness of any of the data provided at this site. The data provided at this site is subject to change at any time. It is understood that the data provided at this site is being used at one’s own risk.”

City of Kansas City, Missouri

“This site provides applications using data that has been modified for use from its original source, www.data.kcmo.gov, the official open data website of the City of Kansas City. The City of Kansas City makes no claims as to the content, accuracy, timeliness, or completeness of any of the data provided at this site. The data provided at this site is subject to change at any time. It is understood that the data provided at this site is being used at one’s own risk.”

City & County of Honolulu

“The data made available here was modified for use from its original source, which is data.Honolulu.gov. The City & County of Honolulu does not vouch for the quality and timeliness of the data presented herein, any analysis of the data presented herein, nor any content, viewpoints, products, or services presented herein.”

Montgomery County, Maryland

“The data made available here has been modified for use from its original source, which is Montgomery County, Maryland ("the County"). THE COUNTY MAKES NO REPRESENTATIONS OR WARRANTIES AS TO THE COMPLETENESS, ACCURACY, OR TIMELINESS OF ANY DATA. THE COUNTY EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. THE COUNTY MAKES NO REPRESENTATION OR WARRANTY AS TO THE WEBISTE OR APPLICATION USING DATA DRAWN FROM DATA.MONTGOMERYCOUNTYMD.GOV OR FOR THE USEFULNESS OR INTEGRITY OF THE WEB SITE OR APPLICATION. The data is subject to change and possible deletion, temporarily or permanently. It is understood that the information contained in the web feed is being used at one's own risk.”

City of Tacoma

“The information and data made available here has been modified for use from its original source, which is the City of Tacoma. The City of Tacoma makes no claims as to the completeness, accuracy, or timeliness of any information and data contained in this application; makes no representation of any kind, including, but not limited to, warranty of the accuracy or fitness for a particular use; nor are any such warranties to be implied or inferred with respect to the information or data furnished herein. The information and data is subject to change without notice. It is understood that the information and data contained in the web site is being used at user’s own risk.”

City of Rochester, New York

“The data made available here has been modified for use from its original source, which is the official website of the City of Rochester, NY. The City of Rochester makes no claims as to the accuracy, timeliness, content, or completeness of any of the data provided in this application. The City of Rochester makes no warranty of the accuracy or fitness for any particular use; nor are any such warranties to be implied or inferred with respect to the information or data furnished herein. The data is subject to change as modifications and updates are complete.”

Licence notices

  • Dallas: Contains information from the Dallas Police Department, City of Dallas, which is made available under the ODC Attribution License.
  • Phoenix: Contains information from the City of Phoenix Police Department, which is made available under the ODC Attribution License.
  • Cleveland: Contains information from the City of Cleveland, which is made available here under the Open Database License (ODbL).
  • Rochester, New York: Contains information from the Rochester Police Department, which is made available here under the Open Database License (ODbL).
  • Scottsdale: Contains information from the City of Scottsdale Open Database Portal, which is made available here under the Open Database License.
  • Washington, DC: Contains data from the Metropolitan Police Department, District of Columbia, licensed under CC BY 4.0.
  • Fort Worth: Contains data from the City of Fort Worth Police Department, licensed under CC BY 4.0.
  • Charlotte: Contains data from the Charlotte-Mecklenburg Police Department, licensed under CC BY-NC-SA 4.0.
  • Indiana: Contains arrest data from the Indiana State Police, published by the Indiana Management Performance Hub, licensed under the Creative Commons Attribution License.

The Creative Commons data above has been modified: combined with other sources into area crime rates.

Source statements

  • Mesa: Source: City of Mesa, Mesa Police Department.
  • Louisville: Source: Louisville Metro Police Department, Louisville Metro Government Open Data Platform. Version: Louisville Metro KY Crime Data, 2023 to 2026 editions. Modifications: combined with other sources into area crime rates.

None of these cities, counties or agencies endorses BelongMaps.

Third-Party Services

Google Maps Platform

Services Used: Maps JavaScript API, Geocoding API, map tile rendering

Map visualization is powered by Google Maps Platform. Use of Google Maps is subject to the Google Maps Platform Terms of Service.

Firebase (Google Cloud)

Services Used: Firebase Authentication for user account management and secure sign-in

Stripe

Services Used: Payment processing for premium subscriptions

All payment information is processed securely by Stripe. BelongMaps does not store credit card numbers or sensitive payment details on our servers. See Stripe's Privacy Policy.

Amazon Associates

Services Used: Product ads marked “Ad” that link to Amazon.com

As an Amazon Associate I earn from qualifying purchases.

Data Accuracy Disclaimer

Important: While we strive to provide accurate and up-to-date information, BelongMaps makes no warranties regarding the accuracy, completeness, or reliability of any data displayed. Data is aggregated from multiple sources and may contain errors, omissions, or outdated information. Users should independently verify critical information before making real estate or relocation decisions. BelongMaps is a discovery tool and should not be the sole basis for purchasing, renting, or investing in real estate.

BelongMaps is not legal, financial, insurance, engineering, or real estate advice. Our flood, wildfire, tornado, and ground-movement layers are derived from government data and are not a substitute for official determinations, property inspections, state-mandated hazard disclosures, or an insurer's own assessment. Overlays and reports describe areas, not individual parcels. The Service shows data about places and events, not about the people who live there. See our Terms of Service for the full limits.

Privacy Policy

Our Privacy Policy is published at belongmaps.com/privacy (last updated ). It is reproduced below in full. The copy is drawn from the same source as that page, so the two cannot differ.

1. Introduction

BelongMaps ("we," "our," or "us") operates www.belongmaps.com (the "Service"). This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our Service. By using BelongMaps, you consent to the data practices described in this policy.

2. Information We Collect

2.1 Information You Provide

When you create an account or use certain features, we may collect:

  • Account Information: Email address, display name, and authentication credentials (managed securely through Firebase Authentication; we never see or store your password in plain text)
  • Profile Settings: Your display preferences, including theme selection (dark/light mode) and map overlay color preferences
  • Saved Filter Sets: Your named filter configurations, including filter selections and parameter values (premium feature)
  • Payment Information: Processed securely through Stripe; we store only subscription status, plan type, and billing cycle dates, never full credit card numbers
  • Support Communications: Messages and feedback you send to our support team

2.2 Information Collected Automatically

When you access the Service, we automatically collect:

  • Device Information: Browser type, operating system, device type, and screen resolution
  • Usage Data: Pages viewed, filters used, map interactions, time spent on the Service
  • Location Data: Approximate location based on IP address (used for initial map positioning only; we do not track precise GPS location)
  • Log Data: IP address, access times, referring URLs, error logs

2.3 Analytics and Performance Monitoring

We use Google Analytics 4 and Firebase Performance Monitoring (both provided by Google) to understand how the Service is used and to keep it fast and reliable. These tools collect information such as:

  • Usage events: Pages viewed and in-app actions such as applying or removing a filter, which filters you combine, creating a share link, generating a report, viewing plans, or starting a subscription
  • Performance data: Page load times, network request timing, and Core Web Vitals from your browser
  • Device and approximate location: Browser and device type, and coarse (city/region-level) location derived from your IP address

We use this information to understand and improve the Service — for example, which features people use and what leads them to subscribe — and we do not sell it. When you are signed in, these events are linked to your account by an internal identifier (never your name or email address), and when you subscribe we record which page led you to the plans page and your analytics browser identifier with the subscription, so we can see the path that led there. We keep a copy of this analytics data in our own Google Cloud account for that analysis. We do not send sensitive details such as specific addresses you search or the values of your filter settings to these tools; the most we record about where you are looking on the map is a general area roughly 50 km across. If you delete your account, that identifier is no longer linked to you. This data is processed by Google in accordance with the Google Privacy Policy.

Your choices: We honor your browser's "Do Not Track" and Global Privacy Control (GPC) signals — when either is enabled, we do not load analytics or performance monitoring at all. You can also opt out globally using the Google Analytics Opt-out Browser Add-on, or by blocking cookies for this site.

3. Cookies, Local Storage, and Browser Data

BelongMaps uses several browser storage technologies so the map picks up where you left off:

3.1 Local Storage

We store the following data in your browser's local storage. None of it leaves your device unless you are signed in and the item is also synced to your account (Section 4).

DataPurposeRetention
Map position & zoomRemember where you left off on the mapUntil cleared
Active filters & their valuesRestore your filter configuration between visitsUntil cleared
Theme and display preferencesRemember dark/light mode and overlay colorUntil cleared
Commute (travel-time) results you requestAvoid recomputing the same commute areaUntil cleared
IP-based approximate locationOpen the map near you without a lookup on every visit24 hours
Sign-in tokenKeep you signed inUntil you sign out
Small flags and bookkeepingWhether you dismissed a notice, which map tile versions you have, which provider you choseUntil cleared

3.2 Service Worker Cache (Cache Storage API)

To make the map faster, a service worker on your device caches:

  • Overlay tiles: The filter and housing-cost overlay images the map has already drawn, so panning back does not refetch them
  • Application assets: Code, images, and fonts the Service needs to load

Cached data is stored locally on your device and can be cleared through your browser's developer tools or by clearing site data.

3.3 Cookies

We use the following types of cookies:

  • Authentication Cookies: Set by Firebase to manage your login session securely
  • Payment Processing Cookies: Set by Stripe during checkout to prevent fraud and complete transactions
  • Google Maps Performance Cookies: Used by Google Maps for load balancing and performance optimization
  • Analytics Cookies: First-party cookies set by Google Analytics on this site only, and not set at all when your browser sends a "Do Not Track" or Global Privacy Control signal (see Section 2.3)

We do not set advertising cookies or cookies that follow you across other websites.

You can control cookies through your browser settings, but disabling them may affect Service functionality (particularly authentication and payments).

4. Cloud-Stored Data

For registered users, we store the following data on our secure cloud servers:

4.1 All Registered Users

  • Account credentials (email address and hashed authentication data, via Firebase)
  • Display name and profile information
  • Account creation date and last login timestamp
  • User preferences (theme, overlay color)

4.2 Premium Subscribers (Additional Data)

  • Subscription Details: Plan type (monthly/annual), subscription status, billing cycle dates, Stripe customer ID
  • Saved Filter Sets: Named filter configurations including filter selections, parameter values, and creation dates
  • Billing History: Invoice references and payment status (actual payment details are stored by Stripe)
  • Real estate professional features: A logo you upload for branded reports, and the email address of a client you invite with a guest code

4.3 Data We Do NOT Store

  • Credit card numbers or bank account details (handled entirely by Stripe)
  • Precise GPS coordinates of your physical location
  • Search history or browsing history outside our Service
  • Personal identification documents

5. How We Use Your Information

We use the information we collect to:

  • Provide, maintain, and improve the Service
  • Process subscription payments and manage your account
  • Personalize your experience (map defaults, saved filters, theme preferences)
  • Sync your preferences and saved filter sets across devices (when logged in)
  • Communicate with you about updates, features, and support requests
  • Monitor and analyze usage patterns to improve performance and features
  • Detect, prevent, and address technical issues, fraud, and abuse
  • Comply with legal obligations

6. Information Sharing and Disclosure

We do not sell your personal information. We may share information in the following circumstances:

6.1 Service Providers

We share data with third-party services that help us operate, including:

  • Firebase (Google): Authentication and user management
  • Stripe: Payment processing and subscription management
  • Google Cloud Platform: Hosting, database, and infrastructure services
  • Google Maps: Map rendering and location services
  • Google Analytics & Firebase Performance Monitoring: Usage analytics and application performance (see Section 2.3)

These providers are bound by their own privacy policies and contractual obligations to protect your data.

6.2 Legal Requirements

We may disclose information if required by law, court order, or government request, or to protect our rights, property, or safety, or that of our users or others.

6.3 Business Transfers

In the event of a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. We will notify you of any such change.

7. Data Security

We implement industry-standard security measures to protect your information, including:

  • HTTPS encryption for all data in transit
  • Encrypted password storage via Firebase Authentication (never stored in plain text)
  • Secure cloud infrastructure with role-based access controls
  • Regular security updates and vulnerability monitoring
  • PCI DSS compliant payment processing through Stripe

However, no method of transmission over the internet is 100% secure. We cannot guarantee absolute security of your data.

8. Data Retention

We retain your information for as long as your account is active or as needed to provide the Service:

  • Account data: Retained while your account is active; deleted within 30 days of an account deletion request
  • Subscription records: Retained for 7 years for tax and legal compliance
  • Analytics data: Linked to your account only by an internal identifier, which is unlinked when you delete your account; aggregate analytics may be kept (see Section 2.3)
  • Local storage and caches: Remain on your device until you clear them

We may also retain certain information as required by law or for legitimate business purposes such as resolving disputes, enforcing our agreements, maintaining records for financial and legal compliance, and preventing fraud and abuse. You may request deletion of your account and associated data at any time (see Section 10).

9. Third-Party Services and Links

The Service contains links to third-party websites and services, including Zillow, Redfin, and Apartments.com for property listings. We are not responsible for the privacy practices of these external sites. We encourage you to review their privacy policies before providing any personal information.

10. Your Rights and Choices

Depending on your jurisdiction, you may have the following rights:

  • Access: Request a copy of your personal data
  • Correction: Update or correct inaccurate information
  • Deletion: Request deletion of your account and data
  • Portability: Receive your data in a portable format
  • Opt-out: Unsubscribe from marketing communications
  • Analytics opt-out: Disable usage analytics and performance monitoring via a "Do Not Track" / GPC browser setting or the tools described in Section 2.3

To exercise these rights, contact us at support@belongmaps.com. We will respond within 30 days.

Clearing Local Data

You can clear locally stored data at any time through your browser:

  • Clear site data in browser settings (removes local storage and cookies)
  • Use browser developer tools to clear Cache Storage (map tiles)
  • Use private/incognito browsing to prevent any local storage

11. California Privacy Rights (CCPA)

California residents have additional rights under the California Consumer Privacy Act (CCPA):

  • Right to know what personal information is collected and how it's used
  • Right to delete personal information
  • Right to opt-out of the sale of personal information (we do not sell your data)
  • Right to non-discrimination for exercising your privacy rights

12. International Users

The Service is hosted in the United States and primarily serves U.S. users. If you access the Service from outside the US, your information may be transferred to, stored, and processed in the US where data protection laws may differ from those in your country. By using the Service, you consent to this transfer.

13. Children's Privacy

The Service is not intended for children under 13 years of age. We do not knowingly collect personal information from children under 13. If we become aware that we have collected such information, we will take steps to delete it promptly.

14. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of significant changes by posting a notice on the Service or sending an email to registered users. Your continued use of the Service after such changes constitutes acceptance of the updated policy.

15. Contact Us

If you have questions or concerns about this Privacy Policy or our data practices, please contact us:

By using BelongMaps, you acknowledge that you have read and understood this Privacy Policy.

By using BelongMaps, you acknowledge that you have read and understood these disclosures and our privacy practices.