Document contents

Governing document

ModFlow Terms of Service

Terms governing authorized access to and use of the ModFlow Discord moderation bot and dashboard.

Effective
Last updated

Read first

Plain-language summary

ModFlow gives authorized Discord server teams tools for moderation, cases, evidence, appeals and conversations, Watchlist review, assignments, Discord event logging, recordings and transcripts, staff workflows, analytics, dashboard administration, optional provider connections, and billing. MIRA and other controlled previews remain subject to separate availability, legal, provider, plan, and permission gates.

  • Customers and Authorized Users must use ModFlow lawfully, secure access, configure least privilege, give required notices, obtain required consent, and keep humans responsible for moderation decisions.
  • Affected Users do not accept these Terms merely because a Discord server uses ModFlow. The Privacy Policy explains how their information may be processed and how to make a request.
  • ModFlow is provided on an as-is and as-available basis. Important limits, including the liability cap and retention limits, appear in the complete Terms.

This summary is only a guide. The complete Terms of Service controls if it conflicts with this summary.

Section 01

Agreement and acceptance

These Terms of Service are an agreement between ModFlow and each Customer and Authorized User that accesses or uses ModFlow. They take effect on July 17, 2026. A Customer accepts them by installing, authorizing, configuring, purchasing, or continuing to use ModFlow for a Discord server. An Authorized User accepts them by accessing ModFlow commands, the dashboard, or other staff features with the Customer's permission.

  1. Customer means the person or organization that installs, configures, purchases, or authorizes ModFlow for a Discord server.
  2. Authorized User means a server owner, administrator, moderator, staff member, or other person whom the Customer permits to access ModFlow commands or dashboard features.
  3. Affected User means a Discord member whose identifiers, messages, activity, evidence, voice data, or moderation history is processed because a Customer uses ModFlow.

An Affected User does not become a Customer, is not treated as an Authorized User, and does not accept these Terms merely because a server installed ModFlow or processed that person's information. If these Terms conflict with a right or protection that applicable law does not allow the parties to waive, that non-waivable law controls to the extent of the conflict.

Section 02

Operator and contact

The service is publicly operated as ModFlow. Questions about these Terms, legal or safety notices, copyright complaints, and privacy or data-rights requests may be sent to [email protected]. That public name and email are the official contact details for this service.

Email is not guaranteed to be confidential or immediately received. Do not send passwords, authentication tokens, payment card details, or unrelated sensitive evidence by ordinary email. Include enough information to identify the relevant server and request without unnecessarily exposing other people.

Section 03

Eligibility and authority

A Customer representative must be at least 18 years old or the age of legal majority where the representative lives, whichever standard applies, and must have authority to bind the Customer and configure the relevant Discord server. Authorized Users must meet Discord's applicable age requirements and any additional requirements imposed by the Customer or applicable law.

Customers and Authorized Users must provide accurate account and configuration information and must not misrepresent identity, authority, ownership, staff status, or permission to access a server. If authority ends, access and credentials must be removed promptly.

Section 04

What ModFlow provides

ModFlow is a Discord-native moderation service. Depending on configuration and availability, it may provide bot commands, moderation cases and sanctions, evidence capture, appeal and Jail conversations, staff notes and assignments, watchlists, native Discord event logging, audit history, trusted-network workflows, dashboard administration, voice recording, live captions and transcription, transcript and media access, activity or behavior analytics, selected Google or Microsoft assignment-file imports, AI-assisted Case investigation, support functions, and optional paid-plan management.

  • Some features are optional, experimental, alpha, beta, limited to particular servers, or dependent on Customer configuration.
  • Storage may use local systems, Cloudflare R2, or other controlled storage according to the active provider configuration; use of one option does not mean every deployment has completed a provider cutover.
  • Transcription, error monitoring, billing, Google or Microsoft file connections, OpenAI-assisted investigation, and other integrations operate only when their providers and related settings are enabled.
  • MIRA is coming soon and default-disabled; Moderator Performance Scorecards are a default-off controlled preview; Automation Rules currently provide stored configuration without a confirmed runtime evaluator; and experimental or placeholder features are not general-availability promises.

ModFlow may add, remove, limit, or change features as the service develops. The description in these Terms is not a promise that every feature is available to every server at all times.

Section 05

Human responsibility

ModFlow supports staff judgment but does not replace it. Customers remain responsible for their community rules, the people they authorize, the evidence they rely on, the notices they provide, the sanctions they impose, the appeals they decide, and the legality, fairness, proportionality, and accuracy of each moderation decision.

