About This Guide

Ad Disclosure

No advertising currently runs on this site. This page states the rules that will govern it when it does, including where ads will never appear and which advertisers we will block.

Where things stand today

No advertising runs on this site. There is no ad network, no sponsored content, no affiliate link, and no paid placement anywhere in the guide as of the date above. Nothing you read here has been paid for by anyone.

We are publishing this page before there is anything to disclose, because the rules are easier to hold to when they are written down in advance.

What will change, and what will not

Advertising is the intended way this guide pays for itself. When it goes live, the following rules apply and this page will be updated to say that it has.

What will not change under any circumstances:

• Editorial independence. No advertiser gets to influence a rating, a ranking, a price figure, or whether a neighborhood is described honestly. If a neighborhood has no grocery store, a steep commute, or a flood history, the page says so regardless of who is buying inventory next to it.
• No paid placement in editorial. Neighborhoods, amenities and articles are never ranked, included or excluded for money. If that ever changes for a specific piece, it will carry a clear label at the top, and it will be the exception rather than a quiet practice.
• No advertorial disguised as editorial. Anything sponsored will be labelled as sponsored, in the piece, not in a footer.

Where ads will and will not appear

When advertising is live:

Ads will never appear:

• Above the first block of content on any page.
• Inside or adjacent to a lead form, where an ad could be mistaken for part of the form.
• On conversion pages: buyer and seller resources, the home valuation page, the agent and contact pages.
• On the map explorer.

Ads will be limited:

• A maximum of three ad units on any page.
• Amenity pages and articles carry the most permissive placement, roughly one in-feed unit per eight to ten items.
• Ad slots have reserved dimensions in the page layout so that loading an ad does not shift the content you are reading. That is a usability commitment as much as a technical one.

Consent: advertising will sit behind the same first-party banner and Cookie settings control that already govern analytics, and declining will mean no ad script loads and no advertising cookie is set. The honest caveat that applies to analytics today would apply here too: ignoring the banner counts as agreeing, because it enables itself after a few seconds. The privacy page sets that out in full.

Categories we will block:

• Competing real-estate brokerages and agent-lead products, because a guide that sends you to a competitor's lead funnel while claiming to be independent is not independent.
• We will also block categories that are predatory in a housing context where the ad platform allows that level of control.

Affiliate links

There are none today. If we ever use one, the link will be disclosed at the point of use, not only on this page.

Why we are telling you this

The value of this guide is that it is honest about places, including their downsides. That is worth nothing if a reader has to wonder whether a paragraph was bought. The purpose of this page is to make the answer checkable rather than a matter of trust.

If you see something on this site that looks like paid placement and is not labelled, tell us. If we got it wrong we will fix it and say so.

Related

See privacy for what the site collects. As of today that includes no advertising cookies of any kind, though it does include Google Analytics, which runs unless you decline the cookie banner and can be changed later from Cookie settings in the footer. See terms for the basis on which the guide is published.

Accessibility

An honest statement of where this site currently stands on accessibility: what is in place, what is known to be missing, and how to tell us when something blocks you.

Our target

We are working toward WCAG 2.1 Level AA. We have not completed a formal audit against it, so we do not claim conformance. What follows is what is in place and what we know is missing.

What is in place

• Semantic HTML. Pages are built with real headings, lists, landmarks and link text rather than styled generic elements, which is the foundation everything else depends on.
• A declared page language (lang="en"), so screen readers pronounce content correctly.
• A skip-to-content link on every page. It stays off-screen until focused, then appears at the top left, and its target moves keyboard focus into the main region rather than only scrolling the page.
• Designed keyboard focus styling. Focus is indicated with a deliberate high-contrast outline and offset rather than left to browser defaults, so you can always see where you are.
• Reduced-motion support. If your system asks for reduced motion, the site honours it: scroll behaviour becomes instant, content reveals appear without transition, background motion stops, animation is effectively disabled, and the animated statistics paint their final value immediately instead of counting up.
• Screen-reader-only text utilities, so labels can be provided to assistive technology without cluttering the visual design.
• Labelled search. The site search uses a search landmark role and its input carries an accessible label.
• Accessible form errors. When an enquiry form is rejected, the fields at fault are marked invalid programmatically, each error message is tied to the input it belongs to rather than just sitting near it, and a summary is announced to screen readers. Fields carry autocomplete hints so a browser or assistive tool can fill them, and every form on a page gets its own field ids so two forms can never collide.
• Text, not pictures of text. Data on this site is real text and real tables, so it can be read aloud, resized, translated and copied.
• Descriptive link text. Links say where they go rather than "click here."
• Image alt text is a required field in our content schema.
• No autoplaying video or carousels, and no time limits anywhere on the site.

