---
title: "Fluxer and AI: how it's built and your messages"
description: "Fluxer isn't vibe-coded and never uses your messages or anything else you post to train, fine-tune or evaluate AI models, and outside contributors follow a published LLM usage policy."
url: "https://fluxer.com/help/fluxer-and-ai"
language: "en"
last_updated: "2026-11-01"
category: "About Fluxer"
---

> Index of Fluxer's official pages for AI agents: https://fluxer.com/llms.txt
> Links to Fluxer pages go to their Markdown versions when they have one. For other Fluxer help, policy or blog links, remove any #section part and add .md to the end.

# Fluxer and AI: how it's built and your messages

Fluxer isn't vibe-coded and never uses your messages or anything else you post to train, fine-tune or evaluate AI models, and outside contributors follow a published LLM usage policy.

Fluxer isn't vibe-coded, and it never uses your messages or anything else you post to train, fine-tune or evaluate AI models, as [section 3.1 of our terms](https://fluxer.com/terms.md) says.

## Is Fluxer vibe-coded?

No, [Fluxer isn't vibe-coded](https://fluxer.com/help/is-fluxer-vibe-coded.md). Our AI stance page [defines vibe coding](https://fluxer.com/ai-stance.md) and says how changes are made, and Fluxer's [source code and its full history](https://github.com/fluxerapp/fluxer/commits/main) are public on GitHub.

## Can contributors use AI tools?

Outside contributors on GitHub follow our [anti-slop policy](https://fluxer.com/ai-stance.md). They can use an LLM privately to research and plan, but they can't submit code, text, images, audio or video an LLM made, even after editing. The one exception is a disclosed machine translation of their own writing, and the [LLM usage policy](https://github.com/fluxerapp/fluxer/blob/main/.github/LLM_USAGE_POLICY.md) in the repository says exactly what is allowed.

## Why does Fluxer have so many lines of code?

Most of the lines that change in Fluxer's repository are translations of the app's text into 34 languages, as [git's counts](https://fluxer.com/ai-stance.md) over five weeks in 2026 show.

## Does Fluxer use AI to detect explicit images?

Fluxer uses a small image classifier to blur or restrict explicit images, and it isn't generative AI or an LLM. [Section 5 of our privacy policy](https://fluxer.com/privacy.md) says exactly what it does and what it doesn't do, and your [sensitive media settings](https://fluxer.com/help/nsfw-detection.md) decide what you see.

## Does Fluxer train AI on my messages?

No. [Section 3.1 of our terms](https://fluxer.com/terms.md) says Fluxer never uses your content to train, fine-tune or evaluate AI or machine learning models, and never sells or licenses it for anyone else's use. Our AI stance page [says the same](https://fluxer.com/ai-stance.md) about everything you post.

## Will Fluxer use AI on public forums?

No. Public forums are planned in [Roadmap 2026](https://fluxer.com/blog/roadmap-2026.md), and the roadmap says Fluxer won't use AI or LLMs to write, summarize or choose anything on a public forum. A public page will show only what people wrote themselves, with nothing generated.

## Why does Fluxer's GitHub history start with one huge commit?

Fluxer was built in private for years, starting as [Hampus's high school project](https://fluxer.com/ai-stance.md). Its GitHub history starts with one commit of nearly 1.5 million lines, dated January 1, 2026.

[About 800,000 of those lines are translations](https://fluxer.com/ai-stance.md), and the rest is work from before the code was public. Many projects start their public history with one commit.

---

Canonical page: https://fluxer.com/help/fluxer-and-ai

Last updated on November 1, 2026