Authorized Users must review relevant context and correct errors before acting. A MIRA finding or citation, staff Scorecard, generated score, summary, Watchlist alert, transcript, route, recommendation, or imported record may be incomplete, biased, or wrong and must not be treated as an automatic command to punish a person or change a staff role. ModFlow does not act as the Customer's moderator, legal adviser, investigator, employer, or final decision-maker.

Section 06

Discord and third-party terms

Discord's Terms of Service, Privacy Policy, Community Guidelines, Developer Terms of Service, Developer Policy, and other applicable platform rules continue to apply. Customers and Authorized Users are responsible for following them and for monitoring platform changes that affect their use of ModFlow.

ModFlow is an independent service. It is not Discord, and Discord does not sponsor, approve, certify, or endorse ModFlow. Other providers have their own terms and privacy practices. Nothing in these Terms grants permission to violate another service's rules or to access Discord data beyond the permissions and purposes lawfully available to the Customer.

Section 07

Accounts, OAuth, and security

The dashboard may use Discord OAuth to authenticate a person, retrieve authorized identity and guild information, maintain a session, and refresh or revoke access as needed. Customers and Authorized Users must use their own authorized accounts, protect Discord credentials, sessions, devices, recovery methods, and bearer links, and must not share credentials or bypass access controls.

  • Grant dashboard and bot access only to people who need it and remove access promptly when duties change.
  • Do not copy OAuth tokens, session cookies, bot tokens, provider secrets, or confidential links into public channels, tickets, screenshots, or untrusted tools.
  • Report suspected compromise, unauthorized access, or mistaken disclosure promptly to the Customer and, when ModFlow may be affected, to [email protected].

Actions taken through an authenticated or otherwise authorized account may be treated as authorized until ModFlow receives and can act on a credible compromise report. ModFlow may invalidate access or require reauthentication when reasonably necessary for security.

Section 08

Customer configuration duties

Customers control substantial parts of how ModFlow operates in their servers and must configure the service responsibly. A default, example, or technically available option is not a legal conclusion that the option is appropriate for every server.

  • Use least-privilege Discord roles, bot permissions, dashboard permissions, channels, and staff teams.
  • Offboard former staff, rotate exposed secrets, review access periodically, and keep owner and emergency contacts current.
  • Choose evidence, recording, transcript, snapshot, analytics, retention, native event-log, Jail and appeal conversation, Watchlist, No Contact, and trusted-network settings that match the Customer's stated purposes and obligations.
  • Review trusted-server relationships, staff access, confidential links, Discord log destinations, retention needs, Google or Microsoft connections, AI investigation approval, and enabled providers on a recurring basis.
  • Test important workflows and maintain appropriate independent records or backups instead of treating ModFlow as the only source of truth.

Section 10

Acceptable use

ModFlow may be used for legitimate, authorized community moderation, safety, support, audit, accountability, and community-management purposes consistent with these Terms, the Customer's disclosed rules, Discord's requirements, and applicable law.

  • Document and review moderation incidents, evidence, sanctions, appeals, and staff actions.
  • Coordinate authorized staff work, improve consistent enforcement, investigate abuse, and protect users or service integrity.
  • Create consent-noticed recordings, captions, or transcripts for legitimate moderation, support, accessibility, or review purposes.
  • Use aggregated or appropriately de-identified information for service operation and improvement where appropriate.
  • Manage authorized server configuration, access, subscriptions, support, and legally required requests.

Section 11

Prohibited conduct

Customers and Authorized Users must not use ModFlow, its data, or access obtained through it to harm people, evade safeguards, interfere with the service, or violate law or platform rules.

  • Do not conduct unlawful or covert surveillance, stalk, harass, intimidate, shame, discriminate against, retaliate against, dox, exploit, or threaten any person.
  • Do not collect credentials, impersonate others, gain unauthorized access, expose secrets, publish confidential links, or misrepresent evidence or staff authority.
  • Do not scrape, bulk extract, resell, broker, repurpose, or combine Discord or ModFlow data for an unauthorized purpose.
  • Do not evade rate limits, permissions, consent controls, feature gates, provider restrictions, or security measures.
  • Do not upload malware, disrupt infrastructure, probe without authorization, overload services, or use ModFlow to facilitate fraud or other abuse.
  • Do not violate Discord's rules, another provider's terms, intellectual-property rights, privacy rights, or other third-party rights.