Known gaps

These are real and we are not going to describe them as anything else.

• Colour contrast has not been formally audited across every component and both themes. We believe body text is comfortable; we have not verified every state of every element against the AA ratio.
• The map explorer is a stylized visual canvas with no non-visual equivalent. If you cannot use it, the same neighborhoods are all reachable as ordinary pages through the directory, but that is a workaround rather than a fix.
• Long neighborhood pages have no in-page skip target beyond the sticky section index. On a page with a dozen sections and several long inventories, that is a real amount of navigation.
• Alt text exists only where the content supplies it. The field is required by the schema, but a required field is not the same as a good description, and we have not reviewed them for quality.
• No formal audit and no assistive-technology testing programme yet. Nothing here has been tested end to end with a screen reader by someone who uses one daily, which is the only test that really counts.
• Third-party and embedded content, where we add it later, may not meet the same standard, and we will say so at the point of use.

What we are doing about it

Next, in rough priority order: run a contrast audit across the token palette and every component state; give the long neighborhood pages proper in-page navigation targets; work out a non-visual equivalent for the map explorer; review alt text for quality rather than presence; and then commission real assistive-technology testing rather than relying on automated checkers.

We will update this page as items move from the gap list to the in-place list, and change the reviewed date when we do.

Corrections to this page

An earlier version of this statement listed designed focus styling and reduced-motion support as missing. Both were in fact already implemented and had been since the site's first build, and we were wrong to list them. One narrower finding was correct: the animated statistics on the home page ignored the reduced-motion setting and counted up regardless. That has been fixed, and they now paint their final value immediately.

We are recording the correction rather than quietly editing it out, because a page about honesty in accessibility claims should be honest about its own.

If something blocks you

This matters more to us than the list above. If any part of this site prevents you from getting information you need, tell us:

• What page you were on.
• What you were trying to do.
• What happened, and what browser, device or assistive technology you were using, if you know.

Use the contact route on this site. We will respond, and if you need information that is trapped in an inaccessible part of the site, we will send it to you in a format that works for you while we fix the underlying problem. You should not have to wait for a code change to get an answer about a neighborhood.

A note on our content

Some of what makes this guide useful is dense: data tables, long inventories of parks and schools, and detailed housing figures. We are conscious that density and accessibility pull against each other. Our approach is to keep the underlying markup simple and semantic so that assistive technology can navigate it, rather than to simplify the content itself. If a particular table or inventory is hard to use with your tools, that is exactly the kind of report we want.

Methodology

How this guide rates neighborhoods, where its numbers come from, why some figures are deliberately left blank, and what we will not do.

The short version

We prefer a blank to a guess. Where a figure is not reliably available for a neighborhood, we leave it null and say why, rather than borrowing a citywide number and presenting it as local. Several pages on this site carry no headline median for exactly that reason, and that is a deliberate result rather than an unfinished one.

Editorial ratings (1 to 5)

Every neighborhood page carries the same nine ratings: walkability, quiet, family friendly, nightlife, nature access, affordability, new construction, lake views, and winter ease.

These are editorial judgements applied consistently across every neighborhood in the guide, not computed scores. They combine public data (the EPA National Walkability Index, Census ACS, City of Duluth parks and street data, NWS climate normals) with on-the-ground assessment of things no dataset captures: how steep a street is, whether a commercial block is genuinely walkable or merely close, and what a neighborhood is like in February rather than in July.

They are comparative within this guide. A 3.5 for walkability means "compared with other Twin Ports neighborhoods," not compared with Manhattan.

Ratings describe places, never the people who live in them. No rating on this site is derived from, or intended to signal, the characteristics of residents.

Walkability, and why we do not use Walk Score

We use the free, public-domain EPA National Walkability Index at block-group level as the data floor, combined with our own editorial walkability rating. We do not license or scrape Walk Score.

The editorial layer exists because distance-based indices measure the wrong thing in this city. Duluth rises several hundred feet from the lake to the ridge. A half mile across level ground and a half mile up a hillside avenue score identically and are not the same trip, particularly between November and March, when a steep residential street is typically cleared after the main routes. Our rating accounts for grade, winter maintenance and whether the reachable destinations are things a household actually needs, rather than only restaurants.

