The short version. DUEX does not receive your source code, your prompts, or your AI provider API keys. Agents run on your infrastructure and call AI providers directly from there. We hold account details, task metadata, and the records needed to operate the service.
1. Who we are
DUEX operates the service at duex.chat and is responsible for the personal
information described here. Contact: [email protected].
DUEX is offered only to customers located in the United States. This policy is written to United States federal and state privacy law.
2. What we do not collect
This is a deliberate design choice, not a policy promise:
| Not collected | Why not |
|---|---|
| Your source code | Repositories are cloned onto your own runner. We receive a cryptographic hash of the diff, not its contents. |
| Your prompts and AI responses | Your runner calls AI providers directly. Prompt bodies are not retained by default and do not transit our servers. |
| Your AI provider API keys | They are configured on your runner. There is no field or table in our systems that stores them. |
| Payment card details | Payments are handled by Stripe on their own hosted pages. We receive only a customer identifier and subscription status. |
3. What we do collect
Account data
- Your GitHub username, numeric user ID, display name and email address, obtained when you sign in.
- Organisation membership and role.
- Session records: a hashed session token, expiry, and browser user agent.
Operational data
- Task titles, objectives and state transitions — objectives are text you write and may describe your work.
- Runner names, platform, attested isolation mode, resource figures and heartbeat times.
- Agent run records: role, provider, model, outcome, and summary text returned by the agent.
- Token counts and cost figures reported by your runner.
- Approval decisions and the reasons you give for them.
- Audit events recording who did what and when.
Billing data
- Stripe customer and subscription identifiers, plan, status and renewal date.
Technical data
- Server logs including IP address, request path, status and timestamp, retained for security and debugging.
4. Why we process it
| Purpose | Detail |
|---|---|
| Providing the service | Authentication, dispatching work, enforcing plan limits |
| Billing | Collecting fees and managing subscriptions |
| Security and abuse prevention | Detecting misuse, protecting the service and other customers |
| Audit and evidence | Recording who approved what, for your compliance and for dispute resolution |
| Service communication | Notices about changes, incidents and billing |
We do not sell your personal information, and we do not share it for cross-context behavioural advertising. We have never done so.
5. Who we share it with
We do not sell personal data. We share only with processors necessary to run the service:
- Stripe — payments and subscription management.
- GitHub — authentication (we receive your profile; we do not retain your GitHub access token).
- Cloudflare — DNS, TLS and edge delivery.
- Our hosting provider — servers running the control plane.
We may disclose data where legally required, or to protect our rights, safety or property.
6. Where it is held
The control plane currently runs on servers located in Germany, operated by our hosting provider. Although DUEX is sold only in the United States, the metadata described above is therefore stored outside it. If that matters to your compliance position, say so before you subscribe — Enterprise customers can arrange United States or self-hosted deployment.
Remember what is not stored there: your source code, your prompts and your API keys never leave your own infrastructure.
7. How long we keep it
| Data | Retention |
|---|---|
| Account and organisation records | While your account exists, then up to 90 days |
| Task, run and evidence records | Per your plan (7 days to 7 years) |
| Audit and approval history | Retained for the plan's evidence period; append-only |
| Billing records | As required by tax and accounting law, typically 7 years |
| Server logs | Up to 90 days |
8. Your rights
Residents of California, Virginia, Colorado, Connecticut, Utah, Texas and other states with comprehensive privacy laws have rights over their personal information. We extend these to all United States customers regardless of state:
- Know and access — what we hold about you and how it is used.
- Correct — inaccurate personal information.
- Delete — subject to the exceptions below.
- Portability — receive your information in a portable format.
- Opt out of sale or sharing — not applicable; we do neither.
- Non-discrimination — exercising a right will not change your price or service.
Exercise any right at [email protected]. We verify requests through your authenticated account and respond within 45 days, extendable once where permitted. An authorised agent may act for you with written permission.
What we cannot delete. Billing records are retained where tax and accounting law requires. Audit, approval and usage records are append-only by design and cannot be altered retrospectively — that is precisely what makes them worth having as evidence. We will disassociate them from your identity where we can do so without destroying their evidentiary value.
If you believe we have not handled a request properly, contact us first. California residents may also contact the California Privacy Protection Agency.
9. Security
- TLS in transit; session tokens and runner credentials stored only as SHA-256 hashes.
- Credential comparison is constant-time; sessions expire and can be revoked.
- Access to operator data requires authentication and is scoped to your organisation.
- Audit, usage and approval records are append-only.
No system is perfectly secure. Report vulnerabilities to [email protected].
10. Children
DUEX is not for anyone under 18. We do not knowingly collect their data.
11. Sensitive information
We do not intentionally collect sensitive personal information as defined by state privacy laws: no government identifiers, financial account numbers, precise geolocation, health information, biometrics, or contents of private communications. Do not place such information in task objectives or approval reasons, which are stored as written.
12. Changes
We will post updates here and, for material changes, notify you in the service or by email. Material changes require fresh acceptance before you can continue using the service.