Acceptable Use Policy

This policy forms part of our Terms of Service and applies to everyone using FlowIn, on the free template library and on paid access alike.

• Plan, describe, or document unlawful activity, or any process whose purpose is to cause harm to people.
• Write descriptions intended to produce sexual, violent, harassing, hateful or abusive content, or content that demeans a person or a group.
• Attempt to drive the underlying model off-task — prompt injection, jailbreaking, or any attempt to make FlowIn emit something other than a process diagram.
• Access FlowIn by automated or scripted means, scrape it, or try to circumvent its rate limits.
• Resell FlowIn’s output as a service, or present FlowIn’s generation capability as your own product. Using the diagrams you make in your own work, including commercially, is fine and expected — reselling the generator is not.
• Submit other people’s confidential or personal data that you have no right to share.

We may suspend or end access that breaks this policy. There is no automated content surveillance behind that sentence — we hold no descriptions to surveil — so in practice enforcement follows a report or an operational signal such as scripted traffic.

To report misuse, write to support@4io.ai. We answer within three business days.

This is worth stating precisely, because “AI product” is often assumed to mean generative media. FlowIn’s pipeline is: your words go to a large language model, which returns FlowScript — a structured text description of a graph. That text is validated against a fixed schema, and only then does FlowIn draw it, using its own renderer.

The model produces text, never pixels. The renderer can express exactly one vocabulary: labelled boxes, decision points, and the arrows between them. There is no prompt that makes it draw a photograph, a face, or anything other than a flow diagram — not because we filter such prompts, but because the schema has no way to represent them.

Content safety on the text step is additionally covered by the model provider’s own safety systems, which apply to every request FlowIn sends.

The date at the top of this page shows when this policy last changed. See also our Terms of Service and Privacy Policy.