To be precise about that winter point, because it does real work in the rating: the adjustment rests on grade and on snow that a hillside street holds longer, not on any guaranteed order of clearing. The City of Duluth sets and revises its own snow-removal priorities, and they can change between seasons and between storms. Confirm the priority status of a specific street with the city rather than inferring it from this guide. The rating would stand even if every street were cleared simultaneously, because a steep avenue is harder to walk and drive in snow regardless of when the plow reaches it.

Where a page shows a numeric walk score, it is our EPA-derived figure plus editorial adjustment, and it is labelled as such.

Census data: the place-versus-tract problem

Tenure, rent and housing-structure figures come from Census ACS 5-year estimates (2023 vintage), pulled at tract level.

Neighborhoods are not Census geographies. Duluth's neighborhood boundaries are historical and often informal; Census tracts are drawn for statistical convenience. They do not line up. So every page carrying ACS data also carries an acs_source note naming the exact tract and FIPS code used, and states plainly that the tract is a best fit for the neighborhood centroid rather than a match.

Where the mismatch is material, the page carries an additional caution explaining it in specific terms. Three real examples from this guide:

• A tract can span a city line and cover two communities at once, so the figures describe the combined area.
• A tract can reach well beyond a small district into a downtown, dragging the median rent far below anything the district itself charges, because it picks up a concentration of multi-unit and subsidized housing.
• A tract can report far more housing units than physically sit in the neighborhood, because it takes in rural land around it. The character it reports may still be accurate even when the count is not.

We publish the numbers with the caveat rather than suppressing them, and we tell you which way the distortion runs.

Prices and market data

Market figures come from Redfin Data Center and Zillow Research (both free and redistributable with attribution), cross-checked against Lake Superior Area REALTORS where possible. Every price carries an as-of date.

Deliberately null medians. We leave a headline median blank when the underlying sample cannot support one. This happens in two situations:

1. Small-sample artifacts. A neighborhood where a handful of sales set the monthly median can show swings of 40%, 77% or 129% year over year. Those are changes in which houses happened to sell, not changes in value. Where we see that, we say so and give an indicative band instead.
2. No published geography. Some neighborhoods have no separate published median at all, and are folded into a larger or adjacent area. We name the proxy, explain how it is likely to mislead, and tell you to price from close comparables.

A null median on this site means "we checked and the honest answer is that no reliable figure exists," not "we have not got to it yet."

Schools

School facts come from NCES Common Core of Data, the Minnesota Department of Education and Wisconsin DPI, all public domain, plus district sites for non-statistical detail.

We build our own transparent rating from state report-card data. We do not republish GreatSchools or other licensed third-party scores, and we do not rate private schools, because state report-card data does not cover them.

On attendance boundaries: these change between years, and several edges in this region are genuinely ambiguous on published maps. Where that is true we say so on the page and tell you to confirm with the district rather than publishing a guess. Listing sheets and search-portal school tags get some of these wrong routinely.

Amenity records, and how we check they still exist

Parks, trails, schools, places of worship, restaurants and organizations each have their own record, sourced and dated.

Places of worship get a specific treatment because the failure mode is severe: a congregation that closed years ago can retain an intact-looking web presence, complete with a social page and a directory listing updated last month. We therefore confirm current operating status against denominational sources only: diocesan parish directories, synod congregation directories, denominational locators, or the congregation's own live site. Commercial church directories are never accepted as sole evidence.

Every worship record carries a status field. Where a congregation has closed, we keep the record marked closed for the historical value and state plainly that it is not a place to attend. Where we cannot confirm current status from a denominational source, we mark it unconfirmed rather than implying it is open.

Fair housing

Every neighborhood page passes a fair-housing review before publication, and carries a fair_housing_reviewed flag once it has.

The rules we apply:

• We describe places and features, never the race, religion, color, national origin, sex, familial status or disability of the people in them, and never imply who does or does not belong anywhere.
• "Who lives here" sections describe life stage and household type only, sourced to Census.
• We do not name the specific ethnic or religious groups who settled or built a neighborhood in narrative prose. Named institutions, including houses of worship and schools, appear under their own names and affiliations, because those are the institutions' own identities.
• Safety sections describe feel plus city-published trend data with a citation. We do not characterize residents and we avoid "safe/unsafe area" verdicts.

Indigenous history

Several places in this region carry Ojibwe names and history. Where we write about them we use the documented record: treaty texts and dates, the City of Duluth's own recorded place names, and the Ojibwe People's Dictionary for language. We attribute place-name translations to a language authority rather than to general web sources.

