Privacy policy
Last updated 20 November 2026
CLI is operated by MojaveSky Solutions LLC ("CLI", "we", "us"), 7122 Black Sage St, Las Vegas, NV 89118, United States. We run clicloud.app, the CLI dashboard and API, the cli command, the MCP server, the CLI connectors for Claude and ChatGPT. This policy explains what we collect when you use them, and what we do with it. Questions go to support@clicloud.app.
What we collect
Your account
- How you sign in: your email address, your GitHub account id and username, or your wallet address, depending on which you use.
- Sign-in records: when each session started and was last used. We use the IP address of each request to limit abuse (for example, too many sign-in attempts) and to protect accounts.
- Second factors: your passkeys' public keys and, if you use an authenticator app, its secret, stored encrypted.
- Connected apps: when you connect an app such as Claude or ChatGPT, the app's name, the projects and daily spending limit you chose, and when it was last used. We store only hashes of its tokens.
What you run on CLI
- Your code and settings: the repositories, images and files you deploy, and your services' settings. Variables are stored encrypted. Secret values can't be read back through the API.
- Your data: what's in your databases, volumes, storage buckets and backups. We don't look at it except to run, back up and restore it, or when you ask us to help with it.
- Logs and metrics: your apps' output, resource use and request counts. For the request inspector we keep the latest 500 requests to each app: method, path, status, timing, size and the client's IP address, but no headers or bodies. Traces your apps send are kept for 3 days.
- Webhook inboxes: the latest 200 requests sent to each inbox, with their headers and bodies. We drop headers that carry passwords or tokens (
Authorization,Cookie) before storing anything. - Activity: who changed what, when, and the one-line reason an agent gave, so you can review and undo changes. Kept for 90 days by default.
Money
- Card payments are handled by Stripe. We get the amount and the payment's status, never your card number.
- USDC payments (x402, deposits, withdrawals) are recorded on public blockchains (Base and Solana). Anyone can see a public blockchain, so the wallet addresses and amounts of those payments are public by nature.
- Your balance and history: credit added, what was spent on what, earnings from APIs you sell, and withdrawals.
AI agents and the connectors
When your agent uses CLI, through the MCP server or a connector for Claude or ChatGPT, we receive the arguments of each tool it calls (for example a service name, or variables to set) and the one-sentence reason it gives. The connectors never receive your conversation, the assistant's memory or your files. If you sign in by email, the ChatGPT connector can see your email address; with a wallet, only its address. The ChatGPT connector doesn't accept secrets through the chat and masks credentials in what it sends back.
Reports about paid APIs
When you report a listing in the Paid APIs directory, we keep the reason, any details you write and your account, to review it. The seller doesn't see who reported it.
This website
clicloud.app doesn't use advertising or analytics trackers. The hosting provider keeps standard request logs.
How we use it
- To run the service: sign you in, deploy and run your apps, bill usage, send the alerts and emails you set up, and answer support requests.
- To keep CLI safe: detect abuse (such as crypto mining or phishing on our machines), stop attacks, and investigate security incidents.
- To improve CLI: understand which features are used and where deploys fail.
- The shared memory of fixes: when a deploy fails and a later change fixes it, we record an anonymous fingerprint of the failure and what kind of change fixed it. We keep no values, names, code or raw logs, and suggest a fix to others only after it has worked in several projects. Turn it off per project in its settings.
We don't sell your data, and we don't use it for advertising.
Who we share it with
We share only what each provider needs to do its job for us. These are the processors that handle personal information for CLI:
| Processor | What it does for CLI | What it receives |
|---|---|---|
| Railway | Hosts CLI's control plane (dashboard, API) and clicloud.app | Everything the control plane stores: accounts, projects, billing and activity records |
| Oracle Cloud | Hosts the servers that build and run your apps and databases | Your code, app data, logs, and the requests visitors send your apps |
| Backblaze (B2) | Stores backups and files | Database backups, CLI's own encrypted database backups, files in storage buckets |
| Stripe | Card payments | Payment amount, email, and card details (which CLI never sees) |
| Coinbase Developer Platform | Settles USDC (x402) payments | The signed payment: wallet address and amount |
| Alchemy, and public Solana RPC nodes | Read blockchains to confirm payments | Wallet addresses and transaction ids |
| Resend | Sends email | Your email address and the email's content: sign-in codes, alerts, email your apps send through CLI |
| GitHub | Sign-in, and deploying from your repositories | Your GitHub id and username; access to the repositories you choose |
| Reown (WalletConnect) | Wallet sign-in from another device | Your wallet address and the sign-in request |
| Name.com | Domains you buy through CLI | The domain and the registration details it requires |
| Anthropic | AI features: Ask CLI, hosted agents, CLI's AI gateway | Only what you or your apps send to those features |
Services you connect yourself (a log drain such as Axiom or Datadog, alert channels such as Slack, Telegram or text messages, a secrets manager, an importer for Heroku or Railway) receive what you set them up to receive. Public blockchains receive USDC payments by their nature.
We may also disclose information when the law requires it, or to protect people from harm. If CLI is ever sold or merged, this policy continues to apply to your information.
Where it's stored
Your account, billing records and activity records are stored in the United States. When a project has a region, such as the European Union, its apps, databases and database backups are stored in that region (see /docs/regions). Projects without a region are stored in the United States. Providers listed above may process information in other countries, under their own safeguards.
How long we keep it
| Information | Kept |
|---|---|
| Your account | Until you delete it. Deleting it removes your sign-in methods, sessions, second factors and memberships at once; we keep only a one-way hash so the same person can't claim free credit twice |
| Projects, services and their data | Until you delete them. Deleted projects can be restored for 7 days, then their services, data and backups are permanently deleted |
| Sign-in sessions | Each ends within 24 hours, sooner if unused |
| Email sign-in codes | 15 minutes |
| Database backups | 7 days |
| CLI's own database backups (these include account records) | The latest 14 daily copies, so deleted information is gone from them within 14 days |
| Deploy logs | With the deploy, until the service or project is deleted |
| App output on our servers | The latest 30 MB per running copy of an app, replaced as it's written and removed with the copy |
| Router access logs (requests to your apps, with visitors' IP addresses) | 14 days |
| Request inspector | The latest 500 requests per app |
| Traces | 3 days |
| Visitor speed measurements | 30 days |
| Cron job runs and their output | 30 days |
| Webhook captures | The latest 200 per inbox |
| Activity records | 90 days |
| Connected apps | Until you disconnect them. Sign-ins nobody finished are deleted within an hour |
| Payment and billing records | As long as tax and accounting law requires (typically 7 years) |
| Support emails | As long as needed to help you, and no longer than 2 years |
Providers keep their own records for the periods in their policies (Stripe, for example, keeps payment records as financial law requires). Information on a public blockchain can't be deleted by anyone.
Your choices and rights
- See and export your data: the dashboard shows everything above, and the exit export downloads your projects' configuration and data.
- Correct it: change your settings, or ask us.
- Delete it: delete a project, or your whole account under Account in the dashboard. You can also email us.
- Disconnect apps: under Account → Connected apps.
- Ask us: email support@clicloud.app, or write to MojaveSky Solutions LLC, 7122 Black Sage St, Las Vegas, NV 89118, United States, for access, correction, deletion, or a question about how we handle your information. We'll answer within 30 days. You can also complain to your local privacy regulator.
Security
All traffic is encrypted with TLS. Variables and stored credentials are encrypted. Tokens are stored only as hashes. You can protect your account with a passkey or an authenticator app. If we learn of a breach that affects your information, we'll tell you.
Children
CLI isn't meant for anyone under 18, and we don't knowingly collect information about children.
Changes
If we change this policy, we'll update the date above. For significant changes, we'll also email account owners or show a notice in the dashboard before they apply.