Trust & Security · RealViu

Four commitments

What we promise before you move a single contact.

Your data is yours

Contacts, enquiries, saved searches and content belong to your brokerage. We never sell them, never market to your clients, and never use one customer's data to benefit another.

You can leave with it

Export contacts, listings content and site pages at any time, not just at the end. If you cancel, your export window stays open for 30 days.

Least access, always

Staff access to customer data is limited to what support requires, is logged, and is granted case by case rather than standing open. Our own admin dashboard isn't hosted on any publicly reachable server. It's on premises, behind multi-factor authentication.

We'll tell you quickly

If a breach creates a real risk of harm we notify affected customers and the Privacy Commissioner of Canada, as PIPEDA requires. Target notice to you within 72 hours of confirming it.

The stack

What the platform actually runs on.

We don't resell someone else's platform under our name. These are the systems your brokerage's site, portals and data sit on: what each one does, and where it runs. The table below lists exactly what data each one touches.

Amazon Web Services

Compute, email delivery through SES, monitoring and encrypted backups. The ground everything else stands on.

Canada · ca-central-1

Supabase

Your brokerage database. One writable primary with replicas in two further regions and automated failover.

Canada primary · 2 replicas

Redis Enterprise

Caching, sessions and rate limiting, plus the vector store the AI assistant retrieves from. No client records held long-term.

Canada · ca-central-1

Cloudflare

CDN, SSL/TLS on your own custom domain, domain security and bot verification on every form. Traffic metadata only.

Global network

NVIDIA

The GPUs our own trained AI model runs on. We host it ourselves. Conversations are never used to train any public model.

Our own infrastructure · Canada

PropTX

Board listing technology, enabled only where your brokerage holds the data agreement. Listing data only, no client records.

Canada

Twilio

One-time passcodes by SMS, and the messaging channel behind the AI Lead Engine. Phone numbers only, used to deliver the message.

US · global

Google Cloud

Sign in with Google for brokerage accounts. Name, email and profile photo only. No Gmail, contacts or Drive access.

US · global

Backblaze B2

File storage: a public bucket for the media your visitors see, and a private bucket that is never publicly reachable.

US

Stripe

Payments and subscriptions. Card numbers never reach our systems. Stripe is a PCI DSS Level 1 provider.

US · global

DDF® · CREA

REALTOR.ca listing distribution, switched on only where your brokerage is authorised for it. Listing data only, no client records.

Canada

SSL/TLS everywhere

Every connection encrypted in transit, including your own custom domain. Certificates are issued and renewed automatically. Nothing for you to track.

All traffic · not a vendor

Product names and logos are the trademarks of their respective owners, shown to identify the services we use. Their appearance here does not imply any partnership with, or endorsement by, those companies.

Where your data lives

Every sub-processor, and what it touches.

Sub-processors are the companies that help us run the platform. Any one of them can hold or move your data, so you're entitled to the list. We give 30 days' notice before adding one. The full detail is in our Data Processing Agreement.

Provider	What it does	Data it touches	Region
Amazon Web Services	Compute, email delivery (SES), monitoring (CloudWatch), internal backups (S3)	All platform data	Canada (ca-central-1)
Supabase	Database, redundant across multiple regions	All platform data	Multi-region, may include outside Canada
Redis Enterprise	Caching, session state and rate limiting	No client records stored long-term	Canada (ca-central-1)
Backblaze B2	File storage: a public bucket for content served to visitors, a private bucket that's never publicly accessible	Uploaded files and media	US
Stripe	Payments and subscriptions	Billing contact and card data (we never see card numbers)	US / global
Cloudflare	CDN, SSL/TLS, domain security, bot verification on our forms	Traffic metadata only, no client records	Global network
Google	Sign in with Google authentication	Name, email and profile photo only. No Gmail, contacts or Drive access	US / global
Twilio	One-time passcode delivery by SMS	Phone number, used only to deliver the code	US / global
Repliers	Listing data delivery under your board licence	Listing data only, no client records	Canada
In-house AI model	Powers the AI assistant, where enabled. Fine-tuned on OpenAI's technology, run on our own infrastructure	Conversation content sent to the assistant; never used to train any public model	Canada (our infrastructure)
Google Analytics & Tag Manager	Site analytics on our own marketing site, and the tag container that loads it. Set only after a visitor accepts cookies, denied by default	Pages viewed and actions taken on realviu.com, plus a cookie identifier. No brokerage or client records	US / global

Where a provider operates outside Canada, foreign authorities may in some circumstances compel access. We use contractual protections and keep the list above current so you can make your own judgment.

How your data moves