Section 12

Prohibited sensitive submissions and uses

Do not submit passwords, authentication tokens, private keys, payment card numbers, bank credentials, government identification documents, or protected health information to ModFlow unless a narrowly defined, lawful workflow expressly requires the information and ModFlow has authorized that workflow in writing. Ordinary moderation tools are not designed as vaults for those materials.

Do not use Discord data, moderation records, allegations, profile signals, voice data, or derived analytics to make or support decisions about employment, housing, credit, lending, insurance, education admission, public benefits, or a person's protected-class status. Do not infer highly sensitive traits or use ModFlow to create secret eligibility or reputation systems outside legitimate community moderation.

Section 13

Customer content and evidence

Customers and Authorized Users remain responsible for the messages, attachments, recordings, transcripts, notes, allegations, rules, appeals, selected Google or Microsoft files, public-web pages, images, configurations, and other material they submit, select, import, capture, or direct ModFlow to process. They must have the rights and authority needed to use that material and must avoid unnecessary or excessive collection.

The Customer grants ModFlow a limited, non-exclusive, worldwide license to host, reproduce, transform, transmit, back up, and display Customer content only as reasonably necessary to provide, secure, support, maintain, troubleshoot, and protect ModFlow; respond to authorized requests; and comply with law. This license ends when the material is deleted from active systems except where continued retention is permitted for backups, legal holds, disputes, security, or other surviving obligations.

Customers should preserve original source material when authenticity, chain of custody, or later review matters. ModFlow does not guarantee that imported or captured evidence is complete, admissible, authentic, or sufficient for a particular decision.

Section 14

Message content and moderation records

ModFlow may process message content, excerpts, links, embeds, reactions, attachments, metadata, and edit or delete versions when needed for an enabled moderation feature, explicit evidence tracking, Case review, appeal DM or internal note, dashboard Jail relay, configured native or external moderation log, assignment, Watchlist review, AI-assisted safety investigation, transcript, or audit trail. Core evidence listeners may continue even when broad general snapshots are disabled.

Broad message snapshots are disabled by default and require explicit enablement and appropriate review. Customers must not enable or use them for an undisclosed purpose. ModFlow does not authorize moderation records or customer message content for unrelated advertising, data brokerage, or training a general-purpose model.

A message edited or deleted in Discord may remain in a case, evidence record, external log, audit trail, backup, or transcript when preservation is necessary and authorized. Discord-side deletion does not by itself prove that every separate copy has been deleted.

Section 15

Voice recording and transcription

Voice recording, live captions, and transcription may be used only for authorized sessions with clear advance notice and any consent required by law, Discord rules, provider terms, or the Customer's commitments. Customers must limit capture to eligible speakers and legitimate purposes and must not conduct covert, unlawful, or unnecessarily broad recording.

When live transcription is enabled, consented speaker audio may be transmitted to Deepgram for speech-to-text processing, and ModFlow may store transcript text, captions, confidence information, speaker timelines, and related artifacts. Deepgram is not used for every session. Provider processing depends on the active configuration and provider availability.

Recordings and transcripts may be delayed, incomplete, mislabeled, unavailable, or inaccurate. Authorized Users must review the underlying context before relying on them. A person who withdraws consent or leaves a session may stop future eligible capture where the workflow supports it, but that action does not necessarily erase lawfully retained case evidence, completed transcripts, backups, or records needed for disputes or legal obligations.

Section 16

Behavior analytics

If appropriately enabled, analytics may derive message counts, language or style signals, channel activity, voice duration, Watchlist heat and pattern summaries, risk or readiness summaries, and controlled staff Scorecard dimensions. These signals can be incomplete, biased, stale, or wrong. Missing evidence is not a zero score. ModFlow does not authorize solely automated punishment, staff role changes, or a decision with legal or similarly significant effects based on a profile or performance score.

Section 17

Trusted-network sharing

A Customer may choose to form a trusted network with another Discord server only through mutual administrator opt-in. Depending on the enabled workflow, authorized staff in the participating server may receive the Discord member identifier and a newly prepared, redacted summary of relevant moderation context. Raw staff notes, raw evidence, attachments, transcripts, internal discussion, and private Discord message or channel references are not shared through this workflow.

