Your data, explained.

What this website stores

When you sign in, the workspace uses your authenticated account identifier and email to keep your agency’s data separate. Saved information includes agency settings, property listings, enquiries, conversations and subscription status. Contact forms store the details you submit so the operator can respond.

The product demonstration

The working demo uses fictional listings and live AI. Messages and relevant property details are sent to the configured AI provider to generate responses. Demo conversations and enquiries are saved in an isolated session for up to 24 hours; expired sessions are removed during subsequent demo use. They are not sent to an external estate agency. Use example contact details. A necessary, HTTP-only cookie identifies your demo session.

Connected property assistants

When enabled, a website assistant sends visitor messages and relevant listing information to the configured AI provider to generate replies. Agency teams can access their own enquiries and conversation history. Do not enter sensitive personal information into chat.

Payments and account access

Payments, when configured, take place with the payment provider. AgentReady stores subscription references and status, not card details. Customer email/password accounts are handled by Supabase when enabled. Necessary, secure HTTP-only cookies maintain sessions. Supabase sends email-confirmation and password-reset messages through the configured email service. Passwords are not stored in AgentReady’s workspace database. Existing operator access may use ChatGPT sign-in during migration. Purchase welcome emails use Resend; recipient email, message content and delivery status are recorded to support sending and retries.

Storage and choices

The hosted workspace stores records in its connected database. The widget may use browser storage to remember a visitor’s conversation on that device. Agencies must supply their own visitor-facing privacy notice and confirm the appropriate retention and data-processing arrangements before activating the service.

Optional Telegram alerts

When an agency enables Telegram, the service sends an event notice and workspace link to the chat it configures. Alerts do not include visitor contact details. Bot tokens are encrypted in storage. Telegram delivery is best effort; the workspace remains the source of enquiry and conversation records.

Agency data controls

Agencies can export workspace records from Settings and delete individual enquiries or conversations. A manual cleanup tool can delete closed records older than a chosen period, after preview and confirmation. It does not delete open work automatically. Telegram delivery attempts store the event type, time and delivery result. Deleting a conversation removes its stored messages; linked enquiries must be deleted separately. New chat clears the widget’s local conversation selection; it does not delete the agency’s saved conversation. Follow-up dates and private notes are visible only in the agency workspace.

Questions and requests

Use the contact form for access, correction or deletion requests. The operator must verify the request and applicable obligations before acting.