Planner privacy

Planner Data & Privacy

The core yard planner does not require an account or property address. Its working state stays in your browser unless you deliberately copy a share link.

Last updated October 2, 2026

What is stored locally

Wrivel saves the current planner state in browser local storage under the key wrivel-plan. That saved state contains the selected unit system, rainfall, property width/depth, entered roof/driveway/hardscape areas, soil and slope selections, mitigation what-if inputs (roof redirect percentage and storage volume), measured route-fall values, field-verification checkbox states, plus the planner sketch objects and their coordinates.

What a share link contains

When you choose Copy share link, Wrivel builds a URL containing those planner inputs—including mitigation values, measured route falls and field-verification states—and a compact representation of the sketch layout. Wrivel creates the link in your browser rather than as an account-based private record. The data is readable from the URL itself by anyone who receives it. When that URL is opened, the full request URL—including its query parameters—is necessarily sent through the site's hosting/security infrastructure and may appear in ordinary technical or security logs.

What not to put in a share link

The planner has no name, address, parcel-number or free-text field, and you should not try to encode sensitive information into a shared URL. Treat a copied share link as information you are intentionally sharing.

How to clear the local plan

Use the Reset control in the planner to remove the wrivel-plan local-storage entry and return to the default sketch. Clearing site data in your browser also removes it.

Other local field-tool data

The Soil Infiltration Field Test stores its current worksheet separately in browser local storage under wrivel-infiltration-test. That entry contains the selected units, optional full-drain time and the three drop/time readings. It is not uploaded by the tool. Use the field test's Reset readings control or clear site data in your browser to remove it.

The Storm Observation Log stores up to 60 local event records under wrivel-storm-log. A record can contain the event date, optional rainfall amount/unit, pooling-duration category, outlet-flow category, a near-building flag and an optional short note. The tool does not upload those entries; Clear log removes them from this browser.

Advertising and infrastructure

Wrivel also uses the site-wide privacy and advertising controls described on the Privacy and Cookies pages. Cloudflare may process ordinary request/security data, and Google AdSense may process advertising data according to applicable consent choices.

Bottom line: the drainage calculation is browser-based. Sharing is optional, and a share URL should be treated as readable by its recipients.