Which markets does PropVista support?

PropVista launches with the United Arab Emirates (Dubai Land Department / RERA / Trakheesi) and Canada (TRREB / RECO / Tarion). The jurisdiction-adapter architecture lets new markets be added without changing the core platform.

How is each brokerage's data kept separate?

Tenant isolation is enforced at the database level using Postgres row-level security, backed by an application-level tenant scope. A request authenticated for one brokerage cannot read or write another brokerage's records.

Is PropVista compliant with Dubai's Trakheesi rules?

Yes. A listing cannot be published in Dubai without a valid Trakheesi permit number. The permit is validated by a compliance gate before the listing is allowed to go live, and permit expiry is monitored.

How is TRREB and VOW compliance handled in Canada?

Canada listings follow board data-access agreements: VOW display requires a registered consumer relationship and a confirmation window, and field-level access (DLA / IDX / VOW / BBO) is gated per the operating brokerage's membership.

Where is PropVista data hosted?

PropVista runs in a single AWS region with multi-AZ redundancy and encrypted backups. Data residency is kept in one region by design until customer demand justifies a residency split.

How PropVista works

PropVista is a multi-tenant, multi-jurisdiction real-estate platform. This page explains where our data comes from, how regulatory compliance is enforced, how your data is kept isolated and secure, and how we stay transparent — the same model auditors and regulators ask about.

How listing data is sourced

PropVista does not scrape consumer portals. UAE inventory comes from direct partner-agency feeds and free, permit-validated seller listings; Canada inventory comes from board-authorised RESO 2.0 feeds (TRREB and others) under signed data-access agreements. Each market is handled by a dedicated jurisdiction adapter, so one regulator's rules never leak into another.

How compliance is enforced

Compliance is enforced in code, not policy. In Dubai, a listing cannot be published without a valid Trakheesi permit — the permit gate runs before the listing ever goes live. In Ontario, VOW display rules, the broker–consumer confirmation window, and field-level access (DLA / IDX / VOW) are applied per board agreement. Every regulated action writes an immutable, seven-year audit-log entry.

How your data is secured

Every brokerage's data is isolated at the database layer with Postgres row-level security plus an application-level tenant scope — a query for one brokerage can never read another's rows. Personal data such as emails, phone numbers and government IDs is encrypted at rest, and logs are scrubbed of personal information before they are written. Data is hosted in a single AWS region with encrypted backups.

How listings are ranked and displayed

PropVista does not sell ranking. Search and match results are ordered by relevance to the buyer's stated requirements — budget, location, property type and timing — never by who paid more. Where a regulator requires specific attribution or disclosure (for example TRREB listing attribution), it is shown exactly as mandated.

Frequently asked questions

Which markets does PropVista support?: PropVista launches with the United Arab Emirates (Dubai Land Department / RERA / Trakheesi) and Canada (TRREB / RECO / Tarion). The jurisdiction-adapter architecture lets new markets be added without changing the core platform.
Does PropVista scrape Bayut, Property Finder or Dubizzle?: No. PropVista does not scrape any portal. UAE secondary inventory comes from direct partner-agency feeds and free, permit-validated seller listings; off-plan data comes from official open-data sources.
How is each brokerage's data kept separate?: Tenant isolation is enforced at the database level using Postgres row-level security, backed by an application-level tenant scope. A request authenticated for one brokerage cannot read or write another brokerage's records.
Is PropVista compliant with Dubai's Trakheesi rules?: Yes. A listing cannot be published in Dubai without a valid Trakheesi permit number. The permit is validated by a compliance gate before the listing is allowed to go live, and permit expiry is monitored.
How is TRREB and VOW compliance handled in Canada?: Canada listings follow board data-access agreements: VOW display requires a registered consumer relationship and a confirmation window, and field-level access (DLA / IDX / VOW / BBO) is gated per the operating brokerage's membership.
Where is PropVista data hosted?: PropVista runs in a single AWS region with multi-AZ redundancy and encrypted backups. Data residency is kept in one region by design until customer demand justifies a residency split.