“Information in your applications belongs to you, and you are responsible for it, as well as for making sure that your content complies with our Terms of Service.”
This analysis describes what Fly.io's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This clause assigns compliance responsibility to the user rather than to Fly.io for application content, meaning users bear the risk of Terms of Service violations arising from their application data.
Interpretive note: The clause contains two independent propositions: ownership of application information and user responsibility for compliance. The canonical claim states the primary proposition (responsibility/compliance); ownership is recorded in omitted_material.
The updated policy now explicitly discloses that Fly.io uses third-party fraud-prevention services that collect device and browser signals (and set cookies) when users create accounts or sign in. Unlike analytics, which users can opt out of via cookie preferences or Google's opt-out tool, this fraud-prevention processing cannot be opted out of. The company states its legal basis is legitimate interest in protecting the platform and users. You can opt out of analytics collection, but fraud-prevention data collection will apply to all account creation and sign-in activity.
View change record →The updated policy discloses that Fly.io now uses PostHog analytics on public, logged-out pages (marketing pages, blog, documentation) in addition to Google Analytics. PostHog stores a random identifier and pageview data such as URL, referrer, and device type in the EU, but does not link this data to user names, email addresses, or Fly.io accounts, and does not capture session recordings, clicks, keystrokes, or form contents. Analytics data is retained for a maximum of 12 months. For users in the EEA, UK, or Switzerland, both Google Analytics and PostHog require explicit consent before being set; you can withdraw consent at any time using the 'Cookie preferences' link in the page footer or by using Google's opt-out browser add-on.
View change record →You are responsible for your application content and must ensure it complies with Fly.io's Terms of Service; Fly.io does not assume that responsibility.
How other platforms handle this
We kindly request you do not disclose certain Data, such as passwords, credit card numbers, PINs or other confidential data during your use of our Services.
Alter or modify any part of the content or services offered on or through the Websites and Platforms
You may provide links to this Web Site, provided that (a) you do not remove or obscure, by framing or otherwise, any portion of this Web Site, including any advertisements, terms of use, copyright notice, and other notices on this Web Site, (b) you immediately deactivate and discontinue providing li...
"Information in your applications belongs to you, and you are responsible for it, as well as for making sure that your content complies with our Terms of Service.Excerpt from Fly.io's Privacy Policy
Get the weekly coverage letter
Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.
This clause assigns compliance responsibility to the user rather than to Fly.io for application content, meaning users bear the risk of Terms of Service violations arising from their application data.
You are responsible for your application content and must ensure it complies with Fly.io's Terms of Service; Fly.io does not assume that responsibility.
ConductAtlas has identified this type of provision across 272 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Fly.io.