Workspace isolation
Teams, agents, tasks, and chats are scoped to your workspace. Role-based collaboration controls who can edit agents or invite guests.
Trust center
Security & compliance
Digio is built for teams that need clear boundaries: isolated workspaces, controlled API access, and transparent data flows to LLM providers—with GDPR-ready policies in our legal center.
Workspace isolation
API keys
GDPR-ready
Trust snapshot · pilot
Illustrative procurement checklist—not a certification badge.
In the product
Boundaries you can see in the workspace
Isolation is not a marketing slide—roles, guests, and API keys are managed where your team already works, beside agents and tasks.
Acme workspace · members
Workflow
Run a security-minded pilot
Procurement teams usually validate Digio in three passes—policies, boundaries, then a limited production pilot.
-
Review policies in-product
Open Privacy, Terms, and Cookie policies from the app—no PDF hunt across email threads.
-
Configure roles & keys
Invite reviewers via collaboration and issue scoped keys on integrations.
-
Pilot one use case
Clone a playbook from templates, run real tasks, and trace model flows on Digio Tokens.
Pillars
What we secure
Six areas buyers ask about first—isolation, storage, API access, model routing, legal, and billing auditability.
Data storage
Account, billing, and workspace metadata live in Digio infrastructure. Task notes and chat history stay tied to your team—not mixed across customers.
API keys & Public API
Integrations use revocable API keys with scoped access. The Agent API exposes catalog and usage tools without exposing other workspaces.
LLM providers
Agent prompts and completions go to the model provider you enable. BYOM and GPU routes to your endpoints when configured.
GDPR & policies
Privacy, Terms, Cookie, and Licenses policies are available in-product. Enterprise buyers can request a DPA via your account contact.
Billing transparency
Wallet debits map to model usage with descriptions in your ledger—see Digio Tokens for rates and estimator.
Data flow
Where your content travels
A typical agent Run stays inside your workspace boundary until you explicitly connect external systems or models.
Your workspace
Tasks, chats, files, and agent config—scoped to your team.
Digio orchestration
Coordinator routes Runs, applies skills, logs debits.
Model provider
Prompt + completion per your enabled model or BYOM endpoint.
Integrations (optional)
Slack, CRM, webhooks—only when you connect them.
Procurement
What enterprise buyers ask
Straight answers you can paste into security questionnaires—then validate in a pilot workspace.
Multi-tenant isolation?
Each customer workspace is logically separated—agents, tasks, chats, and billing do not cross tenant boundaries.
Who can invite users?
Owners and editors manage membership; guests can be limited to specific boards via collaboration settings.
Subprocessors for AI?
Model providers you enable (e.g. OpenAI, Anthropic, Google) process prompts for inference—you control which models are on.
Audit trail for spend?
Wallet ledger entries tie Runs to USD debits—export context from your workspace and token history.
Compare
Workspace security vs. chat-only tabs
Digio is designed for ongoing agent teams—not disposable browser chats with unclear data retention.
Scoped workspaces
Agents, tasks, and history belong to your team workspace—not a shared consumer account.
Roles & guests
Reviewers and clients get explicit permissions—not a single shared login.
Revocable API keys
Automation connects with scoped keys—not pasted passwords in scripts.
Tips
Pass security review faster
Give procurement something to click—policies, roles, and a real pilot beat generic AI assurances.
-
Open Privacy and Terms from the hero buttons—same text users see in-app.
-
Invite legal as a reviewer before agents touch client data.
-
Rotate integration keys after the pilot—issue staging vs. production scopes.
-
Run one function from solutions—prove isolation with real tasks, not slides.
Connected
Validate trust in the product
Security pages are the map—these surfaces are where buyers verify controls during a pilot.
Explore
Related pages
Billing, collaboration, and integrations beside this trust center.
Questions for procurement?
Review our legal policies in-app, then run a pilot workspace with your security checklist.