Skip to content

Security built around your firm's records.

Encryption, permissions and deliberate sharing each protect a different part of your workspace.

Encryption in transit and at rest

Connections to the RealtorVault website use HTTPS. The production database uses encryption at rest, and uploaded files are encrypted at rest by Google Cloud Storage.

Offline cached record payloads and queued changes use AES-GCM encryption in your browser with a non-extractable key. Preferences and storage metadata have different treatment.

Authorized application processes can read records to provide the service, and enabled AI workflows process selected inputs. These protections are not end-to-end encryption that prevents RealtorVault from processing your records.

Private firm records and team permissions

Private workspace queries enforce firm isolation at the database level. Server-enforced roles and permissions govern which records and sensitive economics a member can access. Authorized membership in one firm does not grant access to another firm's private records.

Controlled public sharing

You choose which listings to publish. Public listing views exclude private contacts and deal economics. File access uses scoped checks and time-limited links. Revoking access does not retrieve copies someone has already downloaded or forwarded.

AI assistance has limits

AI features are available only where enabled. Proposed facts and summaries need human review against the source. They do not certify legal title, guarantee ownership or provide a land valuation. The Outreach design preview uses fictional data and does not save customer outreach or send messages.

Operations, recovery and requests

Audit records and diagnostic monitoring help investigate failures and access. Recovery, deletion and backup retention have different lifecycles. See the Privacy Policy for providers and data handling, and contact us to report a security concern or ask about controls relevant to your firm.