Enough information to answer, not a profile about you.

The address you enter is kept in this browser tab for up to 30 minutes so the schedule page can load and a refresh can recover the result. Closing the tab or clearing the lookup removes that temporary browser record.

The lookup is sent through TrashDayNow’s server to resolve the property and request the applicable collection information. Esri, through its ArcGIS service, processes the address for geocoding, and the connected schedule provider receives the resolved address and location context needed to return coverage.

Where no official schedule exists for an address, we may display anonymous, aggregated resident reports (for example, “2 resident reports: Friday — unverified”). These show only a day, a count, and a date — never who reported.

TrashDayNow keeps a service log of each lookup — the address entered, the resolved address, the result shown, the time, and general request context such as approximate city and browser type, but never your exact network address. We use it to find and fix wrong or missing answers and to decide which cities to cover next. Log entries are deleted after 180 days, and we do not sell or share them.

Separately from that log, we maintain two datasets that contain no information about any visitor: a reference database of properties and the collection answers we computed for them (an address, its pickup days, its provider and source — with no record of who looked it up or when each individual lookup happened), and anonymous daily statistics such as how many lookups a city received. These are used to improve coverage and accuracy. We do not sell or license the service log or these datasets, and we do not attempt to identify individuals from any of this data.

If you use “Add to Calendar”, your calendar app periodically re-fetches a schedule link from our server to stay current. That link contains a city, state, service, pickup-day pattern, the source's name, and a random subscription code — never your address. We use the code to count subscriptions and to keep the calendar current for that property: on our side it is linked to the property's privacy-protected key, never to a name, and never to the address itself. We log each fetch (city, state, service, calendar app type, and the code) to understand where the reminders are relied on. A code that is never used is deleted after 30 days; a subscription's record is deleted 180 days after its last fetch.

If you confirm, correct, or contribute a schedule, we keep a privacy-protected record of the location, browser, collection service, source information, weekday choice, and — if you choose to share them — the hauler and pickup frequency. This helps us compare reports without attaching the raw street address to them.

The feedback database does not store the submitted raw address, apartment number, coordinates, IP address, or user-agent string. Apartment and unit identifiers are removed before reports are grouped at a municipal curbside pickup point.

A privacy-protected first-party cookie can remain in the browser for up to one year. It lets us recognise a returning browser — to count visitors, to see whether people come back, and to prevent duplicate reports — and its one-way hash is what the service log, feedback records and calendar subscriptions store. It is never used for advertising, never shared, not set for visitors outside the United States, and not set when a browser sends the Global Privacy Control signal.

Feedback records, including withdrawn reports, are scheduled for removal after 180 days. A resident-informed schedule update can remain active for up to 90 days before it needs to be checked again.

To understand how the site is used we run Google Analytics, Vercel Analytics and Microsoft Clarity. Clarity shows us which pages are read and where people tap, including anonymised replays of how a page was used. The address field, the address suggestions and the resolved address on the schedule page are masked in the browser before anything is sent, so Clarity never receives a street address, and every text field is masked by default. Clarity and Google Analytics set their own first-party cookies to recognise a returning browser and to keep one visit together; Microsoft and Google process that data under their own privacy statements, and we use it only to improve the site. Clarity is not loaded when a browser sends the Global Privacy Control signal.