1. Cookies and similar storage
Cookies and browser local storage can retain information between visits. The current application uses local storage for Supabase authentication sessions and for homes saved by visitors who are not signed in. Local storage is distinct from a cookie but can still affect your privacy.
2. Storage used by the application
No analytics or advertising SDK is configured in the application code reviewed for this page. That does not establish that every deployment or embedded third party is free of cookies.
- Supabase session storage: the sb-<project-reference>-auth-token key stores account-session information so you can remain signed in. It is managed by the authentication client and can be removed by signing out or clearing site data.
- Saved homes: the 32-plus-saved-homes key stores property identifiers for visitors who save homes without signing in. It remains until changed or cleared. Signed-in saved homes are stored in the account database.
3. Embedded and external services
Property pages embed Google Maps. Google Fonts and some Unsplash images are also loaded externally. These requests disclose technical information to their providers, and embedded content may use its own cookies or storage.
A complete deployment-level cookie inventory, third-party storage durations and any required consent controls are being confirmed. This page does not claim that non-essential third-party activity is already blocked.
4. Your controls
You can review, block or clear cookies and site storage in your browser settings. Clearing authentication storage may sign you out; clearing saved-home storage removes locally saved homes. Blocking third-party content can affect maps, fonts or images.
The current application has no cookie-preference panel. Contact the operator with questions about a specific service or storage item.