Rain RadarsBack to the radar explorer

Privacy & cookies

Last updated:

Browsing does not require an account. The site uses its own first-party audience analytics to understand how it is used; it does not use third-party analytics, advertising trackers, or payment forms. You can turn analytics off at any time with “Analytics” in the footer, and doing so does not affect radar features. External map and font providers receive direct browser requests.

What the service receives and why

To deliver pages, radar images, calendars, and status, the server receives technical requests and the IP address needed to return a response. Requests identify selected dates, time windows, and requested radar timestamps. The app's HTTP logs record request paths and response status; a hosting provider or reverse proxy may additionally record IP addresses, browser information, and referrers for delivery, security, and troubleshooting.

Drawing shapes, placing measurement markers, and calculating rainfall take place in your browser. Those shape coordinates are not submitted to the application server by the current code. Map-tile requests can nevertheless reveal the geographical area being viewed to the selected map provider. The app does not request your device's precise location.

Cookies, browser storage, and caching

The public radar viewer does not set cookies. The private owner dashboard uses an HttpOnly session cookie, with Secure on HTTPS and SameSite=Strict, valid for at most seven days and expiring after 24 hours of inactivity. Signing out revokes it. The viewer stores a random analytics identifier (see audience analytics) and your “Don't show again” preference in localStorage on this browser. When checked, the welcome tour stays dismissed across refreshes; when unchecked, it appears again after refreshing. These preferences are not sent to the server; clear this site's browser data to reset them. Radar frames and measurement state are held in browser memory for the current page session; reloading clears that application state. Your browser can separately retain ordinary HTTP cache entries for images, map tiles, fonts, and other resources according to their cache headers.

External providers have their own privacy practices. This notice does not assert that every third-party service is cookie-free. Browser settings can restrict third-party requests, cookies, or cached data, but blocking providers can prevent maps or fonts from loading.

Audience analytics

To understand how much the site is used and which features matter, analytics runs by default when you visit. This is first-party only: reports go to this site's own server and are not shared with or sold to analytics or advertising companies. The site stores a random browser identifier in localStorage, replaced every 90 days. The server stores a keyed hash of that identifier, a random page-session identifier, visit and last-activity times, foreground interaction duration, broad device/browser categories, feature-use counts (history, time scrubbing, spread, cumulative, measurements, map layers, and help), and approximate country. Reports are sent at most about every 15 seconds while there is activity, plus an initial or final report. Unique browsers are an estimate, not identified individuals.

Turning analytics off: use “Analytics” in the footer of any page and choose “Turn off analytics”. This removes the identifier from browser storage, stops further reports from that browser, and is remembered until you clear this site's data or turn analytics back on. Browsers sending a Global Privacy Control or Do Not Track signal are never tracked. Blocking scripts or clearing site data also prevents or resets tracking.

The server receives your IP to deliver requests and can use a locally installed DB-IP Lite country database (CC BY 4.0) to estimate country. This lookup does not send your IP to a location service. The analytics database does not store your raw IP, complete user agent, map coordinates, measurement shapes, form contents, or selected radar dates. Country may be unknown or inaccurate, especially with VPNs or mobile networks.

Visitor records are automatically deleted after 90 days while the service is running. Admin sign-in attempts retain a keyed IP pseudonym, timestamp, and result for 30 days for security and abuse prevention. Analytics records are excluded from deployment backups. Ordinary reverse-proxy access logs are separate and can contain IP addresses under the operational-log policy below. Contact support about existing records; turning analytics off stops future collection and does not automatically delete prior server records.

External providers

Hosting, retention, and international processing

Hosting location: not yet published; confirmation is required before public launch. External providers may process network information outside Israel under their own policies.

Operational-log retention: not yet published; a retention period must be confirmed before public launch. This notice does not promise automatic deletion on an unconfigured schedule.

Contact and your rights

The legal operator's identity is listed on the contact page. To ask about personal information, request access or correction, or request deletion where applicable law provides that right, contact [email protected]. We may need reasonable information to identify the relevant records and verify the request. Do not send passwords, API tokens, or unrelated identity documents.

Emailing support is voluntary. Your email address, message, and information you choose to include are used to handle your inquiry; email delivery is also subject to the email provider's practices. Browsing the service does not require contacting support.

Changes

This notice describes the current implementation. Additional analytics, alerts, accounts, hosted services, or other changes to personal-data handling require an updated notice and any additional permissions required by applicable law.