SKYBOX COMMAND CENTER
USER AGREEMENT
Version 3.3 · Effective August 24, 2026 · Row9 LLC ("Row9", "we", "us", "our")
1.1 This User Agreement (this "Agreement") governs access to and use of the Skybox Command Center platform, including its websites, applications, communication workflows, and related services (collectively, the "Service"), by the school district, school, or athletic organization identified at registration ("Customer", "you") and by each individual who accesses the Service under Customer's account ("Authorized User").
1.2 By accepting this Agreement in the Service, by signing an order form or services agreement that references it, or by accessing or using the Service, on behalf of Customer you agree to this Agreement. The individual accepting represents that he or she has authority to bind Customer; if you do not have that authority, or do not agree, do not use the Service.
1.3 Parents and guardians who use the Service only through registration links provided by a school agree to this Agreement by using those links, but only Sections 4 through 6, 8, 14, and 17 through 20 apply to them, and nothing in this Agreement reduces a school district's obligations to them under applicable law.
If Customer and Row9 have executed a services agreement, order form, or Data Privacy Agreement ("DPA"), then in the event of conflict the following order of precedence applies: (a) the DPA, as to student data and data protection; (b) the executed services agreement or order form; (c) this Agreement. This Agreement fills gaps not addressed in those documents and governs in full where no such document exists.
3.1 Core modules. The Service is an athletics operations platform: game scheduling and confirmation workflows with opposing schools; opponent, facility, and officials directories; transportation coordination; officials assignment workflows; communications (email and SMS) with opposing athletic departments, officials, carriers, and families; reporting; and calendar feeds.
3.2 Student data modules. Modules that involve student personally identifiable information (athlete registration, physicals and eligibility records, rosters containing student records) are enabled for a Customer only under an executed DPA between Row9 and Customer, as described in Section 7.5.
3.3 Changes. We improve the Service continuously and may add, modify, or retire features, provided changes do not materially reduce the core functionality of modules Customer has paid for during a paid term.
3.4 Beta features. Features identified as beta, preview, or pilot are provided as-is for evaluation, may be modified or withdrawn at any time, and are excluded from any performance commitments.
4.1 Named accounts. Each account is for one named individual. Shared or generic accounts are not permitted. Authorized Users must be at least 18 years old. Students are not offered accounts and must not be given credentials.
4.2 Roles. The Service provides role-scoped access (for example: athletic director, athletic department secretary, coach, officials assignor, parent or guardian). Parent and guardian access is limited to the registration module and only for their children who are students of Customer.
4.3 Credentials and links. Authorized Users must keep credentials confidential. Confirmation links and magic links sent to opposing schools, officials, and families are for their named recipients only and must not be forwarded or shared.
4.4 Customer responsibility. Customer is responsible for the acts and omissions of its Authorized Users, for maintaining accurate account rosters, and for promptly deactivating accounts of individuals who leave Customer's employment or no longer require access. Customer will notify Row9 promptly at the contact in Section 20 of any suspected unauthorized access.
4.5 Suspension of compromised accounts. Row9 may suspend an account that it reasonably believes is compromised or is being used in violation of this Agreement, and will notify Customer of the suspension.
You agree not to, and not to permit any Authorized User to:
6.1 Nature of the Service. The Service sends emails and text messages on Customer's behalf as part of its workflows: for example, game confirmation requests and reminders to opposing athletic departments, officials assignment notices, transportation requests to carriers, review links, and, where the registration module is enabled, registration invitations and status notices to parents and guardians. Customer directs and authorizes these communications.
6.2 Consent. Customer warrants that it has the authority and, where required, the consent needed for the Service to contact the recipients whose contact information Customer or its counterparties provide, including consent required by the Telephone Consumer Protection Act and equivalent state laws for text messages.
Recipients may opt out of text messages by replying STOP, and the Service honors opt-outs. Message and data rates may apply to recipients.
6.3 Inbound processing. Replies to Service emails are received and processed by the Service so that confirmations, declines, and proposed changes can be recorded, including automated classification as described in Section 10.
6.4 Not for emergencies. The Service is not designed or intended for emergency communications, life-safety notifications, or time-critical alerts, and must not be relied on for them.
7.1 Ownership. As between Customer and Row9, Customer owns all data submitted to the Service by Customer, its Authorized Users, or its counterparties on its behalf, including schedules, contacts, facilities, transportation records, and, where enabled, registration records ("Customer Data").
7.2 License to Row9. Customer grants Row9 a non-exclusive license to host, copy, transmit, display, and process Customer Data solely to provide, secure, support, and improve the Service and as otherwise permitted by this Agreement, the DPA, or Customer's written instructions. Row9 does not sell Customer Data and does not use it for third-party advertising or marketing.
7.3 Shared game records. Game records are bilateral: when two schools on the platform schedule one another, each school holds its own copy of the game and related workflow history. Data one school enters about a shared game does not become the property of the other school; each school's copy is its own Customer Data.
7.4 Aggregated data. Subject to any restriction that may be imposed by law, Row9 may create and use data that is aggregated or de-identified such that it does not identify Customer, any school, or any individual, to operate, secure, benchmark, and improve the Service.
7.5 Student data; FERPA. Modules involving student personally identifiable information are enabled only under an executed DPA consistent with the Family Educational Rights and Privacy Act ("FERPA") and applicable state law. Where enabled, Row9 acts as a school official with a legitimate educational interest under the district's annual FERPA notification, performs services the district would otherwise perform with its own employees, remains under the district's direct control as to education records, and uses education records only for the purposes of this Agreement and the DPA. Absent an executed DPA, Customer agrees not to enter student personally identifiable information into the Service, and those modules remain disabled.
7.6 Accuracy. Schedule accuracy depends on data entered by Customer and its counterparties. Customer is responsible for reviewing and confirming schedule changes; the Service records and routes them but does not warrant that counterparties' entries are correct.
The Service is a tool for school staff and for parents and guardians. It is not directed to children, and Row9 does not knowingly collect personal information directly from children under 13. Information about students, including students under 13, is provided to the Service by school staff and by parents or guardians. Where the registration module is enabled, the school authorizes Row9 to collect and process that information on the school's behalf as its service provider, and parental notices and consents are handled through the school's registration process and the DPA.
If Customer or an Authorized User provides suggestions or feedback about the Service, Row9 may use them without restriction or obligation, provided Row9 does not disclose the source without permission and does not use Customer Data except as this Agreement allows.
10.1 What the Service does. The Service uses a large language model API operated by Anthropic PBC to classify the intent of inbound email replies in scheduling workflows (for example: confirmed, declined, proposed date change) and to extract the proposed change so staff can act on it.
10.2 Human review. AI classifications are suggestions. Proposed schedule changes detected by AI are flagged for review by Customer's staff and are not applied to a schedule without human action.
10.3 Data boundaries. No student personally identifiable information is submitted to Anthropic. Content submitted for classification is limited to the scheduling correspondence being processed. Under Row9's commercial terms with Anthropic, material submitted through the API is not used to train Anthropic's models.
10.4 Accuracy. AI output can be wrong. Row9 does not warrant the accuracy of any AI classification, and Section 15 applies to AI features. Customer's remedy for a misclassification is correction through the review workflow.
11.1 Program. Row9 maintains administrative, technical, and organizational safeguards appropriate to the size and nature of the Service.
11.2 No warranty; no guarantee. No method of transmission or storage is completely secure; Row9 does not warrant that security incidents will never occur.
11.3 Incident notice. If Row9 confirms a breach of security leading to unauthorized acquisition of or access to unencrypted personal information in the Service, Row9 will notify affected Customers without unreasonable delay, consistent with the Pennsylvania Breach of Personal Information Notification Act, and will provide information reasonably available to help Customer meet its own notification obligations. For student data, the notice and cooperation terms of the DPA control.
12.1 Current sub-processors. The Service runs on and integrates with third-party providers. As of the effective date these are: Railway (hosting); Twilio (SMS delivery); AgentMail, together with its underlying delivery infrastructure Amazon Web Services SES (email delivery); Anthropic PBC (AI classification described in Section 10; no student personal information is sent to Anthropic); Google Maps Platform (geocoding and distance calculation); and PostHog (product analytics and session replay of Service pages, used to diagnose issues and improve the Service).
12.2 Obligations. Each provider's processing is limited to providing its function, under terms that protect Customer Data no less than this Agreement in all material respects.
12.3 Changes. Row9 may change sub-processors and will give notice of material changes through the Service or by email at least 30 days before the new sub-processor processes Customer Data. Objection rights for student data are as set out in the DPA.
13.1 Fees. Fees, if any, are as set out in Customer's order form or written agreement with Row9. If the Service is provided without charge, this Agreement still applies in full.
13.2 Invoices; taxes. Unless the order form says otherwise, invoices are due within 30 days of receipt. Fees exclude taxes; tax-exempt Customers will provide a valid exemption certificate on request.
14.1 Term. This Agreement runs for the term stated in the order form or, if there is none, until terminated. Either party may terminate for convenience on 30 days' written notice if no order form term applies.
14.2 Termination for cause. Either party may terminate if the other materially breaches this Agreement and does not cure within 15 days of written notice. Row9 may suspend or terminate immediately for a material breach of Section 5 (Acceptable Use) or Section 7.5 (Student Data). Failure of Customer to timely pay invoices is grounds for immediate termination of this Agreement by Row9. In the event of any termination by Row9, all outstanding fees are due and payable immediately.
14.3 Effect. On termination: access ends; Section 15's export window applies; and provisions that by their nature survive (including Sections 7, 9, 15, and 16 through 20) survive.
15.1 Export. During the term, Customer may export its Customer Data through the Service's export features, and on request Row9 will provide an export in a common machine-readable format.
15.2 Post-termination. For 30 days after termination, Row9 will make Customer Data available for export. Thereafter Row9 may delete Customer Data from production systems, and copies in routine backups are overwritten in the ordinary course within 90 days, except where retention is required by law. Deletion of student data follows the DPA.
16.1 By Row9. Row9 will defend Customer against third-party claims alleging that the Service, as provided by Row9 and used as permitted, infringes a United States patent, copyright, or trademark or misappropriates a trade secret, and will pay resulting damages finally awarded or agreed in settlement. If such a claim arises, Row9 may procure the right to continue the Service, modify it to be non-infringing, or terminate the affected module and refund prepaid unused fees. This Section states Row9's entire liability for infringement.
16.2 By Customer. To the extent permitted by applicable law, and without waiving any immunity or limitation of liability available to it as a public entity, Customer will defend Row9 against third-party claims arising out of Customer Data (excluding claims covered by Section 16.1), Customer's breach of Section 5 or Section 7.5, or communications Customer directs in violation of Section 6.2, and will pay resulting damages finally awarded or agreed in settlement, except to the extent caused by Row9's breach of this Agreement.
16.3 Process. The indemnified party must give prompt notice, reasonable cooperation, and sole control of the defense to the indemnifying party, provided any settlement requiring more than payment of money by the indemnifying party requires the indemnified party's consent.
17.1 Mutual. Each party warrants it has the legal power to enter into this Agreement.
17.2 Service warranty. Row9 warrants that it will provide the Service with commercially reasonable skill and care and will not materially degrade the core functionality of paid modules during a paid term.
17.3 Disclaimer. Except as stated in this Agreement, the Service is provided "as is" and "as available", and Row9 disclaims all other warranties, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. Row9 does not warrant that the Service will be uninterrupted or error-free.
17.4 Exclusion. Neither party is liable for indirect, incidental, special, consequential, or punitive damages, or for lost profits or revenues, even if advised of the possibility.
17.5 Cap. Each party's total aggregate liability under this Agreement is limited to the fees paid or payable by Customer to Row9 in the 12 months preceding the event giving rise to the claim, including any unpaid balance by Customer, or $100 if the Service is provided without charge.
17.6 Carve-outs. The exclusion in Section 17.4 and the cap in Section 17.5 do not apply to a party's indemnification obligations under Section 16, or to Customer's payment obligations.
18.1 Right-to-Know Law. Customer may be subject to the Pennsylvania Right-to-Know Law. Row9 will, at Customer's reasonable request and expense, cooperate with Customer in responding to a request for public records that implicates records Row9 holds on Customer's behalf. Row9 may refer to Customer any such request it receives directly.
18.2 Conflict with law. Nothing in this Agreement requires Customer to take any action, or make any payment, prohibited by the Pennsylvania Public School Code, the Pennsylvania Constitution, or other applicable law.
19.1 Governing law. This Agreement is governed by the laws of the State of North Carolina, without regard to conflicts rules.
19.2 ARBITRATION. ALL DISPUTES ARISING OUT OF OR RELATING TO THIS AGREEMENT ARE SUBJECT TO BINDING ARBITRATION. In the event of a dispute, Customer waives any sovereign or governmental immunity, and consents to binding arbitration. Arbitration shall be conducted by a single arbitrator under the Commercial Arbitration Rules of the American Arbitration Association ("AAA"). However, the parties may choose to have the dispute arbitrated by a single arbitrator whom the parties jointly select, without AAA administration. If the parties cannot agree on an arbitrator, then the arbitration shall be managed by the AAA. Exclusive venue for any judicial proceedings related to the arbitration is the state and federal courts sitting in Allegheny County, Pennsylvania, and each party consents to their jurisdiction. The arbitration may be conducted either in person or remotely, as the parties may agree. Should the arbitration be managed by the AAA, the parties shall each be responsible for paying one half of the AAA's fees, but the losing party shall ultimately be responsible for all of the AAA's fees.
19.3 Force majeure. Neither party is liable for delay or failure caused by events beyond its reasonable control, including utility or hosting provider failures, provided the affected party uses reasonable efforts to mitigate. This Section does not excuse payment obligations.
19.4 Assignment. Neither party may assign this Agreement without the other's written consent, except Row9 may assign it in connection with a merger, acquisition, or sale of substantially all assets, with notice to Customer.
19.5 Changes to this Agreement. Row9 may amend this Agreement by posting a new version with a new version number and notifying Customer's account email. Material changes take effect on acceptance or 30 days after notice, whichever comes first; continued use after that date is acceptance. Changes do not reduce Row9's obligations under an executed services agreement or DPA during its term.
19.6 Notices. Notices to Customer may be given through the Service or to Customer's account email. Notices to Row9 go to the contact in Section 20 and are effective on receipt.
19.7 Miscellaneous. This Agreement, together with the documents in Section 2, is the entire agreement about the Service and supersedes prior discussions on that subject. If a provision is unenforceable, the remainder stays in effect. Failure to enforce is not waiver. The parties are independent contractors. There are no third-party beneficiaries, except that parents and guardians may rely on Section 1.3.
Row9 LLC · Kerry Keating · kerrykeating3@gmail.com · 408-771-3438
© 2026 Row9 LLC. All rights reserved.