Security: what we do with your company's data, and what we never do
SecurityA brokerage's chats are its business. Brokbase is built so that one company can never see another, so that nothing leaves a company without a person confirming it, and so that a document from a stranger cannot harm the system that reads it.
Isolation
- Every record carries the company it belongs to; the database enforces the boundary with row-level security, and the application talks to it through narrow, audited functions rather than direct table access.
- Inside a company the owner chooses between shared records and private mode, where each broker sees only their own.
- Platform administration uses separate credentials and a separate audit trail.
Outgoing messages
The system never sends a message to a client on its own. Answers, reminders and documents are prepared and shown to the broker; only a confirmation in the workspace or the app sends them, and an uncertain send is never retried automatically.
Documents and models
Files are archived once with a checksum, parsed in an isolated process with time and memory limits, and read by models that may only publish a value they can quote from a page. Chat messages are never cached across companies; identical documents are recognised by checksum only.
Where and how long
Data lives in Azure UAE North (Dubai) with daily backups. Sign-in is by one-time email code, Google or Apple; there are no passwords to leak. Retention and deletion are described in the privacy policy.
Reporting a problem
Write to [email protected]. We acknowledge within one working day and do not pursue researchers who report in good faith.