> ## Documentation Index
> Fetch the complete documentation index at: https://docs.decisional.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Security Policy
> How Decisional protects agent execution, credentials, workspace data, production infrastructure, and customer data processing.
Decisional agents execute real code against real business data. The security architecture is built around enforced boundaries: sandboxed execution, credential isolation, workspace-scoped access control, and hardened production infrastructure.
Every control described here is implemented as an architecture-level constraint, not as a best-effort usage policy.
**No AI model training:** Decisional does not use client data, Customer Personal Data, prompts, files, integration records, agent inputs, or agent outputs to train AI models. Decisional also does not permit third-party model providers to train their models on customer data submitted through Decisional.
Every workflow execution runs inside short-lived compute boundaries, with additional isolation for code-execution steps.
Agent code calls tools through brokered IDs. Raw OAuth tokens and API keys never enter the sandbox.
Workspace data is scoped by `workspace_id`, backed by role checks and invite-gated onboarding.
Encryption, container hardening, deployment safety, rate limiting, and structured logging protect production systems.
## Sandboxed Execution
Decisional treats containment as a non-negotiable invariant. Each execution is enclosed by multiple boundaries so a failure in one layer does not propagate beyond it.
Each workflow execution receives its own short-lived runtime, created on demand and destroyed after completion. Runtimes are resource-capped, run without elevated privileges, have no persistent storage, and access platform data only through authenticated API calls.
Code-execution steps run in separate ephemeral compute environments with their own lifecycle. Sandboxes have hard timeouts, are destroyed on completion, and receive execution-scoped identifiers rather than credentials.
Workflow code runs with least-privilege access to authorized service interfaces only. It cannot directly access underlying credentials, platform databases, host infrastructure, or unrelated customer workspaces.
If an execution runtime crashes mid-run, the run resumes from the last checkpoint. Completed nodes are not re-executed, with node-level semantics backed by database checkpoints and durable artifact recovery.
## Trustless Credentials
The core credential guarantee is simple: agent code never sees raw credentials. Credentials are not placed in environment variables, function arguments, logs, or sandbox-visible state.
### Credential Storage
Connected-app access tokens and integration credentials are maintained by Composio, Decisional's integrations provider. Decisional stores brokered references to those credentials, not raw connected-app secrets, and agent code receives tool IDs instead of credentials.
For credentials and secrets Decisional stores directly, values are encrypted at rest with AES-256-GCM authenticated encryption. Key versioning supports rotation without downtime: old keys remain available for decryption, while new encryptions use the current key version.
Credential access is scoped to `workspace_id` and `user_id`, making credentials private by default with explicit sharing controls for team workflows.
### Brokered Proxy Pattern
Tool execution flows through a brokered chain where each layer sees only the minimum information it needs.
```text theme={null}
Agent code -> Routing service -> Composio / credential provider -> External API
tool ID credential refs decrypts in memory executes call
```
1. Agent code requests an authorized tool action using an internal tool identifier and structured parameters.
2. The routing service resolves the tool ID to provider configuration and credential references, never raw secrets.
3. Composio or the relevant credential provider is the decryption point for connected-app calls and holds decrypted material only as needed to execute the outbound call.
4. The provider adapter receives the live credential and executes against the upstream API. Raw connected-app credentials are not serialized into agent state, prompts, run logs, or sandbox-visible storage.
Are scoped to read-only operations. By default, read tools are allowed unless policy overrides require approval or block them.
Can require explicit human approval before actions such as sending email or updating records proceed.
Write approvals are recorded with acting identity, timestamp, run context, and operation metadata.
## Access Control & Multi-Tenancy
Each customer's data is isolated at the workspace layer. Agents, runs, credentials, files, schedules, and related entities carry a `workspace_id` foreign key, and protected data access is scoped through that workspace boundary.
### Role Hierarchy
| Role | View | Edit / Run | Manage Members | Delete Workspace |
| ------ | ---- | ---------- | -------------- | ---------------- |
| Viewer | Yes | No | No | No |
| Editor | Yes | Yes | No | No |
| Admin | Yes | Yes | Yes | No |
| Owner | Yes | Yes | Yes | Yes |
Every protected endpoint performs two checks: membership in the target workspace, then role-level permission for the requested operation.
New users cannot access protected workspace resources until invited by an Admin or Owner. Invitations use non-guessable, time-limited tokens.
Credentials are private by default. Workspace sharing is opt-in and enforced at every credential access point.
`dex_`-prefixed tokens are hashed before storage, scoped to specific permissions, and tracked by last-used timestamp.
Agents are private by default. Public run surfaces remain separated from protected workspace endpoints and are still governed by agent and tool policy.
## Infrastructure & Compliance
Production infrastructure enforces the lower-level controls that support the agent runtime, credential model, and tenant boundary.
Credentials are encrypted at rest with AES-256-GCM. Production database connections enforce TLS, and service-to-service calls use HTTPS.
Production containers use minimized images, non-root users, health checks, and path traversal protections.
Blue-green deployments validate health before traffic switches, with automatic rollback and graceful connection draining.
Distributed rate limiting protects public surfaces. Structured logs avoid credential values and record UUIDs plus metadata.
### Security Review Clarifications
| Review question | Decisional answer |
| -------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| What is the "Security Policy" referenced by the DPA? | This page is Decisional's Security Policy for the DPA. The public URL is [https://docs.decisional.com/security](https://docs.decisional.com/security). |
| Is there a SOC 2 report or trust center for integration credentials? | Connected-app access tokens and credentials are maintained by Composio, Decisional's integrations provider. Composio's Trust Center, including SOC 2 materials, is available at [https://trust.composio.dev](https://trust.composio.dev). |
| Are credentials encrypted? | Composio maintains integration credentials for connected apps. Decisional does not expose raw connected-app credentials to agents, sandboxes, prompts, logs, or run state. Credentials Decisional stores directly are encrypted at rest with AES-256-GCM, and service communication uses TLS/HTTPS. |
| Where is the current subprocessor list? | The maintained subprocessor list is the source of truth and is available at [Decisional Sub-Processors](https://app.notion.com/p/decisional/Decisional-Sub-Processors-12559fcfa75c80c7a954f514d08694b3). |
| Will customer data train AI models? | No. Client data, Customer Personal Data, prompts, files, integration records, agent inputs, agent outputs, and customer information are not used to train Decisional or third-party AI models. |
| Can customers object to material processing changes? | Yes. Decisional can add the material-change objection and termination language below to the DPA or customer agreement. |
| Can customers get specific deletion timing? | Yes. Decisional can add the 30-day during-term deletion timing language below to the DPA or customer agreement. |
### Data Processing Agreement
Decisional supports customer security and privacy reviews through a standard Data Processing Agreement based on the [Common Paper Data Processing Agreement Standard Terms v1.0](https://commonpaper.com/standards/data-processing-agreement/1.0).
The DPA has two parts: the customer-specific Cover Page and the Common Paper DPA Standard Terms. The Cover Page completes the agreement details, including the governing sales agreement, approved subprocessors, provider security contact, restricted transfer details, and the Annex I and Annex II processing information. If a signed DPA or customer agreement differs from this page, the executed agreement controls.
### DPA Clause Map
| DPA clause | What it means for Decisional customers |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cover Page, "Using this DPA" | The Cover Page controls if it conflicts with the standard terms. Capitalized terms are defined by the Cover Page, the DPA Standard Terms, or the customer agreement. |
| Cover Page, Annex II | Technical and organizational security measures are tied to the Security Policy referenced by the agreement. This page summarizes those controls. |
| Cover Page, Service Provider Relationship | Where CCPA applies, Decisional acts as a service provider for a limited and specified business purpose. Decisional does not sell or share Personal Data provided by the customer and does not retain, use, or disclose it except as needed to provide the service, as stated in the agreement, or as permitted by applicable data protection law. |
| Sections 1.1 and 1.2 | Decisional is a Processor when the customer is a Controller, and a Subprocessor when the customer is a Processor. |
| Sections 2.2 and 2.3 | Decisional processes Customer Personal Data only to provide and maintain the service, as configured through customer use of the service, as documented in the agreement, or under other written customer instructions acknowledged by Decisional. |
| Section 2.3 addendum | Customers may request a right to object to material service updates that increase privacy, security, or compliance risk. Pending resolution, Decisional will not implement the change for that Customer Data if the addendum language below is included in the agreement. |
| Section 2.6 | Subprocessors must be approved, listed with identity, country, and processing tasks, and bound by written obligations that limit access and use to the subcontracted service obligations. |
| Section 3 | Restricted transfers are supported through appropriate safeguards, including EEA SCCs, the UK Addendum, and Swiss transfer adjustments where applicable. |
| Section 4 | Security Incident notice is provided without undue delay where feasible and no later than 72 hours after Decisional becomes aware of the incident. |
| Sections 5.1 through 5.3 | Customers can request information reasonably necessary to verify DPA compliance, including security reports where available and reasonable written security due diligence requests. DPA compliance records are maintained for 3 years after the DPA ends. |
| Sections 6.1 and 6.2 | Decisional assists with third-party inquiries, data subject requests, DPIAs, and DTIAs where required by applicable data protection law and consistent with the DPA. |
| Sections 7.1 and 7.2 | Customers can delete Customer Personal Data through service functionality. After DPA expiration, Decisional returns or deletes Customer Personal Data at customer instruction unless further retention is required or authorized by law. Customers may request the 30-day during-term deletion timing language below. |
| Section 9 | If documents conflict, the order of precedence is: EEA SCCs or UK Addendum, then the DPA, then the customer agreement. |
| Section 10 | DPA obligations continue until the customer stops transferring Customer Personal Data to Decisional and Decisional stops processing it. |
### Available DPA Addendum Language
Decisional can include the following language in a customer DPA or agreement when requested.
**Material processing changes**
Where Decisional updates the Service and, by notice to Customer, changes the categories of data subjects, personal data, special category data, frequency of transfer, nature or purpose of processing, or duration of processing, Customer shall have the right to object to any such change that materially increases privacy, security, or compliance risk to Customer or to data subjects. Customer must raise such objection in writing within thirty (30) days of receiving Decisional's notice. The parties shall negotiate in good faith to resolve the objection within thirty (30) days. If the parties are unable to resolve the objection within that period, Customer may terminate the affected Service (or this Agreement in whole) without penalty upon written notice, and Decisional shall return or delete the affected Customer Data in accordance with the Deletion and Return of Customer Data section. Pending resolution, Decisional shall not implement the change with respect to Customer Data.
**During-term deletion timing**
During the Term, Decisional shall delete Customer Data no later than thirty (30) days after such data is no longer required for the purpose for which it was processed, or earlier upon Customer's written instruction, except to the extent retention is required by applicable law.
Where the customer is a Controller, Decisional acts as a Processor for Customer Personal Data. Where the customer is a Processor, Decisional acts as a Subprocessor.
The standard service scope covers Decisional's hosted SaaS product, including the web app, AI agents, APIs, integrations, workflow automation features, Dex, and associated services.
Standard processing covers customer end users or customers, including user activity and analysis data such as device information, IP address, and location information.
The standard DPA does not contemplate processing GDPR Article 9 special category data unless separately agreed in writing.
### Processing Activities
Decisional processes Customer Personal Data only to provide, maintain, secure, and improve the contracted service according to customer instructions and the applicable agreement. The standard cover page describes the following processing details.
| Activity | Examples |
| --------------- | ----------------------------------------------------------------------------------------------------------- |
| Receiving data | Collection, access, retrieval, recording, and data entry |
| Holding data | Storage, organization, and structuring |
| Using data | Analysis, consultation, testing, automated decision-making, and profiling as configured through the service |
| Protecting data | Access restrictions, encryption, monitoring, and security testing |
For standard configurations, data transfer frequency is batch sync every 24 hours or as otherwise agreed with the customer. Processing continues for as long as needed to provide the service, follow documented customer instructions, or comply with applicable law.
### International Transfers
The standard DPA includes transfer mechanics for restricted transfers under GDPR and UK GDPR. Where required, the EEA Standard Contractual Clauses and UK Addendum are incorporated through the DPA and completed by the customer-specific Cover Page.
The standard Cover Page identifies the Netherlands for EEA transfers and England and Wales for UK transfers. Customer-specific agreements may change those details.
### Customer Data Use Limits
Decisional's standard DPA and service provider terms limit how Customer Personal Data can be used.
Client data, Customer Personal Data, prompts, files, integration records, agent inputs, and agent outputs are not used to train Decisional or third-party AI models.
Where CCPA applies, Decisional does not sell or share Personal Data provided by the customer.
Decisional does not retain, use, or disclose Personal Data except as necessary to provide the service, as stated in the agreement, or as permitted by applicable data protection law.
Processing follows the customer's documented instructions, service configuration, the agreement, and any additional written instructions acknowledged by Decisional.
### Security Incidents, Deletion, and Review
Upon becoming aware of a Security Incident, Decisional notifies the customer without undue delay when feasible and no later than 72 hours after awareness, then provides timely information and takes reasonable containment and investigation steps.
Customers can delete Customer Personal Data through service functionality. After DPA expiration, Decisional returns or deletes covered data at the customer's instruction unless further retention is required or authorized by applicable law.
Decisional responds to reasonable written security, privacy, due diligence, and audit questionnaire requests according to the DPA and applicable confidentiality obligations.
Where available and appropriate, Decisional provides security report summaries or additional information under confidentiality so customers can verify security controls.
For compliance reviews, contact [founders@decisional.com](mailto:founders@decisional.com).
### Sub-Processors
Decisional uses vetted sub-processors for categories such as cloud infrastructure, authentication, model execution, sandboxed code execution, integration connectivity, observability, analytics, and payments.
Approved subprocessors are listed in the applicable DPA cover page or maintained subprocessor list so vendor names, locations, and processing purposes can stay accurate as the service evolves. The maintained Notion list is the source of truth: [Decisional Sub-Processors](https://app.notion.com/p/decisional/Decisional-Sub-Processors-12559fcfa75c80c7a954f514d08694b3).
Under Section 2.6 of the reviewed DPA, Decisional:
* provides advance written notice of intended subprocessor additions or replacements before beginning use of the new subprocessor;
* gives customers information needed to exercise their objection rights during the advance notice period;
* keeps written agreements requiring subprocessors to access and use Customer Personal Data only as needed for the subcontracted obligations and consistently with the agreement;
* imposes GDPR Article 28-style data protection obligations on subprocessors where GDPR applies;
* shares subprocessor agreements on request where required by the DPA, subject to redactions for confidential information, business secrets, and personal data; and
* remains responsible for subcontracted processing obligations, including subprocessor acts and omissions.
If a customer objects to a new subprocessor, the reviewed DPA provides cure paths such as canceling use of the subprocessor for that customer's data, offering an alternative service path, taking corrective steps, or disabling the affected service feature. If the objection remains unresolved and no commercially feasible alternative exists, the DPA allows termination of the affected subscriptions, order forms, or usage with refund of applicable prepaid fees for unused periods.
## FAQ
This page is Decisional's Security Policy for the DPA and is available at [https://docs.decisional.com/security](https://docs.decisional.com/security). It summarizes Decisional's technical and organizational measures, including sandboxed execution, credential isolation, access control, encryption, subprocessors, incident response, deletion, and DPA commitments.
Connected-app access tokens and credentials are maintained by Composio, Decisional's integrations provider. Composio's Trust Center, including SOC 2 materials, is available at [https://trust.composio.dev](https://trust.composio.dev). Decisional can provide additional security due diligence responses under the applicable agreement and confidentiality obligations.
Connected-app access tokens and integration credentials are maintained by Composio. Decisional stores brokered references to credentials, not raw connected-app secrets, and agent code receives tool IDs instead of credentials. Raw connected-app credentials are not serialized into agent state, prompts, run logs, or sandbox-visible storage.
Composio maintains connected-app credentials for integration calls. For credentials and secrets Decisional stores directly, values are encrypted at rest with AES-256-GCM authenticated encryption. Production database connections enforce TLS, and service-to-service calls use HTTPS.
No. Client data, Customer Personal Data, prompts, files, integration records, agent inputs, agent outputs, and customer information are not used to train Decisional or third-party AI models.
The maintained Notion list is the source of truth for current subprocessors, including provider names, processing activities, locations, and implementation dates. It is available at [Decisional Sub-Processors](https://app.notion.com/p/decisional/Decisional-Sub-Processors-12559fcfa75c80c7a954f514d08694b3).
No. The maintained subprocessor list identifies each provider's role and processing activity. Service providers used only for business operations may receive limited account information and usage data rather than Customer Personal Data.
Yes, subject to the applicable DPA. Under Section 2.6 of the reviewed DPA, Decisional provides advance written notice of intended subprocessor additions or replacements, gives customers information needed to exercise objection rights, and works through the cure paths described in the DPA if a customer objects.
Yes, Decisional can add the material processing change language shown above to the DPA or customer agreement. The clause gives customers 30 days to object to changes that materially increase privacy, security, or compliance risk, requires good-faith negotiation, and allows termination of the affected service if the objection is unresolved.
The reviewed DPA requires deletion through service functionality and return or deletion at DPA expiration at customer instruction unless further retention is required or authorized by law. Decisional can also add the 30-day during-term deletion timing language shown above to the DPA or customer agreement.
The standard DPA does not contemplate processing GDPR Article 9 special category data unless separately agreed in writing.
Under Section 4 of the reviewed DPA, Decisional notifies customers without undue delay where feasible and no later than 72 hours after becoming aware of a Security Incident, then provides timely information and takes reasonable containment and investigation steps.
The standard DPA includes transfer mechanics for restricted transfers under GDPR and UK GDPR. Where required, the EEA Standard Contractual Clauses and UK Addendum are incorporated through the DPA and completed by the customer-specific Cover Page.
Contact [founders@decisional.com](mailto:founders@decisional.com) for compliance reviews, security due diligence, subprocessor questions, DPA edits, or security report requests.