Privacy Policy

Last updated: 2026-10-29 · This policy is written to be read, not skimmed past.

The short version

Tilezza is built so that using it requires processing as little personal data as technically possible. Map tile delivery stores no personal data at all: no visitor IP addresses, no cookies, no fingerprints, no identifiers. If you only ever load a map that uses Tilezza, we hold nothing about you.

Map tile delivery (visitors of our customers' sites)

When a website loads tiles from tilezza.eu, our servers technically receive your IP address to answer the request — that is how the internet works. We do not write it to disk: access logs are configured without IP fields, error logging is minimal, and no analytics run on tile traffic. Requests carry no cookies. Aggregate counters (how many tiles a given API key served per day) contain no personal data. Legal basis: none needed — no personal data is stored.

Account holders (developers who sign up)

If you create an account we store: your email address, a salted password hash (scrypt — we cannot see your password), your API keys, and daily tile-count aggregates per key. That is the complete list. Legal basis: performance of a contract (Art. 6(1)(b) GDPR). We keep this data while your account exists; delete your account (email us) and it is removed.

Cookies & analytics

The public website sets no cookies — hence no consent banner. After logging into the dashboard we set one strictly-necessary session cookie (sid, HttpOnly, Secure), which needs no consent under the ePrivacy rules.

For aggregate page statistics we use our own, self-hosted, cookieless analytics (Umami-based, served from our EU infrastructure at analyzza.com — a Digital Dynamics service). It sets no cookies, stores no persistent identifiers, does not follow you across sites, and produces only aggregate counts (page views, referrers, country-level location). Tile API traffic is never measured — analytics run only on our own web pages.

Abuse filtering & country statistics

On our own content pages (not on the tile API), the server determines in memory, at the moment of the request, which country an IP address belongs to and, if it is on our list, the network operator (for example a cloud provider). We use this to filter out bulk automated downloading (scraping) and to produce per-country totals. Only these labels are logged, together with the time, the domain, the site section (for example flood-map), a coarse browser type (for example “Chrome”, “bot”), the two-letter browser language code, and whether the visit came from a search engine, from our own sites or elsewhere. The IP address, the full user-agent string and the referring page address are not logged. We also measure whether an IP address requests more pages per minute than usual: for this the server keeps the IP address briefly, only in an in-memory counter (never written to disk and continuously overwritten by newer visitors); only the result (“ok” or “fast”) is logged. Logs are kept for 14 days. Legal basis: legitimate interest (GDPR Art. 6(1)(f)) — protecting the service from bulk automated downloading. The IP-to-country database comes from iptoasn.com (public domain). Visitors from the EU and the EEA are never excluded on the basis of their country.

Human check (all our sites)

Because of bulk automated scraping, some visitors see a short check page before the content: those whose IP address belongs to a country on the list above, and those whose browser shows signs of automation (for example no language setting, or an automated/headless browser). This applies to all our own sites (the radar sites, the international sites and the content sections of tilezza.eu), not to the tile API or embeds. Search engine, AI search, link preview and monitoring robots are never checked.

The check runs on our own server (the open-source Cap software, a short computation in the browser): no data goes to third parties and no external script is loaded. We look at a few technical browser properties (automation flag, language list, screen size); these are not stored. After a successful check we set a security cookie (tz_kapu) for 24 hours containing only a signed random identifier and the expiry time; with it you can load up to a human-paced number of pages per hour, after which we check again. The cookie is strictly necessary for providing the service securely, so no consent is required. We keep a daily count per site (checks shown, checks passed), without IP addresses.
Legal basis: legitimate interest (GDPR Art. 6(1)(f)) — protecting the service. If you are wrongly unable to pass the check, write to info@tilezza.eu.

Geo Filter service (our customers and their visitors)

Our customers (operators of websites using Geo Filter): account data (email address, password hash), website settings (domain, level, blocked countries and networks, exceptions) and daily aggregated counts per website. Legal basis: performance of the contract (GDPR Art. 6(1)(b)); billing data is kept for 8 years as required by accounting law (Art. 6(1)(c)). Daily counts are kept for 400 days; when an account is deleted, its websites’ settings and statistics are deleted immediately.

Our customers’ visitors: the filter runs on the customer’s own server. A visitor’s IP address and browser are processed there, transiently — the controller is that website’s operator, not us. We receive only daily aggregated counts (country, network ID (ASN), decision: allowed / challenged / blocked / human / bot / trap) — never IP addresses, URLs, browser identifiers or cookies. These are not personal data, so we are not a processor in this respect.

Shared reputation list: from the per-network counts of websites that opt in to sharing, we calculate which data-center networks send almost only automated traffic; participants show those networks the challenge page (never a block). A network is an organisation, not a person. Only verified websites count (the domain points at the reporting server, or the filter serves /.well-known/tilezza-geoszuro — for this we look up the domain’s public DNS records and that one URL). Shared protection (“give and get”) and sending daily statistics can each be switched off per website; with sending off we receive nothing from that site.

Reporting server: so that a website running on several servers does not overwrite its own statistics, we store a 12-character keyed hash of the reporting server’s address, not the address itself.

Where and who

All infrastructure is located in the European Union and operated by us. No data is transferred to third countries, and no third-party processors touch tile traffic. Data controller: Digital Dynamics (contact: info@digitaldynamics.hu).

Your rights

Access, rectification, erasure, restriction, portability, objection — email info@digitaldynamics.hu and we respond within 30 days. You may also lodge a complaint with your supervisory authority (in Hungary: NAIH, naih.hu).