Terms, in plain words.

Using the tools

Every tool on BENIBIX is free to use, for personal and commercial work, with no account. Nothing is locked. Please do not try to break the site, overload it, or use it to harm others.

What you make is yours

The files, scripts, prompts and READMEs a tool produces from your input belong to you. You may use, change and publish them however you like, without credit. The tools run in your browser, so what you type into them is not sent to me, unless you send me feedback privately (see the privacy page). One exception: other people's work a tool hands you, such as the icons in Icon Studio, stays under its own licence.

Provided as they are

The tools are built and tested with care, and explain where their facts come from, but they are provided as they are, without warranty. Read what a tool gives you before you run it, especially scripts and settings that change how other programs behave. I am not liable for damage caused by using the tools or what they produce, except where the law does not allow this to be excluded.

Other companies' names

BENIBIX is independent. It is not made, endorsed or supported by Anthropic, OpenAI, GitHub, Microsoft, Google, Salesforce, Figma, Midjourney, Black Forest Labs, Stability AI, Ideogram, Recraft, ByteDance, Adobe, Pixar, Atlassian, Meta, Apple, Tailwind Labs, Bain & Company, Snowflake, Amazon, Notion, the PostgreSQL Community Association, the DuckDB Foundation, the Python Software Foundation, the OpenJS Foundation, the Linux Foundation, Linus Torvalds, Canonical, Software in the Public Interest, Docker, JetBrains, Grafana Labs, Datadog, Honeycomb, Linear, Oracle, the Rust Foundation, Vercel, Spotify, WakaTime, LeetCode, X, Mastodon or any other company whose products the tools work with. “Anthropic”, “Claude”, “Claude Code”, “Opus”, “Sonnet”, “Haiku” and “Fable” are trademarks of Anthropic PBC, “Sora”, “GPT Image”, “OpenAI”, “Codex”, “ChatGPT” and “DALL·E” of OpenAI, “GitHub” of GitHub, Inc., “Power BI”, “Excel”, “AppSource”, “Azure Maps”, “Microsoft Foundry”, “Windows”, “WSL”, “PowerShell”, “VS Code”, “TypeScript”, “Playwright”, “Fluent”, “Office”, “Microsoft 365”, “Teams”, “Microsoft”, “SQL Server”, “LinkedIn” and “PowerPoint” of Microsoft Corporation, “Gemini”, “Nano Banana”, “Veo”, “Google Sheets”, “Google Cloud”, “Vertex AI”, “Material Symbols”, “Material Design”, “Android”, “Google”, “BigQuery”, “YouTube”, “Go”, “Imagen”, “Looker Studio” and “Google Drive” of Google LLC, “Tableau”, “Heroku” and “Slack” of Salesforce, Inc., “Figma” of Figma, Inc., “Midjourney” and “Niji” of Midjourney, Inc., “FLUX” of Black Forest Labs, “Stable Diffusion” and “SDXL” of Stability AI, “Ideogram” of Ideogram AI Inc., “Recraft” of Recraft, “TikTok” and “Seedream” of ByteDance Ltd., “Firefly” of Adobe Inc., “Pixar” of Pixar, “Confluence” and “Jira” of Atlassian Pty Ltd, “Instagram”, “Facebook” and “React” of Meta Platforms, Inc., “macOS”, “Mac”, “iOS” and “Apple Mail” of Apple Inc., “Tailwind CSS” of Tailwind Labs Inc., “Net Promoter” and “NPS” of Bain & Company, Inc., NICE Systems, Inc. and Fred Reichheld, “Snowflake” of Snowflake Inc., “AWS”, “Amazon Bedrock” and “Amazon Redshift” of Amazon.com, Inc. or its affiliates, “Notion” of Notion Labs, Inc., “PostgreSQL” and “Postgres” of the PostgreSQL Community Association, “DuckDB” of the DuckDB Foundation, “Python” of the Python Software Foundation, “Node.js” of the OpenJS Foundation, “OpenTelemetry” and “Kubernetes” of The Linux Foundation, “Linux” of Linus Torvalds, “Ubuntu” of Canonical Ltd., “Debian” of Software in the Public Interest, Inc., “Docker” of Docker, Inc., “JetBrains” of JetBrains s.r.o., “Grafana” of Raintank, Inc. (Grafana Labs), “Datadog” of Datadog, Inc., “Honeycomb” of Hound Technology, Inc. (Honeycomb), “Linear” of Linear Orbit, Inc., “JavaScript” of Oracle Corporation, “Rust” of the Rust Foundation, “Vercel” of Vercel Inc., “Spotify” of Spotify AB, “WakaTime” of WakaTime, “LeetCode” of LeetCode, LLC, “X” of X Corp. and “Mastodon” of Mastodon gGmbH. They are used only to say what the tools work with or refer to, and every other product name on this site belongs to its owner too. No tool's name starts with another company's mark: a tool for a product is called by its own name first, with the product after it (“Usage Insights for Claude Code”).