We do not invent texture we cannot source, and we do not write a confident paragraph about pre-contact presence built on secondary summaries. Where the record is thin, the page says less rather than more.

Sourcing rules

• Every factual claim carries a source and an accessed date.
• Facts are free; expression is not. We harvest facts and write original prose. We do not bulk-copy descriptions.
• We do not scrape sites whose terms prohibit it, including AllTrails, Zillow listings, GreatSchools and Niche.
• Where something is genuinely not on the public record, we mark it `` in the source rather than filling the gap with a plausible invention. Those markers are a to-do list, not decoration.

Corrections

We would rather be corrected than be wrong. If something here is inaccurate, tell us what and where and we will fix it and update the reviewed date on the page. Every page shows when it was last reviewed.

What this guide is not

It is not an appraisal, a market forecast, or advice about a specific transaction. Ratings are editorial opinion. Prices are dated third-party figures that move. Before acting on anything here, verify it for the specific property and talk to a licensed professional.

Sources

Where the facts on this site come from. Every source below is public record, free to redistribute with attribution, or used with permission, and every claim on a page carries its own citation and accessed date.

Demographics and housing characteristics

• US Census Bureau, American Community Survey (ACS) 5-year estimates, 2023 vintage, pulled at tract level via the Census API. Backbone for owner-occupancy, renter share, median rent and housing structure mix. Public domain.
• Census TIGER/Line boundary files.

Neighborhoods are not Census geographies. See the methodology page for how we handle the mismatch and where we flag it.

Market and prices

• Redfin Data Center and Zillow Research, both free and redistributable with attribution.
• Lake Superior Area REALTORS, the authoritative local association, for cross-checks.
• FHFA and FRED for longer-run context.

Listings themselves come from the MLS via IDX, which requires a broker agreement. This guide does not carry live listings.

Schools

• NCES Common Core of Data (public domain) for enrollment, grade span, and school identifiers.
• Minnesota Department of Education report card data.
• Wisconsin DPI / WISEdash for the Wisconsin side.
• District websites for non-statistical detail such as programs and campus arrangements.

We build our own transparent ratings from state data. We do not republish GreatSchools, Niche, or other licensed scores.

Parks, trails and recreation

• City of Duluth Parks and Recreation, including the parks listing and project pages.
• City of Superior parks information.
• Minnesota DNR and Wisconsin DNR for state parks, forests and trails.
• National Park Service where relevant.
• Superior Hiking Trail Association and COGGS for trail facts.
• OpenStreetMap / Overpass (ODbL, attributed) for geographic detail.

We do not scrape AllTrails.

Walkability

• EPA National Walkability Index, public domain, at block-group level, combined with our own editorial rating. We do not license or scrape Walk Score. Method on the methodology page.

Climate and winter

• NOAA / National Weather Service, Duluth office, for snowfall normals and records. The 1991 to 2020 seasonal snowfall normal of 90.2 inches, and the 140.1 inch record season of 2022 to 2023, both come from here.
• Minnesota DNR State Climatology Office.

Places of worship

• Diocesan parish directories and diocesan sites.
• Denominational synod and conference directories, including the ELCA Northeastern Minnesota Synod.
• Denominational locators for bodies including the LCMS and the AALC/TAALC.
• Denominational statistical services, including the United Methodist Church's own data service, which is how we confirm closures.
• Congregations' own live websites.

Commercial church directories are never used as sole evidence that a congregation is currently operating. See the methodology page for why.

Organizations and nonprofits

• IRS Form 990 Exempt Organization Business Master File, public domain and filterable by ZIP.
• Chambers of commerce and the City of Duluth community-club roster.
• Candid / GuideStar profiles.

History, place names and local color

• MNopedia, from the Minnesota Historical Society.
• Zenith City Press and Perfect Duluth Day for local history, cited and rewritten.
• Duluth News Tribune, including its "Our Neighborhoods" reporting.
• The Ojibwe People's Dictionary (University of Minnesota Department of American Indian Studies and University Libraries) for Ojibwe language and place-name glosses.
• City of Duluth for officially recorded Ojibwe place names.
• Treaty texts and Treaties Matter (Minnesota Humanities Center and partners) for treaty history.
• 1854 Treaty Authority for the administration of retained treaty rights in the ceded territory.
• Minnesota Digital Library primary-source sets.

Public safety

• Duluth Police Department annual reports, for citywide published trend data.

