Privacy policy

Who is responsible

This policy covers the Agent Loadout website, dashboard, API and AI integrations. Workspace owners decide which people, agents and connected apps may access their workspace data.

Data we process

We process account names, email addresses, membership roles, workspace and agent settings, connection permissions and billing references. Email features process senders, recipients, subjects, message bodies, attachments, delivery events and mailbox state. Vault features store encrypted credentials and authenticator secrets. Wallet features process card identifiers, spending rules and activity; authorized tools can retrieve full card details. Machine features process configuration, files, commands, output and access sessions.

Why we process data

We use this data to provide the features you request, authenticate users, enforce permissions and quotas, deliver email, maintain resources, handle billing and answer support requests. Contract-related processing relies on Article 6(1)(b) GDPR, legal obligations on Article 6(1)(c), and proportionate service security and abuse prevention on Article 6(1)(f). Where processing requires consent, Article 6(1)(a) applies and you may withdraw that consent for the future.

Connecting an AI app

Connecting ChatGPT, Claude, Grok or another client grants access to one selected agent with the permissions you approve. We receive tool inputs and return the requested data to that client. We do not request your full conversation history. With the relevant permissions, results can include email content, passwords, API keys, one-time codes, payment card details or machine files. The connected AI provider processes those results under its own terms and privacy policy. Only approve access to data you want that provider to receive.

A connection may be shared across multiple assistants within the AI provider's account. Disconnecting stops future access through that connection; it cannot remove data already returned to the provider or undo completed actions.

Service providers and recipients

Hosting, database and storage use Cloudflare and PlanetScale; sign-in uses WorkOS. Email delivery uses Amazon Web Services, or a configured email provider. Billing and card services use Autumn and Stripe. Enabled machine features use Boat. PostHog supports product analytics, error monitoring and feature availability. When TypeSafe screening is enabled, email content needed for screening and account setup details needed for abuse screening are sent to that service. Email recipients, configured webhooks and AI clients receive data when the corresponding feature is used.

Service providers and connected apps may process data outside Germany or the European Economic Area. The applicable provider arrangements and transfer safeguards depend on the service used. Contact support@loadout.email for information about the providers and safeguards relevant to your workspace.

Cookies, analytics and logs

Sign-in cookies keep your session secure; workspace and language settings preserve your choices. When configured, PostHog receives product events, page views, account identifiers and technical error information. Session recording and automatic click capture are disabled. Security, delivery and audit records can include actor identifiers, operation types, resource identifiers, timestamps and technical request information. Credential values are excluded from normal application logs.

To understand how people find and start using the service, we also record where a visit came from: the referring site, campaign parameters in the link you followed, the page you landed on and the pricing option you chose. A first-party cookie keeps this for 30 days until you sign in, and the documentation site at docs.agent-loadout.com uses the same analytics project so that a visit which starts there can be connected to a later sign-up. We do not use advertising networks and do not sell this data. Browsers that send a Global Privacy Control or Do Not Track signal are not tracked at all. This processing relies on our legitimate interest in improving the service under Article 6(1)(f) GDPR; you may object at any time.

Retention and deletion

Workspace data is retained while needed to provide the service, subject to your plan and deletion choices. Free Sandbox mail expires after seven days. Unused attachment uploads expire after 24 hours unless retained by a saved draft. Paid mailbox retention follows the plan shown in the dashboard. Deletions and resource cleanup run in background jobs. Billing, security and audit records may be retained where needed for legal obligations, dispute handling or abuse prevention. Provider backups and records follow their applicable retention arrangements.

Your choices and rights

You can review and revoke agent connections, change permitted access, export mail and delete eligible resources in the dashboard. Contact support@loadout.email to request access, correction, deletion, restriction or portability of your personal data, to object to processing based on legitimate interests, or to withdraw consent. We may need to verify your identity. You may complain to a data protection supervisory authority, including the Brandenburg authority at lda.brandenburg.de. Providing account and feature data is necessary for the corresponding service; withholding it can prevent that feature from working.

Automated checks

Automated spam screening, sender restrictions, spending rules and resource limits can quarantine messages or reject actions. Contact support if you believe a restriction was applied incorrectly. These controls do not replace your review of consequential actions performed by an AI assistant.