Privacy at Reai

Information you give us

A demo request includes your name, mobile number, optional agency, property focus, enquiry volume and preferred demo time. We use those details to arrange and follow up on your request. Sending the form requests a conversation; it does not book a calendar event or start a subscription.

An agent workspace contains the profile, listings, clients, knowledge, settings and work activity that you provide or authorize Reai to process. You are responsible for having permission to use client information in the service.

WhatsApp and the Assistant

Connecting a work number lets Reai process new messages for the features you enable. New enquiries may be classified to distinguish work from non-work messages. Reai does not import your previous WhatsApp chat history. Use a dedicated work number rather than a personal number.

Relevant conversation and workspace context can be sent to the configured AI provider to draft and check replies. Human approvals and conversation controls still apply. Numeric usage and reviewed feedback help us assess the service; Reai does not use your message text, names or documents to train its own language model.

Your Google Calendar connection

Google Calendar is optional. You choose an owned calendar for Reai appointments and the calendars whose busy periods should block proposed times. Reai reads calendar-list information to offer those choices, and free/busy information to check availability. Conflict checks do not need the titles or descriptions of unrelated events.

With the required approvals, Reai creates appointments and checks, reschedules or cancels events tied to its own booking records. An appointment can include the client name and phone number, property or meeting location, and time. Those details are sent to Google. The booking workflow verifies the recorded event before changing it.

OAuth access and refresh tokens, selected-calendar information and Reai booking records are stored to support your connection and its recovery. Private integration credentials and appointment content are encrypted in application storage. Availability is used to propose and check appointment times; it is not used for advertising or credit decisions.

Reai follows the Google API Services User Data Policy, including its Limited Use requirements. Google data is used for the user-facing calendar features you authorize and the security and operation of those features. We do not sell Google data, use it for personalized advertising, or use it to train general-purpose AI models.

You can disconnect Calendar in Connections and revoke access in your Google Account settings. Disconnecting stops local access; Reai reports separately whether Google confirmed token revocation. Disconnecting does not itself delete appointments already in Google Calendar.

Service providers and protection

Reai uses providers including Supabase for authentication and storage, Vercel for web hosting, Railway for the connection worker, Anthropic for AI processing, and Google when Calendar is connected. WhatsApp operates the messaging service. These providers may process relevant information internationally; Singapore is our first property market, not a Singapore-only processing restriction.

Private workspace records and demo-request contact details are protected with access controls and application encryption. Essential cookies support sign-in. Hosting services process request metadata for delivery and security; demo intake uses keyed identifiers for abuse protection. Private workspace information is not made public on the landing page.

Access to private workspace content for support is limited by the scope and expiry you authorize and is recorded. Company demo enquiries are kept separate from agents’ client workspaces and are available only through authorized operator controls.

Retention, access and deletion

Demo requests are retained for arranging and following up on the demo and can be deleted by an authorized operator. There is no automatic deletion period currently configured. Deletion removes the encrypted contact details; minimal request, deletion and operator-audit metadata remain to prevent a retried form submission from restoring deleted details. Keyed abuse-prevention counters older than two days are pruned during later intake. Contact dev@reai.sg to request correction or deletion.

Workspace owners can request an export or deletion through Account & data. A submitted request is not proof of completed deletion: unresolved calendar operations, security records, provider-held records and backup schedules may affect completion. The workspace shows the recorded outcome. Information already held by an external provider is also governed by that provider’s controls and terms.

Updates and contact

We update this notice when the service’s data practices change. Changes to Google-data use beyond your existing consent require an updated disclosure and consent where applicable. Contact dev@reai.sg with questions about this notice or your data.