AI AIRES

Privacy and data notice

Clear context for better lead follow-up.

AIRES is built to help real estate teams understand where a lead came from, what the visitor showed interest in, and who should follow up next. This notice explains the current data practices for the public website, demo flows, and private Lead Hub.

Last updated July 4, 2026

Request a full demo View Lead Hub Review CRM strategy

What is captured

AIRES connects form submissions to useful first-party context.

A basic contact form tells a brokerage who raised their hand. AIRES adds practical context around the request so a broker or agent can respond with less guesswork.

Public website activity

  • Pages viewed during the current browser session.
  • Buttons or links clicked before a form is submitted.
  • Referrer and campaign details when they are available.
  • Basic listing, community, event, or demo-page context.

Lead form submissions

  • The contact details and message a visitor chooses to submit.
  • The source page, selected interest, property, community, or event.
  • A short first-party journey summary attached to the lead record.
  • Routing fields used to assign the right agent, team, or broker queue.

Private Hub workflow

  • Lead status, priority, assignment, tasks, notes, and follow-up activity.
  • Client, agent, event, project, CRM export, and support-package settings.
  • Operational logs that help diagnose routing, access, or delivery issues.
  • Feature flags and module settings for each brokerage workspace.

How it is used

The goal is better routing, faster follow-up, and clearer accountability.

  • Route inquiries to the right person or team.
  • Give agents and brokers useful context for follow-up.
  • Show which pages, listings, or communities influenced a request.
  • Support demo, onboarding, reporting, export, and CRM handoff workflows.
  • Improve launch planning, support quality, and client accountability.

Visitor choice

Submitting a form is intentional.

Public session context is stored in the visitor's browser during the current session and is attached to AIRES lead forms when the visitor chooses to submit a request. Visitors should avoid submitting sensitive personal information that is not needed for real estate follow-up.

Client workspaces

Brokerage data should stay scoped.

AIRES is moving toward a multi-client operating-system model where each brokerage has its own branding, domains, agents, routing, modules, and feature flags. Production workspaces should use named Hub accounts, role-based access, secure credentials, data-retention terms, and client-specific CRM handoff rules. Demo access should move to approved brokerage users before a production launch.

Operating boundaries

What AIRES does not treat as public.

  • AIRES does not sell submitted lead data.
  • Public journey tracking is first-party and session-based.
  • The public website does not expose protected Hub records or credentials.
  • Protected Hub access should use named brokerage accounts with role-based permissions for production launches.
  • Live walkthrough access should move to named brokerage accounts before production use.
  • CRM and notification credentials should stay in secure server-side configuration.