Privacy: Section 8 Rent Calculator

Calculation inputs stay in the page

Rent, income, utility allowances, payment standards and deduction entries are processed by JavaScript in your browser. The calculator does not submit those amounts to its aggregate event endpoint or save them in cookies or browser storage. If you choose to copy a scenario link, its URL fragment contains the entered figures. Fragments are not part of the HTTP request sent to this site, but anyone receiving that full link can read them. Browser history, extensions and a sharing application can also retain a copied link. Use that feature only for information you are comfortable sharing; reopening it requires confirmation of the applicable program amounts.

Reference requests and hosting

The ZIP lookup downloads a public reference shard selected by the first two ZIP digits. The complete five-digit code is matched locally against the downloaded data. Infrastructure therefore receives a request for a two-digit-prefix file, while the aggregate event payload does not include the entered ZIP. Ordinary page and asset requests also reach Cloudflare hosting, which necessarily handles connection information to deliver responses. This policy does not claim that hosting providers keep no operational logs. Opening a HUD or housing-agency citation takes you to a different service with its own collection practices.

Aggregate interaction events

The first-party events table records a limited set of actions: viewing a page, starting or completing a calculation, scrolling, opening a source, selecting a jurisdiction, copying a scenario or printing. Its fields include a page pathname, event name, a bounded interaction label, an in-memory random page-view identifier, referrer hostname, broad acquisition source and medium, country, mobile-layout flag and page template. The identifier is not written to persistent browser storage. Income figures, rent amounts and entered ZIPs are not permitted event fields. Infrastructure logs and this aggregate events table are different records; a claim about one should not be read as a claim about the other.

Correction messages and choices

A correction submission deliberately sends the page, report category, message and optional reply email to the publisher's corrections table. A timestamp and site identifier accompany it. No IP address or user agent is stored in that table. Personal details written into the message become part of that report, so avoid benefit identifiers and confidential housing records. We do not promise a fixed retention period or an automated deletion portal that does not exist. You may use the correction form to ask about a submitted report. Advertising is disabled in this build; any future advertising integration needs an updated description of its actual behavior rather than a generic claim about consent.