Research boldly. Use responsibly.

01 — Scope

Who and what this policy covers

In shortThese rules apply to every FlowMaster account, feature, API request, team space, shared flow, and AI request.

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:

• threaten, stalk, bully, extort, intimidate, or coordinate targeted harassment against a person or protected group;
• promote hatred or dehumanization, or praise violence against people because of protected characteristics;
• create, solicit, possess, or distribute sexual content involving anyone under 18, or facilitate grooming, exploitation, trafficking, or non-consensual sexual content;
• encourage suicide, self-harm, eating-disorder behavior, or other imminent physical harm, outside of responsible educational, prevention, or support contexts;
• impersonate another person or organization deceptively, or misrepresent affiliation with a school, team, tournament, or FlowMaster; or
• plan, instruct, or facilitate violence, abuse, theft, fraud, weapon construction, illegal drug production, or other serious wrongdoing.

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

In shortUse AI to find and understand material—not to invent proof.

• Verify the original. Open the source, confirm the author, publication, date, quotation, surrounding context, and any qualifications before relying on a search or AI result.
• Do not fabricate. Never present generated, altered, composite, or nonexistent text as a real quotation, card, study, statistic, ruling, source, or URL.
• Do not distort. Do not deliberately remove words, context, methodology, dates, or qualifications in a way that reverses or materially misrepresents a source.
• Follow event rules. You are responsible for league, tournament, school, classroom, disclosure, citation, clipping, and generative-AI rules that apply to you. FlowMaster cannot determine eligibility or admissibility.
• Respect assessment rules. Do not use FlowMaster to cheat on an exam, graded assignment, authorship requirement, or competition rule that prohibits assistance.

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

• Do not expose private personal information, credentials, financial information, precise location, private communications, or sensitive records without a lawful and legitimate reason.
• Do not record, upload, or transcribe another person unless you have the consent required by your tournament, school, venue, and applicable law. Recording laws differ by location; you are responsible for checking them.
• Upload, quote, distribute, and share only material you own or are permitted to use. Respect copyright, licenses, paywalls, confidentiality, and source-access restrictions.
• Do not use a share code or team key you were not authorized to receive, and do not forward private appeal links or account-recovery codes.
• Do not use someone’s name, image, team identity, or profile to impersonate them or falsely attribute content to them.

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

In shortCollaboration is shareable; identity and paid access are not.

• Do not share, lend, sell, rent, or publicly post an account password, session token, verification code, Apple transaction record, team key, or other access credential.
• Do not let multiple people rotate through one individual Pro account. Use FlowMaster’s flow-sharing features or obtain the appropriate team seats.
• Do not resell access, create account farms, use disposable accounts to evade restrictions, or manipulate referrals, gifts, trials, refunds, seats, or plan limits.
• Do not access another account without authorization, even if credentials or a token were accidentally exposed.
• Do not circumvent a suspension, ban, device verification, rate limit, feature gate, collaboration role, or entitlement check.

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:

• malware, credential theft, phishing, denial-of-service activity, destructive payloads, or attempts to compromise users, staff, infrastructure, databases, storage, or real-time rooms;
• automated requests, bulk extraction, crawlers, or bots that are not expressly authorized and that burden the Service, collect user data, or bypass rate and usage limits;
• testing another user’s account or private data, exploiting a vulnerability beyond what is reasonably needed to demonstrate it, or retaining data encountered during research; and
• reverse engineering, tampering, or circumvention of technical protections except to the limited extent applicable law expressly permits it.

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:

• produce convincing fabricated evidence, forged citations, deceptive impersonation, non-consensual intimate imagery, or fraudulent documents;
• identify, track, profile, or make high-impact decisions about a person using sensitive personal data;
• develop malicious code, evade security controls, steal credentials, or automate abuse of another service;
• generate targeted threats, harassment, exploitative sexual content, or instructions intended to cause serious harm; or
• evade provider safety measures by encoding, fragmenting, or disguising a prohibited request.

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.