Privacy Policy
CloudLink is a connector that turns a local app — and optionally an OpenCode machine — into a shareable HTTPS link. This policy explains what the service does and does not handle.
Independent project
CloudLink (OpenCode Cloud Link) is an independent project. It is not built by the OpenCode team, is not endorsed by them, and is not affiliated with them in any way. “OpenCode” is used only to describe the software this connector works with. OpenCode and its trademarks belong to their respective owners.
Your local content
Your repository, source files, build output, terminal output, prompts, responses, and model provider credentials are handled on your machine. They are not sent to, stored by, or processed by the CloudLink control plane.
When you expose a local service, the content of that service is served to the visitors you authorize through the tunnel. It is not stored by the control plane. When the OpenCode integration is enabled, OpenCode traffic is likewise proxied to your machine and is not stored by the control plane.
Data travels between the visitor and your machine through a Cloudflare Tunnel. Cloudflare terminates TLS at its edge as part of delivering the connection and is therefore able to see that traffic in transit; it is not stored by us.
What the control plane stores
To establish and manage connections, our control plane stores only account and connection metadata:
- The account email address used for browser sign-in
- Account, machine, and opaque installation identifiers
- Machines you have paired, their names, and tunnel hostnames
- Pairings (short-lived and single-use) and their timestamps
- Subscription status, entitlement, and expiry used to authorize access
- Stripe customer and subscription identifiers when web billing is used
- Operational records needed to provision and retire tunnels
It does not store your app content, prompts, responses, source code, terminal output, file contents, device secrets, or model provider credentials. Device credentials are issued as signed, machine-scoped tokens with an expiry and are verified locally by the connector.
Subscription and billing
Browser subscriptions are processed by Stripe. App Store and Google Play purchases are processed by the respective store. We receive subscription status and an opaque account or customer identifier; we do not receive your payment card details. Receipts, taxes, refunds, and renewal notices come from Stripe or the store that processed the purchase.
Local storage
On your machine, connection state is stored in your operating system’s
application-support location. Tunnel tokens and the browser credential are kept
in the macOS or Windows native credential store, or in a private 0600 file on
Linux.
Your choices
You can stop remote access at any time by quitting the connector, disabling or revoking a service share, or deleting a machine. Deleting a machine removes its tunnel and DNS record. Uninstalling retains local configuration and credentials unless you remove them. Cancelling a subscription is done through the Stripe Customer Portal or the app store account used to purchase it.
Changes and contact
We may update this policy as the product evolves. Material changes will be reflected on this page with a new effective date. For privacy requests, use the OpenCode Mobile support page.