Overassessed / privacy

Privacy

You type your home address into this site, so you should know exactly where it goes. Short version: it goes to our server just long enough to answer you, and nowhere else.

When you check an address

Your address travels to our server in the web request. The server looks it up in its copy of Maryland's public assessment roll, builds the result page, and sends it back. The look-up is processed in memory, answered, and forgotten: our web-server configuration turns access logging off, so look-ups are not written to server logs.

The result pages also tell other machines to forget them: they are sent with a no-store header (your browser and any caches between us are told not to keep a copy), they carry a noindex tag, and our robots.txt blocks them from search-engine crawls.

The printable packet

Some links on this site carry the parcel's SDAT account number instead of the address; the two point to the same public record. The evidence packet works this way: the account number in the link does reach our server, because building the comparison table takes the full statewide roll (about 2.4 million parcels), which only the server holds. The server builds the page from that public roll, sends it to you, and keeps nothing: no copy of the packet is stored, and the no-access-log rule above covers the request. The printing itself happens in your browser; we never see the printout.

What we never collect

No accounts, no sign-ins, no cookies, no analytics, no trackers, no ads. Our pages load no third-party scripts, fonts, or images, so no other company watches you use this site.

Owner names: Maryland's roll lists them, but our ingest never requests those columns from the state, so names never reach our systems at all.

What the server does see

Like every website, our server sees your IP address when you connect. We use it only to slow down runaway automated traffic, with a short-lived counter held in memory; there is no access log for it to land in. One honest exception: if the service breaks mid-request, the web server can write a technical error line so we can fix the outage, and that line can include the web address you requested. It is the only time a request can touch a log, and it is used for nothing else.

The API and agent endpoints

Requests to /v1/check and /mcp follow the same rules: processed in memory, answered with a no-store header, and covered by the same no-access-log rule.

Email

If you write to support@agentlookups.ai, we have your email address and what you sent. We use it to reply and for nothing else.

This page describes the site as it runs today; if the design ever changes, this page changes with it. Overassessed is run by TopHat Monkey Software LLC (about this site).