Your company. Your data. Your rules.
A Digital FTE works with real accounts and real money, so the platform is built around control: isolation by design, permissions on every action, approvals before anything leaves your company, and a log of all of it. This page lists what is enforced, not badges.
Six controls, on every request.
- 01
Tenant isolation
Every record is scoped to your organization. Queries that reach the database carry your organization, always.
- 02
Per-property scoping
Websites, stores and ad accounts are separate properties. One FTE's property never sees another's memory, targets or setup.
- 03
Roles and permissions
Owner, admin, member and custom roles decide who can hire, approve, publish and spend. Every protected action checks a permission.
- 04
Approval gates
Nothing publishes, sends or spends without an approval unless you have granted that autonomy level, and you can take it back.
- 05
Audit trail
Every proposal, approval, publish and token spent is logged with who, what and when.
- 06
Token hard-stop
Work is metered against one organization wallet. At zero the FTEs pause; nothing runs on credit.
Where your data goes, and where it does not.
- In transit
- HTTPS (TLS) between your browser, the platform, and the systems the FTE works in.
- At rest
- Integration credentials and API keys are encrypted before storage, with a key held separately from the data. They never appear in responses or logs.
- Sessions
- Short-lived access tokens with a rotating, httpOnly refresh cookie. The browser never talks to the API directly.
- Model providers
- Work is done through the Claude Agent SDK; you can bring your own provider key. We do not train models on your data.
- Revocation and deletion
- Disconnect any integration from the workspace at any time. Ask privacy@ftes.ai to delete your organization's data.
Found something? Tell us.
Email security@ftes.ai with what you found and how to reproduce it. We read every report, reply, and credit researchers who ask to be credited. Please do not access data that is not yours while testing.
Certifications: none claimed. We publish what we enforce rather than badges; ask us for detail on any control and we will answer in writing.
Security questionnaire? Send it over.
We answer in writing, control by control.