We cite city-published trends and do not characterize residents. See the fair-housing section of the methodology page.

Taxes and government

• City of Duluth finance and auditor pages.
• Minnesota Department of Revenue and Wisconsin Department of Revenue.
• County assessor records for parcel-level tax bills, which is the only reliable way to compare property tax across the state line.

Images

Photography follows our imagery policy: owner-supplied images where provided, otherwise public-record sources (city, tourism bureau, MN/WI DNR, NPS, Creative Commons and public domain) with attribution recorded on the image, and AI-generated images only for generic atmospheric use, labelled as such. We never present an AI-generated image as a photograph of a specific real property or named landmark, and we never depict identifiable real people.

What we deliberately do not use

• Walk Score (licensed).
• GreatSchools, Niche and similar licensed rating services.
• AllTrails and Zillow listing content (terms prohibit scraping).
• Commercial business and church directories as a sole source for whether something is currently open.

Corrections

If a source here is out of date, or a claim on a page does not match its citation, tell us what and where. We will fix it and update the reviewed date on the affected page.

Privacy

What this site collects: nothing beyond a session cookie and server logs unless you submit an enquiry form, and the full list of what an enquiry stores. Written to describe how the site actually works rather than to cover everything a website might hypothetically do.

The short version

Three things, and only three, and you control two of them.

1. Server logs and a session cookie, always. Ordinary operational data, described below.
2. What you type into an enquiry form, only if you submit one, along with a short list of the neighborhood pages you have viewed, which is kept in your own browser and sent only at that moment. Every form on this site is optional.
3. Google Analytics, unless you decline the cookie banner. If you ignore the banner it switches on by itself after a few seconds. Decline, and no analytics script loads and your browser never contacts Google. You can change the answer any time from Cookie settings on the About This Guide page (linked as Learn More in the footer).

There is no advertising on this site today, no tracking pixels, no account system, and nothing is sold or rented to anyone.

What we collect when you submit a form

The site has enquiry forms: a contact block, a home-valuation request, a neighborhood or market-report request, and an agent enquiry. They all post to the same place. When you submit one, we store:

• Your email address. This is the only required field, because we cannot reply without it.
• Your name, if you give it.
• Your phone number, if you give it.
• What you are interested in, chosen from a fixed list: buying, selling, both, a valuation, a report, relocation, or a general enquiry.
• A neighborhood or area of interest, if you give it.
• A street address, if you give it. The valuation form asks for one, because a valuation is about a specific property. Only fill this in if you want us to look at that property.
• Your message, if you write one.
• Which form you used and which page you were on when you submitted it, so your enquiry arrives with context.
• A short list of the neighborhood pages you have looked at on this site. This one deserves its own explanation, immediately below.
• The date and time, and a short reference code generated for your enquiry.

That is the complete list. We do not record your IP address, your browser's user-agent string, or the page that referred you as part of an enquiry, and there is no fingerprinting or profiling attached to it. (Your IP address is briefly sent to Cloudflare when you submit any form, purely to check you are not a bot — see Third parties — but it is not stored with your enquiry.)

Two other forms

Beyond the enquiry forms above, two smaller forms exist, and each stores only what it needs:

• "Submit an idea" on a neighborhood page stores the idea or suggestion you write (required), your name and email if you choose to give them, and which neighborhood it was about. Name and email are optional; we only need them to reply if you want one.
• "Report an inaccurate detail" on a guide page stores the correction you describe (required), your email if you give it, and which page and section it was about, so we can find and fix the detail. Email is optional.

Both are handled exactly like an enquiry — written to files on the server and emailed to the owner (see below) — and neither records your IP address, user-agent, or referring page.

About the neighborhood list

As you read, your browser keeps a short list of which neighborhood pages you have opened. It is stored in your own browser using local storage, and it stays there.

It is not sent anywhere unless you submit an enquiry. If you never use a form, that list never leaves your device, and we never see it. If you do submit one, it is sent with your enquiry so that whoever replies knows which areas you were actually looking at, rather than having to ask.

The specifics, so you can judge it rather than take our word for it:

• It is only neighborhood names, not every page you visited, not how long you stayed, and not anything you typed.
• It is first party. It is not shared with Google Analytics, with any advertiser, or with any other third party, and it is not joined to analytics data.
• It is stored locally, so clearing this site's data in your browser erases it. Private or incognito browsing will not retain it between sessions either.
• Once submitted with an enquiry it is kept with that enquiry, under the same retention rule as everything else on this page.

