Skip to main content

Version 1.0 · Last updated 2026-05-19 · This policy is currently under legal review. Its wording may be refined before launch, and any material change will be announced in advance.

Terms of Service — GridBlitz

1. Acceptance of Terms

Welcome to GridBlitz. We help private groups — friends, family, coworkers, neighbors, your weekly crew — organize football-squares games during football season. GridBlitz is built for invite-only games among people who already know each other; it is not a public marketplace, a betting platform, or a money-handler. (See Section 4 below for the full description of what the platform does and does not do.)

These Terms of Service ("Terms") govern your use of GridBlitz. By creating an account, accessing the platform, or using any feature, you agree to these Terms. The Terms form a binding agreement between you and GridBlitz (the "Platform Operator").

If you do not agree with any part of these Terms, do not create an account, do not host a game on GridBlitz, and do not join a game on GridBlitz.


2. Definitions

These capitalized terms have the meanings set out below throughout this document.

  • GridBlitz, the Platform, we, us, our — the GridBlitz software-as-a-service ("SaaS") coordination platform and its accompanying services.
  • You, your, User — any individual who creates an account, accesses, or uses GridBlitz.
  • Account — your registered identity on GridBlitz, created at signup.
  • Host — a User who creates a Grid (game) on GridBlitz and manages the participants, schedule, and any offline money arrangements with those participants.
  • Player — a User who is invited to and joins a Grid hosted by another User.
  • Grid — a 10-by-10 digital game grid on GridBlitz, organized around a real-world NFL matchup. (Despite the everyday term "board" some users may default to, the canonical name on GridBlitz is "Grid" per LEGAL §4 mandatory terminology — see Section 4.)
  • Square (also "Tile" in some system contexts) — an individual cell of a Grid. The user-facing term is "Square"; "Tile" is the system-of-record term used in some technical surfaces.
  • Score Match — a Square whose row/column number combination corresponds to the current or final score of the matchup the Grid is built around.
  • Content — text, images, names, and other material you provide to GridBlitz (e.g., your display name, custom Square name, Grid name).
  • Acceptable Use Policy (AUP) — the separate document governing prohibited behavior on the Platform. See Section 6.
  • Privacy Policy — the separate document governing GridBlitz's collection and handling of your data. See Sections 7.1, 10, and the separate Privacy Policy document.
  • Hosting Purchase & Refund Policy — the separate document governing host-side payments for platform access. See Section 9.

3. Eligibility & Account Registration

3.1 Minimum Age

You must be at least 18 years old to use GridBlitz. You confirm this by completing the age attestation step at signup. If you are under 18, you may not create or use a GridBlitz Account, and you must immediately stop using the Platform.

The 18+ requirement is an extra protective layer (sometimes called "defense-in-depth"). GridBlitz itself is a coordination platform and does not collect, hold, or distribute money between participants (see Section 4 below). However, the underlying activity that GridBlitz helps organize — private money pools managed offline between Hosts and their Players — may fall under gambling regulations in some jurisdictions. Adult-only access is intended to protect both Users and the Platform's classification.

Per ADR-025 (Age Attestation Promotion), your age attestation is recorded by GridBlitz at the moment of submission and is permanent for your Account. There is no expiration and no un-attest path; the attestation is preserved as part of the compliance audit trail.

3.2 Account Registration

To create a GridBlitz Account, you must provide:

  • A valid email address (you control)
  • A password (if using email + password sign-in) OR a sign-in via Google OAuth, OR a sign-in via Magic Link delivered to your email
  • A display name
  • Truthful confirmation that you are at least 18 years old

You must keep your Account information accurate. You may not impersonate another person or misrepresent your identity.

3.3 One Account per User

Each User is permitted one Account on GridBlitz. Creating multiple Accounts to evade enforcement actions (suspension, ban, suppression — see Section 7) is prohibited.

3.4 Account Security

You are responsible for keeping your Account credentials secure. Activities performed through your Account are attributed to you. If you believe your Account has been accessed without your authorization, notify GridBlitz immediately at (to be finalized before launch).

GridBlitz uses an industry-standard third-party authentication service. Sessions persist across browser closes via secure refresh tokens (so you stay signed in when you come back later). Multiple concurrent sessions are permitted — you can be signed in on your phone and laptop at the same time. You can sign out of all sessions via Account Settings.


