# Privacy

> How LocalCloud uses basic usage information and web analytics, how to turn off runtime telemetry and website analytics, and how to contact us.
>
> Source: https://local.cloud/docs/privacy/

Your local service data is stored in your LocalCloud runtime and configured storage. Connected tools and jobs you configure can send data elsewhere.

## Runtime reporting

We collect basic technical, usage, and diagnostic details to maintain LocalCloud and improve reliability. These include environment information, aggregate service and Console activity, service health, and errors. Reports use a pseudonymous identifier and are sent at startup and periodically while telemetry is enabled.

## Disable telemetry

Set this in the **LocalCloud container’s environment** before starting or recreating it:

```text
LOCALCLOUD_TELEMETRY=false
```

With Docker, add `-e LOCALCLOUD_TELEMETRY=false` to your `docker run` command. With Docker Compose, set it under the LocalCloud service’s `environment` section.

**This stops regular runtime and Console reporting.** When a reporting key is configured, one startup event still records that telemetry is disabled.

Update checks, license validation where enforced, live-cloud authentication, and jobs or feedback you choose to send can still make network requests.

## Website analytics

We use basic web analytics to understand visits, usage, and performance. Analytics providers collect the browser, device, network, and interaction details needed to provide these services. Search text and feedback you submit may also be recorded to improve the documentation.

PostHog also collects dead clicks (clicks with no visible response) to help us find usability problems. On desktop-sized viewports, it collects heatmaps and sampled session recordings. On mobile-sized viewports, recordings and heatmaps are disabled; page visits, clicks, searches, copy actions, and errors remain enabled. Input values are masked in recordings. Console logs, network request and response contents, and canvas recording are disabled.

We collect sampled browser performance measurements to find slow pages and interactions. Reports include the website release so we can identify regressions after changes.

When someone downloads the install script from `local.cloud/install.sh`, the site’s Cloudflare Worker sends PostHog one `install_script_fetched` event with a random one-time identifier, the downloading tool (curl, wget, or other), the country Cloudflare derives from the request, and, when the download was linked from a local.cloud page, that page’s path. It does not send the IP address or create a person profile.

Please do not include secrets, credentials, personal data, or customer data in search or feedback fields. The runtime telemetry setting does not control website analytics.

### Turn website analytics off

Every page has an **Analytics: On** control at the bottom of the footer. Select it to switch to **Analytics: Off**: the site then stops PostHog capture and session recording and no longer loads the PostHog or Cloudflare Web Analytics scripts in that browser, so it records no page views, searches, copies, clicks, or heatmaps from it. The choice is stored in your browser until you switch it back or clear site data.

If your browser sends a Global Privacy Control or Do Not Track signal, the site treats analytics as off without any action from you, and the footer control shows **Analytics: Off** with the signal’s name. The install script event above is counted by the server when the script is downloaded, so this browser setting does not apply to it.

## Contact

For privacy questions or deletion requests, email [info@local.cloud](mailto:info@local.cloud?subject=Privacy%20request). Other ways to reach us are on the [contact page](https://local.cloud/contact/).