InfraFlowDocsSign in

Last updated 13 October 2026

Privacy policy

The short version: InfraFlow keeps what it needs to work, nothing for advertising, and no tracker.

01What an account holds

  • Your name and email address. Your password is kept only as a hash; if you sign in with GitHub, the identifier of that account.
  • For each device signed in: when, from which IP address and with which browser, so that you can end the sessions you do not recognise.
  • An activity log of who changed what in a workspace, with the IP address, readable by that workspace's members.
  • If you take a paid plan, payment goes through Mollie: your card never reaches our servers. We keep the invoices.

02What you put on the platform

Your code, images, databases, buckets, logs and variables are yours. Variables and other secrets are encrypted. We do not read, sell or reuse any of it; it is accessed only to keep the platform running or to answer a request you made. If it contains other people's personal data, you are responsible for it.

03Visitors of what you host

Requests to what you host pass through our edge, which records the time, IP address, country, path, status and user agent of each: that is what your Requests, Analytics and firewall pages show, and what lets the firewall refuse abusive traffic. Firewall events are kept 24 hours. The country is looked up on our own servers, and the browser check and CAPTCHA are our own: no third party is called.

04Cookies and trackers

Only what the site cannot work without: ifl_session keeps you signed in, and ifl_oauth lives for the few minutes of a sign-in through GitHub. No analytics, no advertising, no tracker from anyone else.

05Your rights

You can see, correct and delete most of your data from the dashboard. For anything else, including a copy of your data or the deletion of your account, write to hello@infraflow.app from the address of the account. If you live in the European Union, the GDPR gives you these rights, and that of complaining to your data protection authority.