Privacy Policy

1. Who we are

Everpod is operated by DEH Technologies LLC, a Wyoming limited liability company, doing business as Everpod. For privacy questions or requests, contact privacy@everpod.ai. For security reports, use security@everpod.ai; for anything else, support@everpod.ai. The Terms of Service are the binding agreement; this policy explains how we handle personal information under it.

Everpod offers two kinds of pod: a developer pod, a cloud computer you administer yourself, with the agents you chose installed; and a managed pod, OpenClaw set up and run for you. Most of this policy is the same for both; where they differ, the section says what holds for each.

2. What we hold, and what we don’t collect

Account Data (we hold this): your email address, sign-in records, your pod’s basic details (such as its name and status), subscription records, and support correspondence. If you make API keys, we keep a record of each one (such as its name, its last four characters, and when it was made, last used and revoked), and not the key itself. If you contact us or fill in a form on our site, we keep what you send us; the same goes for a support report your agent files with us when you ask it to, which carries only the text you approved. To keep accounts secure and to spot abuse (such as fraudulent sign-ups), we also record technical details when you sign in and use the app: your IP address, the country it suggests, your browser’s language, and an identifier for your device. Payment details are different: checkout is run by Paddle as Merchant of Record under its own privacy policy, and we never see your card number; we receive only transaction metadata (what was bought, when, receipt identifiers).

Referrals: when you arrive on everpod.ai through the link of one of our affiliates, we remember on your device, for up to 90 days, which affiliate’s link it was. If you then start a pod, we record that affiliate with your account, and send the provider that runs our affiliate program an identifier for your account and the amount, date and reference of each payment, so the affiliate’s commission can be worked out. We don’t send it your email address or anything on your pod, and we don’t tell the affiliate who you are.

Affiliate Data (if you join our affiliate program): your name (and your business’s, if you join as one), email address, country, whether you are a US person for tax purposes, the details of the account we pay you into, and the records of your referrals, commissions and payouts. Before your first payout we also ask for a US tax form, which we keep in our own records and never with the program’s provider.

Pod Content (we host this, we don’t collect it): what you tell your agent, what it remembers, the files it makes, and everything else on your pod live on that machine, whose contents you control. Pod Content is not part of our systems: we don’t collect, inspect, index, or analyze it. Section 5 covers how long it lives; section 7 covers the narrow circumstances in which we can access it.

Site and app usage (analytics): we use analytics to understand how our website and app are used. This covers only our site and app. It never touches your pod; your agent and your conversations with it are not part of it.

What we don’t do: no advertising trackers on our site; no selling or sharing of personal information for advertising; no use of your content to train AI models. Credentials you give your agent (your own model keys and sign-ins, channel tokens) live on your pod, not in our systems. We use cookies and similar storage on your device to keep you signed in, for the analytics above, and to remember an affiliate’s referral.

3. Our role

For Account Data and Affiliate Data, we are the controller: we decide what’s needed to run your account or the program, and section 10 lists your rights over it. For Pod Content, our role is that of a hosting provider (in data-protection terms, closer to a processor): you decide what is on your pod and what your agent does, and we supply the machine, acting on your instructions. For a developer pod, those are to host it, back it up, and delete it when you leave; running it is yours. For a managed pod, they are also to keep it secure and keep it running.

4. Where your data lives

• Your pod and everything on it: data centers in Germany or Finland (both in the EU) operated by Hetzner, with backups in the same region. Pods are hosted in Europe today; if that ever changes, we’ll update this policy first.
• Account Data: the United States (our account/auth database, our website hosting, and analytics) and the EU (our own servers).
• Affiliate Data: the EU (the provider that runs our affiliate program) and the United States (our payout provider and our own records).
• Network edge: traffic to our site, and to a managed pod’s sign-in page, passes through Cloudflare’s global network. You reach a developer pod over your own Tailscale network instead.
• Model traffic: see section 6.

5. How long we keep things

Persistence is the product: Pod Content lives for the life of your subscription; that’s the point of a pod. Backups are made daily and rotate over roughly 7 days, so anything you delete on your pod ages out of backups on that cycle too.

When you cancel, your pod stops at the end of the paid period, and 7 days later we permanently delete the machine, its contents, and its backups, and revoke its credentials. The grace window exists so an accidental cancellation isn’t a catastrophe; past it, the deletion is permanent and we can’t undo it.

Account Data is kept while you have an account and deleted on request when no longer needed (email privacy@everpod.ai), except records we must keep for tax, accounting, or legal reasons. Affiliate Data is kept while you are in the affiliate program, and payout and tax records for as long as the law requires after you leave it.

6. Model providers (your agent’s thinking)

When your agent thinks, the conversation context is sent to an AI model provider; that’s how AI agents work. Which provider, and whose terms cover it, depends on the kind of pod.

Developer pods. A developer pod includes no Included Usage. You sign in to each agent with your own account or key, under your own agreement with its provider, and your sign-ins never pass through us. That provider’s policies, not this section, govern that traffic.

Managed pods. Included Usage (and any additional usage you buy from us) is routed through OpenRouter under our account. Here is how it is handled:

