Privacy Policy

Agentic Cloud Computer creates coding agents that run on their own cloud machines, driven from Telegram. It is built and run by Saddam Baialiev — Adam — an independent developer in Bishkek, Kyrgyz Republic, who is the controller of the data described here. There is no company behind it, and no one else has access to your data.

This page says what data the service touches, where it lives, and how to get rid of it. For anything it doesn’t answer:

Email [email protected]. One person reads it, usually within a day.

Saddam Baialiev, trading as Agentic Cloud Computer
Bishkek, Kyrgyz Republic

Telegram account basics. Your Telegram user ID, name, username, and chat IDs — needed to route messages between you and your agents.

The setup chat. Your conversation with the factory bot is stored so it can pick up where it left off.

Conversations with your agents — not stored by us. They live in the harness’s session files on the agent’s own machine and are destroyed with it. Our logs carry plumbing — timestamps, machine IDs, errors — not the text of your messages.

Sign-in tokens. Signing in to Claude or ChatGPT gives your agent a session token, which we store encrypted so the agent stays signed in across rebuilds. We never see or store your password.

Code and files. Whatever your agent makes stays on its machine’s disk. We keep no copy, no backup, no archive.

Subscription status. If you subscribe to Plus, we store what Paddle tells us about the subscription — plan, status, billing-period end, and Paddle’s customer and subscription IDs — linked to your account, because it decides what your account can do. Checkout and card handling happen entirely at Paddle, our merchant of record, under Paddle’s privacy policy; we never see card numbers.

Agent machines and their disks run on Fly.io, currently in Amsterdam, encrypted at rest. Account records, the setup chat, and sign-in tokens live in Google Cloud Firestore, encrypted at rest. Our backend server runs at Hetzner in Germany.

Messages travel over Telegram, under Telegram’s own privacy policy. Telegram does not offer end-to-end encryption for bot chats, so your conversation with an agent sits on Telegram’s servers like any cloud chat; we relay it without keeping a copy.

Anthropic or OpenAI receive what your agent sends them — prompts, code, context — under the subscription you signed in with and the terms you accepted there. Nothing routes through our API keys.

Paddle, our merchant of record, sees what you give it at checkout if you subscribe to Plus — payment details, billing country, email.

The hosting providers in section 3 process data in order to host it. Nobody else: we don’t sell data, don’t run ads, and don’t use third-party analytics.

We can reach machines and logs for debugging, and we use that to fix your problem — not to browse your work.

Delete an agent and its machine and disk are destroyed at the host within about a minute. A machine idle for three days is recycled the same way (the agent warns you a day ahead). Account records and the setup chat last as long as your account does.

Want everything gone — records, tokens, all of it? Email us and we’ll confirm when it’s done. You can also revoke your agent’s sign-in token at any moment from your Anthropic or OpenAI account settings, which cuts off its access to your subscription immediately.

Disks and databases are encrypted at rest, sign-in tokens live in secret storage, and each agent’s machine is isolated — one machine per agent, reachable only through our backend. No system is perfectly secure, but the blast radius of any single machine is one agent’s work.

The service is not directed at children under 16 — Telegram itself requires users to be at least 16.

Updates to this policy appear here with a new effective date; material changes will be announced through the factory bot.

Email [email protected]. One person reads it, usually within a day.

Saddam Baialiev, trading as Agentic Cloud Computer
Bishkek, Kyrgyz Republic