4. Platform Description & Classification

GridBlitz is a private, invite-only SaaS coordination platform. It provides digital tools that help small groups of people who already know each other — friends, family, coworkers, "just your crew" — organize football-squares games. Every game is invite-only and host-controlled by design. The Platform's role is to:

  • Provide a 10-by-10 digital Grid with persistent state
  • Help Hosts schedule games against real-world NFL matchups
  • Coordinate Player invitations and join requests
  • Display matchup scores from a third-party NFL data feed
  • Surface which Square's row/column numbers correspond to the current or final score (a Score Match)

Games on GridBlitz are not publicly listed, not discoverable by search, and not joinable without a Host's approval. There is no public game directory, no public leaderboard, no public player profile. The platform's load-bearing posture — private groups + invite-only access + host-controlled permissions — is intentional and structural, not just messaging.

4.1 What the Platform Does NOT Do

GridBlitz does NOT, by design and as a matter of architecture, ever:

  • Collect, process, hold, transfer, or distribute money between Players, between Hosts and Players, or between any participants in a Grid
  • Determine "winners" of a Grid in any monetary or prize-distribution sense
  • Provide escrow, payment processing, or settlement services between participants
  • Operate as a gambling platform, betting service, financial intermediary, prize authority, or any similar entity
  • Award prizes, payouts, jackpots, or winnings to Players
  • Take any cut, commission, percentage, fee, or charge from any money that Players contribute to a Host or that a Host distributes to Players

Any money associated with a Grid is entirely offline between the Host and that Host's Players. The Host sets all rules, collects any contributions directly from Players (outside the Platform), and distributes any payouts directly to Players (outside the Platform). GridBlitz is not a party to any such arrangement and has no knowledge of, control over, or involvement in any monetary transactions between Users.

4.2 What You Pay GridBlitz For

If you choose to purchase Platform access as a Host (see Section 9 — Purchases & Refunds), you are paying GridBlitz a SaaS subscription or one-time purchase fee for access to game-management tools. This is a software fee, not a gambling stake, entry fee, or wager. You are buying digital tools, not a position in a prize pool.

Players do not pay GridBlitz to claim Squares. Player-side actions on the Platform (claiming a Square, joining a Grid, viewing scores) are free.

4.3 Score Match, Not Prize Distribution

The Platform shows you which Square corresponds to a score at the end of each quarter and at the final whistle. This is data display — the Platform records and shows the score from an external NFL data feed and identifies which Square's row/column numbers match. The Platform does not interpret this as a "win" in any monetary or prize sense. Whether the Host treats a Score Match as the basis for a payout in their offline arrangement with their Players is entirely the Host's decision, made outside the Platform.


5. User Responsibilities

5.1 Host Responsibilities

If you create a Grid on GridBlitz, you are the Host of that Grid. As Host, you are responsible for:

  • Determining the rules of your Grid (entry contribution if any, payout structure if any, payout method, dispute resolution among your Players)
  • Inviting only Players you intend to invite
  • Approving or declining join requests from Players
  • Managing any money your Players contribute and any payouts your Players receive — entirely outside the Platform
  • Complying with all applicable laws in your jurisdiction, including any laws that may apply to private money pools, social gaming, or related activities
  • Not using GridBlitz in any way that would cause GridBlitz to violate any applicable law

The Platform provides the digital coordination layer. The legal, financial, and social arrangements among you and your Players are yours to manage and your responsibility.

5.2 Player Responsibilities

If you join a Grid hosted by another User, you are a Player in that Grid. As Player, you are responsible for:

  • Understanding the rules your Host has set for the Grid (entry contribution if any, payout structure if any)
  • Settling any money matters with your Host directly — entirely outside the Platform
  • Complying with all applicable laws in your jurisdiction
  • Treating your Host and fellow Players respectfully (see the Acceptable Use Policy)

5.3 Jurisdictional Compliance

You are responsible for ensuring your use of GridBlitz complies with all applicable laws in your jurisdiction. Some jurisdictions classify private money pools as gambling and impose specific legal requirements, restrictions, or prohibitions. Some jurisdictions have narrow social-gaming exceptions. GridBlitz does not provide legal advice and does not determine whether your specific use is legal in your jurisdiction.

