IDX data handling
Security one-pager for brokers, compliance officers, and IT reviewers.
Texto e ilustraciones generadas por IA — no se requiere video demo.
Resultados compuestos ilustrativos — no un cliente nombrado salvo que se indique.
Data flow
MLS data flows from approved RESO/Trestle feeds into tenant-isolated cache tables. Public site reads from cache — not live MLS credentials in the browser.
- Tenant row-level isolation
- Refresh on cron + on-demand invalidation
- No resale of MLS data to third parties
- Webhook and API access logged
Access control
Broker admins control agent roster, routing rules, and portal users via RBAC. MLS credentials stored encrypted at rest.
- RBAC permission keys per workspace
- Audit trail on admin changes
- GDPR/LGPD export and deletion workflows
- Policy-controlled call recording where enabled
Retention
Cached listing rows follow MLS vendor display rules; off-market listings purge on schedule. Lead and conversation data retention configurable per tenant policy.
Is data shared between broker clients?
No — each tenant workspace is fully isolated.
Where is data hosted?
Production on Railway with US-region infrastructure; see Trust Center for current subprocessors.