We are describing this in detail because a record of what you have been browsing is a more revealing thing than a name and an email address, and it should not arrive as a surprise in a reply from an agent.

How it is used. To read your enquiry, reply to it, and where relevant connect you with a local agent. Nothing else.

Where it is stored and who sees it. Enquiries are written to files on the server, not to a database and not to a third-party marketing platform, and a copy is emailed to the site owner through Resend, an email-delivery provider (Third parties). They are reviewed by the site owner. We do not sell, rent or trade them.

How long we keep it. Until your enquiry has been dealt with, and no longer than one year afterwards as a business record. If you want yours removed sooner, ask and we will remove it.

A note on what you write. The message box is free text and reaches a person. Please do not put financial account details, government identifiers, or health information into it. Nothing on this site needs them.

What we collect whether or not you use a form

Server logs. Like effectively every website, the server records requests. A log entry typically includes your IP address, the page requested, the time, the referring page if there is one, and your browser's user-agent string. These are used to operate the site, diagnose faults and identify abuse. They are not used to build a profile of you, and they are not joined to form submissions.

A session cookie. The site runs on Laravel, which sets a session cookie and a related CSRF token cookie. These are strictly functional: they let the site work correctly across page loads and protect form submissions from cross-site request forgery. They do not track you across other websites. The session lifetime is currently 120 minutes.

Search terms you type. The search box submits by GET, which means what you searched for appears in the URL and therefore in server logs. Do not type anything into it that you would not want recorded in a log file. We do not link searches to identities.

Analytics, and the cookie banner

We use Google Analytics (GA4) to understand which pages people read and how they arrive, so we know what to write next.

How the banner behaves, stated plainly. When you first arrive, a banner asks about cookies and counts down. If you do not act on it, analytics turns itself on a few seconds later. If you decline, it does not.

That is timed implied consent, not explicit opt-in, and we would rather say so in those words than describe it as a choice you actively made. Doing nothing counts as agreeing. If that is not what you want, decline, and the decision sticks.

If you decline, no analytics script is fetched, no analytics cookie is set, and your browser makes no request to Google at all. That is not a preference we ask Google to honour; the code simply never loads their script. The guide works identically either way, and nothing is withheld from you for declining.

If you decline after it has already started, the page reloads itself into a clean state. Scripts that have already run in a page cannot be unloaded, so rather than leave analytics running until you navigate away, the site reloads without it. Some data from the seconds before you declined will already have reached Google; from the reload onward, nothing does.

If analytics is on, whether because you accepted or because the timer elapsed, Google Analytics loads and sets its own cookies, and usage data about your visit is shared with Google as a processor. Two settings are applied on our side:

• IP anonymisation is on.
• Google Signals is off, so your visit is not fed into cross-device tracking or ad personalisation.

Google's own handling of that data is governed by Google's privacy policy, not ours.

The consent cookie itself. Recording the outcome requires one first-party cookie, dg_consent_v1. It stores nothing but the answer, lasts about 180 days, and is set whichever way the decision goes, because otherwise we would have to ask you on every page.

Changing your mind, at any time. There is a Cookie settings control on the About This Guide page, reachable from the Learn More link in the footer of every page. It reopens the choice and tells you what is currently set, so you are changing a known state rather than guessing, and a decision made once, or made for you by the timer, is not permanent.

Advertising

No advertising runs on this site today. There is no ad network and no publisher account wired up. When advertising is introduced it will sit behind the same banner and the same Cookie settings control as analytics, and this page and the ad disclosure page will be updated to describe it before it goes live.

What we do not collect

• No tracking pixels or social widgets that report your visit to a third party.
• No account system. There is nothing to sign up for and no password to store.
• No sale or sharing of personal information. We do not sell it, rent it, or trade it.
• No third-party consent platform. The banner is our own first-party code, so accepting it does not hand your choice to a consent-management vendor.

Asking us about your information, or asking us to delete it

If you have sent us an enquiry and want a copy of it, want it corrected, or want it deleted, ask and we will do it. Use the contact form on this site, or the owner's email address if you have it, and tell us the email address you originally used so we can find the right record. If you have your reference code, include it.

Depending on where you live you may have rights of this kind under law. We are not going to claim compliance with a particular framework we have not been audited against, so we will simply say this: ask, and we will honour the request.

Third parties

A short list of third parties process data on our behalf or receive it as a necessary part of a feature.