Prompt Gallery and Character Prompt Builder: prompts and AI images

Every example image in Prompt Gallery and every picture of a ready-made character in Character Prompt Builder is generated with artificial intelligence (Google Gemini) and both tools say so on every picture, in line with the transparency rules of the EU AI Act (Regulation (EU) 2024/1689, Art. 50). People shown in the images are generated and do not depict real persons.

• The prompt texts (the gallery's prompts and the ready-made characters' answers and prompts) are licensed under Creative Commons Attribution 4.0 (CC BY 4.0). Generating images or videos with a prompt, for private or commercial work, needs no credit. Republishing the prompt texts, for example in another prompt collection, needs credit: the tool's name (“Prompt Gallery” or “Character Prompt Builder”) with a link to this site. A prompt the builder writes from your own answers is yours, like anything else a tool makes from your input.
• The example images may be used for any purpose, including commercial use, without credit. Purely AI-generated images may not be protected by copyright under EU and Austrian law, so I claim none in them. I cannot guarantee an image is free of third-party rights (a trademark, a logo, a resemblance to an existing work or person); check before important commercial use.
• When you publish AI images: disclose that a realistic image is AI-generated, especially of a person (EU AI Act, Art. 50(4)); use photos of other people as a reference only with their permission (GDPR; § 78 Austrian Copyright Act); and follow the terms of the AI tool you use.
• Results from AI tools vary, so a prompt may give a different result from its example. Names such as Gemini, Nano Banana, Imagen, Veo, Midjourney, Niji, Flux, Ideogram, GPT Image, DALL·E, Sora, Firefly, Stable Diffusion, SDXL, Seedream, Recraft and Pixar (in the art style “Pixar-style 3D”) belong to their owners, who do not endorse either tool.

Icon Studio: open-source icons

The icons in Icon Studio are not mine. They come from eight open-source sets (Lucide, Tabler, Phosphor, Fluent, Heroicons, Bootstrap, Iconoir and Material Symbols), and each stays under its set's licence: MIT, ISC or Apache 2.0. All three allow private and commercial use, changes included, for free.

• Keep the set's licence notice with the icons you share or ship, for example in your project's licence or credits file. The licence button in the app lists every set's licence, and a zip from Select puts the licences in it for you.
• Material Symbols is under Apache 2.0, which also asks that changed files say they were changed. An icon you styled (colour, background, shadow, motion) is a changed file, so note the change beside the licence, for example “icons from Material Symbols, recoloured”.
• The styling you add is yours, like anything else a tool makes from your input. The sets' makers do not endorse Icon Studio.

Report Design Studio: palettes and fonts

The themes, layouts and files you make in Report Design Studio are yours, like anything else a tool makes from your input. A few of the colours and fonts in it come from others:

• The colour-blind-safe palettes follow published work: Okabe and Ito's Color Universal Design, Paul Tol's schemes, and ColorBrewer's Set2 and Dark2. The Cool–Warm and Brown–Teal ramps are ColorBrewer's RdBu and BrBG. ColorBrewer's colour schemes are by Cynthia Brewer, Mark Harrower and The Pennsylvania State University, under the Apache License 2.0. Viridis, Magma and Cividis come from Matplotlib and Mako from seaborn. Name the source when you republish one of these palettes as a set.
• The fonts the report preview draws with (Anton, Arimo, Comic Neue, Cousine, Fira Sans, Gelasio, Open Sans, PT Serif and Tinos) stand in for the Windows fonts a theme names, and are under the SIL Open Font License 1.1, which ships with them. A theme only names its font; the font itself comes from the computer that opens the report.

KPI Atlas: definitions, code and benchmarks

The definitions, formulas, DAX, SQL and Excel in KPI Atlas are mine. Copy them into your own reports, dashboards, models and documents, for personal or commercial work, and change them as you need, without credit. A KPI set you export is yours.

• The code uses example table and column names. Check what it returns against your own data before you rely on it, the same way you would check a colleague's measure.
• A benchmark is a typical range as it is often reported, given only where one holds broadly, with its source where it names one (for example the US Bureau of Labor Statistics or the DORA research). It is a starting point for your own target, not a standard, and none of it is financial, medical or legal advice.
• Net Promoter®, NPS® and the related names are trademarks of Bain & Company, Inc., NICE Systems, Inc. and Fred Reichheld, who do not endorse KPI Atlas.

Profile README Studio: pictures, icons, fonts and the workflow

The README, the pictures and the workflow file Profile README Studio makes from your input are yours. Use, change and share them, for personal or commercial work, without credit. A few things inside them come from others:

• The marks on the tech stack tiles are from Devicon, and the marks on badges and logo tiles from Tabler Icons, both under the MIT License. Each picture with such a mark carries that licence notice in a comment; keep it when you copy the picture elsewhere.
• Brand logos and names belong to their owners. A logo on your profile says that you use the product; it does not mean its owner endorses you, your profile or Profile README Studio.
• The typing line carries its font inside the picture, unchanged: one of 20 fonts under the SIL Open Font License 1.1, or Ubuntu Mono under the Ubuntu Font Licence 1.0, both of which allow that. The picture names the font and its licence.
• The cards show the numbers GitHub reports for your account, and the WakaTime card the numbers WakaTime reports; check a figure that matters there. The profile workflow runs in your repository, under your GitHub account and GitHub's terms, with the repository's own token, or with your own token if you add one as the PROFILE_TOKEN secret.
• The visitor counter and Spotify now playing blocks point at services others run (komarev.com and spotify-github-profile.kittinanx.com), under their own terms; they can change or stop at any time.

Statusline Studio: scripts, icons and palettes

The status line scripts and settings that Statusline Studio makes are yours, like anything else a tool makes from your input. They run on your computer, so:

• The install command writes the script to ~/.claude/ and changes ~/.claude/settings.json, after saving copies of the script and settings it replaces with .bak added to their names (for example statusline.sh.bak and settings.json.bak). Read it before you paste it into a terminal, as you would any command.
• A “Custom shell command” segment runs the command you give it every time the line updates. A design opened from someone else's share link shows you each such command and asks before keeping it; only keep the ones you understand.
• The Nerd Font icons are from Nerd Fonts (MIT), which collects open-source icon sets such as Font Awesome (CC BY 4.0), Material Design Icons (Apache 2.0) and Octicons (MIT); each keeps its licence, all listed in the icon licences. A script holds only the icons' code points, never the font.
• The Dracula, Nord, Tokyo Night, Gruvbox, Catppuccin, Solarized and Rosé Pine palettes follow the colours of the open-source themes of those names, whose makers do not endorse Statusline Studio.

Config Studio for Claude Code and Config Studio for Codex: the install script

The files and the install script that Config Studio for Claude Code and Config Studio for Codex make are yours, like anything else a tool makes from your input. They change how Claude Code or Codex behaves on your computer, so:

• The install script writes to ~/.claude/ or ~/.codex/ and to the project you run it in. Before it changes a file it copies it to a dated folder in ~/.benibix-backups/, with an undo.sh that puts everything back. To merge into a settings file you already have it needs Python 3 (3.11 or later for Codex's TOML), and without it it stops before writing anything. Read it before you run it.
• The facts are checked against one version of each program (named on each tool's page) and its documentation. A later version can rename, change or drop a setting, so check one that matters against the program's own documentation.
• A hook, a command rule or an MCP server you add runs on your computer with your rights. Permission rules, the sandbox and the starter packs make mistakes less likely; they are not a guarantee that nothing harmful runs.
• A setup you share, as a plan, a script or a plugin, carries what you put in it. The studios warn about something shaped like a key or a token, but look through what you send before you send it.

Usage Insights for Claude Code: your history and your team's

Usage Insights for Claude Code reads the files Claude Code writes on your computer, in your browser. Its numbers are only as good as those files:

• Claude Code's file format is its own and changes between versions, so after an update a number can be missing or off until the tool catches up. Check a figure that matters against Claude Code's own record before you rely on it.
• The cost is what Claude Code records at API prices. On a subscription it is not what you paid, and it is never a bill. Time saved and active time are estimates, and the dashboard labels them as such.
• The Team view adds up files that people export and hand over themselves; nothing passes through me. If you collect colleagues' files at work, you decide what is collected and what it is used for, and the rules on monitoring at work apply to you: in Austria, for example, a measure that checks how employees work may need the works council's agreement (§ 96 ArbVG) or, without one, each person's consent (§ 10 AVRAG). Tell people what the files hold before they export them. Hiding groups under five people helps, but does not replace that.

Usage Insights for Codex: your history and your team's

Usage Insights for Codex reads the session files Codex writes on your computer, in your browser. Its numbers are only as good as those files:

• Codex's file format is its own and changes between versions, so after an update a number can be missing or off until the tool catches up. Check a figure that matters against Codex's own record, such as /status, before you rely on it.
• The usage limits are the shares of your 5-hour and weekly windows that Codex recorded at the time, not your plan's terms. Session files hold no prices, so the dashboard shows no cost unless an events file you load carries one. Time saved and active time are estimates, and the dashboard labels them as such.
• The Team view adds up files that people export and hand over themselves; nothing passes through me. If you collect colleagues' files at work, you decide what is collected and what it is used for, and the rules on monitoring at work apply to you: in Austria, for example, a measure that checks how employees work may need the works council's agreement (§ 96 ArbVG) or, without one, each person's consent (§ 10 AVRAG). Tell people what the files hold before they export them. Hiding groups under five people helps, but does not replace that.

Changes

These terms may change as the site grows; this page always has the current version. Who runs the site, and how to reach me, is in the imprint.