Each Customer is responsible for a lawful basis, accurate notice, proportional sharing, appropriate recipients, access control, correction, and handling requests relating to its own disclosure and use. A recipient becomes responsible for the copies it receives and must not use them for unrelated surveillance, harassment, discrimination, retaliation, or public shaming.

Revoking a trusted relationship stops future sharing to the extent supported by the workflow, but it cannot automatically retract copies already lawfully received, included in a case, exported, backed up, or retained for an independent legal reason.

Section 19

Privacy and data processing

The ModFlow Privacy Policy is incorporated into these Terms and describes categories of information, sources, purposes, recipients, retention, choices, and request procedures. Customers must read it before configuring the service and must provide any additional server-specific notice for their own processing.

Roles depend on context. A Customer generally determines its server's moderation purposes, staff access, enabled features, evidence choices, trusted relationships, and decisions. ModFlow operates the service and may process information on the Customer's instructions for those workflows while also determining limited purposes such as authentication, security, billing, support, legal compliance, and protection of the service. Labels such as controller, business, processor, or service provider apply only where the relevant law and facts make them applicable.

Section 20

Third-party providers

ModFlow depends on Discord and may use hosting infrastructure including AWS where used, Cloudflare R2 where configured, Deepgram when transcription is enabled, Sentry when monitoring is configured, Stripe when billing is used, OpenAI only for an approved MIRA investigation, Google or Microsoft when an authorized assignment-file connection is used, and controlled backup or storage operators. The active providers and storage path can vary by deployment and feature.

Third-party systems are governed by their own terms, privacy practices, availability, limits, and security controls. ModFlow is not responsible for a provider outage, API change, account restriction, data loss, or other provider conduct beyond responsibility that applicable law does not permit ModFlow to exclude. Customers must not assume a provider feature or setting is available merely because it is described in these Terms.

Section 22

Beta, changes, and availability

ModFlow and particular features may be described as alpha, beta, controlled preview, coming soon, experimental, configuration only, working-tree only, placeholder, or otherwise unfinished. Those labels are separate from plan inclusion and deployment. Such features may contain defects, change without compatibility guarantees, produce incomplete results, or be discontinued. Customers should not rely on an unfinished feature as the only method for a critical legal, safety, evidence, or business function.

ModFlow may perform maintenance, impose reasonable usage or security limits, change integrations, and respond to Discord API, policy, permission, or data-access changes. There is no uptime, response-time, feature-continuity, or uninterrupted-access guarantee. Where practicable, material changes will be communicated through the service, documentation, dashboard, Discord, or the contact information available to ModFlow.

Section 23

Suspension and termination

ModFlow may restrict, suspend, or terminate access when reasonably necessary to address abuse, security compromise, legal or safety risk, nonpayment, platform or provider requirements, excessive load, violation of these Terms, discontinuation, or protection of ModFlow, users, providers, or third parties. Urgent action may occur without advance notice when notice would increase risk or be impracticable.

A Customer may remove ModFlow from its server, revoke permissions, cancel an eligible subscription, or stop using the service. Removal or termination stops future service processing to the extent the workflow and platform permit but does not automatically delete every case, moderation record, evidence item, recording, transcript, audit record, billing record, backup, legal hold, or copy held by an independent recipient.

Terms that by their nature should survive continue after termination, including provisions about ownership, Customer content licenses needed for retained copies, confidentiality, payment obligations, disclaimers, liability limits, indemnity, disputes, retention, and general interpretation.

Section 24

Intellectual property, feedback, and notices

ModFlow and licensors retain rights in ModFlow, including software, service design, documentation, branding, and original content, subject to third-party and open-source rights. These Terms grant only a limited, revocable, non-transferable right to use available ModFlow features for an authorized Customer's internal community-management purposes.

Customers and Authorized Users may not copy, sell, sublicense, reverse engineer except where that restriction is prohibited, remove notices, misuse ModFlow branding, imply endorsement, or use confusingly similar marks. If a person voluntarily provides feedback, that person grants ModFlow a perpetual, worldwide, royalty-free right to use and incorporate the feedback without an obligation to compensate or attribute it.

A copyright or other intellectual-property complaint should identify the protected work, the challenged material and its location, the complainant's contact details and authority, a good-faith explanation, and any statement or signature required by applicable law. Send the complaint to [email protected]. ModFlow may remove or restrict material while reviewing a credible notice.

Section 25

Disclaimers

