Privacy notice · 14 October 2026
A useful calculation without a user profile
Rain Tank Planner has no accounts and does not sell personal information. The production service is designed to avoid saving exact coordinates or uploaded rainfall, and its own measurement contains daily totals rather than visitor records.
Controller and contact
Kenneth Fagermo, Norway, operates Rain Tank Planner and is the data controller for processing described here. Privacy questions and rights requests can be sent to privacy@raintankplanner.com.
What the calculator processes
In NASA mode, the planner automatically loads historical precipitation and average daily high and low temperatures when the page opens using the point shown in the form, and when you change the coordinates or history length. This can happen before you press Compare tank sizes, including while roof or water-use inputs are incomplete. The preview request sends the shown coordinates and history length to this application; it does not include your tank, roof or water-use inputs. The default map point does not use your device's location.
The application rounds coordinates to the source meteorology grid before requesting NASA POWER data. Exact submitted coordinates are used in working memory but are not written to the rainfall cache, request logs or aggregate metrics. NASA receives the rounded grid point, requested date range, precipitation and temperature parameters, and the application server's request metadata. The public grid-period response may be cached on the server for up to 30 days.
The checked daily history is held in the current page's memory and reused for the monthly climate chart, the historical water-flow illustration and automatic recalculation. Editing the tank, roof, water-use or unit inputs does not make another weather request for an already loaded history. Pressing Compare tank sizes sends your scenario inputs to this application for the comparison; after a successful comparison, automatic input edits recalculate locally using the checked record. Closing the page releases its in-memory history; the application does not save it in browser storage.
When you choose “Use my location,” your browser asks for permission. The site receives coordinates only after you approve the browser prompt. You can enter coordinates manually instead. A copied scenario link uses the rounded grid point, not the exact coordinates displayed in the form.
The historical-rainfall calculator displays a map using images downloaded directly from OpenStreetMap. The provider receives your IP address, browser information, this site's origin and the map areas you view. Clicking a point fills the form; it does not send your calculation or rainfall file to OpenStreetMap.
Town or postcode search runs only when you submit it. The application sends that search text to the Photon place-search service through our server. We do not forward your IP address or calculator inputs. A bounded in-memory cache holds hashed search keys and public place results for up to 24 hours; neither search text nor selected places are written to disk or analytics. The search is intended for towns and postcodes rather than personal addresses.
The initial unit setting and suggested delivery country use Cloudflare's approximate country information when available, with your browser's language region as a fallback. These are starting settings that you can change; shared calculation links retain their units. The country hint itself is not saved. When you use the supplier section, its selected delivery country is counted in daily aggregates described below.
For a local rainfall CSV, the browser extracts only the date and rainfall columns and sends the normalized rows to this application for the current calculation. The rows are not written to disk or included in metrics. Do not put names, addresses, notes, or other personal information in the file.
The garden-watering helper calculates in your browser without uploading or saving its tank, water-use, pressure or delivery inputs. Its link from a tank result carries only capacity, daily use and units in the URL fragment (the part after #), which is not sent to the server. The page view may add to the same fixed daily page counts described below. A separate request to this site's server reads the public supplier-link setting, with no calculation inputs or selected country attached.
The optional next-rain refill forecast runs only when you request it. Place search works as described above. The forecast request sends your selected coordinates, rounded to two decimal places, through our server to MET Norway; it does not forward your IP address, place label, tank inputs, roof area or water-use values. The server caches public weather responses by that rounded point and the provider's expiry time, then normalizes future intervals for each request. Forecast projections and roof inputs stay in your browser. We do not record forecast selections or requests in aggregate analytics.
Choosing Copy water-budget link in the garden helper copies a link containing the completed water-budget assumptions and any entered pressure or delivery measurements in the URL fragment. Forecast location and roof inputs are not included. Anyone you give the link to can reopen those values. The site does not save the link or record a garden-link copy event. If clipboard access is unavailable, it displays the same link for manual copying.
Operational and aggregate data
The application keeps IP-address request counters in volatile memory for up to 15 minutes to prevent excessive calculator or measurement requests. It does not write those counters to disk. The application itself does not create access logs containing IP addresses, coordinates, user-agent strings, or calculation contents.
Daily aggregate metrics record page counts by a fixed public-page name, calculation requests, successes, failures, source type (NASA or local CSV), cache outcome, response time totals, and counts of result downloads, copied scenario links, “Print / Save PDF” button use and optional “Was this useful?” Yes/No responses. Printing happens in your browser; the printable summary and PDF are not uploaded or saved by the application server. Feedback stores only a daily Yes or No count, without a calculation identifier or free-text response. Supplier measurement adds counts of section views, delivery-country selections, supplier-link clicks, local-search clicks and accepted “Compare this size” selections. Breakdowns use only fixed supplier names, selected delivery countries and broad capacity bands; exact tank sizes and individual event records are not saved. These are activity counts, not unique visitors or confirmed purchases.
Metrics do not record the URL query string, referrer, search term, exact scenario values, filename, link contents or a visitor identifier. These counts cannot be connected to a person, IP address, coordinate, browser, or uploaded file. They are kept for up to 400 days to measure whether the service works and is useful, and whether supplier links merit future commercial partnerships. Suppliers receive no visitor-level analytics from us.
Cookies, advertising, and browser analytics
Quick roof choices and the automatic water-use scenarios use the same current calculation inputs. A selected roof-estimate label is held in the page and can accompany a shared scenario, exported comparison or printable summary. The application does not save this label in usage totals or add it to supplier links. Low, normal and high water-use cases count as one calculation request, not three separate visits or calculations.
Known automated user agents and requests explicitly marked as checks are excluded from new aggregate counts. A user-agent value is evaluated only in request memory and is not added to saved metrics. To use the calculator without adding usage counts, open the planner with usage counting off. This applies to that page and its calculation, feedback and supplier events; it uses no cookie or visitor identifier. Earlier aggregate counts are unchanged, and the remaining counts are not verified human visitors.
At the date above, the site sets no cookies and loads no advertising or third-party browser analytics script. Its AdSense ownership meta tag and ads.txt entry are passive text: they do not contact Google from your browser or display advertising.
Google Search Console may separately provide aggregate information about how pages appeared in Google Search, such as impressions, clicks, broad country, device, page, and search-query data. Protected operational reports keep that evidence separate from local planner totals and do not attempt to identify or join visitors across the two systems.
Advertising will not be activated until the site is approved and an appropriate Google-certified consent platform is configured for visitors in the EEA, United Kingdom, and Switzerland. This notice and the site controls will be updated before that change. Declining optional advertising storage will not prevent use of the planner.
If Google advertising is enabled
Google ads are currently inactive. The following describes planned advertising only. If enabled, third-party vendors, including Google, may use cookies to serve ads based on your previous visits to this site or other websites, subject to your choices and applicable consent requirements. Google's advertising cookies enable Google and its partners to serve ads based on those visits.
You can manage or opt out of Google's personalized advertising through Google Ads Settings. For other participating vendors, WebChoices provides advertising opt-out options. These external services have their own privacy policies and may use browser storage to remember your choices. Opening this privacy notice does not contact them; following a link sends a normal browser request to the selected service.
Before advertising is activated, this notice will identify the vendors actually used, link to their privacy information and describe the site's consent controls. A Google-certified consent platform will be used for relevant visitors in the EEA, United Kingdom and Switzerland. Until those controls are configured and verified, this site will continue to use passive AdSense ownership verification without loading ad code. See how Google uses advertising information.
Providers and international processing
Supplier cards use a local list of public links; displaying the cards does not contact suppliers. If you click a supplier or search link, the destination receives a normal request from your browser and handles it under its own privacy policy. Supplier links identify a product; search links include only nominal capacity and your chosen country. We do not include your coordinates, home address, water-use inputs or uploaded rainfall in those links.
The garden helper's local equipment search includes only an irrigation search phrase and your chosen country. Its US shop link may be an affiliate link when a programme has been approved and configured; an active affiliate link is labelled beside the link. It includes our public publisher identifier, and the destination or its affiliate service may use cookies to attribute a purchase under its own policy. Displaying the link sets no cookie here and sends no request to the merchant. We do not add your garden inputs or a visitor identifier to it.
- Cloudflare delivers and protects the public site through its network. It necessarily processes network information such as IP addresses and security signals under its own documented retention and transfer safeguards. See Cloudflare’s privacy policy.
- OpenStreetMap Foundation provides the map images directly to your browser. See the OpenStreetMap privacy policy.
- Photon, hosted by komoot, provides OpenStreetMap-based place search. It receives submitted search text and the application server's request metadata. See the Photon service information.
- NASA POWER supplies public precipitation and temperature history. It receives the rounded grid point and the application server’s network request metadata, not the visitor’s IP address or other planner inputs. See the NASA privacy policy.
- MET Norway supplies the optional weather forecast. It receives the selected point rounded to two decimal places and the application server's request metadata. See MET Norway’s privacy information and the weather API terms.
Purpose and legal basis
The calculation inputs and short-lived security counter are processed for the legitimate interests of delivering, securing, and improving a free requested service. Browser geolocation is used only after your permission. We limit the data and retention because the same purposes do not require an identity profile.
Your choices and rights
You can avoid browser geolocation, enter a broader regional grid point, use a local CSV, or leave the site. Depending on applicable law, you may request access, correction, deletion, restriction, portability, or object to processing. Because the application deliberately does not create visitor records, there may be no stored record that can be linked back to you.
You may also complain to the Norwegian Data Protection Authority (Datatilsynet) or your local supervisory authority.
Changes
Material changes—especially the activation of advertising, cookies, or new measurement—will be reflected here with a new date. The current version remains available at this URL.