Privacy Policy — TLV Next (tlvnext.com)
Last updated: 30 September 2026 · Version 0.12
1. Short version
TLV Next is a static map site. It has no accounts, no cookies and no advertising. It counts visits and measures how quickly the map loads and responds, with cookie-free tools that do not identify you and never receive the address you searched for or where you are looking on the map; section 5 says exactly what they do receive. The site does not collect, store or sell personal information about you. The only other personal data that exists at all is the record of requests to the site that the hosting company keeps, for up to 30 days, and, only while the aerial photographs fail to load, the requests your browser then sends to OpenStreetMap for its street map (section 3). The aerial photographs on the map come from this site, which keeps copies of recently requested photographs for about a day (section 3 gives the exact limits) so they load faster; those copies are pictures of the city and are not linked to you. Your location, if you choose to use it, never leaves your device: the site receives only the requests for the map data and aerial photographs of the area the map then shows, as it does for any view (section 3).
2. Who is responsible
The site is run by a private individual in Israel. Contact for anything about privacy: tlvnext@bdbd.net, or the project's issue tracker on GitHub if you would rather not use email.
Under the Protection of Privacy Law, 5741-1981, as amended by Amendment 13 (in force since 14 August 2025), the operator is the "controller" of any personal data described here and the hosting company is a "processor" acting on the operator's instructions.
3. What data exists, where, and for how long
| Data | Where | Why | How long |
|---|---|---|---|
| Server access logs: IP address, browser user agent, requested URL, timestamp | Hosting company, Vercel Inc. (USA); servers may be outside Israel | Running and securing the site | Up to 30 days. The site's hosting plan includes Vercel Observability Plus, whose documentation gives 30 days' retention for request data and runtime logs (Vercel); Vercel may keep security and infrastructure logs longer under its own policy. |
| Map coordinates in a shared link | In the URL you copy or receive | So the link opens the same view | Only in the URL; the site does not store it |
| Your device location | On your device only | Centering the map when you press "use my location" | The coordinates are never sent anywhere and are discarded when you leave. The map then loads the map data and aerial photographs of that area from the site, as it does for any view (next row). |
| Requests for map data and aerial photographs: which files and photograph tiles the map asked for, which shows the area on screen | Part of the server access logs above, at Vercel | Showing the map | As the access logs above. The municipality's server never receives your IP address or anything else of yours: the site fetches from it itself. |
| Copies of the aerial photographs themselves | Vercel's caches: its content delivery network, in the region that served each request (for visitors in Israel, Frankfurt), and a store in Frankfurt | So the photographs load quickly, including right after the site is updated, without asking the municipality again | Fresh for up to a day; a copy that is no longer fresh can be kept up to a week more, until it is next requested and refreshed. A copy records which photograph it is and when it was fetched, and nothing about who asked for it: no IP address, nothing that identifies a visitor. |
| Only if the aerial photographs fail to load: your IP address, your browser's user agent, the map tiles requested (which show the area on screen), and that the request came from tlvnext.com, but not from which page or view | The OpenStreetMap Foundation (United Kingdom), contacted directly by your browser | The map falls back to OpenStreetMap's map while the municipality's photographs are unavailable, and returns to the photographs within about 20 seconds of their coming back | Under the OpenStreetMap Foundation's privacy policy; the site has no control over it |
The site never asks for your name, email, ID number or any other identifying detail, and the operator does not receive any. The operator does not read individual log lines in the ordinary course; the hosting dashboard shows them in aggregate and for troubleshooting.
4. Cookies and local storage
The site sets no cookies and uses no tracking pixels or fingerprinting.
One thing is kept on your device: the language you chose. If you switch the map to English or back to Hebrew, that choice is stored in your browser’s local storage, so your next visit opens in the language you read. It is one word, it never leaves your device, it is not a cookie and it identifies nobody. Clearing this site’s data in your browser removes it, and the map works exactly the same without it.
As with any website, your browser also keeps its own temporary copies of what it downloaded, so that a reload is quick: the aerial photographs are used without asking again for an hour, and kept after that until your browser clears them. They stay in your browser, and clearing this site's data removes them.
Nothing else is stored on your device. The site does not remember what you searched for, where you looked, or that you have been here before. The copies of aerial photographs described in section 3 are pictures of the city, kept for everyone for about a day (section 3 gives the exact limits); they are not a record of who looked at them.
5. Analytics
The site uses Vercel Web Analytics, run by the same company that hosts it. It sets no cookie, stores nothing on your device and does not build a profile of you across sites or visits.
For each page view it records the page address, the site you arrived from, a coarse country, and the family of your device, browser and operating system. If you arrived by a link someone shared from the map, it also records the two tags that link carries, utm_source=share and utm_medium (native, copy or postcard, naming how it was shared; any other value is dropped), so that visits from shared links can be counted. That is all.
Since 24 September 2026 the site also uses Vercel Speed Insights, from the same company, to measure how quickly the map loads and responds for real visitors. For each page view it sends a few timings (how long the page took to start arriving and to show its largest element, how much the layout shifted, and how quickly the page answered a tap or a key), which element of the page each timing concerns, and the connection type your browser reports (for example "4g"). Like the visit count, it sets no cookie and stores nothing on your device, and Vercel derives from the request the same coarse country and device, browser and operating system family.
Since 27 September 2026 the site also uses Vercel Web Analytics to count the moments when it gave a visitor a bad experience, so that they can be found and fixed: the page freezing for half a second or more while the map moves, or just after a tap on one of its controls; the buildings taking more than five seconds to appear; the map failing to start, falling back to a simpler drawing, or losing its graphics; the aerial photographs failing and the street map being shown instead; a map data file failing to load; an error in the site's own code; and three or more quick taps on the same spot. Each count carries only which of these it was and a few coarse details: how long a freeze lasted, in a band (for example "1–2 seconds"); which kind of movement or which of the site's controls it followed (for example "touch" or "search"); the map's zoom level as a whole number, and whether it showed today or what is coming; why the map could not start or fell back; which kind of data file failed; and, for an error, its type, which of the site's own script files it came from, the name of the function it failed in, and its message with anything that could be an address, a number, a link or text typed into the site removed on your device before it is sent. At most six are sent per visit. They record nothing about your device beyond what the visit count already records, and like the rest they never receive your search or your position.
A freeze is also counted when it happens just before the page is left or hidden, or as a tap goes down, and a count named "reload", with no details of its own, says that the page was reloaded; it is one of the same six.
From time to time a small share of visits, chosen at random on your device for each visit and not remembered, try an automatic way of choosing between a detailed and a faster drawing of the map. To tell whether it helps, each of the counts above also carries which of the two groups the visit was in, and each visit sends one more count: which drawing the map started with and ended with, how many times it switched by itself (at most twice), and whether you changed the setting yourself. Like the rest, it carries nothing about your device and never your search or your position.
Since 29 September 2026 the site also counts each postcard made from the share menu, with Vercel Web Analytics: whether it was saved, handed to the share sheet or could not be made, and whether the map showed today or what is coming. It carries only that, with nothing about your device beyond what the visit count already records: not the place, not the picture and not the link. At most ten are counted per visit.
Since 30 September 2026 the site also counts four ordinary actions with Vercel Web Analytics, to learn which parts of the map visitors find and use:
- switching between today and what is coming (to which, and whether by the switch or by opening a link);
- a search (only whether a suggestion was chosen, the search was left, or nothing was found; never what was typed);
- opening a card (only its kind: a building, a permit, a permit application or a plan; never which one);
- switching the language (to which).
Each count carries only that, with nothing about your device beyond what the visit count already records: not the place, not the search text and not the building. At most ten of each are counted per visit.
One thing neither tool records, deliberately. This map writes what you are looking at into the address bar, so the address bar can hold the street you searched for and the exact point the map is centred on, which after you use the "my location" button is roughly where you are standing. Before anything is sent, the site strips the address bar down to the bare page path and discards the rest, keeping only those two sharing tags, and only for the page view. Neither service ever receives your search or your position. The relevant code is in src/analytics.js, src/campaign.js, src/events.js, src/signals.js and src/upgrade.js in the public repository, and you are welcome to check it.
If you would rather not be counted at all, any content blocker that blocks analytics will stop both, and the map works exactly the same without it.
6. Transfers outside Israel
Because the host is a US company, access logs and the analytics records of section 5 may be held outside Israel. Under the Privacy Protection (Transfer of Data to Databases Abroad) Regulations, 5761-2001, regulation 2(4) allows transfer to a recipient that has contractually undertaken to keep the data under conditions applying to a database in Israel; the Privacy Protection Authority's 2024 opinion on regulation 2(4) recognises such undertakings "with the necessary changes". Vercel's Data Processing Addendum (effective 31 March 2026) contains processor undertakings and the EU Standard Contractual Clauses, and Vercel is certified under the EU-US Data Privacy Framework.
One transfer is not the site's to arrange. If the municipality's aerial photographs fail to load, your browser fetches OpenStreetMap's map directly from the OpenStreetMap Foundation in the United Kingdom, which then receives your IP address under its own policy. The site sends it nothing, and the map shows the aerial photographs whenever they are available.
7. No database registration, no DPO
The site keeps no database of personal data. As the operator understands Amendment 13, registration now applies only to databases whose main purpose is trading personal data on more than 10,000 people and to public bodies, and a data protection officer is required only for large-scale or sensitive processing. Neither applies here.
8. Your rights
You may ask what data about you exists, ask for correction or deletion, or complain. Because the site holds nothing that identifies you, the honest answer will usually be that nothing is held; requests about access logs will be passed to the host where feasible. Write to tlvnext@bdbd.net, or open an issue on the project's issue tracker on GitHub. You may also contact the Privacy Protection Authority.
9. Children
The site is a public map with no interaction beyond browsing. It collects no data from anyone, including children.
10. Security
The site is served over HTTPS. Because it is static and stores nothing about you, the main risk lies in the hosting layer, which is covered by Vercel's security programme.
11. Changes
Changes are posted here with a new date. A material change will be visible in the first section of this page.
30 September 2026, version 0.12. Section 5: the site counts four ordinary actions (switching between today and what is coming, a search, opening a card, and switching the language), each with only its kind or outcome: never the search text, the place or which card. Nothing more is collected about you or your device.
29 September 2026, version 0.11. Section 5: a link sent with a postcard carries utm_medium=postcard, and each postcard made is counted, with only whether it was saved, handed to the share sheet or could not be made, and whether the map showed today or what is coming. A sharing tag with any other value is no longer recorded. Nothing more is collected about you or your device.
28 September 2026, version 0.10. Section 5: from time to time a small share of visits tries automatic switching between the detailed and the faster drawing, and the counts say which group a visit was in, plus one count per visit on the drawing it started and ended with.
27 September 2026, version 0.9. Section 5: a freeze is also counted when it happens just before the page is left or hidden, or as a tap goes down, and a "reload" count says that the page was reloaded. An error count also carries the name of the function it failed in and its message, with anything that could be an address, a number, a link or text typed into the site removed on your device first. Nothing is collected about you or your device.
27 September 2026, version 0.8. Section 5: the count of moments when dragging the map froze the page becomes a count of bad experiences more widely: freezes while the map moves or after a tap on a control, a slow first view of the buildings, the map failing or falling back, the aerial photographs failing, a map data file failing to load, errors in the site's own code, and repeated quick taps. Each count carries only the coarse details section 5 lists, at most six per visit. Nothing is collected about you or your device.
26 September 2026, version 0.7. Section 5: the site now also counts the moments when dragging the map froze the page for more than half a second, with the same Vercel Web Analytics. Each count carries only the length of the freeze in a band, the zoom level and whether the map showed today or what is coming, at most three per visit. Nothing else is collected about you.
25 September 2026, version 0.6. Two changes. Section 5: a page view from a link shared from the map now carries the link's two sharing tags, so shared-link visits can be counted; nothing else of the address is sent, and Speed Insights still receives the bare page path only. Section 3: the row on counting how many different IP addresses requested each aerial photograph is gone, because the site no longer does it. The photographs are no longer chosen for pre-loading by those counts after each update. Nothing new is collected about you.
24 September 2026, version 0.5. The site now also measures how quickly the map loads and responds for visitors, with Vercel Speed Insights. Section 5 names it and what it receives; like the visit count, it never receives your search or your position. Sections 1 and 6 mention it. Nothing else changes.
24 September 2026, version 0.4. A correction first: section 3 gave the hosting company's request logs as kept for a day at most; the site's plan keeps them for up to 30 days, and sections 1 and 3 now say so. The aerial photographs are now kept in the site's caches for about a day, including across updates of the site, and the most requested of the photographs asked for by at least 30 different addresses are loaded in advance after each update. Section 3 now lists both, and also the requests for map data and photographs that the access logs already held, and the OpenStreetMap fallback, whose requests go from your browser to the OpenStreetMap Foundation; the data sources page now lists it too. Section 1 now names the fallback, and says that using your location does not send it, but does load the map of that area. Section 4 now mentions your browser's own temporary copies. Nothing is collected about you that was not collected before.
23 September 2026, version 0.3. Section 4 now names the one thing kept on your device, the language you chose, and says that nothing else is stored.
19 September 2026, version 0.2. Visit counting was added, as section 5 anticipated. Section 5 now names the tool and what it receives, and section 1 no longer says the site has no analytics.
12. Contact
tlvnext@bdbd.net, or the project's issue tracker on GitHub — the operator, Israel.