We built ClearSpot so nobody has to move blind again.
One day we were house-hunting. The view was postcard-perfect. What we could not see: three wind turbines planned 480 m away, a pollen-heavy grove at the edge of the garden, and a motorway that turned the night into a sustained 62 dB hum. By the time we understood, the paperwork was signed.
Why
Environmental exposure is not abstract. It is headaches, poor sleep, allergies flaring up, a baby crying at 3 a.m. because of low-frequency noise. Each of those sources has open public data. Cross-referencing them is a weekend project for an engineer - and completely out of reach for someone who is just trying to choose where to live, work, or send their kids to school.
ClearSpot exists because we want that information to be one tap away, in plain language, for everyone. No dashboards. No spreadsheets. A single verdict: clear, or not clear, and why.
How
We fetch open datasets from governments, research agencies and citizen networks. We normalise them to a common grid, tag each cell with a severity score tuned to the sensitivities you declared during onboarding, then we render the result on a globe you can rotate with a finger.
L'intera pipeline è verificabile: la pagina Informazioni elenca ogni fonte a monte, le guide agli indicatori sotto Fonti dati spiegano le soglie, e il back-office conserva un registro dei crawl consultabile. Non inventiamo numeri. Quando le evidenze sono controverse, come spesso per l'infrasuono delle turbine eoliche, lo diciamo e colleghiamo studi discordanti.
What
A free web app, PWA-installable, that tells you in under two seconds whether the spot under your feet is clear or not. It is not a medical tool. It is a map and a conversation starter.
Everything on ClearSpot is GDPR-first. Your sensitivity profile stays on your device unless you explicitly create an account. We log no location without your consent. The site runs on a tiny VPS in Europe, with no third-party tracker beyond the analytics you opt in to.
Where next?
Read the blog for the science behind each module, or drop us a line in the guestbook.
Where was the idea born? Read the blog Say hi Data sources Privacy policy