Privacy Policy

Test projects, tasks, case artifacts, local device sessions, and most configuration are intended to remain on your computer.

When you configure AI providers, connect mobile devices, or use Ember Cloud (private deployment), related data may leave the machine according to your setup. Treat those integrations as privileged.

The public website provides documentation, release links, static assets, redirects, and machine-readable release metadata. Downloads are distributed through GitHub Releases.

Hosting providers, GitHub, browsers, and network intermediaries may process standard request metadata such as IP address, user agent, URL, referrer, and timestamps according to their own systems and policies.

When you send PRDs, test notes, screenshots, or other context to a configured model provider, that traffic is governed by the provider, API endpoint, and account you choose.

Review each provider's privacy policy, retention behavior, regional routing, and acceptable use terms before processing sensitive test data.

Private Ember Cloud deployments, ember-mcp, CI tokens, and cloud device sessions may expose test data or device screens within your organization's network boundary.

Scope access tokens, rotate credentials, and disable integrations that are no longer needed.

For privacy questions about Ember, open an issue in the public GitHub repository and avoid posting secrets, tokens, private repository content, or personal data in the issue body.