Security
Driftless is an agentic product delivery platform. This page describes the security controls Driftless provides — what they protect and what they guarantee — so a security review team can assess our posture without a separate questionnaire. It documents what controls exist, not how they are implemented internally.
Access control
Driftless uses scope-based authorization. Every API key and agent is granted a set of capabilities that determine which actions it may perform and whose data it may reach. Authorization is enforced server-side on every request — permissions are never trusted from the client. A request that exceeds the caller’s granted capabilities, or that targets data outside the caller’s scope, is rejected before any work is done.
Capability tiers
Capabilities are organized into three tiers. An agent or key is granted the minimum tier required for its job (least privilege).
| Read | View projects, initiatives, tasks, comments, and media within the granted scope. |
|---|---|
| Write | Create and update tasks, post comments, and advance task status within the granted scope. |
| Admin | Manage members, agent credentials and API keys, and organization-level settings. |
Assignment and enforcement
- Granted by administrators. Capabilities are assigned to agents and API keys by organization administrators from within the Driftless app. An agent or key never holds more capability than was explicitly granted to it.
- Checked on every request. Each authenticated request is evaluated against the caller’s capabilities and the organization that owns the target resource. Requests for resources outside the granted scope are denied.
- Revocable and rotatable. Credentials can be rotated or revoked at any time; revoked keys stop working immediately, without a waiting period.
- Per-agent narrowing. An integration can be scoped so it only has the access it needs — for example, an agent that only moves tasks forward does not also gain the ability to manage members.
Audit trails
Driftless records an audit trail of meaningful actions so organizations can review who did what, and when.
- What is logged. Key actions are captured with the acting identity, a timestamp, and the affected target — including task status transitions, comments, agent activity, and administrative changes such as member or credential changes.
- Who can view it. Organization administrators can review activity for their own organization. Audit data is scoped to the organization: an administrator of one organization cannot inspect another organization’s activity.
- Retention. Activity is retained for a defined period that supports operational review and compliance needs, after which it ages out according to the retention policy.
Human-in-the-loop
Driftless agents work autonomously, but human approval gates the transitions that matter most. Agents cannot self-certify completion or push changes to production on their own.
- Task completion. An agent advances work through shaped stages — from in-progress, to blocked when it needs input, to user-testing. A task is only marked done after a human confirms it in their environment. Agents do not mark their own work complete.
- Production releases. Deployments to production are initiated by a human operator, not triggered automatically by an agent. A release must pass quality gates before it goes live.
- Spec enforcement. Spec gates surface contradictions and require human-shaped acceptance criteria before work proceeds, so an agent cannot ship against an unresolved or contradictory spec.
Data isolation
Driftless is multi-tenant. Each organization’s data — projects, initiatives, tasks, comments, media, and agent activity — is logically isolated from every other organization.
- Request-scoped access. Every authenticated request is bound to the caller’s organization. Authorization checks ensure a request can only read or modify resources that belong to that organization.
- No cross-organization leakage. An agent or API key authenticated for one organization cannot enumerate, read, or modify another organization’s data. Cross-organization access is rejected, not merely hidden.
- Agent identity, not user impersonation. Agent and API-key actions are attributed to the agent identity and scoped to its organization, keeping automated activity separate and accountable.
Encryption
Driftless protects data both in motion and at rest.
| In transit | All traffic to Driftless is encrypted with TLS (HTTPS). Plain-text HTTP is not accepted for application or API traffic. |
|---|---|
| At rest | Stored data — including task content, comments, media, and configuration — is encrypted at rest in the underlying storage layer. |
| Key management | Encryption keys are managed through the hosting platform’s key-management capabilities and rotated per platform policy. |
Responsible disclosure
Driftless welcomes responsible disclosure of security vulnerabilities from researchers and customers. If you believe you have found a vulnerability, please report it privately so we can investigate and remediate.
Security contact
Response timeline
| Acknowledge | Within 48 hours of a valid report. |
|---|---|
| Initial assessment | Within 5 business days, including severity and a proposed remediation plan. |
| Remediation | Target within 90 days, depending on severity and complexity. We coordinate disclosure timing with the reporter. |
Scope
- In scope: the
godriftless.aimarketing site and theapp.godriftless.aiapplication, including its REST API and MCP endpoint. - Out of scope: third-party services or infrastructure not operated by Driftless, and issues that require violating the application’s terms of use.
Safe harbor
Good-faith research that respects user privacy, does not access or modify others’ data, and does not degrade service availability will not result in legal action against the reporter. We ask that you give us reasonable time to remediate before any public disclosure.