Protected Account Access
Every app page and server operation checks authentication. Project membership and database row-level security restrict access to saved agents, chats, workflows and reports.

Security at Taken
Your accounts. Your data. Your control.
Taken is designed around protected account access, project isolation and controlled AI actions. we're building technology that puts users in control of their automation.
Overview
Taken combines financial agents and workflows with project access controls, protected API credentials and independent execution permissions.
Every app page and server operation checks authentication. Project membership and database row-level security restrict access to saved agents, chats, workflows and reports.
Project-scoped records are checked on the server and in the database. Switching projects loads that project’s data; account-wide connections remain permission-controlled.
Connected account keys are encrypted on the server. They are not included in model prompts or returned to the app.
Models interpret instructions; verified tools and independent permission checks control execution. Live order submission remains disabled.
Cancel an agent run or control a workflow from its saved execution. Approval requests link to the exact action under review.
Sessions and Inbox preserve real results, failures, timestamps and pending actions. Queued work is never presented as completed.
Standards
We use these frameworks to guide how Taken is built. Taken has not been audited or certified against SOC 2, ISO 27001 or AIUC-1, and this is not a claim of GDPR compliance.
Saved agents, chats, workflows and reports stay within their project’s access boundary.
Access boundary
Financial tools run through explicit capabilities and permissions. Model reasoning cannot bypass execution checks.
Steps that fail the check are refused — the AI can't override it.
Taken is designed to keep infrastructure API credentials in secure server-side environments rather than exposing them through the public application.
Public app
no secrets
Server-side secrets
Review progress in Sessions and Inbox. Open the originating execution to inspect results or take action.
Trading
Safeguards reduce risk — they can't remove it. Trading always carries the risk of loss.
Server-side membership checks and database policies protect project records.
Accounts are selected explicitly. Tool availability and financial scope are checked before execution.
External connected-app changes require the existing approval flow. A model response or Inbox notification cannot grant authorization.
Review genuine task, workflow and tool records in Sessions, Chat and Inbox.
Real brokerage and exchange order submission is disabled. Research, simulation and supported paper-order drafts are distinguished from live executions.
Read the Trading Risk Disclosure.
Our technology
Authentication and database with row-level security.
AI models interpret financial instructions and analyze tool results.
Observed IEX and supported crypto market data.
Application hosting and background execution.
Subscription payments and billing.
Third-party trademarks belong to their respective owners. Their inclusion does not imply endorsement. Taken does not hold its providers' security certifications.
Transparency
What we collect, why, and who processes it.
Privacy Policy
Your responsibilities and ours when using Taken.
Terms of Service
The risks of AI-assisted and automated trading.
Trading Risk Disclosure
The browser storage Taken uses and your choices.
Cookie Policy
Found a vulnerability or suspect unauthorized access? Email contact@taken.trade.
Legal, privacy or regulatory notices? Email legal@taken.trade.
FAQ
Built to help you stay in control of your AI-powered workflows.