Security
Last updated: September 2026
Check it yourself
Three independent scanners grade geolens.eu from the public internet. Each link runs the scan live, takes about a minute, and needs no account.
What stands guard
Encrypted in transit, with no way back. Modern TLS everywhere, and a one-year instruction to browsers to refuse plain connections, subdomains included.
Framing by other sites is refused, and content-type guessing is turned off, before any of our code runs. The exception is the embed URL, which exists to be put in someone else's page.
Sign-in has its own tighter limit. 30 attempts a minute per address against the 300 everything else gets, counted separately.
Sessions live in a hardened cookie that no script can read. There is no bearer token to leak.
Admin actions are permissioned one by one, and recorded. Disabling an account revokes its access immediately, allowlisted or not. The record is a table an administrator could still edit; making it tamper-evident is on the list.
The service and its database are EU-hosted. Both run on DigitalOcean's European Union infrastructure.
Nothing reaches production without the full gate. Type-check, lint, the architecture checks and the whole test suite, frontend and backend, run locally before every push to main. Dependency updates arrive as automated weekly pull requests. There is no scheduled code-scanning.
What we don't do
No ad networks, no session-replay, nothing sold. Google Analytics is the only measurement here, and its tag loads only after you accept analytics.
No cookies if you browse signed out on "Essential only". Your consent choice and any unsaved draft sit in your own browser's local storage and never leave the device.
No analytics event carries your identity. Never your email, your name, your account id, and never the query string, which is where the titles and labels you type into a chart live.
No certification we have not earned. There is no compliance badge on this page, and there will not be one until there is a document behind it.
Your data has handles you can pull
One action erases the account. It takes your profile, your saved and published work, your follows and your billing link with it, in a single database transaction.
Two things survive, and we would rather say so. Feedback you sent and engagement counters are stripped of any link to you rather than destroyed, and security audit entries naming your address are kept.
Take your work with you. Your account, everything you have made, and your follows download as one file, self-serve, with no request form.
Every processor is named. The companies that help run GeoLens are listed on the privacy page, each with the one job it does.
Report a vulnerability
Write to hello@geolens.eu with SECURITY in the subject, or start from /.well-known/security.txt.
Acknowledged within 3 working days, a first assessment within 7 working days, and a fix or a dated plan within 30 days for anything we rate high or critical.
If your personal data is ever caught in an incident, you hear from us as the GDPR requires. If a window passes in silence it was missed, not ignored, and a nudge is welcome.