Imprint and privacy

This English text is a convenience translation. In case of doubt, the German version is the legally binding one.

Media owner and service provider
Lucas Moreira Jakubeit
Bloch-Bauer-Promenade 8
1100 Vienna, Austria
[email protected]
LinkedIn
Press & press kit

Sole proprietorship. Business purpose: services in automated data processing and information technology (free trade). Trade authority: Magistrat der Stadt Wien, GISA number 40177007. Member of the Vienna Economic Chamber (Wirtschaftskammer Wien). Professional law: Austrian Trade Regulation Act (Gewerbeordnung), available at ris.bka.gv.at.

Editorial line: independent information on residential locations, light and surroundings in Vienna based on open data; no advertising, no paid placements.

Data sources & licences

Listed as an Open Data application on data.gv.at.

Open Government Data, City of Vienna — data.wien.gv.at
District boundaries (GeoJSON), schools, pharmacies, supermarkets, doctors, geocoding, tree register (street-tree density shown as „Trees & shade"; tree positions in the 3D light view and as 3D trees on the map at close zoom), zoning plan (building-class heights in the 3D light view), surface and terrain model (2007 flight) with the 2025 orthophoto (tree crowns in courtyards and gardens that the tree register doesn't list — processed and hosted on our domain), garages incl. Park and Ride (public car parks for the „Parking" map lens and the garage line of the mobility card), licensed café terraces (map layer, the „sit outside" search, the neighbourhood trait and the 3D close-up; located at the venue’s address point), Wien Energie EV charging on public ground (map layer, the charging line of the mobility card, the „EV" search; merged into sites) and green building locations (roof, façade, courtyard: map layer). Licence: CC BY 3.0 AT / CC BY 4.0

