Security and trust
An agent that can query your warehouse, browse your suppliers and send email is only useful if you can trust where it stops. This is how the platform keeps it inside the lines, and what you can check for yourself.
Last reviewed October 2026
Defence in depth
No single control is trusted to hold alone. A request has to pass identity, organization scope, the agent's own permissions and a vault before anything runs, and it leaves a record whatever the outcome.
We design for the day a model is fooled by a hostile web page or message. So limits do not depend on the model behaving: the key is not in reach, the sites are listed, sending is capped and the sandbox is empty.
Organization and person isolation
Ownership and connection decide what a row can be read or changed by, enforced by the database itself. A bug in a page cannot turn into a leak, because the page never had the access in the first place.
Organization A
Organization B
Connected person
Execution
Anything an agent writes and runs, and anything in a tool, executes in a separate isolated service, not in the system that holds your conversations and credentials.
Your data
Retention is written into the system, and several clean-ups run in the database itself so they hold even if another service is down.
The infrastructure providers that process data on our behalf are listed in the Privacy Policy. Text sent to an AI model to produce a reply is processed by the model provider the platform is configured to use.
Controls you hold
Every one of these is enforced by the platform on each action, and none depends on the model choosing to comply.
Nothing is available to an agent until you switch it on. Each tool also has its own switch for connected people.
The browser reaches the sites you list. Logins go in through a form the assistant never reads.
Email goes only to the people you allow, within a daily limit, with delivery status on every message.
You open each group or contact as read, send or both. The gateway re-checks every send, with a daily cap and duplicate protection.
A key can be used only against the hosts you name for it. With none named, it cannot be used in a generic request at all.
When a plan lapses or a balance runs out, the agent pauses. It cannot spend what is not there.
Pausing a connected person stops their access without touching their history.
Messages, status changes, every task step and every model call are recorded with their cost.
Practices
Handled by a dedicated, audited authentication provider with email and Google sign-in. We do not implement our own authentication or store your password in plaintext.
Uses that provider's own consent screen with the standard authorization-code flow and PKCE. We never see or ask for the password of a service you connect.
Processed by Razorpay. A top-up is credited only after a signed confirmation arrives from Razorpay's servers, never on a browser's say-so, so a closed tab cannot create or lose a credit.
Messages read from WhatsApp are handed to the agent as untrusted text, not as instructions, and a send needs both permission on the chat and passing the daily and duplicate checks.
Messages, status changes, task steps and model calls are recorded, so a decision can be traced to the input that caused it.
No certification badges: we would rather not imply any we do not hold. Architecture walkthroughs and security questionnaires are answered directly on request.
Responsible disclosure
If you believe you have found a security issue in Parasync Agents, please report it to team@parasync.in instead of disclosing it publicly.
What helps
We take every report seriously, acknowledge it promptly and keep you updated while we investigate and fix it.