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.
Sandboxed execution
Every workflow execution runs inside short-lived compute boundaries, with additional isolation for code-execution steps.
Trustless credentials
Agent code calls tools through brokered IDs. Raw OAuth tokens and API keys never enter the sandbox.
Access control
Workspace data is scoped by
workspace_id, backed by role checks and invite-gated onboarding.Infrastructure hardening
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.1
Ephemeral execution containers
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.
2
Isolated code sandboxes
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.
3
Restricted execution namespace
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.
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 toworkspace_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.- Agent code requests an authorized tool action using an internal tool identifier and structured parameters.
- The routing service resolves the tool ID to provider configuration and credential references, never raw secrets.
- 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.
- 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.
Read tools
Are scoped to read-only operations. By default, read tools are allowed unless policy overrides require approval or block them.
Write tools
Can require explicit human approval before actions such as sending email or updating records proceed.
Audit trail
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 aworkspace_id foreign key, and protected data access is scoped through that workspace boundary.
Role Hierarchy
Every protected endpoint performs two checks: membership in the target workspace, then role-level permission for the requested operation.
Invite-gated onboarding
New users cannot access protected workspace resources until invited by an Admin or Owner. Invitations use non-guessable, time-limited tokens.
Credential visibility
Credentials are private by default. Workspace sharing is opt-in and enforced at every credential access point.
API token security
dex_-prefixed tokens are hashed before storage, scoped to specific permissions, and tracked by last-used timestamp.Public agent sharing
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.Encryption
Credentials are encrypted at rest with AES-256-GCM. Production database connections enforce TLS, and service-to-service calls use HTTPS.
Container hardening
Production containers use minimized images, non-root users, health checks, and path traversal protections.
Deployment safety
Blue-green deployments validate health before traffic switches, with automatic rollback and graceful connection draining.
Rate limiting and logging
Distributed rate limiting protects public surfaces. Structured logs avoid credential values and record UUIDs plus metadata.
Security Review Clarifications
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. 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
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.Processing role
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.
Service scope
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.
Personal data categories
Standard processing covers customer end users or customers, including user activity and analysis data such as device information, IP address, and location information.
Special category data
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.
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.No model training
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.
No sale or sharing
Where CCPA applies, Decisional does not sell or share Personal Data provided by the customer.
Limited use
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.
Instruction-bound processing
Processing follows the customer’s documented instructions, service configuration, the agreement, and any additional written instructions acknowledged by Decisional.
Security Incidents, Deletion, and Review
Security incident response
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.
Deletion
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.
Security due diligence
Decisional responds to reasonable written security, privacy, due diligence, and audit questionnaire requests according to the DPA and applicable confidentiality obligations.
Security reports
Where available and appropriate, Decisional provides security report summaries or additional information under confidentiality so customers can verify security controls.
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. 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.
FAQ
What is the Security Policy referenced by the DPA?
What is the Security Policy referenced by the DPA?
This page is Decisional’s Security Policy for the DPA and is available at 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.
Do you have a SOC 2 report or trust center?
Do you have a SOC 2 report or trust center?
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. Decisional can provide additional security due diligence responses under the applicable agreement and confidentiality obligations.
Where are access tokens and integration credentials stored?
Where are access tokens and integration credentials stored?
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.
Are credentials encrypted?
Are credentials encrypted?
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.
Will our data be used to train AI models?
Will our data be used to 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.
Who are Decisional's subprocessors?
Who are Decisional's subprocessors?
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.
Do all subprocessors receive Customer Personal Data?
Do all subprocessors receive Customer Personal Data?
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.
Can we object to new subprocessors?
Can we object to new subprocessors?
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.
Can we object to material processing changes?
Can we object to material processing changes?
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.
How quickly will Decisional delete Customer Data?
How quickly will Decisional delete Customer Data?
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.
Does Decisional process special category data?
Does Decisional process special category data?
The standard DPA does not contemplate processing GDPR Article 9 special category data unless separately agreed in writing.
How quickly does Decisional notify customers of a Security Incident?
How quickly does Decisional notify customers of a Security Incident?
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.
How are international transfers handled?
How are international transfers handled?
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.
Who should we contact for compliance review?
Who should we contact for compliance review?
Contact founders@decisional.com for compliance reviews, security due diligence, subprocessor questions, DPA edits, or security report requests.