OpenStreetMap / Overpass API / Nominatim — openstreetmap.org
Map rendering, parks, green areas, gastronomy. POI enrichment: museums, theatres, libraries, playgrounds, bakeries, markets, sports facilities, universities, Heurigen, dog zones, sausage stands, kebab shops, pizzerias, public car parks (supplementing the city's garage register), publicly accessible EV charging by operators other than Wien Energie (supplementing the City’s charging list). Geocoding fallback (address search): nominatim.openstreetmap.org. Licence: ODbL 1.0

GTFS Wiener Linien — wienerlinien.at
Stops, lines, types (metro, tram, bus, S-Bahn). Licence: CC BY 4.0

Climate data (GeoSphere Austria) — data.hub.geosphere.at
Official annual and monthly values from the Wien Hohe Warte station (sunshine, precipitation, temperature, summer/hot/frost/snow days) since 2020; tropical nights, wind and the current year from the daily series. For the “Weather & climate” page and the climate overview. 1991–2020 normals: City of Vienna / GeoSphere. Licence: CC BY 4.0

Police crime-report statistics Vienna 2022–2024 — BMI / LPD Wien
Report counts per district, processed into a safety index (1–10). Full 2022/2023 table: NEOS enquiry, Hietzing district council, Sept. 2024. Confirmed 2024 data for 6 districts: LPD Wien press release April 2025.

Population data 2025 — Wikipedia / Statistics Austria
Resident population per district for per-capita normalisation. Licence: CC BY-SA 4.0

Purchase prices — district medians from the land register, i.e. prices actually PAID rather than asked: Statistics Austria, average property prices (as of 2025, CC BY 4.0 — data source: Statistics Austria, data.statistik.gv.at). Where Statistics Austria publishes no figure for a district (fewer than 10 transactions) the field stays empty rather than estimated. A district median also carries quality and location effects. The comparable sale prices in Azima come from the finer table of the same source, Wohnungspreise 2025 (geometric means per district, construction year, floor area and with/without outdoor space, sales 2021–2025 adjusted to 2025; CC BY 4.0, selected per address and multiplied by the floor area — modified). An estimate, not a valuation.

Rents — district asking rents (new lettings), carried forward via the Statistics Austria House Price Index (Q1 2026 preliminary, +5.5% since 2024). There is no official rent per Vienna district — the MRG Richtwert (€6.74/m² from 1 April 2026) is a legal term for pre-1945 reference rents and is the same across the city. So what stands here is an asking rent, not a contract rent. Non-binding orientation values, no warranty.

Property listings (export) — links to the property portals willhaben, ImmoScout24, derStandard Immobilien and FindMyHome. Vienna Living Map shows no listings of its own, stores no listing data and brokers no flats — it only generates links to each portal’s public search, pre-filtered by district/ZIP. Brands & content remain with the respective portals.

Character images (reference photos) — Wikimedia Commons, Openverse, Mapillary, Panoramax & Unsplash
Publicly & freely licensed (Creative Commons / CC-BY-SA, or the Unsplash licence) photos of the respective area serve as a template; they are transferred server-side into the app’s consistent visual style. Licence & author remain with the respective source. If no fitting photo exists for an area, an AI-generated, generic Vienna motif (no specific place, no invented address) is created instead, hinting only at the atmosphere.

Software used

QR code generator — Project Nayuki (nayuki.io)
Licence: MIT. Generates the QR codes in the PDF export entirely in the browser — the contained link address is encoded locally and transmitted to no server.

SunCalc — Vladimir Agafonkin (github.com/mourner/suncalc)
Licence: MIT. Computes sun position and daylight for the „Atmosphere & Light" display entirely in the browser — no data is transmitted.

Pascal — Pascal Group Inc. (github.com/pascalorg/editor)
Licence: MIT. The 3D building editor the stage uses to build the opened house — walls, windows, doors, roofs and rooms, in the browser. Furniture and floors are Azima's own; no file from Pascal's sample folder is served.

three.js — three.js authors (github.com/mrdoob/three.js)
Licence: MIT. Draws the 3D stage in the browser.

MapLibre GL JS — MapLibre contributors (github.com/maplibre/maplibre-gl-js)
Licence: BSD-3-Clause. Draws the map and the city around the stage in the browser.

Draco decoder — Google LLC (github.com/google/draco)
Licence: Apache 2.0. Unpacks compressed 3D models if the stage loads one (since 10 Oct 2026 it builds its furniture itself). The decoder is served from our own server, not from a Google server — no request goes to a third party.

Disclaimer

All figures are non-binding estimates based on publicly available data. The Living Score and all derived metrics are relative orientation values for quality of life — not purchase, rental, investment or legal advice.

Azima is browser-based software for the automated analysis of building data, sun position, shading and floor plans. It produces a digital analysis report; it is not a legal, structural or architectural expert opinion and not individual advice. A measured drawback of a place is never removed, only explained better.

Grätzl values are interpolations from district data; deviations at street level are possible. Safety metrics are based on police report statistics and do not necessarily reflect the subjective sense of safety. For concrete purchase or rental decisions we recommend professional property advice and visiting in person. Linked property listings come from third-party portals; we accept no warranty for their availability, timeliness, prices and content.

Data as of: 16. Juni 2026. Vienna Living Map is in active development; methodology and data sources may change without notice.

Privacy

The controller within the meaning of the GDPR is Lucas Moreira Jakubeit, Bloch-Bauer-Promenade 8, 1100 Vienna (contact: [email protected]). Vienna Living Map creates no usage profiles, sets no analytics cookies and uses no advertising or tracking services. The app does not measure individual usage behaviour. Only an aggregated, server-side reach figure is recorded. See the section “Reach measurement” for details.

Local storage. Personal settings (chosen persona, map layers, heatmap state, and after a crash of the 3D view a lighter rendering level for 30 days together with a crash log for diagnostics), saved favourites (addresses, Grätzl, districts) and a search history of recent queries are stored exclusively in the browser’s localStorage. This data does not leave the device and is not transmitted to any server. For your housing diary (“My Vienna”): saved places, personal reasons, notes, viewing dates and decision histories are stored exclusively locally on your device. These contents are not transmitted to Vienna Living Map and are not used for reach measurement or analysis. An optional device transfer (file, link or QR code) moves your favourites straight from one device to another — you carry the data yourself; there is no server and no account. An optional “My route” destination (e.g. your work address for the travel-time line) is likewise stored locally only; the travel time is estimated entirely in the browser and the destination is never transmitted to any server (only the one-off address lookup uses the geocoding interface described below). “Today in Vienna” start page (/en/today/): Up to two addresses (home, work) that you save there are stored only in your browser’s localStorage (key “vlm-orte-v1”) and are not transmitted to Vienna Living Map. When you save one, the typed address goes once to the City of Vienna address service (data.wien.gv.at). For departures, your browser sends only the numbers of the nearest stop platforms to our server (/api/abfahrten), which asks Wiener Linien and caches the answer briefly — never your address or coordinates; Wiener Linien see our server, not you. The travel time to work is estimated in the browser. The date of your last visit (“vlm-heute-besuch-v1”) marks what is new since then and also stays on the device. The always-on view keeps the screen awake via your browser’s wake-lock function; no data is transmitted for that. Your browser fetches the list of the latest films when you open the page and every 15 minutes after that from our own domain (tiles.viennalivingmap.com/hub/, Cloudflare storage); only the technically usual connection data goes to our storage, nothing from your saved places. Weather and sun times refer to the fixed centre of Vienna, not to your location. There is no sign-in and no merging with other data. Favourites and search history can be deleted at any time within the app (or by clearing browser data). Legal basis: Art. 6(1)(f) GDPR (legitimate interest in a user-friendly storage of settings, favourites and search history on your own device).

“Vienna in motion” (/en/live-transit/). Directions are computed by your browser from the timetable data; start, destination and time do not leave the device for that. For the live times (the departures at a stop, the first departure of a route within the next hour and the delay of nearby vehicles and of the one you select) your browser sends only the numbers of the stop platforms to our server (/api/abfahrten), which asks Wiener Linien and caches the answer briefly — never your start, destination or location. If you type an address, that text goes once to the City of Vienna address service (data.wien.gv.at, without cookies), which returns its location. “My location” stays on the device. Your station (“My station”) and the recently searched routes between two stops (key “f-wege”, never an address or a location) are stored only in your browser’s localStorage. If you report in the vehicle card how full a vehicle is (“Empty”, “Some standing”, “Packed”), your browser sends only the line, the direction and the level to our server (/api/andrang-meldung). The server sets the day and hour itself; only a counter per day, line, direction and hour is stored in our database — no individual report, no IP address, no identifier, no cookie. Your IP address serves only briefly in the server’s memory as a brake against mass reports and is not stored. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in more accurate crowding information for everyone).

