Privacy

Routeup CLI

The Routeup CLI has no product analytics or telemetry. Local routing works without an account and without contacting a Routeup server. Public exposure uses the server selected by the user.

Website analytics

routeup.dev uses a self-hosted instance of Umami. Its tracker does not use cookies or store personally identifiable information. It may record page views, referrers, browser and operating-system information, device type, and approximate country in anonymized form.

The site also records anonymous interactions with install, documentation, GitHub, recipe, and hosted-token-request controls. Token-request events contain only whether the request succeeded or failed; email addresses and namespaces are not sent to analytics.

Self-hosted Umami data is retained until it is manually deleted. Your theme preference is stored only in your browser.

Hosted-token requests

The token request form collects the email address and preferred namespace you enter. The request is delivered through Resend so it can be reviewed and answered. Routeup does not add your IP address or location to the request.

These emails do not have an automatic deletion schedule. You can ask for a request to be deleted by emailing [email protected].

Hosting

Cloudflare hosts and delivers the website and processes network requests needed to operate and protect it. The hosted-token form is optional, and you can block the analytics script in your browser.

Routeup's hosted public edge runs on Fly.io in its Singapore (sin) region. When you enable public exposure, requests pass through that infrastructure before they travel over an encrypted Routeup tunnel to your local agent.

Contact

For privacy questions or deletion requests, email [email protected].