Security

Business data is scoped in the API and database row-level security. Team permissions and business-scoped API keys govern access; owner-only settings remain separate.

Passwords use scrypt hashes. Dashboard sessions expire after seven days. Provider credentials entered through setup are encrypted with the deployment’s private vault key.

Optional recordings require an authenticated, authorised request. They are not served as permanent public audio URLs. Audio access checks include the call, business and retention expiry.

Protecting server disks, database backups and downloaded data remains the operator’s responsibility. Audio expiry is not a promise of erasure from every backup or copy.

The shared business core checks action permissions and required confirmations. Call records expose action outcomes, citations and handoff state so an operator can investigate what happened.

These controls reduce risk; they do not guarantee that an AI answer is always correct or that a provider is always available.

The supplied installation uses HTTPS and separate database roles. Operators manage DNS, host access, updates, monitoring, backups and recovery testing.

Provider region settings must match actual account entitlements. They do not establish end-to-end data residency by themselves. See the provider overview.

Email hello@avrosh.com with the affected version, a concise description and reproduction steps. Do not include live credentials, private call recordings or other customers’ data.