What stimmo does
with your data.

stimmo has no user accounts, no login, and no persistent per-visitor profile. Each form submission is processed as an independent request: the address, surface, condition and other listing details you enter are used only to compute that one estimate and are not stored against your identity.

Producing an estimate requires two lookups against external, non-profit map data providers:

• the address you enter is geocoded to coordinates via OpenStreetMap's Nominatim service;
• nearby amenities (schools, transit, parks, and similar) are looked up via the Overpass API, which also serves OpenStreetMap data.

Both are called per-request with the coordinates needed to answer the query; stimmo does not otherwise share your input with third parties.

If you use the "share" button on a result, the estimate payload (the listing details and computed verdict — explicitly not any personal data about you) is stored in a small, self-hosted, content-addressed SQLite database so the short link keeps working when others open it. There is nothing tying a share link back to who created it.

stimmo collects aggregate, anonymous Prometheus counters — request counts and latencies by route, and share-link open/render outcomes. These are operational metrics, not per-user tracking: they carry no IP address, cookie, or identifier tied to a specific visitor.

If a Cloudflare Web Analytics token is configured, this page also loads Cloudflare's privacy-first analytics beacon, which does not use cookies or persistent identifiers to track individuals across sites.

stimmo runs behind Cloudflare, used as a reverse proxy and CDN to serve the site reliably. Cloudflare processes standard connection metadata (like your IP address) as part of routing the request, under its own privacy policy.