openbroker
Security
Brokerages trust openbroker with their contacts, deals, calls and texts. Here's how we keep them safe.
Last updated: November 18, 2026
Each brokerage is walled off
openbroker hosts many brokerages, and the database itself keeps each one's records apart. Every request and every background job works inside a single brokerage, so a mistake returns nothing rather than another brokerage's data. Brokerages that compete in the same town never see each other's contacts, deals or homes.
People see what their role allows
- Brokers see and change everything, and manage settings, phone numbers, the team and API keys.
- Office admins see and edit every record and assign owners, without settings or keys.
- Agents see only the contacts, deals, calls and texts they own.
A record outside someone's view reads as "not found", so its existence can't even be confirmed. The same rules apply everywhere: in the app, the iPhone app, the API and connected AI assistants.
A record that can't be rewritten
Every change is recorded: who made it, when, and what it was before and after, including changes made through the API, an AI assistant or an automation. The history can only be added to; it can't be edited or deleted. Contacts, deals and homes are archived rather than deleted, and people who leave are deactivated, so nothing disappears.
Support only when you let us in
Our team can't open a brokerage's records unless one of its brokers lets us in, for 48 hours or a week. Brokers see a banner while access is on and can end it at any time, and every change we make shows in the history under our name. The only exception is setting up a new brokerage, before it goes live.
Sign-in, keys and connected apps
- Passwords are never stored in readable form, and people can also sign in with a one-time link sent by email.
- API keys are stored hashed, can be limited to reading, and act with their creator's current role.
- AI assistants such as Claude and ChatGPT connect through each person's own sign-in and approval, with that person's role. Anyone can disconnect one at any time, and it stops at once.
- Tokens for connected services are stored encrypted.
- Webhooks we send are signed, so your tools can check they came from us.
Hosting
openbroker runs on servers in the United States. All traffic to openbroker is encrypted with HTTPS.
AI and your data
openbroker sends call transcripts, texts and forwarded closing mail to AI models to write recaps and suggestions.
- We only use AI providers that don't collect or train on what they're sent.
- Before a model reads closing mail, openbroker removes Social Security, account, routing and card numbers. Wire instructions and bank statements are never sent to a model at all.
- Forwarded emails and their attachments are read once and not kept. The deal keeps a summary.
- A broker can turn AI off for the whole brokerage, and separately choose whether scanned documents are read.
- AI only reads what the person it's working for is allowed to see.
Calls and texts
Texts only go to people who agreed to them, and opt-outs (STOP and the like) hold across the whole brokerage. A recording notice can play at the start of calls; it's on for brokerages in states where everyone on a call must agree to recording. Agents call leads from the brokerage's numbers, so they never give out their own.
Your data, your exit
The brokerage's data is the brokerage's. Brokers can download everything at any time: records, history, calls, texts and emails. If a brokerage cancels, its brokers have 90 days to download it, and then we delete its data.
Reporting a security issue
If you think you've found a security problem, please email hello@openbroker.com with the details. Please don't access or change data that isn't yours while looking.