GridBlitz reserves the right to restrict Platform availability in jurisdictions where its operation is legally questionable. See Section 7 for enforcement and Section 12 for governing law.


6. Prohibited Use

The full enumeration of prohibited behavior, abuse-prevention standards, and reporting procedures lives in the GridBlitz Acceptable Use Policy ("AUP"). By accepting these Terms, you also agree to the AUP.

How these Terms relate to the AUP. The AUP is the more detailed companion document. These Terms set out the overall contract; the AUP fills in the specifics of prohibited behavior. If the AUP and these Terms ever appear to disagree, these Terms control on the overall contract questions, and the AUP controls on the behavioral specifics it was written to govern.

The following activities are explicitly prohibited (this list is not exhaustive — see the AUP for the complete list):

  • Using the Platform to organize, facilitate, or promote any activity that is illegal in your jurisdiction or in the United States
  • Misrepresenting your identity or impersonating another User, real person, or organization
  • Harassing, threatening, or abusing other Users
  • Creating multiple Accounts to evade enforcement actions (suspension, ban, suppression)
  • Scraping, automated access, or unauthorized data extraction from the Platform
  • Reverse-engineering, decompiling, or otherwise attempting to discover the source code of the Platform
  • Using the Platform to send unsolicited bulk communications (spam) to other Users
  • Operating the Platform in any way that creates legal or financial exposure for GridBlitz or its operators
  • Bypassing or attempting to bypass any technical safeguard, rate limit, or access control

Violation of the AUP or this section may result in enforcement actions per Section 7.


7. Account Suspension & Termination

7.1 Voluntary Account Deletion by You

You may request deletion of your Account at any time through Account Settings. The deletion flow runs in four steps per ADR-028 (Account Deletion + Cascading Anonymization).

A note on game lifecycle states used below. Throughout this section we refer to Grid (game) states by name: DRAFT = the host is setting the game up but hasn't opened it for joins; FILLING = the game is accepting players claiming Squares; LOCKED = the host has locked the game and drawn the row/column numbers, ready for kickoff; LIVE = the underlying NFL matchup is in progress; FINAL = the matchup is over and the game's final state is recorded.

Step 1 — Active-Engagement Pre-Check. Before deletion proceeds, GridBlitz checks for ongoing games or open commitments that would block deletion:

  • As Host: if you currently host any Grid in DRAFT, FILLING, LOCKED, or LIVE state, deletion is blocked. You must first cancel those Grids (for DRAFT/FILLING; your hosting credit is restored per the Hosting Purchase & Refund Policy) or wait for those Grids to reach FINAL state (for LOCKED/LIVE; you cannot cancel a LIVE game while the underlying NFL matchup is in progress).
  • As Player: if you currently own any active Square in any Grid in DRAFT, FILLING, LOCKED, or LIVE state, deletion is blocked. You must first release those Squares (for DRAFT/FILLING; releasable through the in-app release flow with no platform-side penalty) or wait for those Grids to reach FINAL state (for LOCKED/LIVE; once a game LOCKS, Squares cannot be voluntarily released so the row/column numbers stay fixed for the duration).

If either check fails, GridBlitz returns an error explaining which game is blocking and how to resolve it. Both checks must clear before deletion proceeds.

Step 2 — Confirmation Email. If both checks pass, GridBlitz sends a confirmation email to your registered email address with a one-time verification link. Click the link to confirm; without confirmation, no deletion occurs. This step exists so that an accidental click — or someone who briefly gained access to your account — can't delete your account without your separate email-side approval.

Step 3 — Soft-Delete + Cascading Anonymization. On confirmation, GridBlitz:

  • Marks your Account as deleted ("soft-delete" — your data is marked deleted but preserved for 30 days in case you want to undo) and anonymizes your email, name, and profile fields with redacted placeholders
  • Replaces your identifying information with placeholders everywhere it appears across the platform (called "cascading anonymization" — a sweep that touches audit log entries, notification records, historical Square ownership snapshots, and block relationships, so your name and email no longer appear anywhere)
  • Records the deletion in the compliance audit trail per ADR-022

Step 4 — 30-Day Reversibility Window. For 30 days after confirmation, you may restore your Account via support escalation. Restoration is a manual operation. After 30 days, an automated system permanently removes your Account row from the database. After permanent removal, the cascading-anonymization replacements stay in place; audit log entries persist per the 7-year retention policy in Section 10 below.

