SITEDIA

Terms of Service

Effective October 2, 2026

1. Scope

These Terms govern your use of sitedia (the "Service"). By using the Service you agree to these Terms.

2. The Service

sitedia generates site analysis diagrams, 3D models, and sun, wind, and thermal comfort simulations from public spatial data.

Basic features are available without an account. Pro features require a paid pass. The Plans page lists which features are Pro.

Coverage for buildings, parcels, terrain, and vegetation depends on the source date, resolution, and regional availability of the underlying data. Not every dataset or feature is available at every location. Check the assumptions and units shown in the interface and the guides before relying on a result.

3. Accounts

You may create an account with Google or with an email address. You are responsible for your account and sign-in credentials. Accounts may not be transferred or shared.

4. Paid passes

Pro features are used with a paid pass. Pass types, prices, and periods are shown on the Plans page and at checkout. A pass is valid only in the edition where it is bought — a pass bought in the US edition covers US sites only.

A pass period starts when your payment is confirmed. It ends at the same time on the same calendar date 3 months or 1 year later, depending on the pass. If that date does not exist in the final month, the period ends on the last day of that month. If you buy a pass while another pass is active, the new period starts when the current period ends.

A pass is a one-time purchase and does not renew automatically.

Free features remain available after a pass ends.

You must be 18 or older to buy a pass.

Polar Software, Inc. sells passes and processes payments as the merchant of record. Payment transactions are also governed by the Polar buyer terms. Consumer rights that cannot be waived under applicable law are unaffected.

Cancellations and refunds follow the Refund policy. The Refund policy does not limit consumer rights under applicable law.

5. Your outputs

You may use generated outputs in coursework, reports, and commercial projects, subject to the license terms and attribution requirements of the underlying data sources.

A pass does not transfer copyright in third-party data, and does not grant the right to extract or resell source datasets in bulk. Data that comes from OpenStreetMap (for example, transit stops, the walking network, and some building footprints) is licensed under the ODbL 1.0, and these Terms do not limit your rights under that license.

Where sitedia shows an Esri basemap or aerial image (for example, the aerial view in the UK version), that content is for viewing inside sitedia only. You must comply with Esri's applicable terms of use (the ArcGIS Location Platform terms, available from Esri Legal): you may not download, extract, cache, or redistribute that content, and you must not remove or hide the Esri attribution shown with it.

sitedia does not store your outputs in your account. Save the files you need to your own device.

When you show or distribute an output to others, include the Credits line shown under the diagrams.

6. Acceptable use

The following are prohibited. We may restrict access to an account that engages in them, with notice of the reason and how to appeal.

  1. Circumventing authentication or usage limits
  2. Accessing another person's account without authorization
  3. Automated bulk requests that disrupt the Service
  4. Infringing the rights of others

7. Limitations

Outputs are references for early-stage design. They are not certified surveys, legal boundaries, structural or environmental certifications, or permitting decisions.

Verify design and safety decisions against authoritative records and professional review.

Transit stop names and routes come from the agencies' public schedule data, provided as is and not endorsed by those agencies. For San Francisco: the San Francisco Municipal Transportation Agency (SFMTA) and its employees, officers, directors and agents shall not be liable for damages of any kind arising from the use of SFMTA transit data or any application that uses that data, including but not limited to direct, indirect, incidental, punitive and consequential, and/or special damages. For Boston: MBTA transit data is provided by the Massachusetts Department of Transportation (MassDOT) as is; MassDOT and the MBTA do not endorse sitedia. For Washington, DC: station and stop names come from Open Data DC (CC BY 4.0), which takes them from WMATA; WMATA and the District of Columbia do not endorse sitedia.

For Chicago: zoning, park and street data come from the City of Chicago Data Portal. 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. Parcel and building records come from Cook County Open Data (Cook County Assessor's Office), and station and stop names from OpenStreetMap (ODbL).

For Miami: parcel, street, park and transit data come from Miami-Dade County GIS, provided as is; Miami 21 zoning comes from the City of Miami under CC BY 4.0. Neither endorses sitedia.

For Dallas: parcel and appraisal records come from the Dallas Central Appraisal District, provided as is, in Collin County from the Collin Central Appraisal District through the Texas Open Data Portal, and in Denton and Kaufman counties from the Texas Geographic Information Office's StratMap parcels (CC0); zoning, park and street data come from the City of Dallas, for informational purposes only — not a survey and not suitable for legal, engineering or surveying purposes (Texas Government Code § 2051.102); bus stop locations, names and routes come from METRO's transit data — Route and arrival data provided by permission of METRO; METRO, the Metropolitan Transit Authority of Harris County, Texas, may withdraw that permission and does not endorse sitedia — and station names from OpenStreetMap (ODbL). Neither the District nor the City endorses sitedia.

For Houston: parcels and years built come from the Harris Central Appraisal District through the Texas Geographic Information Office's StratMap parcels (CC0); land-use, park and major-thoroughfare data come from the City of Houston GIS, which is in the public domain and provided for general reference only; bus stop locations, names and routes come from METRO's transit data — Route and arrival data provided by permission of METRO; METRO, the Metropolitan Transit Authority of Harris County, Texas, may withdraw that permission and does not endorse sitedia — and station names from OpenStreetMap (ODbL). Neither the District nor the City endorses sitedia.

For Denver: parcels, zoning, parks and street classes come from the City of Denver Open Data Catalog, licensed under CC BY 3.0; the data has been modified for use (joined to building footprints and drawn as diagrams). The City and County of Denver provides it as is, without warranty of any kind, and not for engineering purposes, and does not endorse sitedia. Bus stops and rail stations come from the Regional Transportation District's GTFS data under RTD's license agreement (a limited, revocable license, provided as is); sitedia is not endorsed by, sponsored by or affiliated with RTD.

For Seattle: parcels, years built, present use and floor area come from the King County Department of Assessments through the City of Seattle's parcel layer and King County GIS Open Data; zoning, park and street data come from the City of Seattle's open data. King County and the City of Seattle provide the data as is, without warranty of any kind, and do not endorse sitedia. Station and stop names come from OpenStreetMap (ODbL).

For Minneapolis: building use, years built, floor area, zoning, parks and street classes come from the City of Minneapolis's open data, dedicated to the public domain (CC0); parcel outlines come from Hennepin County GIS, which provides them "as is", with no representation as to completeness or accuracy and with no warranty of any kind, not for legal, engineering or surveying purposes. Station and stop names come from OpenStreetMap (ODbL).

Nothing here excludes liability for willful misconduct or gross negligence, or any liability that cannot be excluded under applicable law.

8. Changes

We will post notice of changes to these Terms in the Service at least 7 days before they take effect, or 30 days before for changes that are unfavorable to users.

9. Governing law and disputes

Inquiries and complaints may be sent to [email protected].

These Terms are governed by the laws of the Republic of Korea. Mandatory consumer protections where you live may also apply.

Effective date

These Terms take effect on October 2, 2026 and replace the Terms effective September 18, 2026.

Updated October 3, 2026: added the San Francisco, Boston and Washington, DC transit data notices in section 7.

Updated October 4, 2026: added the Chicago, Miami, Dallas, Houston and Denver data notices in section 7, and stated that a pass is valid only in the edition where it is bought (this was already how passes worked).

Updated October 6, 2026: added the Seattle and Minneapolis data notices in section 7.