Security & trust

How Renggo handles your conversations and data.

This page describes controls that exist in the product today. It isn't a list of certifications. If your review needs more, talk to us.

Control and data

You stay in control of every conversation

Clear records, clear handovers and clear rules about data, so your agent works the way your business and your regulators expect.

Route chats to the right person, or transfer calls with a spoken briefing so no one has to ask twice.

Transcripts, the actions taken and the reason each conversation ended, in one log you can export.

Call recording is switched on per agent, only where you decide you need it.

Admins, members and read-only viewers, each scoped to your organisation.

Our data processing agreement and list of sub-processors are available for your review.

Enterprise customers can run their live conversations on an orchestrator reserved for them alone.

Security

The details a security review usually asks about.

Organisation isolation
Every record belongs to an organisation, and every query is scoped to the organisation of the signed-in user, never to an ID supplied by the browser. Live call state is namespaced per organisation.
Role checks
API actions check the user's role before they run.
Encrypted credentials
Keys and credentials you give Renggo, for model providers, Twilio and integrations, are encrypted before they're stored.
Sessions
Sign-in uses short-lived access tokens, with refresh tokens stored hashed. Each live call is authorised by its own short-lived token issued for that session.
Your keys, your carrier
Bring your own model provider keys and your own Twilio account, so usage is billed to, and visible in, accounts you control.
Guarded URL fetching
When Renggo fetches a URL for a knowledge base, it refuses redirects, caps the download size and validates the destination.

Send us your questionnaire or requirements and we'll respond with specifics.