The full mechanics are documented in this Section 7.1 + the separate Privacy Policy. The 30-day reversibility window is GridBlitz's current commitment; we may shorten or extend this window in future policy updates per Section 13.

7.2 Enforcement Actions by GridBlitz

GridBlitz reserves the right to limit, suspend, or terminate your Account in cases including but not limited to:

  • Violation of these Terms or the AUP
  • Behavior that creates risk for other Users, the Platform, or its operators
  • Abuse of Platform features (spam, harassment, scraping, evasion of enforcement)
  • Activity that is illegal in any applicable jurisdiction
  • Misrepresentation in your registration or use of the Platform

Per LEGAL §9 (Enforcement Disclosure Boundaries), GridBlitz does NOT publicly disclose:

  • The specific thresholds that trigger enforcement actions
  • The detection mechanisms or algorithms used to identify policy violations
  • The internal rate limits, scoring, or moderation logic that informs enforcement decisions

GridBlitz disclaims any obligation to provide advance notice of enforcement actions in cases where notice would compromise the effectiveness of safeguards against abuse. Where notice can be given without compromising safeguards, GridBlitz endeavors to provide it.

Appeal mechanism. If your Account is suspended or terminated and you believe the action was a mistake, you may request a review by contacting GridBlitz through the support channel in Section 15 below. We don't disclose specific detection or threshold logic in the review (per LEGAL §9 — that protects the safeguards from abuse), but we will reconsider the action on the merits.

7.3 Effect of Termination

If GridBlitz terminates your Account, your access to the Platform ends. You may be subject to cascading anonymization per Section 7.1 above. Sections of these Terms intended to survive termination (including Sections 4 [Platform Classification], 8 [Intellectual Property], 11 [Disclaimers], 12 [Dispute Resolution], 13 [Modifications], 14 [Severability], and 15 [Contact]) continue in effect.


8. Intellectual Property

8.1 GridBlitz Platform IP

GridBlitz and its operators own all rights, title, and interest in the Platform, including the software, brand assets (logo, name, visual design), product copy, content library, and platform infrastructure. You may not copy, modify, distribute, sell, or create derivative works of any Platform IP without GridBlitz's prior written authorization.

The GridBlitz name and brand are owned by GridBlitz's operators. You may not use the GridBlitz name or brand in a way that suggests endorsement, partnership, or affiliation without authorization.

8.2 Your Content

You retain all rights to Content you create or provide on the Platform — your display name, custom Square name, Grid name, and so on. By providing that Content, you give GridBlitz permission to use, store, display, and transmit it for the purpose of operating the Platform and providing the service to you and the people you've invited. (In legal terms this is a "non-exclusive, worldwide, royalty-free license" — meaning we can use the Content to run the platform but we don't own it, we're not the only ones who can use it, and we're not paying you for it. You keep the rights.) For example: your Players see your display name on a Grid you host because that license lets GridBlitz show your name to them.

You may not provide Content that:

  • Infringes on another person's intellectual property (e.g., uses a name, logo, or trademark you do not own)
  • Is defamatory, harassing, obscene, or otherwise prohibited per the AUP
  • Misrepresents your identity (see Section 5.1 / 5.2)

8.3 NFL and Third-Party Trademark Disclosure

GridBlitz is not affiliated with, endorsed by, or sponsored by the National Football League (NFL), any NFL team, the NFL Players Association, or any organization licensed by the NFL. Names and marks of the NFL, its teams, and related entities are trademarks of their respective owners.

GridBlitz organizes Grids around real-world NFL matchups by referencing matchup data from an external NFL data feed. The Platform displays matchups using city-based identifiers (e.g., "Kansas City vs. Philadelphia") rather than team names, logos, or other trademarked NFL IP. In editorial content (e.g., the GridBlitz blog or SEO content surfaces), the Platform may reference NFL terminology only to describe or refer to a real-world matchup — a legal concept called "nominative fair use" that allows referring to a trademarked name when you're identifying the thing the trademark names, not implying endorsement.

If you provide Content that uses an NFL trademark (e.g., naming your Grid with a team name), you do so at your own risk and represent that your use is permitted.


9. Purchases & Refunds (Host-Side Only)

