HomeWalkBack to HomeWalk
Data & security

How a HomeWalk stays private

A customer HomeWalk is designed to be shared directly between a business and its customer. It is not a public profile, searchable property page or open photo gallery.

Private customer links

Customers receive a long, opaque link rather than a predictable customer or property ID. The private token is stored by HomeWalk in hashed form. Customer HomeWalk pages are also configured with search-engine instructions not to index or follow them.

Private uploads

Property photos, electricity bills and similar customer files are stored in a private Supabase Storage bucket. HomeWalk creates signed upload and download links when a permitted customer or workspace user needs to transfer a file. Those file links are time-limited rather than permanently public.

Workspace separation

Business users sign in to a HomeWalk workspace. Server-side checks scope customer records to the workspace associated with the authorised user or admin token. Database Row Level Security is enabled on HomeWalk’s core tables, while privileged service credentials remain on the server and are not exposed to the customer browser.

Infrastructure

HomeWalk currently uses Supabase for authentication, database, private storage and server-side functions, with the primary project configured in Sydney, Australia. Vercel hosts and delivers the Next.js web application. Supporting delivery, security and logging infrastructure may operate across other locations.

What customers should do

What pilot businesses should do

Last updated 16 October 2026. Security controls are reviewed as HomeWalk moves from founding pilot toward broader commercial use.