What estate.sh stores.
Server logs, request metadata, API usage, error logs, and public listing data needed to run the search product. Favourites are stored in your browser's local storage and are not account-backed at launch.
§ Privacy · launch
How estate.sh handles logs, local browser storage, contact emails, API traffic, and third-party services.
Four surfaces
The launch product is read-only and unauthenticated. The only personal data we touch is what you send to a mailbox or what flows through your browser when assets load.
Server logs, request metadata, API usage, error logs, and public listing data needed to run the search product. Favourites are stored in your browser's local storage and are not account-backed at launch.
The message, sender address, and any supplied context are used to respond to the request and handle corrections, takedowns, support, or API/commercial enquiries.
The launch product avoids account cookies. If analytics are added, this page must be updated before launch to describe the provider and events. Map, hosting, exchange-rate, and source-image providers may receive request metadata when their assets load.
Public API requests may be logged for abuse prevention, debugging, rate limiting, and reliability. Do not send private personal data to the public API.
Open question
Email us with the URL and the field. We process source-owner notices and personal-data requests with the same priority.