Cloudflare Turnstile. Every form on this site is protected from spam and bots by Cloudflare Turnstile. When you submit a form, a Turnstile token and your IP address are sent to Cloudflare so it can confirm you are not an automated bot. We do not store your IP address; Cloudflare processes it for that verification under its own privacy terms. If Turnstile is not configured, this step does not run and no data goes to Cloudflare.

Resend. When you submit a form, its contents are emailed to the site owner through Resend, an email-delivery provider acting as our processor. Resend handles the message in transit to deliver it; it is not a marketing platform and your details are not added to any mailing list.

Google Analytics (only if enabled, and only after consent, as described above). When active it loads from Google, sets its own cookies, and shares usage data with Google as a processor, with IP anonymisation on and Google Signals off. Google's handling of that data is governed by Google's own privacy policy.

Fonts are self-hosted. The typefaces are served from this site's own server. Unlike many sites, your browser makes no request to Google Fonts or any third-party font service, so no third party receives your IP address to render the type.

Beyond that, pages may link out to other websites, including city, state and federal data sources, school districts, and businesses we describe. Those sites have their own privacy practices and we are not responsible for them. A link is not an endorsement.

Our hosting provider processes requests on our behalf, necessarily sees the traffic described in the server-log section above, and stores the enquiry files on our behalf.

Your choices

The banner. Declining is a real option and it is respected in full. But it is a decision you have to make in the moment, because ignoring the banner enables analytics rather than blocking it.

Cookie settings. The control on the About This Guide page (via Learn More in the footer) reopens the choice and reports what is currently set, so you can turn analytics off later just as easily as at the start.

Cookies and local storage. You can block or delete both in your browser. Blocking the session cookie will not stop you reading the site, and clearing this site's data also erases the neighborhood list described above. Note that it also erases your recorded choice, so the banner will ask again.

Do Not Track. We do not act on the Do Not Track header, and given that analytics switches on unless you decline, that is worth stating rather than glossing: if you rely on the header alone, it will not stop analytics here. Use the banner or Cookie settings.

Blocking it yourself. A content blocker or a browser that blocks third-party analytics will stop Google Analytics on this site, and we do nothing to detect or work around that.

Not sending us anything. Every form on this site is optional. You can read the entire guide without submitting one, and nothing about you is stored beyond the server logs described above if you do not.

Children

This site is aimed at adults making housing decisions. We do not knowingly collect information from children.

Security

We keep the site patched and we do not store personal data we do not need, which is the most effective security measure available to us. No site can promise perfect security, and we are not going to.

Changes to this policy

This page was last updated (20 August 2026) to reflect the current site: three submission forms are live (enquiries, "submit an idea", and "report an inaccurate detail"), all now protected by Cloudflare Turnstile and delivered to the owner by email through Resend; the site's fonts are now self-hosted, so no font request goes to Google. Consent-gated analytics is supported and loads only after consent; advertising is not live yet. When advertising is introduced, this page and the ad disclosure page will be updated to describe it, and the reviewed date at the top will change. Material changes will be described rather than quietly folded in.

Contact

Questions about this policy, or a request about your information, can go through the contact route on this site.

Terms of Use

The terms on which this guide is published: informational only, not advice about a specific transaction, no agency relationship, and an honest account of how far the data can be trusted.

What this site is

An independent editorial guide to neighborhoods, housing and daily life in Duluth, Superior and the surrounding Twin Ports region. It exists to help people understand places.

What this site is not

It is not advice about a specific transaction. Nothing here is an appraisal, a valuation, a market forecast, a recommendation to buy or sell a particular property, or a substitute for professional advice.

It does not create an agency relationship. Reading this site, using a form on it, or contacting us does not make anyone your agent, broker, or fiduciary. No agency relationship exists unless it is created by a separate written agreement.

It is not an offer. Descriptions of neighborhoods and properties are editorial, not solicitations.

It is not legal, tax, financial, engineering or inspection advice. Where we discuss property taxes across the Minnesota and Wisconsin line, inspection findings on older houses, or treaty history, we are describing the landscape, not advising you. Consult a licensed professional for your situation.

How far you can trust the data

We work hard on accuracy and we are explicit about its limits.