ModFlow does not guarantee a moderation outcome, the truth of an allegation, evidence completeness or admissibility, transcript or caption accuracy, profile accuracy, data recovery, provider performance, compatibility with every Discord change, uninterrupted operation, or that every defect or security risk will be detected or corrected. Some jurisdictions do not allow particular disclaimers, so those disclaimers apply only to the extent permitted.

Section 26

Limitation of liability

To the maximum extent permitted by applicable law, ModFlow and any service contributors will not be liable for indirect, incidental, special, exemplary, punitive, or consequential damages, or for lost profits, revenue, goodwill, opportunities, data, evidence, or use, arising from or related to ModFlow, even if advised that such loss was possible.

To the maximum extent permitted by applicable law, the aggregate liability of ModFlow for all claims arising from or related to ModFlow or these Terms will not exceed the greater of the fees the Customer paid for ModFlow during the 12 months preceding the event giving rise to the claim or USD 100.

These exclusions and the cap do not apply to liability that applicable law does not permit the parties to exclude or limit. They apply regardless of the legal theory and reflect the allocation of risk on which the service is offered.

Section 27

Indemnity

To the extent enforceable under applicable law, each Customer will defend, indemnify, and hold harmless ModFlow and service contributors from third-party claims, damages, judgments, penalties, costs, and reasonable legal fees arising from the Customer's or its Authorized Users' unlawful configuration or use, Customer content, failure to provide required notice or consent, moderation decisions, trusted-network disclosures, breach of these Terms, or violation of law or third-party rights.

ModFlow will give reasonably prompt notice of a covered claim when practicable and may participate with counsel of its choice. A Customer may not settle a claim in a way that admits wrongdoing by, imposes an obligation on, or restricts ModFlow without written consent. This section does not require indemnity where prohibited by law.

Section 28

Informal dispute notice

Before filing a non-urgent dispute against ModFlow, a Customer or Authorized User should send a good-faith written notice to [email protected] describing the issue, relevant server or account, requested resolution, and supporting facts. The parties should allow 30 days after receipt to try to resolve the dispute informally.

This informal process does not require a person to miss a statutory filing deadline, prevent a request for urgent injunctive or other emergency relief, override a non-waivable right, or create mandatory arbitration. Either party may proceed in a court of competent jurisdiction when informal resolution is unsuccessful or inappropriate.

Section 29

Applicable law and courts

These Terms and disputes relating to ModFlow are governed by the law that is applicable under the relevant conflict-of-law and consumer-protection rules. Any proceeding may be brought in a court of competent jurisdiction. Nothing in these Terms selects an exclusive state, country, or venue, creates mandatory arbitration, waives participation in a class or collective process, or removes rights that cannot lawfully be waived.

Section 30

General terms

  • A Customer may not assign these Terms or transfer access without ModFlow's consent, except where applicable law permits the transfer. ModFlow may assign these Terms in connection with a service reorganization, transfer, or succession, subject to applicable notice duties.
  • Neither party is responsible for delay caused by events beyond reasonable control, but this does not excuse payment already due or duties that can still reasonably be performed.
  • If a provision is unenforceable, it will be limited or removed only to the minimum extent necessary, and the remaining provisions continue.
  • A failure to enforce a provision is not a waiver. A waiver must be clear and applies only to the specific circumstance.
  • These Terms, the Privacy Policy, checkout terms, and any expressly incorporated service terms form the entire agreement about ModFlow and replace prior statements on the same subject.
  • Headings and summaries aid reading and do not narrow the controlling text. The words including and such as are not limiting.
  • Notices may be delivered electronically through email, Discord, the dashboard, the website, or service documentation when that method is lawful and reasonable.

Provisions concerning ownership, content, confidentiality, payment, retained data, disclaimers, liability, indemnity, disputes, interpretation, and any other term that must survive to have effect continue after suspension, removal, or termination.

Section 31

Changes and contact

ModFlow may update these Terms to reflect service, provider, security, legal, or operational changes. The last-updated date will change. Where practicable and required, material changes will be announced through the website, dashboard, Discord, email, or another reasonable channel before they take effect.

Continued use after an updated version becomes effective constitutes acceptance by a Customer or Authorized User to the extent allowed by law. If a Customer does not agree, it must stop authorizing use, remove ModFlow, and cancel applicable paid features. Changes do not retroactively remove non-waivable rights or turn an Affected User into a contracting party.

Questions, safety concerns, legal notices, copyright complaints, and privacy or data-rights requests may be sent to ModFlow at [email protected].