Usage Policy

This Policy explains what is and is not permitted when using FlowMaster, including rules for accounts, collaboration, evidence, AI features, and service security.

01 — Scope

Who and what this policy covers

This Usage Policy is effective July 21, 2026.

This Usage Policy is part of the FlowMaster Terms of Service. It applies to content you submit, actions you take, collaboration you enable, and ways you access the Service.

We interpret the policy with the educational and competitive context of debate in mind. Researching, quoting, criticizing, or arguing about war, discrimination, crime, public health, sexuality, self-harm, or other sensitive issues in good faith is generally permitted. The same topic may violate this policy when used to target a person, facilitate wrongdoing, or create an unreasonable risk of harm.

02 — People

Protect safety and treat people with respect

Do not use FlowMaster to:

Sharp clash, evidence comparison, and criticism of public ideas are part of debate. Personal abuse and real-world targeting are not.

03 — Evidence

Preserve academic and evidence integrity

Good-faith mistakes are different from deliberate falsification. Correct an error promptly and preserve the source trail collaborators need to verify shared evidence.

04 — Rights

Respect privacy, consent, and ownership

Responsible quotation and analysis may be protected by fair-use or similar doctrines, but FlowMaster cannot decide that for you.

05 — Access

Use accounts and plans as intended

06 — Integrity

Do not attack or degrade the Service

Do not attempt to disrupt, overload, probe, scrape, or gain unauthorized access to FlowMaster or its providers. Prohibited activity includes:

We welcome good-faith security research. Stop when you encounter private data, avoid disruption, and report the issue promptly using our security contact. Do not demand payment or public disclosure as a condition of protecting users.

07 — AI

Additional restrictions for AI and search

Do not use FlowMaster’s AI, evidence search, file processing, transcription, or agent features to generate or transform content that violates this policy. In particular, do not use them to:

FlowMaster may limit a request when necessary to protect people or systems, even when similar subject matter would be permitted as clearly framed debate research.

08 — Enforcement

How we respond to violations

We consider context, intent, severity, repetition, risk, and efforts to correct a problem. Depending on the situation, we may warn the user, remove or limit content or features, invalidate a code or session, require verification, temporarily suspend an account, restrict a device or network, or permanently terminate access.

We may act immediately when necessary to protect a person, preserve the Service, prevent fraud, or comply with law. We may also preserve relevant records and cooperate with lawful requests. Enforcement against one account does not create an obligation to take the same action in every superficially similar case.

Appeals

If an account is suspended, the suspension email may include a private appeal link tied to that account. Use that link to explain relevant context or a mistake; do not share it. We review appeals in good faith and may uphold, shorten, or reverse an action. Abuse of the appeal channel, false identity information, or repeated duplicate submissions may be disregarded.

09 — Contact

Report a concern

Report suspected abuse or a policy question to support@flowmasterdebate.com. Include the minimum information needed to investigate and do not forward sensitive evidence more broadly than necessary.

For a security vulnerability, use the address and instructions in security.txt. For privacy or data-rights concerns, see the Privacy Policy.