My properties (Azima). Every address calculated in Azima (address, coordinate, floor, the three sun reference days, the sun hours on the 21st of every month for comparing two properties, potential figure) is kept as a list exclusively on the device (localStorage, at most 50); likewise an entered building height, buildable area and electricity price. No account, no transmission. Anyone who has bought a report or taken out a subscription can voluntarily sync the list across their devices (a switch, off by default): the list is then encrypted in the browser (AES-GCM 256, key derived from the Azima key) and stored as ciphertext under the Azima key at Cloudflare (KV, EU data centres) — the server cannot read any address; it stores only the ciphertext and the time, and deletes it three years after the last change. Turning the switch off or choosing “Delete from server” removes the ciphertext; the list on the device remains. Other people who know the Azima key (a team) see the same list. Legal basis: Art. 6(1)(b) GDPR (sync as part of the purchased service) or (f) (local storage).

Local cache (service worker). To speed up load times and for limited offline use, the app files plus the public, non-personal map data (district boundaries, parks, POIs from open data) are stored in the browser’s cache on the device. This data does not leave the device. Neither search queries nor personal data are cached; requests to third parties (map tiles, geocoding, AI search) are explicitly excluded. If you explicitly choose “Save for the walk” on a residential walk, its public route data is additionally stored locally — this too stays entirely on the device and can be removed individually under “Mein Wien → Offline & storage”. So that the spatial view of a flat shows a picture straight away the next time you open it, the device keeps a preview image of the most recently opened views (at most four, in the browser’s IndexedDB storage). It is never transmitted and disappears when browser data is cleared. The app can be installed as a web app; installations are neither measured nor transmitted to us. The cache can be removed at any time by clearing browser data. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in short load times); the storage is technically necessary for the application requested by the user.

