KNOW WHAT STAYS

Your data in this demonstration.

Use sample information only. This is a fictional property-search experience.

Property catalogue

All property references, prices, areas and facts are synthetic and versioned with the website. Nothing is for sale or rent. Licensed reference photographs show real interiors but do not document these fictional properties. The map has no real addresses, location tracking, external map tiles or geocoding.

Saved interests in this browser

The shortlist stores up to 12 public property IDs in localStorage under merefield:saved:v1. It remains until you remove it or clear this site’s browser storage. It does not sync between devices. If storage is damaged or unavailable, interests stay in memory for that page only, and a notice explains this.

Sample enquiries on the demo server

Submitting the form sends selected property IDs, a preferred date window, sample name, example.com email and optional sample note to this demo server. These are stored in a local SQLite database. No adviser, business, email or SMS service receives the submission.

A random session cookie named mf_session is HttpOnly and SameSite=Lax. A separate mf_csrf cookie protects form submissions. Cookies last at most 24 hours. The database keeps only a hash of the session token. It stores request references and creation times to make retries safe.

Lifetime and deletion

The server refuses access when a session reaches 24 hours. Expired records are deleted in bounded batches when the server starts or handles a mutation; physical cleanup can occur later if the demo is idle. Clear my demo immediately deletes your current server session and its enquiry records. It does not erase your separately saved property interests.

Logs and services

The application does not log request bodies, sample notes or arbitrary search terms. It uses no analytics, tracking pixels, third-party maps, payment service or real message delivery. Fonts, photographs and conceptual diagrams are served locally. This local build makes no claim about a future hosting provider’s logs; hosting configuration requires a separate review.

Recovery copies

A local recovery test uses synthetic records in separate test databases. This build does not automatically back up visitor enquiries. Any future backup and deletion policy must be reviewed before public hosting.