Built to act within
the access you already set.
An assistant that can take actions has to be held to a higher standard than one that only answers. Here is how Mahadrone handles your data, your tools, and your employees' requests.
The permission-awareness guarantee
Mahadrone acts only within the requesting employee's own access.
Every action is checked twice: against the roles your admins set in Mahadrone, and against the employee's own permissions in the connected tool. If an employee could not do something themselves, Mahadrone will not do it for them.
What is stored, and why.
Mahadrone stores what it needs to route requests, keep conversations coherent, and give admins an audit trail. It does not copy entire connected systems.
Requests and replies
The text of a request, the reply given, and the thread it happened in.
So the employee can continue the conversation and admins can review it.
Action records
Which tool a request was routed to, the action taken, and the result.
This is the audit trail.
Connection settings
Which tools are connected, their scopes, and the credentials needed to reach them.
So requests can be routed. Credentials are stored encrypted.
Workspace settings
Roles, groups, enabled actions, and channel restrictions.
So your admins' controls are applied to every request.
How data is protected.
Encryption in transit
Traffic between chat platforms, Mahadrone, and connected tools is encrypted using TLS.
Encryption at rest
Stored requests, action records, and connection credentials are encrypted at rest.
Retention you set
Request and action logs are kept for the retention period configured for your workspace, then deleted.
Scoped connections
Each tool connection is limited to the scopes an admin approves, shown in plain language.
Revocable access
Disconnecting a tool stops routing to it immediately and removes its stored credentials.
Restricted staff access
Access to customer workspaces by our team is limited to support you request.
Access scope per connection, in plain words.
For every connected tool, the admin console lists what Mahadrone can read and what it can change. Knowledge connections are read only. Task connections can only perform the actions an admin has switched on.
Compliance, stated honestly.
We only claim certifications we hold. For your vendor review, talk to us and we will share our current security documentation, answer your questionnaire, and walk through how Mahadrone fits your policies.
Have a security review to run?
Share your security questionnaire with us
Sign upPrefer a walkthrough first? Talk to us