Skip to content
C3Control / Continuity

Privacy Policy

Last updated: July 29, 2026

1. Privacy-First Approach

C3 is built around infrastructure you operate. C3 Mobile and Desktop send control traffic through your NATS hub, while C3Sync uses a separate account on that hub for durable synchronization. Application payloads are encrypted on your devices before reaching the hub.

C3 does not provide a hosted relay and does not receive your prompts, terminal output, synchronized files, agent sessions, credentials, or encryption keys. Your hub can observe routing subjects, message sizes, timing, and network metadata, but not encrypted payload content.

2. How C3 Works

Your hub

You choose where the hub runs and how devices reach it: a local network, a private overlay such as Tailscale, or an address you expose yourself. Bridges and C3Sync devices use pinned TLS; Mobile and Desktop use a pinned WebSocket connection.

Endpoint storage

Credentials and pair keys remain on enrolled devices in the operating system credential store, or in an explicitly selected encrypted-file fallback on headless hosts. Cached non-secret topology and session metadata may remain on a client until you remove its local enrollment.

3. Website Analytics

Our website uses PostHog for privacy-friendly analytics. PostHog helps us understand how visitors use our website so we can improve the experience.

  • Analytics applies to getc3.app, not control or sync payloads
  • We use it to understand aggregate page and interaction performance
  • Waitlist submissions contain the email address and product interest you provide
  • You can use the C3 applications without the website analytics path

4. Third-Party Services

Infrastructure you choose

NATS, hosting providers, VPN or overlay networks, Git hosts, coding-agent vendors, and Herdr are separate services or projects you operate or select. Their policies apply independently. C3 never sends application content to an agent vendor itself; the agent process running on your machine communicates according to its own setup.

Website services

Firebase processes waitlist requests and PostHog processes website analytics. Razorpay and Dodo may process optional support payments. These services do not receive C3 control or sync payloads.

5. Your Privacy Choices

Keep traffic private

Run the hub on a network or private overlay you control and do not expose its listeners publicly.

Revoke a device

Revoke its hub credential and its per-bridge pairing state; removing local app data alone does not revoke remote access.

Remove website data

Contact us to request deletion of a waitlist record or payment-support information held by C3.

6. Changes to This Policy

We may update this privacy policy from time to time. Any changes will be posted on this page with an updated revision date. We encourage you to review this page periodically.

Contact

If you have any questions about this privacy policy, please contact us at cccuiapp@gmail.com