Privacy Policy

This Privacy Policy explains what data Tailwatch processes for the hosted service, how we use it, and which third-party providers help us operate it. We do not sell personal data.

Effective March 5, 2026

Minimal collection

We collect only the account, device, and event data required to operate Tailwatch and protect accounts.

No ad-tech profiling

We do not use ad networks, behavioral advertising profiles, or cross-site ad trackers.

You control your content

You keep ownership of your event payloads. We process them only to provide the service.

What data we process

Account data

If you sign in with GitHub, we receive basic profile details your provider makes available (such as name, email, and avatar).

Published event data

Event records you explicitly send to Tailwatch (for example, through publish API requests), including path, status, timestamp, and optional content text.

Device data

Device key, device name, browser/system metadata, last-seen timestamps, and (if enabled) web push subscription details.

Volume data

Volume names, API keys, key status, and notification settings.

Request and security metadata

Standard request metadata may include IP address, user-agent, route path, and timestamp for service delivery, security, and reliability operations.

Local storage and cookies

Tailwatch uses essential local storage/cookie-like mechanisms for authentication sessions, device identity, and user experience state.

We do not currently use advertising cookies.

Why and how we use data

  • To operate the service and display your dashboard data.
  • To authenticate users and protect accounts.
  • To deliver push notifications when you enable them.
  • To improve stability, security, and abuse prevention.

Third-party services

Tailwatch currently uses the following providers to run the hosted service:

Cloudflare (hosting, edge, and security)

Delivers the application and API at the edge and may process request metadata (for example IP address and user-agent) for delivery, observability, and abuse protection.

Convex (application backend and data store)

Stores and processes account, device, volume, and event data to power Tailwatch features.

GitHub OAuth (sign-in provider)

If you sign in with GitHub, GitHub provides account/profile data according to your GitHub settings and permissions.

Browser push providers (Apple, Google, Mozilla)

When notifications are enabled, your browser shares subscription endpoint details with its push vendor, and encrypted notification payloads are sent through that vendor.

If you self-host Tailwatch, your own infrastructure choices and data handling practices apply.

Retention and your choices

  • You can delete devices and volumes from in-app settings, which removes associated records from the hosted service.
  • You can disable browser notifications at any time in your browser and in Tailwatch settings.
  • You can request account or data help through the project support channel.