If you create a Host Account, you may purchase digital tools for managing additional Grids. The pricing tiers, what each tier includes, and the conditions for refunds are described in the GridBlitz Hosting Purchase & Refund Policy.

By making a purchase, you agree to the Hosting Purchase & Refund Policy.

Required disclaimer per LEGAL §8. Per the LEGAL_COMPLIANCE_FRAMEWORK_v1.md mandatory checkout disclaimer: "You are purchasing platform access for game management tools. GridBlitz does not process, hold, or distribute money between game participants."

Payments are processed by Stripe (a third-party payment processor — the same service many SaaS platforms use to handle card transactions) under Stripe's terms of service. By making a purchase, you agree to Stripe's terms as a payment processor.


10. Audit Log & Data Retention

GridBlitz maintains a tamper-resistant internal record (an "append-only audit log" per ADR-022) of important actions on the Platform — Grid creation, Square claiming, invite minting, account deletion, and similar state-changing events. The audit log is internal to GridBlitz, used by GridBlitz's operators for compliance defense and incident investigation. It is not a User-facing surface.

The audit log retains records for 7 years by default. This retention window is calibrated to several external standards we have to satisfy:

  • US record-retention norms for SaaS services (typically 4–7 years)
  • "GDPR Article 5(1)(e)" — a European Union privacy-law rule that says we shouldn't keep data "longer than necessary"; 7 years is the standard duration that meets compliance-evidence retention without overshooting
  • Apple App Store, Stripe, and similar third-party compliance review windows

