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/50
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). 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). 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.

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.

Draco decoder — Google LLC (github.com/google/draco)
Licence: Apache 2.0. Unpacks compressed 3D furniture models of the stage. 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/50, 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). 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).

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”. 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. The precise coordinate of the displayed location plus a radius of about 150 metres is transmitted (without account, without cookies, without tracking), only when opening an address detail card or starting a light check — this precision is technically required for the real shadow cast of the surrounding facades. 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), 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. 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. 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 share 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).

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 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 Brevo (Sendinblue GmbH, Berlin; processor, processing in the EU; legal basis Art. 6(1)(c) GDPR). 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).

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 there is no coordinate, only the address goes to the City of Vienna's address service. 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 is the nearest public garage in the mobility card: the garage list is a static public file 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.

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. For this evaluation, VLM does not take or store IP addresses, device information, country information, referrers, visited pages 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. 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).