Postnow

Privacy

Plain English summary of how this MVP handles your input. Last updated 12 June 2026. See also our legal & disclaimer page.

What you enter

You may enter a UK postcode or address, choose buying or renting, and optional priorities. Reports are generated from that input plus public data sources. We do not require an account to use the core service.

What we store

Depending on configuration, data is stored in local server files (development) or Supabase/Postgres (production). This includes opaque report sessions (full search input in server-side JSON only, 7-day retention), optional beta feedback, postcode monitor sign-ups, and purchase records. A redacted query preview (postcode or truncated text) may be stored for support — never in public URLs.

Optional email

Email is optional for beta feedback and only used if you choose to leave it for follow-up. Report email delivery and postcode monitoring require an email address for the feature you request. We do not sell personal data.

Report URLs

New reports use opaque links such as /report/r/rs_abc123… — your address is not placed in the URL. Legacy /report?query=… URLs redirect to opaque sessions automatically; avoid bookmarking or sharing legacy links manually as they briefly expose the query string.

Cookies

Essential cookies only in this MVP. If payment gating is enabled, a signed HTTP-only cookie (byo_paid_access) may remember that you unlocked a 1-hour full report for a specific saved report session after Stripe checkout — this is necessary to deliver the service you paid for. We do not use advertising, analytics or third-party tracking cookies. A simple notice is shown on first visit; acknowledgement is stored in your browser local storage, not a cookie. See our cookies page for detail.

Public data sources

Reports draw on public UK datasets (EPC, Land Registry, planning, flood, crime and others). Those datasets are maintained by third parties; we do not control what they publish or retain. See our data sources & licences page for detail on each source, update frequency and limitations.

Recently viewed reports (this device)

If you use Compare with another home, we may store a short list of recently viewed report session IDs and safe labels in your browser localStorage only — not on our servers. You can remove entries or clear this list in the comparison UI. Do not share report session links unless you are comfortable with someone else opening that saved report.

Saved report comparison

When you compare saved reports, we process opaque session IDs server-side to regenerate comparison results. Comparison URLs contain session IDs — treat them as private links. Sessions expire after seven days according to our existing report retention.

Area Finder searches

When you use Area Finder, we process your optional destination and manual candidate areas to generate comparison results. We do not persistently store these inputs in this MVP beyond short-lived server caches for amenities, transport proximity and public-data lookups. Avoid entering unnecessary personal details — a postcode, station or town is sufficient.

Ofcom postcode cache

When Ofcom broadband or mobile APIs are configured, we may cache normalised postcode-level results for up to 30 days (local file in development, Supabase in production) to reduce duplicate API requests. We store parsed signals only — not your full address and not raw API responses for resale. Purpose: quota saving and reliability.

Logs

Server error logs may record technical failures. We avoid logging full addresses or postcodes in routine logs. Do not include sensitive personal information in optional feedback comments.

Your rights

If you have used a feature that stored your email (feedback, monitoring or purchase), you can ask us to delete it by contacting the address below. This MVP is operated from the UK; we aim to handle personal data carefully and proportionately.

Privacy questions? Contact support@postnow.co.uk.