Skip to content

Unofficial parody. The software is real. Unofficial parody of infloww.com. Not affiliated with Infloww. The software is real; the jokes are ours.

Inflowwww
Menu

Privacy policy

This site sets no cookies, loads nothing from third parties and runs no analytics. The app keeps each agency's data in its own database.

This website

  • It is static HTML and CSS, plus one small script for the copy buttons, the pricing slider and the sign-in forms, all served from this site.
  • It sets no cookies and stores nothing in your browser.
  • It loads no fonts, scripts or images from anyone else, and runs no analytics or tracking pixels.
  • Its sign-up and sign-in forms send your username and password straight to the Inflowwww app at https://app.inflowwww.com, never to this site. When the app sends you back with an error, the error and your username ride after the # in the address, which your browser does not send to this site's host; the password is never in the address.

Hosting

GitHub Pages serves this site. GitHub handles every request to serve it and keeps its own logs, under the GitHub General Privacy Statement. We don't get those logs. Links to the repository take you to GitHub, under the same statement.

The self-hosted app

Inflowwww runs on the server it is installed on. Its database (service/chatterly.db, SQLite) and the captured sessions (service/sessions/) live there.

One app serves many agencies. Each agency account sees only its own creators and their chats. The exception: whoever runs the app can make an account the master, and the master sees every agency.

The project receives no data from your install. The items below send data out only when you use them. OnlyFans itself is not on the list: OnlyFans traffic goes through the proxies you configure, and through the server's own IP when none is set.

  • The LLM keys (in .env or on the Creators page): requests go to that provider, under its terms.
  • Fan photos: with DEEPINFRA_API_KEY set, photos fans send are described by DeepInfra by default, together with the fan's recent messages. That covers every fan who has paid and a few reads for fans who haven't, whether or not an automation is on. The per-account setting image_describe_enabled turns it off.
  • The vault describe pass: with DEEPINFRA_API_KEY set, it sends your vault's images to DeepInfra.
  • The tunnel profile: traffic goes through a Cloudflare quick tunnel.
  • The chat's translate toggle: message text goes to Google Translate's free endpoint. It needs no key, so nothing else warns you.
  • The proxy check: it calls api.ipify.org and ipinfo.io to see which IP a proxy exits from.
  • Vault Pro's Google Drive import, if a Drive key is set: the Drive links you paste go to Google's Drive API. The key can't be set from the dashboard on a fresh install (that card needs an admin account, which the current build never creates); a GOOGLE_DRIVE_API_KEY in the relay's environment, for example in docker-compose.override.yml, also turns it on.
  • GIFs: the dashboard loads GIFs in chats from media.giphy.com, and the incoming-message hook asks giphy.com for the title of each GIF a fan sends, by default.
  • Webhooks: an owner-configured webhook can forward events, including fan messages, to a URL you choose.
  • The legacy Google Sheets export automation, if you turn it on: it writes to Google Sheets.
  • Building the app image downloads its font from Google Fonts. At runtime the font is served from your server.

Questions

Contact us. Others can read it, so leave out anything personal.