(Quick reference: CCPA is the California Consumer Privacy Act, a US state privacy law; GDPR is the EU's General Data Protection Regulation. Both grant users certain rights over data we hold about them.)

When you delete your Account (Section 7.1), the audit log preserves the historical record of events — these events can't be edited or removed retroactively. Only the user-identifying portions (your User ID and any user-identifying payload fields like display name) are replaced with placeholders via the cascading-anonymization sweep described in Step 3 of Section 7.1 above. The event itself remains in the log so that the historical record stays intact.

See Section 7.1 above + the separate Privacy Policy for the broader data collection, usage, retention, and deletion framework.


11. Disclaimers & Limitation of Liability

What this section covers (plain English): this is the standard "things we don't promise" and "limits on what we owe you if something goes wrong" section that every SaaS terms-of-service has. Attorney v2 markup will produce the binding language. The structure below previews the substantive areas.

(to be finalized before launch)

11.1 Service "As Is" (to be finalized before launch)

The Platform is provided on an "as is" and "as available" basis (legal shorthand meaning: we provide GridBlitz with the current set of features it has today, and we don't promise it'll be free of bugs, downtime, or imperfections), without warranties of any kind, express or implied, including but not limited to warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, or availability.

11.2 No Guarantee of Outcome

GridBlitz records and displays scores from an external NFL data feed. The Platform makes no guarantee about the accuracy, timeliness, or completeness of NFL score data. GridBlitz does not determine winners, payouts, or prize distributions — those decisions, if any, are made by the Host outside the Platform per Section 4.

The outcome of any NFL matchup is determined by real-world sporting events outside GridBlitz's control. The Platform makes no representation about NFL outcomes.

11.3 Host Responsibility for Offline Arrangements

GridBlitz is not a party to any offline money arrangement among Users. The Platform Operator is not responsible for:

  • Money collection, holding, or distribution between Hosts and Players
  • Disputes between Host and Players about contributions, payouts, or fairness
  • Tax reporting on amounts contributed or distributed offline
  • Compliance with state, federal, or international gambling, money-transmission, or financial-services regulations applicable to the offline arrangement

11.4 Limitation of Liability (to be finalized before launch)

Plain English first: this clause caps the maximum amount of money GridBlitz could be required to pay if something went wrong and you sued us. Caps like this are standard in every SaaS terms of service and exist because a small platform can't carry unlimited financial risk for every user interaction. The cap below is a placeholder; attorney v2 will set the specific amount per market norms.

To the maximum extent permitted by applicable law, GridBlitz's total liability for any claim arising from or relating to these Terms or the Platform is limited to (to be finalized before launch).

In no event will GridBlitz be liable for indirect, incidental, consequential, punitive, or exemplary damages — meaning damages that ripple outward from the original issue, such as lost profits, lost data, business interruption, or loss of goodwill — even if advised of the possibility of such damages.

11.5 Indemnification (to be finalized before launch)

Plain English first: "indemnification" means: if a third party sues GridBlitz because of something YOU did, you agree to cover GridBlitz's legal costs and any resulting payouts. This is standard SaaS contract language and applies only to claims caused by your conduct — not to claims about GridBlitz's own conduct. Attorney v2 will refine the exact scope.

You agree to indemnify and hold harmless GridBlitz and its operators (meaning: you'll cover their legal defense costs and any resulting awards) from any claim, loss, liability, or expense (including reasonable attorneys' fees) arising from:

  • Your violation of these Terms
  • Your use of the Platform in violation of applicable law
  • Any offline money arrangement you enter into with other Users
  • Your Content provided to the Platform
  • (to be finalized before launch)

12. Dispute Resolution & Governing Law

What this section covers (plain English): if you and GridBlitz ever have a serious disagreement that can't be resolved informally, this section says (a) which state's laws apply, (b) where any formal proceeding happens (court vs. arbitration), and (c) whether you can join with other users in a single combined proceeding (a "class action"). These are standard SaaS clauses; the choices below reflect GridBlitz's business decisions (Session 209, gate G-A.5/G-A.6 — binding AAA arbitration + class-action waiver + governing law tied to the LLC formation state). Attorney v2 markup finalizes the precise binding wording per LEGAL §12 item 3; this document stays DRAFT until then.

(to be finalized before launch)

12.1 Governing Law (to be finalized before launch)

These Terms are governed by the laws of the State of GridBlitz's LLC formation (to be finalized before launch), without regard to its conflict-of-laws principles.

12.2 Dispute Resolution Forum (to be finalized before launch)

Any dispute arising from these Terms or your use of the Platform that cannot be resolved informally under Section 12.4 will be resolved by binding arbitration administered by the American Arbitration Association (AAA) under its Consumer Arbitration Rules, rather than in court — except that either party may (a) bring an individual claim in small-claims court if it qualifies, or (b) seek injunctive or other equitable relief for intellectual-property infringement or unauthorized access. (to be finalized before launch)

12.3 Class-Action Waiver (to be finalized before launch)

To the maximum extent permitted by applicable law, you and GridBlitz each agree that any dispute will be brought only in an individual capacity, and not as a plaintiff or class member in any purported class, collective, consolidated, or representative proceeding; the arbitrator may not consolidate more than one person's claims. (to be finalized before launch)

12.4 Informal Resolution First

Before initiating any formal dispute resolution, you and GridBlitz agree to attempt to resolve the dispute informally by contacting (to be finalized before launch) and providing 30 days for response.


13. Modifications to Terms

GridBlitz may update these Terms over time — adding new features, fixing gaps, complying with new laws, or clarifying existing terms. When we make a material change — meaning a change that meaningfully affects what data we collect, how we use it, what you're paying for, or what rights you have — we will notify Users at least 30 days (GridBlitz business decision, Session 209, gate G-A.6) before the changes take effect, by both of the following (to be finalized before launch):

  • Email to the email address on file with your Account, AND
  • An in-app banner or notification on next sign-in

If you do not agree with a material change to these Terms, your options are: (a) stop using the Platform before the effective date, or (b) request Account deletion per Section 7.1.

Non-material changes (e.g., typo corrections, clarifications, contact information updates) take effect immediately and are recorded in the changelog (top of this document).

Each version of these Terms is preserved with its effective date. You may request the current and historical versions from GridBlitz at any time per Section 15.


14. Severability & Entire Agreement

What this section covers (plain English): four standard housekeeping clauses that every SaaS contract has. They handle: (a) what happens if a court strikes down one provision (the rest still applies), (b) what counts as the full agreement (this doc + the linked policies, nothing else), (c) whether GridBlitz losing a rule once means we waived it forever (no), and (d) whether you can transfer your rights under this agreement to someone else (no).

(to be finalized before launch)

14.1 Severability

Plain English: if a court throws out one clause, the rest of the contract still applies.

If any provision of these Terms is held by a court or arbitrator to be unenforceable, the remaining provisions remain in effect to the maximum extent permitted by applicable law.

14.2 Entire Agreement

Plain English: this document (plus the documents it links to) is the full agreement between you and GridBlitz. Verbal promises, marketing copy, prior drafts — none of those control once these Terms apply.

These Terms (together with the AUP, Privacy Policy, Hosting Purchase & Refund Policy, and Cookie Policy referenced herein) constitute the entire agreement between you and GridBlitz regarding your use of the Platform. They supersede any prior agreements or understandings.

14.3 No Waiver

GridBlitz's failure to enforce any provision of these Terms is not a waiver of that or any other provision.

14.4 Assignment

You may not assign these Terms or any rights under them without GridBlitz's prior written consent. GridBlitz may assign these Terms in connection with a merger, acquisition, or sale of assets.

14.5 Force Majeure (to be finalized before launch)

Plain English: "force majeure" is a French phrase that means "superior force" — it's the legal label for events outside anyone's reasonable control. This clause says: if something major and unavoidable disrupts GridBlitz (or disrupts you), neither side is on the hook for the delay or failure it caused.

Neither party is liable for delay or failure to perform caused by events outside their reasonable control, including but not limited to acts of God (e.g., earthquakes, severe weather), war, terrorism, civil unrest, natural disaster, pandemic, internet or telecommunications outage, or third-party service provider failure.


15. Contact Information

Questions about these Terms or the Platform may be directed to:

  • Operating Entity: (to be finalized before launch)
  • Email: (to be finalized before launch)
  • Mailing Address: (to be finalized before launch)

Disputes are addressed per Section 12 above. General inquiries, support requests, and Account-related questions are addressed by the email or in-app support channel at sign-in.


Appendix A — Required Disclosures Summary

The following disclosures are made consistent with the GridBlitz LEGAL_COMPLIANCE_FRAMEWORK_v1.md governance authority:

  1. Platform Classification (per CLAUDE.md §1 + LEGAL §1). GridBlitz is a SaaS coordination platform, not a gambling platform, betting service, financial intermediary, or prize authority.
  2. Money-Handling Statement (per LEGAL §3 Critical Rule 1). GridBlitz does not collect, process, hold, transfer, or distribute money between participants. All Player–Host money flows are offline and outside the Platform.
  3. Score Display (per LEGAL §6). Score Match data is a display of factual NFL score data; it is not a determination of winners or distribution of prizes.
  4. Suppression Disclosure (per LEGAL §9). GridBlitz reserves the right to enforce these Terms and the AUP. The Platform does not publicly disclose enforcement thresholds, detection logic, or moderation algorithms (consistent with PRD §31 P-5 Silent Enforcement).
  5. Audit Log Retention (per ADR-022). GridBlitz maintains an internal audit log of state-changing actions with 7-year retention per Section 10.
  6. Account Deletion (per ADR-028). Voluntary deletion follows the active-engagement pre-check + soft-delete + cascading-anonymization + 30-day reversibility mechanics in Section 7.1.
  7. NFL Trademark Disclaimer (per LEGAL §5). GridBlitz is not affiliated with, endorsed by, or sponsored by the NFL or any NFL team. NFL marks are trademarks of their respective owners.

Appendix B — Definitions Cross-Reference

For convenience, defined terms in this document and where they live:

  • GridBlitz / Platform / we / us / our — Section 2
  • You / your / User — Section 2
  • Account — Section 2
  • Host — Section 2 (Host responsibilities: Section 5.1)
  • Player — Section 2 (Player responsibilities: Section 5.2)
  • Grid — Section 2
  • Square / Tile — Section 2
  • Score Match — Section 2 (operational description: Section 4.3)
  • Content — Section 2 (intellectual property: Section 8.2)
  • Acceptable Use Policy (AUP) — Section 6
  • Privacy Policy — referenced in Section 7.1 + Section 10 + separate Privacy Policy document at 01_global/canonical/legal/policies/PRIVACY_POLICY_v1.md (Code v1 DRAFT Session 112 SC2; pending attorney v2 per Phase H of LEGAL_PAGES_DRAFTING_CHARTER.md)
  • Hosting Purchase & Refund Policy — Section 9 reference + separate Refund Policy document
  • Cookie Policy — referenced in Section 14.2 + separate Cookie Policy document at 01_global/canonical/legal/policies/COOKIE_POLICY_v1.md (Code v1 DRAFT Session 115 SC1; pending attorney v2 per Phase H of LEGAL_PAGES_DRAFTING_CHARTER.md)