Every hop, every gate, drawn as it actually runs.

Pick a flow. The map lights up the servers involved and animates the data moving between them. Listing data, AI, email, lead automation and sign-in each take a different route, and each has its own gate.

Swipe the map sideways to see every hop →

Data moving out / forwardReply, check or encrypted writeGate or processing step

Listing data

MLS listings only reach a site whose brokerage is licensed for that board, enforced twice, in two different places.

Repliers delivers MLS IDX and sold data to RealViu.
The licence gate admits only the boards your brokerage has a data agreement for.
The API server asks the database to confirm. Approved boards are stored there too, so nothing can leak by a second route.
The API returns to the frontend server, which renders your site.
Your visitor's browser gets the page, over TLS, on your domain.

AI Assistant

Our own model, on our own GPUs. Redis holds vectors of your content, never listing data, and nothing is sent to a public model.

A visitor asks a question in the assistant on your site; the frontend server receives it.
The frontend hands it to our self-hosted GPU running RealViu's own trained model.
The model retrieves context (RAG) from Redis Enterprise, which continuously vectors your content, not listing data.
The answer returns to the frontend, which sanitizes it before anything is shown.
The reply lands in the visitor's browser.

Database

Primary–replica architecture: one writable primary in Canada, replicas in two more regions, automated failover.

Every write goes to the single primary in Canada.
Changes replicate to two standby replicas in other regions.
If the primary fails, failover is automatic. A replica is promoted.
All API keys and customer keys are encrypted at the database level. Nothing is stored raw.
The auth server and API server are the only paths in. No direct public access to the database.

Email

White-labelled sending on your verified domain, with delivery stats flowing back into your portal.

Amazon SES verifies your brokerage domain, so mail leaves as you@yourdomain.
Listing alerts and Marketing Centre campaigns are sent by the API through SES.
SES delivers to your clients, agents and brokerage.
An AWS event caller returns opens, clicks, rejections and unsubscribes to the API.
Those stats appear in your portal, and unsubscribes are honoured automatically.

Automated AI Lead Engine

Its own server. It works over SMS, calls (coming soon) and email, to your brokerage, your agents and their clients, and only fires triggers you designed.

Inbound messages arrive via Twilio (SMS) and IMAP (email).
The Lead Engine server sends the conversation for AI processing on our GPU, using Redis for retrieval.
It checks the main database through the API: the lead, the agent, and the flow your brokerage or agent designed.
Only approved triggers fire: an SMS or call via Twilio, an email via SES, a notification to the agent's portal.
Every step is logged against the lead so the brokerage sees it.

Sign-in

A dedicated auth server. Google sign-in for brokerage customers, Twilio OTP for phone verification, credentials never stored raw.

A user signs in on your site; the frontend passes it to the auth server.
Brokerage customers can use Sign in with Google. We receive name, email and photo only.
Phone verification sends a one-time code through Twilio.
The auth server confirms against the database, where secrets are encrypted at rest.
A session is issued back to the browser, scoped to that brokerage's tenant.

How the platform is secured

Six controls, stated plainly.

Every plan is fully white-labelled and every brokerage is isolated. These are the controls behind that, without the marketing gloss.

Encryption

TLS on every connection, including your custom domain. Data encrypted at rest by the hosting platform.

Tenant isolation

Every brokerage runs on its own subdomain with scoped access. One customer cannot see another's contacts, listings or content.

Access control

Roles for brokerage admins and agents. Staff access requires named accounts with multi-factor authentication.

Backups

Automated backups, rolled off within 35 days, with restores tested quarterly. A backup nobody has restored is a hope, not a backup.

Email authentication

SPF, DKIM and DMARC configured on your domain, so your alerts reach inboxes and your brand can't be spoofed easily.

Payments

Card data is handled entirely by Stripe, a PCI DSS Level 1 provider. Card numbers never reach our systems.

Report a vulnerability

Email support@realviu.com. We acknowledge within one business day and will not pursue researchers who report in good faith and don't access customer data.

Privacy requests

Access, correction or deletion: support@realviu.com. We respond within 30 days.

Incidents

A public status page is on the roadmap. Until then, outages and incidents are emailed directly to brokerage admins.

Last updated August 2026. This page is reviewed as our infrastructure and practices change.

Your brokerage's data, and how we look after it.

What we promise before you move a single contact.

What the platform actually runs on.

Every sub-processor, and what it touches.

Every hop, every gate, drawn as it actually runs.

Listing data

AI Assistant

Database

Email

Automated AI Lead Engine

Sign-in

Six controls, stated plainly.

We'll complete your questionnaire and walk your IT contact through it.