DocsReference
Security and access
The browser, the server and the database each have a different job. That separation protects the workspace.
By the Callaroo team. Updated November 2026
Callaroo has a web dashboard and a call service that handles calls. The dashboard reads business data through the signed-in account. The call service holds the phone company and voice service keys. Service keys are not sent to the browser.
Swipe the diagram sideways to see the full flow.
The browser talks to the dashboard server. The server talks to the database and the outside services. The browser never receives a service key.
One workspace at a time
Every record belongs to one workspace. The database checks the workspace before it returns a call, order, booking, message or menu item. A request for another workspace returns nothing, even if the page asks for it. The page also checks the role, but the database makes the final check.
- The workspace comes from the signed-in account, not from a number the assistant supplies.
- A caller on the phone cannot read another customer's order or the shop totals.
- A member of another workspace cannot open your records by guessing a code.
- Setup work such as number provisioning and billing runs on the server, not in the browser.
Card data
- Stripe handles the card number, expiry date and security code.
- Callaroo keeps the plan, invoice status, card brand and the last four digits.
- The assistant has no payment tool and cannot take a card payment for food or services.
- Never send a card number, a password or a private sign-in link in a support message.
Calls and messages
- Automatic notices from the phone company are checked before they are used.
- A message is not called delivered until the phone company reports delivery.
- A STOP reply is recorded and blocks later sends until the customer sends START.
- Recordings are available only when recording is enabled at the phone company and workspace storage is configured.
- Playback links are short lived and requested by a signed-in member. They are not public links.
What owners should do
Give each person their own account and the lowest role that lets them do the job.
Remove access on the day someone leaves.
Keep the owner email and password secure.
Review staff access at least once a month.
Do not paste card numbers, passwords or private sign-in links into a note or a support email.
The public Security page describes the controls in the code today. We do not claim a third party security certification that we do not hold.
If you suspect a problem
Contact support with the workspace name, what you saw and the time it happened. Do not test another business's data and do not run a disruptive test on a live number. If a person is at risk, contact the emergency services first.