• OpenRouter does not store your prompts or your agent’s responses.
• We enforce, at the routing layer, that Included Usage is never sent to model providers that use API traffic to train their models, whichever model your pod is set to.
• We also enforce that Included Usage is only sent to providers that do not keep your prompts or your agent’s responses. That covers the model your pod starts on, and every model except those made by OpenAI, Anthropic, Google and xAI.
• For those four labs’ models, the provider serving them may keep API traffic for a time for abuse monitoring (the labs themselves currently state 30 to 55 days, and some keep traffic their safety systems flag for longer). None trains on it.

If you bring your own key or connect your own model subscription (BYOK) to a managed pod, your model traffic runs under your own agreement with that provider, and their policies, not this section, govern it.

7. When we can access your pod

Developer pods. Once you have joined a developer pod to your Tailscale network, switched off its key expiry and logged in, we remove the access we used to set it up. From then on we have no login on it: no key and no account. We host the server it runs on and keep its daily backups. We do not read its disk or its backups, except with your permission during support, or where the law requires it.

Managed pods. We do not access or read a managed pod’s content (conversations, memory, files) except with your permission during support, or where required for security, abuse investigation, or by law. The machine it runs on does need maintaining, and that is what our access is for. Setting your pod up, keeping it running, approving device pairings, running security checks, applying managed updates, doing what you ask from your pod’s page and stopping it when your subscription ends are routine, done the same way on every managed pod; helping when you ask for support and investigating security or abuse problems on your pod are approved case by case. Machine sign-in is by cryptographic key, password login is disabled, and the access is used for nothing else.

8. Who we share data with

We use a small set of providers to run Everpod. They process data only to provide their service to us:

Paddle (checkout, taxes, receipts) is our Merchant of Record and an independent controller of buyer and payment data, not a subprocessor. The accounts you bring are your own, not our vendors: on a developer pod, your Tailscale network and the accounts or keys you sign your agents in with; on a managed pod, the messaging platforms you connect (Telegram, WhatsApp, and similar) and any model account of your own. We’ll post at least 15 days’ notice here before materially changing this list. Beyond the table: we disclose personal information only with your consent, to comply with law or valid legal process, to protect our rights or users’ safety, or as part of a merger or acquisition (in which case this policy continues to apply to it).

9. International transfers

Pods are hosted in Europe, and Account Data is processed in the United States and the EU (section 4). Model traffic is processed where the provider runs (section 6). Where EU/UK law requires safeguards for a transfer, we rely on our providers’ data-processing agreements, including Standard Contractual Clauses where applicable.

10. Your rights

We use your information to provide the service you signed up for, as our agreement with you requires, and to keep it secure, prevent abuse and understand how our site and app are used, which are our legitimate interests. The records we must keep for tax, accounting, or legal reasons (section 5) are kept because the law requires them. An affiliate’s information is used to run the affiliate program and pay them, as our agreement with them requires; remembering and recording which affiliate referred a customer is our legitimate interest in paying affiliates for the customers they bring.

Depending on where you live (the EU/UK under GDPR, several U.S. states, and elsewhere), you may have rights to access, correct, delete, or export personal information we hold about you, to object to or restrict processing, and to complain to your local supervisory authority. Email privacy@everpod.ai and we’ll respond within a month (or sooner where your law requires); if we deny a request, we’ll say why, and you can appeal by replying. We’ll verify requests against the email on the account, and we never discriminate for exercising rights.

For Pod Content, the fastest path is usually direct: it’s your machine. On a developer pod you can copy or delete anything on it yourself; we have no login on it to make a copy, so within the grace window we switch it back on at your request and you copy what you need yourself. On a managed pod, your agent can show you, send you, or delete anything on it when you ask, and if you’d like a full copy of your Pod Content, email support@everpod.ai and we’ll provide one in a common archive format. Cancelling deletes everything on the schedule in section 5.

11. Security

Security is a core part of what you pay us for. Each pod is a separate machine serving one customer, and it accepts no incoming connections from the open internet, which is the route attacks on an ordinary server take. Your agent can still browse and use the internet normally; its connections start from inside the pod, not from outside. Traffic between you and your pod, and between your pod and the AI model provider it thinks with, is encrypted; backups are made daily and we test restores.

Developer pods. You reach a developer pod over your own Tailscale network. Once it is handed over, its software and how it is secured are yours, since we have no login on it; its operating system’s security updates install themselves unless you change that (section 7; Terms, section 3).

Managed pods. Every managed pod is security-checked before you get the keys, and you reach it through a private, authenticated path tied to your email. The one exception to no incoming connections is a public address for your agent, which you switch on in your pod’s settings when a task needs it: through it, other services and automations can send your agent messages, and your agent can put a web app of its own online. Nothing else on the pod is reachable through it, and the control panel never is. Its software versions are pinned and updates are tested before we apply them.

No one can promise absolute security, and we don’t. If we confirm a security incident affecting your data in our systems, your pod or its backups, we’ll notify you without undue delay and no later than 48 hours after confirming it. Report vulnerabilities or suspected incidents to security@everpod.ai. Our Security overview describes these safeguards in more detail.

12. Age, changes, contact

Everpod is for adults: you must be at least 18 to use it, and we don’t knowingly collect personal information from anyone younger. When this policy changes materially, we’ll note it here with a new date (prior versions stay available from this page’s archive links) and tell you by email or with a notice on our site if the change affects you. Questions: privacy@everpod.ai.