• Prices and market figures are dated third-party estimates that change. Every one carries an as-of date and a source. A median is a description of past sales, not a prediction about a specific house.
• Some figures are deliberately blank. Where a reliable neighborhood-level figure does not exist, we leave it blank and explain why, rather than substituting a broader number. A blank is a finding, not an omission.
• Census figures are tract-level. Neighborhood boundaries and Census geographies do not align. Pages carrying Census data name the tract used and flag where the mismatch distorts the result.
• Ratings are editorial opinion, applied consistently across the guide, and are not measurements.
• School attendance boundaries change, and several boundaries in this region are genuinely ambiguous on published maps. Confirm any assignment with the district before relying on it. Do not rely on this site, a listing sheet, or a search portal for school assignment.
• Business, congregation and organization details change, sometimes without any public signal. We check and date what we can and mark what we cannot.

The methodology and sources pages describe all of this in detail. Read them if a number here matters to your decision.

Verify anything you are going to act on. For a specific property, that means the current listing, a survey, an inspection, the actual tax bill, and the district.

Fair housing

This guide is published in compliance with fair housing law. We describe places and features and never the protected characteristics of the people who live in them, and nothing on this site should be read as steering anyone toward or away from any neighborhood. If you believe something here falls short of that, tell us and we will correct it.

Your use of the site

Please do not use the site to break the law, attempt to gain unauthorized access, place unreasonable automated load on it, or scrape it wholesale for republication.

You may quote reasonable extracts with attribution and a link. You may not copy the guide's content in bulk to build a competing resource.

Intellectual property

The editorial writing, ratings, structure and compilation on this site are ours. Underlying facts, and public-domain data from federal, state and municipal sources, are not owned by anyone and we make no claim to them. Third-party marks and images belong to their owners; images carry their credit and licence where we hold that information.

Links to other sites

We link out to data sources, districts, agencies and local businesses. We do not control those sites and are not responsible for their content, accuracy or practices. A link is not an endorsement.

Forms on this site

Three kinds of form are live: enquiry forms (contact, valuation and report requests), a "submit an idea" form on neighborhood pages, and a "report an inaccurate detail" form on guide pages. When you submit any of them, what you enter is stored on our server and sent to the site owner. Every form is protected by an anti-bot check (Cloudflare Turnstile). The privacy page lists exactly what each collects, how long it is kept, and how to ask us to delete it.

Some things follow from that:

• Submitting a form does not create an agency relationship, as set out above; an enquiry starts a conversation.
• Please do not put sensitive information in a message or idea box: no financial account details, government identifiers or health information. Nothing on this site needs them, and the box is free text that reaches a person.
• You are responsible for the accuracy of what you submit, and for having the right to submit it. Do not enter someone else's personal details, including a property address, unless you are entitled to.
• Ideas and corrections you send may be used to improve the guide. If you submit a suggestion or report an inaccuracy, you permit us to act on it and to incorporate factual corrections into the guide, without obligation to you and without any claim by you to the resulting content. We are not obliged to use, respond to, or retain any submission.

Disclaimer and liability

The site is provided "as is" and "as available," without warranties of any kind, express or implied, including any implied warranty of merchantability, fitness for a particular purpose, or accuracy.

To the fullest extent permitted by law, we are not liable for any loss arising from your use of, or reliance on, this site, including any decision to buy, sell, rent or move. Some jurisdictions do not allow certain limitations, so parts of this may not apply to you.

Changes

We may update these terms. The reviewed date at the top will change when we do, and continued use after that constitutes acceptance.

Governing law

These terms are governed by the laws of the State of Minnesota, without regard to its conflict-of-laws rules.

Contact

Questions about these terms, or a correction to something on the site, can go through the contact route on this site.

Cookies

What cookies this guide sets, why, and how to control them. Analytics and advertising cookies load only with your consent, and the guide works fully without them.

The short version

The guide works fully with no optional cookies. Analytics and advertising cookies are not set unless you allow them, and you can change your choice at any time.

Essential cookies

One small first-party cookie remembers your cookie choice so you are not asked again on every page. It stores only that choice and expires after 180 days. It does not identify you and is never shared.

Analytics and advertising cookies

If analytics or advertising are enabled on the guide, the relevant cookies load only after you consent. Decline and none are set; the guide behaves identically. When active, these cookies are set by Google (Analytics and, where present, AdSense) and are governed by Google's own policies in addition to this notice.

At present the guide runs without analytics or advertising configured, so no such cookies are set at all.

Managing your choice

When optional cookies are in use, a Cookie settings control appears so you can review or withdraw consent at any time. Withdrawing consent stops the relevant cookies loading on the pages you visit afterward.

Questions

Questions about cookies can go through the contact form or the addresses in the privacy notice.

Cookie settings