Legal
Privacy Policy
Effective date: February 14, 2026 · Last updated: February 14, 2026
1. Overview
CloudSH ("we", "us", "our") respects your privacy. This Privacy Policy explains what data we collect, how we use it, and your rights regarding that data. It applies to the CloudSH client application (app.cloudsh.io), relay service (relay.cloudsh.io), and marketing site (cloudsh.io).
CloudSH is a self-hosted terminal access tool. Your terminal servers run on your own hardware — we do not have access to your server data, terminal sessions, files, or commands. This policy covers only the data processed by our managed services (relay, authentication, billing).
2. Data We Collect
Account Data
When you create an account, we collect:
- Email address (from your OAuth provider)
- OAuth provider ID (GitHub or Google)
- Account creation date
Server Registry Data
When you register a server with the relay service, we store:
- Server name and optional subdomain
- Server status (online/offline) and last-seen timestamp
- Tunnel URL (ephemeral, changes on each server restart)
- Server authentication token (hashed)
Billing Data
If you subscribe to a paid plan, Stripe processes your payment. We store:
- Stripe customer ID (a reference, not your card details)
- Current plan (free or pro)
We never see or store your credit card number, CVV, or billing address. Stripe handles all payment processing. See Stripe's Privacy Policy.
Client-Side Data
The CloudSH web app stores data locally in your browser (IndexedDB):
- Server connection details (name, URL)
- Authentication tokens (encrypted)
- Terminal preferences (font size, scrollback length)
This data never leaves your device and is not transmitted to our servers.
Automatically Collected Data
When you use the relay service, standard request metadata is processed:
- IP address (used for rate limiting, not stored long-term)
- Request timestamps
We do not use tracking cookies, analytics scripts, or advertising pixels on any CloudSH property.
3. How We Use Your Data
- Authentication: Your email and OAuth provider ID verify your identity and associate your servers with your account.
- Relay service: Server registry data enables pairing code resolution, subdomain routing, and connection brokering between your devices and servers.
- Billing: Stripe customer IDs link your account to your subscription for plan enforcement.
- Security: IP addresses are used for rate limiting and abuse prevention. We do not log or retain IPs beyond the request lifecycle.
- Service improvement: Aggregated, anonymized usage data (e.g., total registered servers, active connections) may be used to improve the Service. No individual data is used for this purpose.
4. Data We Do NOT Collect
To be explicit about what we do not access:
- Terminal session content (commands, output, history)
- Files on your servers
- Server system information (OS, CPU, memory, disk)
- Browsing history or behavior outside CloudSH
- Location data beyond IP-derived country (for rate limiting)
WebSocket connections between your browser and your server are proxied through Cloudflare's network. We do not inspect, log, or store the content of these connections.
5. Third-Party Services
CloudSH uses the following third-party services:
| Service | Purpose | Data Shared |
|---|---|---|
| Supabase | Authentication, database | Email, OAuth ID, server registry |
| Stripe | Payment processing | Email, payment details (direct to Stripe) |
| Cloudflare | CDN, DDoS protection, Workers runtime, Tunnels | IP address, request metadata |
| Vercel | Client app hosting | IP address, request metadata |
6. Cookies
CloudSH does not use tracking cookies, advertising cookies, or third-party analytics cookies. The client application uses browser local storage (IndexedDB) to store authentication tokens and preferences. These are not cookies and are not transmitted to our servers.
7. Data Retention
- Account data: Retained until you delete your account.
- Server registry: Retained while you have an active account. Removed when you delete your account or remove a server.
- Pairing codes: Automatically expire after 5 minutes.
- Billing data: Stripe retains payment records per their own retention policy. We remove your Stripe customer ID from our database upon account deletion.
- IP addresses: Not stored beyond the request lifecycle (used only for in-memory rate limiting).
8. Your Rights
Depending on your jurisdiction, you may have the following rights:
- Access: Request a copy of all data we hold about you. Use the "Export My Data" button in Settings, or email us.
- Correction: Update your account information through the Settings page.
- Deletion: Delete your account and all associated data from the Settings page. We will process the deletion within 30 days.
- Portability: Export your data in a machine-readable format (JSON) from the Settings page.
- Objection: If you believe we are processing your data unlawfully, contact us.
For EU/EEA Residents (GDPR)
Our legal basis for processing your data is: (a) contractual necessity (to provide the Service), and (b) legitimate interest (security and abuse prevention). You may lodge a complaint with your local data protection authority.
For California Residents (CCPA)
We do not sell personal information. We do not share personal information for cross-context behavioral advertising. You may request deletion of your data as described above.
9. Security
We use industry-standard security measures to protect your data: TLS encryption for all connections, bcrypt password hashing, HMAC-verified webhooks, and Cloudflare DDoS protection. Authentication tokens are stored encrypted in your browser. Server-to-relay communication uses authenticated tokens.
No system is perfectly secure. If you discover a security vulnerability, please report it to [email protected].
10. Children's Privacy
CloudSH is not intended for use by anyone under 13 years of age. We do not knowingly collect data from children. If you believe a child has created an account, contact us and we will delete it.
11. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of material changes via email or an in-app notice at least 14 days before they take effect. The "Last updated" date at the top reflects the most recent revision.
12. Contact
Questions about this Privacy Policy or your data? Contact us at [email protected].