Address search. Search queries are sent primarily to the City of Vienna geocoding service (data.wien.gv.at, OGD Wien). If it is unavailable, an automatic fallback to Nominatim (nominatim.openstreetmap.org, OpenStreetMap Foundation, UK) is used; the entered address and the IP address are transmitted. When you click a point on the map, the clicked coordinate is sent to Nominatim to display the address (reverse geocoding). Legal basis: Art. 6(1)(f) GDPR (legitimate interest in providing the search function). Server-side, search queries are not stored permanently; an optional search history is kept exclusively locally in the browser (see „Local storage") and can be deleted at any time.

Map display. The map is served entirely from our own infrastructure: vector tiles, map fonts and map icons live on our own servers (Cloudflare, storage with EU jurisdiction — see “Hosting”). No external map service is involved — no third party learns which map section you are viewing. This also holds for the 3D view when zoomed in far: buildings, trees (the City of Vienna tree register, served as our own static dataset from our servers) and the terrain relief all come exclusively from our own infrastructure. Map data: © OpenStreetMap contributors (ODbL), processed with Protomaps. Legal basis for the technical delivery: Art. 6(1)(f) GDPR (legitimate interest in displaying the requested map).

Light & shadow (building surroundings). For the light display of an address („Atmosphere & Light") and for the light check (Azima) the surrounding building outlines are queried from OpenStreetMap via the Overpass API (EU) — i.e. from the same dataset that already geocoded the address. Since 16 October 2026 only an area rounded to about 110 metres and generously widened, which fully contains the radius of about 150 metres, is transmitted — never the precise coordinate (without account, without cookies, without tracking), and only when opening an address detail card or starting a light check. Before that the browser asks the City of Vienna's official building model with the same rounded area; OpenStreetMap is the last resort. Where the official Vienna roof model is already available as a static sheet, this query is skipped entirely: only a one-square-kilometre sheet is loaded, which reveals no address. The shadow computation runs locally in the browser; the result is cached only on the device. No coordinate is transmitted to our own servers in the process. For the 3D light view, street trees (tree register), and for the 3D stage the building typology of neighbouring houses (building period; in Azima also for the construction-year class of the comparable sale prices), are additionally loaded as open data directly from the City of Vienna (data.wien.gv.at, Austria); only a grid-rounded surrounding area is transmitted, never the exact address. Zoning and building classes (zoning plan), the “Zoning & protection” card and the other official data for the address (noise, river flooding, heavy rain, internet; in the Azima report also plot, monuments list, contaminated sites, radon, earthquakes, terrain and ground) are instead loaded as tiles from our own domain: a tile sheet of about one square kilometre is loaded and matched to the address in the browser — neither address nor coordinate is sent to third parties. The zoning-plan excerpt on the Azima page and in the report loads city-map tiles through our domain (like the aerial images); the City of Vienna only sees, from our server, the number of a tile about 100 m across — never the address, coordinate or your IP address. The same goes for the aerial time travel in the “Property” chapter (the City of Vienna’s aerial images from 1938 to today, tiles about 150 m across). Legal basis: Art. 6(1)(f) GDPR (legitimate interest in the requested light display and information).

Property report (Azima). The report for an address (image of the view, hours of direct sun per room, location) is generated entirely in the browser; an uploaded floor plan is read on the device and not transmitted. If you enter a sender name, contact or logo, these are stored only in your own browser’s localStorage (key “azima.marke”); they never reach a server and can be deleted there at any time. The letterhead of the Azima page (name, logo, contact, legal block; key “azima.blattmarke.v1”) and the purchase price and energy certificate entered in the purchase sheet (key “azima.objektangaben.v1”, per address) are likewise kept only in localStorage; they are only placed into the PDF your browser generates and never reach a server. If you start the light check from the address field on the Azima page or via a partner link (/azima/#adresse=…&partner=…), the address is handed over only inside your own browser (sessionStorage key “azima-start”, read and deleted at start); a partner identifier stays in sessionStorage for the session (“azima-partner”) and is never sent to a server. The QR code on the Azima report likewise carries address, coordinate and floor only after the # sign (/azima/#adresse=…&lat=…&geschoss=…) — the browser never sends that part to a server; the page keeps the values in sessionStorage for the start (“azima-start-zusatz”, read and deleted) and then opens the spatial view. When the start comes from “Vienna in motion” (the pill “The Azima world starts here” from zoom 16.5, since 11 November 2026), only the map centre, viewing direction and time of day stand after the # sign — no address; the page asks Nominatim for the nearest address to that map centre (the same reverse lookup as a click on the main map) and then proceeds as for a typed address. Since 15 October 2026 the same applies to the “Share link” button and to the link on the project sheet and listing package: address, coordinate, floor, time and view stand only after the # sign. One exception, stated openly: while a place is open, it stands in your browser’s address bar (?lat=…&lng=…&address=…) so that Back and bookmarks work. If you reload that page or open the bookmark, the browser sends this line with the page request to Cloudflare, through which Vienna Living Map is delivered. VLM does not evaluate or store that part — the reach measurement reads only the path, never the query. The report link carries the report itself — address, floor, rooms and hours — encoded in the URL, without image or logo: whoever passes on the link passes on exactly these details, and the recipient sees the sheet without the spatial view. The location text and OpenImmo package („For agency software") are also made in the browser: an imported OpenImmo XML and a PDF created during the same visit are kept only in the working memory of the open page for this — not stored, not transmitted, discarded when the page is closed. The package is downloaded as a file to your own device; the copy button puts the location text on the clipboard. If the file holds several objects and all of them are calculated ("Enrich all objects"), only street and house number of objects without a coordinate in the XML go to the City of Vienna's address service — the same lookup as typing an address; the XML itself still never leaves the device. What happens to either afterwards, such as importing it into agency software, is up to the person passing it on. Reports and links are never stored server-side. Legal basis: Art. 6(1)(b) and (f) GDPR (generating the requested report; legitimate interest in storing the sender locally).

Floor-plan studio. A plan drawn in the studio (walls, openings, room names, furniture, title) is stored only in your own browser’s localStorage (key “azima.studio.v1”, plus the chosen sheet layers under “azima.studio.ebenen.v1”); “Start over” clears the plan, and deleting the site data in the browser removes both. An imported plan (PDF, image, plan JSON, DXF, DWG, IFC) is read in the browser — text recognition runs on the device — and is not transmitted. Exports (PNG, PDF, SVG, DXF, IFC, JSON) are made in the browser and downloaded to your own device or passed on through the device’s share menu; sender name and logo on the sheet come from the same letterhead as above (“azima.blattmarke.v1”). “Measure it at a Vienna address” puts the plan into the same storage as an imported floor plan (“azima-grundriss”, “azima-grundriss-lang”) and opens Azima; the plan reaches no server then either. Legal basis: Art. 6(1)(b) GDPR (the requested tool).

Purchase, Premium and the Azima seal (Paddle). Single reports and the Premium subscription are sold by Paddle.com Market Ltd (London, United Kingdom) as merchant of record. Paddle’s payment window only loads when you click “buy” — before that there is no Paddle script and no Paddle cookie. Payment details, e-mail address and, where applicable, billing address and VAT ID are entered directly with Paddle, which is an independent controller for them (paddle.com/legal/privacy). An adequacy decision of the European Commission exists for the United Kingdom. We ourselves receive no payment details and do not store your e-mail address. Our server only learns from Paddle that a random Azima key has been paid (webhook with verified signature) and records Paddle’s subscription, customer and transaction IDs, the time of purchase, the subscription status and, for a single report, your consent to immediate creation (version and time) in a key-value store at Cloudflare (Workers KV; event IDs for 30 days, purchase entries for as long as the report or subscription is usable) — so that the customer portal can open and a refund revokes the unlock. If you came via a link with campaign tags (such as utm_source=tiktok), the checkout passes these tags to Paddle with the purchase so we can see which channel brings sales; they live only in the link and in the page’s memory, nothing is stored on your device for this. If you withdraw via “Withdraw from contract” (section 13a FAGG), Azima stores the declaration — name, e-mail address, Azima key or invoice number, date and time — for three years as proof for both sides and initiates the refund with Paddle; you see the acknowledgement of receipt immediately as a page and a file. The confirmations by e-mail — the purchase confirmation (section 7(3) FAGG, with your Azima key and, for a single report, your consent) and the acknowledgement of a withdrawal (section 13a FAGG) — are sent through Mailjet (Mailjet SAS, Paris; processor, processing in the EU) and, if that fails, as plain text through Brevo (Sendinblue GmbH, Berlin; likewise a processor in the EU); legal basis Art. 6(1)(c) GDPR. With Mailjet, open and click tracking is switched off for every one of these e-mails — no tracking pixel, no redirected links; the plain-text version through Brevo carries no tracking pixel. For the purchase confirmation our server reads the address you gave when buying once from Paddle and does not store it; it only records that the confirmation was sent (three years). The Azima key is generated by your browser (localStorage “azima-kauf” for Premium, “azima-berichte” per single report) — without a name, account or address; Azima shows it to you after buying so that you can bring the purchase to another device. For invoices, payment method and cancellation the page /premium/ opens Paddle’s customer portal on your click: our server creates a portal session with Paddle’s customer and subscription IDs (the API key stays on the server) and forwards you to paddle.com, where Paddle’s privacy policy applies. For the Azima seal the browser sends the Azima key and a checksum of the property (SHA-256 over Azima key, address and floor) to the Azima server. The checksum contains neither the floor plan nor the address in plain text. With the Azima key it could be matched by trying the entries of an address directory — Azima does not do that; the checksum is stored only for a single report, to bind it to one flat. The server signs a short form (HMAC). The verification link in the PDF contains only type, property identifier, a short form derived from the Azima key from which the key cannot be recovered, and the date; the check stores nothing. Legal basis: Art. 6(1)(b) GDPR (performance of the contract) and (f) (protecting the purchase path against abuse).

Browser extension for property portals (since 24 October 2026; Chrome, Edge, Firefox): whoever installs the extension sees a Vienna Living Map card under the address line of Vienna listings on willhaben.at, ImmoScout24, immodirekt.at, derStandard Immobilien, immowelt.at, findmyhome.at and wohnnet.at. For that the extension reads only the location the listing itself shows (address line, postcode, coordinate, floor, price per square metre) — in the browser, on listing pages, nowhere else. From our domain it loads three public files once a day (neighbourhoods, districts, U-Bahn stations; no address in the request) and, as soon as the card is visible, the frame of the light widget as described below (address in the fragment, no referrer; the frame loads the building heights of the surroundings). Only if the listing names no coordinate and the address has a house number does the address go to the City of Vienna's address service. The extension sets no cookies, counts nothing, stores in the browser only the three files and whether the card is open or closed, and sends neither listing nor user to us; like any request, our server sees the IP address in the access log. It is not affiliated with any portal. Legal basis: Art. 6(1)(b) GDPR (the display requested by the person who installed it).

Light widget on other sites ("Sunlight at this address"): if an agent or a portal embeds the widget, the visitor's browser loads a small page from our domain into a frame. Address, floor and partner key sit in the fragment of the URL (after "#") and are not transmitted to our server; the frame sends no referrer. The browser calculates the hours of sun itself, from the building heights it loads from our domain as on this site. If too few buildings are found there, it asks the City of Vienna's building model and, as a last resort, OpenStreetMap (Overpass) — both only with an area rounded to about 110 metres. If there is no coordinate, only the address goes to the City of Vienna's address service. For the roof (solar and green-roof potential) the browser asks the City of Vienna's solar potential register with an area rounded to about 40 metres and loads the roof surfaces from our domain. No cookies, no tracking; like any request, our server sees the IP address in the access log. Legal basis: Art. 6(1)(f) GDPR (showing the information requested by the embedding provider).

Current weather. In the detail card the „Atmosphere & Light" section shows the current weather (icon & temperature). For this, only the rounded coordinates of the displayed location (no personal data) are transmitted to Open-Meteo (Open-Meteo, Germany/EU). Open-Meteo works without an account, without cookies and without tracking; the request happens only when opening an address detail card, not on page load. Open-Meteo privacy & terms. Sun position and daylight, by contrast, are computed locally in the browser (no transmission) — as are the nearest public garage and the nearest EV charging site in the mobility card, and the café terraces, greening projects and charging sites around an address (Azima report): the lists are static public files served from our own domain, the distance is computed on the device and the location is not sent anywhere for it. Legal basis: Art. 6(1)(f) GDPR.

Voice search. Currently disabled: there is no microphone button, Vienna Living Map requests no microphone access and uses no speech recognition. Background: the browser-native Web Speech API does not work reliably everywhere (in some browsers server-side at the vendor, blocked in many corporate networks, on iOS only in Safari) — we prefer not to show a feature that silently fails or raises GDPR questions. A privacy-compliant re-introduction is possible once it is reliable.

AI search (optional). If you actively use the AI-assisted search, only the search text you enter is transmitted to the Google Gemini API (Google Ireland Ltd., Ireland, or Google LLC, USA) in order to translate it into structured search criteria. The request runs server-side via a Cloudflare function; your IP address is not passed on to Google. Transmission happens only when you trigger the search explicitly — not on page load and not on every keystroke. Please do not enter personal data in the search field. To speed things up and protect against abuse, the search text is cached briefly and transiently in memory and the IP address is used for a temporary request limit; there is no permanent storage and no profiling. Processing by Google is governed by their privacy terms. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in the search function). For the transfer to the USA, Google relies on the EU Commission’s adequacy decision (EU-US Data Privacy Framework, Art. 45 GDPR) and additionally on Standard Contractual Clauses (Art. 46 GDPR). Google privacy policy.

AI place description (optional). When opening an address, a short, location-related description is — where available — generated via the same Google Gemini API (server-side via Cloudflare). Only derived location features are transmitted (district/Grätzl, score and dimensions, walking minutes to everyday destinations, the nearest public station, tree/water hints) — not the exact address and no precise coordinates. The result is cached locally in your browser so it is generated only once per location; there is no permanent server-side storage and no profiling. If generation fails (offline/blocked), a locally computed description remains. Legal basis and USA transfer as for the AI search (Art. 6(1)(f) GDPR; EU-US Data Privacy Framework / Standard Contractual Clauses).

Character image & weather context. The atmospheric image on the detail card shows the character of the area. For this, server-side (Cloudflare) the name of the Grätzl or district and — for an address, to find a more fitting nearby photo — rounded coordinates of the location are processed (the same coarseness as the weather request, not the exact address, no personal data): a publicly and freely licensed reference photo of the area from open image sources (Wikimedia Commons, Openverse, Mapillary, Panoramax — each CC or CC-BY-SA — and Unsplash) is searched, checked server-side via the Gemini API for suitability and transferred into the app’s calm, consistent visual style (only style & mood are changed, the real place is preserved, no places are invented). The generated image is cached once server-side (Cloudflare edge cache or KV) and delivered identically; only public, non-personal images are stored. If no suitable photo exists for an area, an AI-generated, generic Vienna motif (no specific place, no invented address, no text, signs or people — only the atmosphere) is created instead; if that fails too, the app shows a purely locally browser-computed abstract colour composition. The weather context „Today in Vienna" is queried for the fixed Vienna city centre (Open-Meteo), not for your location.

Flat export (listing links). On request, VLM generates a list of links to available flats on the portals willhaben, ImmoScout24, derStandard and FindMyHome — pre-filtered by district/ZIP and, for an address, a radius you choose. These links are assembled locally in your browser; no data and in particular never your exact address is transmitted to our own servers — only the district/ZIP level is used. Only when you click a link does the respective portal open as an independent third party with its own privacy policy (an IP address and cookies may arise there); „All portals" links go via Google search. VLM scrapes nothing, hosts no listings and is no real-estate broker. Legal basis: Art. 6(1)(f) GDPR.

Hosting. The website is provided via Cloudflare Pages (Cloudflare Inc., USA). Technically necessary connection data (IP address, timestamp, browser information) is processed by Cloudflare. Cloudflare’s “Network Error Logging” (browser error reports to Cloudflare) is disabled for this website. For the public reach display, Vienna Living Map only receives aggregated daily totals from Cloudflare Zone Analytics (see “Reach measurement”). Processing takes place under a data processing agreement (Cloudflare Data Processing Addendum); for transfers to the USA, Cloudflare uses Standard Contractual Clauses (SCCs) pursuant to Art. 46(2)(c) GDPR. Cloudflare privacy policy. Legal basis: Art. 6(1)(f) GDPR.

Fonts are served locally. No content from Google Fonts or comparable third parties is loaded.

Contact “Write to me” (contact page, Azima, developers page): the card has no server. Your text stays in your browser. “Write on LinkedIn” copies it to your device’s clipboard and opens my LinkedIn profile in a new tab — what happens there is governed by LinkedIn. “By email” opens your own mail app with subject and text. The message only reaches me once you send it there yourself. No LinkedIn script is loaded, and no address you checked is written into the text.

Reach measurement (server-side)

Vienna Living Map does not measure individual usage events in your browser. No analytics code, no analytics cookies, no user, session or device identifiers and no dwell-time measurement are used for this.

To estimate the overall reach of the service, we use an aggregated visits figure from Cloudflare Zone Analytics. Cloudflare provides this figure based on the technical website traffic at its network edge.

From this, Vienna Living Map only takes and stores daily totals of date and number of visits. Since 8 October 2026 (extended on 14, 15, 18, 19, 20, 22, 23, 24, 25 and 30 October and on 10 November 2026), VLM additionally reads, for a fixed list of public addresses (the Azima pages, the index of building heights and the height data sheets that the Azima view and the light card of an address load — the sheets counted as a total, without any address —, since 25 October 2026 the index of roof colours, which only the 3D view loads, the frame of the light widget on partner sites, seven short addresses from the films, the home page — only its path, never the query behind it —, fifty other public pages and, since 23 October 2026, the two requests around a purchase — checking the purchase status (after payment, when restoring a purchase and before a Premium checkout) and sending the confirmation; only the path, never the purchase key in the query —, since 24 October 2026 the program files of the purchase sheet and the duel sheet, which the browser loads once per device when the sheet is first opened, and since 30 October 2026 four short addresses through which the field “Your address from above” in “Today in Vienna” and a link on the home page forward, plus the forwarding of the film cards there — counted per film, never the address you type, which stays in the browser —, and since the evening of 30 October 2026 the pages of “Vienna in motion” (the map, the figures page, the line and stop pages — only their path; what someone does on the map stays uncounted) and, since 10 November 2026, four short addresses through which the line “How does it feel to live here?” at the stops of “Vienna in motion” forwards to the map at that stop and to the light check — only the path; the evaluation does not read the position of the stop in the query —, the daily number of requests per address — again only as a total, with no reference to individual visitors, and not stored permanently (at most one hour in a cache). For this evaluation, VLM does not take or store IP addresses, device information, country information, referrers or personal content.

A visit does not necessarily correspond to a unique person. Returning visits can be counted more than once. Depending on the Cloudflare data basis, automated requests can also be part of the technical reach figure.

The aggregated reach number is displayed publicly in the “Vienna in numbers” section. The daily aggregates stored by VLM contain only the date and the aggregated number of visits. They are not combined with other information and are not used to create individual profiles.

The legal basis for this reach evaluation is Art. 6(1)(f) GDPR. Our legitimate interest is to be able to assess the reach and development of this service in highly aggregated form. The technical processing of connection data by Cloudflare for hosting, security and delivery is described in the “Hosting” section.

Accessibility

Vienna Living Map is developed with the aim of being as barrier-free as possible, and follows the WCAG 2.1, level AA. Implemented are, among others, keyboard operability, visible focus, sufficient contrast, large touch targets, labelled controls and respect for „reduced motion". Known limitation: the interactive map is only of limited use with screen readers — the central content (Living Score, rating, story, data) is, however, also accessible as text without the map. This statement is a self-declaration and is continuously improved. The full accessibility statement under the Austrian Accessibility Act (BaFG) names the standard, the status, known gaps and the complaint route. Please report barriers to [email protected] — we aim to respond promptly.

Your rights as a data subject

Under the GDPR you have the following rights: access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21). Please direct requests to [email protected].

You also have the right to lodge a complaint with the Austrian Data Protection Authority (dsb.gv.at, Barichgasse 40–42, 1030 Vienna).