A small beta with limited data collection

Optional aggregate analytics

When enabled, Plausible receives coarse product events such as search use and successful Watch actions. We send no search text, address, postcode, coordinates, email, Watch identifier or private token. Page URLs are reduced to broad routes and referrers to their origin.

Plausible processes the request IP and browser information to produce aggregate statistics on EU infrastructure. We add no persistent analytics identifier, recording or advertising tracker. This cannot reliably measure people returning across days or devices. Your Watch subscription is independent of this choice.

Plausible data policy

What Into View stores

The beta has no user accounts. It uses sessionStorage only to return you from an information page to the map and uses localStorage only if you save an analytics opt-out preference. If you request to manage all your watches, it sets one secure, HTTP-only cookie for a temporary two-hour session; that cookie is not used for advertising or analytics. Browser storage is not required to retain an area watch. No advertising is installed. Optional aggregate product analytics is disabled unless configured.

Search terms are sent to an Into View server. Complete postcodes use Postcodes.io; town and settlement searches also use Postcodes.io when needed. Curated project matches remain in your browser. When you open or move a Watch preview, or create a Watch, its coordinates may be sent to Postcodes.io to find a nearby postcode district. A selected search can supply a server-signed safe label instead, avoiding another lookup. Geoapify address search is currently disabled; Into View does not send searches or Watch coordinates to Geoapify in this configuration. Geocoders receive the query or coordinates and necessary language settings from our server, never your Watch email, Watch ID, management token or session identifier. Searches and resolved locations may remain in a bounded server memory cache for five minutes. Into View does not log search terms or provider responses or save a search history. The selected Watch-safe label is stored with the Watch; it normally omits house numbers, flat details, business names and full postcodes. Existing labels are retained until deliberately enriched. Hosting providers may retain normal request/security logs.

If you create an area watch, Into View stores the email address you provide, the watched centre, its displayed location label and radius, your change-type and timing preferences, and operational timestamps needed to evaluate and deliver the watch. A watched area may reveal somewhere you live or work, so Into View treats the location as personal data. It does not label a watch as home or work and does not collect continuous location history.

A watch remains pending until you use the verification link emailed to you. Verification and management links use high-entropy secrets; the database stores only one-way hashes of those secrets. Alert history stores source-record identifiers and meaningful-state fingerprints so the same update is not repeatedly emailed. It does not create an account, password, profile or marketing subscription.

A manage-all request temporarily stores the normalized email with one-way hashes of a single-use 45-minute email token and, after exchange, a two-hour session token. The raw tokens are not stored. They become unusable on expiry or explicit invalidation and are removed by bounded housekeeping; the request is rate-limited using hashed email and network identifiers.

Planning information

Into View processes selected facts from council planning records and licensed data feeds to explain proposed changes. These include application references, proposals, site addresses, planning decisions, dates and approximate locations. Coverage varies by council, and an approval does not establish that construction has started.

We discard structured applicant, agent and officer contact fields during feed processing. We do not publish a raw feed or a contact directory. Public proposal text may still contain personal information supplied in a planning record. If you identify inaccurate or unnecessary personal information, contact us using the details below so we can review it and the source. Temporary feed files are deleted after processing; stored facts and backups are subject to the applicable licence and our correction and deletion procedures.

Location and sharing

“Use my location” asks your browser for permission. If allowed, the coordinates are used in the browser to move the map and are not stored by Into View. Moving the map causes the map provider to receive requests for the viewed map tiles, which can reveal an approximate area of interest alongside normal request information.

Sharing uses your device’s share sheet where available, or copies the public Into View link to your clipboard. The destination app or service has its own privacy terms.

Infrastructure and third parties

The site is hosted on Vercel. Like other web infrastructure, Vercel processes request and device information such as IP address, approximate location derived from IP, browser details, requested pages, timestamps, errors and security logs. Operational retention depends on the hosting account and provider settings.

Map styles, vector tiles, labels and fonts are requested from OpenFreeMap. Its published privacy policy says its normal server logs are anonymised and include browser type, referring pages, timestamps and operating system without IP addresses by default. It may temporarily log IP addresses for up to 30 days when investigating a security incident, and may use Cloudflare to deliver the service. OpenStreetMap supplies the data packaged in those tiles, but the browser does not request tiles directly from the public OpenStreetMap tile servers.

You can read the current OpenFreeMap privacy policy. Supabase stores the roadwork dataset and is queried only by the Into View server; the browser receives normalised public map records and does not connect to the database directly. Supabase also stores area watches and their delivery history.

Into View uses Resend as its transactional-email provider when production email delivery is enabled. Resend receives the destination email address and the content needed to send verification, confirmation and requested watch-digest messages. Into View does not add tracking pixels or use watch emails for marketing.

Postcode and settlement lookup uses the Postcodes.io API, which is maintained by Ideal Postcodes and built from postcode directory and open mapping data. Because the lookup is proxied by Into View, Postcodes.io receives the requested postcode from Into View’s server rather than a direct request from your browser. See the current Postcodes.io licence information.

Following a linked council, government or project source takes you to that organisation’s website and privacy terms.

Pausing, deleting and retention

Every confirmation and digest email for an active watch contains a secure management link. You can edit preferences, pause a watch or delete and unsubscribe immediately without an account. Deletion removes the stored email and watched location from the live watch record, invalidates its access links and stops future messages. Associated baseline and delivery records remain linked to the pseudonymised watch until that record is removed after 30 days. Minimal delivery and security records may also remain in infrastructure backups and operational logs for their normal retention period before expiry.

Expired pending watches are pseudonymised after seven days, rate-limit records are removed after two days, and deleted watch records are removed after 30 days by the watch job. Infrastructure backups may take longer to expire under provider retention settings. Into View does not sell watch data, infer journeys from it or ask for marketing consent; watch emails are service messages requested by the person creating the watch.

Operator and privacy contact

Into View is operated by Kirill Lyakhovets, trading as Into View. For privacy enquiries, contact privacy@intoview.uk. The operator still needs to confirm exact operational-log retention and complete a human UK privacy review. This technical notice is not legal advice and will be updated as the service changes.