flypod

Legal

Privacy

Effective October 20, 2026

flypod collects the minimum data needed to deploy and serve your files, operate accounts, prevent abuse, and keep the service reliable.

Data you provide

Operational data

flypod processes request metadata such as IP address, user agent, timestamps, response status, and security signals to rate-limit requests, detect abuse, troubleshoot failures, and protect the service. Render receipts may include a screenshot, console output, and failed network requests when that feature is enabled.

Analytics and advertising

flypod.dev and docs.flypod.dev use PostHog to count visits and measure how the product is used, and the X (Twitter) conversion pixel to measure whether ads on X bring people here. The X pixel loads a script from X, which may set cookies and receive the page address, your IP address and browser details. When an ad on X leads to an account, flypod may also report that conversion to X from its servers, identified by the ad click ID or by a one-way hash of your email address, never the address itself. Neither runs on sites deployed with flypod, and the X pixel does not run on the account pages.

The flypod command-line tool keeps a random install id on your machine and sends it, with its version number, on its requests, so deploys can be counted per install rather than per site. It also sends one word naming the coding agent that ran it (such as claude_code, or none) and whether it ran in CI, read from environment variables those tools set; the variables themselves are never sent. When a command fails against flypod.dev, it reports the error code and, for uploads that were too large or empty, the shape of the upload: file counts, sizes per kind of file, and whether the folder looks like a project. Never file names, paths or contents. Set DO_NOT_TRACK=1 to turn all of it off. To count deploys from the same person over time, the server also records a keyed hash of the caller's network and kind of client; it does not rotate, and raw IP addresses are not stored in analytics.

Retention

Anonymous sites expire after 14 days and are removed by garbage collection. Owned sites remain until you delete them or your account. Operational records may be kept only as long as needed for security, reliability, and legal obligations.

Sharing

flypod does not sell personal data. Data may be processed by infrastructure, email, analytics and advertising providers that help operate and grow the service, as described above, or disclosed when required by law or necessary to prevent abuse. A deployed site is public to anyone who has its URL unless the product explicitly says otherwise.

Your choices

You can use flypod without an account, delete individual owned sites from the dashboard, or delete your account and its owned sites. Do not upload secrets or personal data you do not have the right to publish.

Contact

You can act on most privacy requests yourself: delete individual owned sites, or delete your account and every site it owns, from the dashboard. For any other privacy question or request, email privacy@flypod.dev.

To report content hosted on a flypod.page subdomain, use the abuse page or abuse@flypod.dev.