FSO Console™ agreement

Version Beta V.2 · SHA-256 3e0c3115326a579de7e4f8bcb5631c9d793c19133daae986faf5c7dda0ecde80

FSO Console™ Beta Test Agreement

Effective date: October 16, 2026. This revised agreement replaces the version named "Beta V.1."

Beta Test, Non-Disclosure, and Evaluation Agreement

This Beta Test, Non-Disclosure, and Evaluation Agreement (the "Agreement") is entered into between INTS2, Intelligence Support & Services, LLC, a Texas limited liability company with its headquarters in North Carolina, the owner and operator of FSO Console™ ("INTS2," "we," or "us"), and the individual and the organization the individual represents that accept it (together, "Tester" or "you").

How you accept. You accept this Agreement by checking the acceptance box and clicking "I Agree" (or a similar button) during sign-up, or by accessing or using FSO Console™. If you accept on behalf of an organization, you represent that you have authority to bind it. If you do not agree, do not create an account or use FSO Console™.

IMPORTANT — READ BEFORE ACCEPTING. FSO Console™ is pre-release BETA software. It may contain errors, may lose or corrupt data, and is provided "AS IS." You are solely responsible for all data you enter, and INTS2 is not liable for any loss of that data (Sections 3 and 9). Do not enter classified information (Section 3.2).

1. Definitions

2. The Beta Program

2.1 Limited right to use. Subject to this Agreement, INTS2 grants you a limited, revocable, non-exclusive, non-transferable, non-sublicensable right to access and use FSO Console™ during the Beta Period, solely to evaluate the Service and provide Feedback (the "Permitted Purpose").

2.2 Thirty-day Beta Period. The Beta Period lasts thirty (30) calendar days. Your beta authorization expires at the end of the Beta Period unless INTS2 extends it in writing (email is sufficient). After expiry, the software may restrict new entries, but you will always be able to view and export your Tester Data. INTS2 may end the Beta Period early, for any reason, by notice to you, and you will then stop using the software as described in Section 10.3.

2.3 No fees; no commitment. The Service is provided free of charge during the Beta Period. Neither party is obligated to enter into any further agreement, subscription, or purchase.

2.4 Pre-release software and updates. The software is under active development. INTS2 may release new versions that add, change, or remove features, and you choose whether and when to install them. INTS2 cannot take your Instance offline, and you are responsible for operating, maintaining, and updating it. The production version of FSO Console™ may differ materially from the beta.

2.5 Evaluation use only. You may not rely on FSO Console™ as your system of record or as your sole means of meeting any regulatory, reporting, or recordkeeping obligation during the Beta Period. You will keep your official records in your existing systems (for example, NISS, DISS, or other internal systems).

2.6 Accounts and access inside your Instance. Your Owner and any Alternate control who may register, join, and see your company's data in your Instance. You are responsible for all activity under your accounts, including by your Personnel. INTS2 cannot grant, revoke, reset, or recover any user's access inside your Instance, and account recovery is your responsibility.

3. Your Data and Your Responsibility for It

3.1 You are responsible for all Tester Data. You are solely responsible for all Tester Data, including its accuracy, legality, and quality, and for having every right, consent, and authorization needed to enter it into FSO Console™. This includes any notice to, or consent from, your Personnel or other individuals whose information you enter.

3.2 UNCLASSIFIED only — prohibited data. FSO Console™ is not accredited to store or process classified information. You will not enter, upload, or transmit:

  1. Classified national security information at any level, or information whose classification is unknown;
  2. Controlled Unclassified Information (CUI), unless INTS2 has first agreed in writing that a specific category is permitted;
  3. Export-controlled technical data (ITAR or EAR);
  4. Social Security Numbers, full dates and places of birth paired with names, passport numbers, financial account numbers, or medical information; or
  5. Any data you are not authorized to share with a third-party service provider.

INTS2 strongly recommends that you use fictitious or sample data for testing. If you enter prohibited data, you are solely responsible for the consequences, including any required incident reporting to your Government Contracting Activity or DCSA. You will remove prohibited data from your environment promptly once you become aware of it, and INTS2 may terminate this Agreement and decline to issue further authorization codes if it learns of a violation.

3.3 BETA — loss of data is your risk. You acknowledge that FSO Console™ is pre-release software under active development and that Tester Data may be lost, corrupted, altered, exposed through a defect, or deleted, including through resets, updates, migrations, or termination of the beta. INTS2 does not guarantee the backup, recovery, retention, or integrity of any Tester Data. You are solely responsible for the backup, retention, and recovery of your Google environment and for keeping independent copies of anything you need. A defect in the software could alter or delete Tester Data in your Instance. INTS2 cannot access your Instance and therefore cannot recover, restore, or repair Tester Data or lost user access. To the fullest extent permitted by law, INTS2, its parent, affiliates, members, managers, officers, employees, contractors, licensors, and hosting providers (the "INTS2 Parties") are not responsible or liable for any loss, corruption, or unavailability of Tester Data, or for any consequence of it, including missed reporting deadlines, compliance findings, or rating impacts.

3.4 Outputs require your review. Scores, suggested answers, auto-populated checklist items, generated memos, and other outputs may be wrong or incomplete. You will independently verify every output before relying on it or submitting it to anyone.

3.5 No verification of identity or clearance. The software does not verify any CAGE Code, Unique Entity Identifier (UEI), facility clearance, personnel clearance, or other identity or eligibility information against SAM.gov, DISS, NISS, or any other source. CAGE Codes and UEIs are format-checked only. All such information is self-attested by you, and you are solely responsible for its accuracy and lawful use.

4. Confidentiality and Use Restrictions

4.1 Non-disclosure. You will hold INTS2's Confidential Information in strict confidence and protect it with at least reasonable care. You will not disclose it to anyone except Personnel who need to know it for the Permitted Purpose and who are bound by written confidentiality obligations at least as protective as this Agreement. You are responsible for any breach by your Personnel.

4.2 Use restriction. You will use Confidential Information solely for the Permitted Purpose. You will not use it, in whole or in part, for your own benefit or anyone else's, including to design, develop, improve, specify, procure, or market any product, service, or capability. This restriction applies whether or not the use involves any disclosure to a third party.

4.3 No residuals. This Agreement contains no "residuals" right. You may not use or disclose Confidential Information on the basis that it is retained in the unaided memory or general knowledge of any person.

4.4 No AI tools or outside systems. You will not enter, paste, upload, or screen-capture Confidential Information into any third-party artificial intelligence, machine learning, or large language model service, or any other system outside your direct control, other than FSO Console™ itself.

4.5 No public statements. You will not publish reviews, benchmarks, screenshots, videos, or descriptions of the Service without INTS2's prior written consent.

4.6 Exclusions. Confidential Information does not include information you can show, by contemporaneous written records, (a) is or becomes public through no fault of yours; (b) you lawfully knew before INTS2 disclosed it, without restriction; (c) you lawfully received from a third party without a duty of confidentiality; or (d) was independently developed by Personnel who had no access to the Confidential Information and without any use of or reference to it. You bear the burden of proving any exclusion.

4.7 Compelled disclosure. If law or a court or government order requires you to disclose Confidential Information, you may do so only to the extent required, after giving INTS2 prompt prior notice (where lawful) and reasonable cooperation in seeking protective treatment.

4.8 Third-party information. Some Confidential Information may belong to INTS2's licensors or vendors. Your obligations apply equally to it, and those parties are intended third-party beneficiaries of this Section 4 as to their own information.

5. Intellectual Property

5.1 INTS2 owns the Service. FSO Console™, the Confidential Information, and all related intellectual property rights are and remain the exclusive property of INTS2 and its licensors. Nothing in this Agreement grants you any license or right, by implication, estoppel, or otherwise, except the limited right in Section 2.1. INTS2 reserves all rights not expressly granted.

5.2 Prohibited actions. You will not, and will not permit anyone to: (a) reverse engineer, decompile, disassemble, or attempt to derive the source code, architecture, algorithms, data structures, or scoring logic of the Service; (b) copy, modify, translate, frame, or create derivative works of the Service or its documentation; (c) copy or extract the software's code, workflows, or templates (exporting your own Tester Data with the built-in export feature is permitted); (d) conduct benchmarking or competitive analysis other than as INTS2 authorizes in writing; (e) probe, scan, or test the Service's security, except by reporting suspected vulnerabilities to INTS2; (f) sublicense, sell, rent, or provide the Service to any third party; or (g) remove or alter any proprietary or confidentiality notice.

5.3 Feedback belongs to INTS2. You hereby irrevocably assign to INTS2 all right, title, and interest in and to all Feedback, including all intellectual property rights in it. INTS2 may use, modify, and commercialize Feedback without restriction, attribution, or compensation. You will not submit Feedback that you know is subject to a third party's rights.

5.4 Derived IP. You hereby irrevocably assign to INTS2 all right, title, and interest in any invention, improvement, adaptation, derivative work, or other work product that you or your Personnel conceive or create during the Beta Period or within twelve (12) months after it, and that is based upon, derived from, or could not have been created without access to the Confidential Information ("Derived IP"). You will promptly disclose Derived IP to INTS2 and sign any documents reasonably needed to perfect INTS2's rights, at INTS2's expense. No joint ownership of any intellectual property is created by this Agreement.

5.5 Covenant not to file. During the Beta Period and for five (5) years after it, you will not file, or help anyone file, any patent, design, copyright, or trademark application that claims, discloses, or is based on Confidential Information or Derived IP. Any filing made in breach of this Section is held in trust for INTS2 and will be assigned to INTS2 on demand.

5.6 Non-circumvention. During the Beta Period and for eighteen (18) months after it, you will not, directly or indirectly, use Confidential Information to develop, commission, procure, or commercialize any software or service that performs facility security, NISPOM / 32 CFR Part 117 compliance management, self-inspection, or security-rating functions; or approach any developer, vendor, or licensor identified to you through the Confidential Information to obtain or replicate the Service in a manner that circumvents INTS2. Nothing in this Section restricts you from using commercially available products that were developed without use of Confidential Information.

6. Feedback Channel and End-of-Beta Survey

6.1 Submitting Feedback by email. You may send comments, suggestions, and bug reports from within FSO Console™, provided your account is connected to your email according to the setup instructions INTS2 provides. Feedback sent this way is transmitted from your email account to INTS2's designated feedback address. You authorize the Service to send those messages on your behalf only when you initiate them. INTS2 does not read, store, or access any other content of your mailbox.

6.2 What not to include. Your Feedback messages are subject to Section 3.2. Do not include classified, CUI, export-controlled, or sensitive personal information in Feedback or attachments. You are responsible for your email system's configuration and security and for complying with your organization's email and security policies.

6.3 Consent to the survey. By accepting this Agreement, you consent to INTS2 sending you a survey about your beta experience by email, on or after the thirtieth (30th) day of the Beta Period, and up to two (2) reminder emails within the following fourteen (14) days. Completing the survey is voluntary. Survey responses are Feedback under Section 5.3.

6.4 Other communications. INTS2 may also send you service and administrative messages related to the beta (for example, outage notices, changes, or the end of the Beta Period). INTS2 will not send you marketing email under this Agreement unless you separately opt in, and every non-administrative message will include a way to unsubscribe.

7. Our Commitments to You

7.1 Your data stays in your environment. The software runs as an isolated Instance in your own Google Cloud or Google Workspace environment, and Tester Data is stored only there. INTS2 does not host Tester Data, receives no copy of it, and keeps no central store of customer data. You own your Tester Data.

7.2 No vendor access. INTS2 has no remote administrative connection, backdoor, recovery key, or other means to access, view, change, recover, or delete Tester Data or to administer your Instance. The software does not send usage data or Tester Data to INTS2. INTS2 receives only what you choose to send, such as Feedback.

7.3 What INTS2 does hold. INTS2 holds only the information you give it to join the beta (name, title, organization, and email), your acceptance record, the authorization codes it issues to you, and Feedback you send. INTS2 treats this information as confidential and uses it only to run the beta, contact you under Section 6, and enforce this Agreement.

7.4 Your data is always available to you. The software includes a full-data export that produces a complete, re-readable copy of your records and stored documents. The export remains available before, during, and after the Beta Period, regardless of authorization status, for as long as you have access to the software within the Google environment, and so long as the software functions as designed. INTS2 will not withhold or restrict your access to your own Tester Data.

7.5 Security. INTS2 will use commercially reasonable secure-development practices and will not build any hidden access into the software. You are responsible for the security, access controls, backups, and administration of your environment and Instance, including your Google account and email configuration. Section 3.3 continues to apply.

7.6 Vulnerability notice. If INTS2 learns of a security vulnerability in the software that could expose or alter Tester Data, INTS2 will notify you without undue delay, and in any event within seventy-two (72) hours, and will make a fix or workaround available when one exists. Installing it is your responsibility.

7.7 End of the beta. When the Beta Period ends, your Tester Data remains in your environment for you to keep, export, or delete.

7.8 Your right to leave. You may stop using the Service at any time without notifying INTS2 and end this Agreement at any time by notice to INTS2 (Section 10.2).

8. Not an Official Government Tool; No Professional Advice

8.1 Not affiliated with the Government. FSO Console™ is an independent commercial product. It is not developed, endorsed, approved, or certified by the Defense Counterintelligence and Security Agency (DCSA), the Department of Defense/War, or any other government agency. References to the NISPOM (32 CFR Part 117), the DCSA Self-Inspection Handbook, the DCSA Security Rating Score Tool, NISS, DISS, or SEAD 3 are for reference only.

8.2 Unofficial scores. Any self-inspection score, criteria result, or security rating the Service displays is an unofficial estimate. Only DCSA assigns an official security rating.

8.3 No legal or compliance advice. The Service, its templates, and its outputs are not legal, regulatory, or compliance advice. You and your Senior Management Official and Facility Security Officer remain solely responsible for your organization's compliance with 32 CFR Part 117, your DD Form 254s, and all other applicable requirements, and for all reports and submissions to the Government.

9. Disclaimers, Limitation of Liability, and Indemnity

9.1 Disclaimer of warranties. THE SERVICE IS A BETA PROVIDED "AS IS" AND "AS AVAILABLE," WITH ALL FAULTS. TO THE FULLEST EXTENT PERMITTED BY LAW, THE INTS2 PARTIES DISCLAIM ALL WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, AND THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, SECURE, OR THAT DATA WILL BE PRESERVED.

9.2 Exclusion of damages. TO THE FULLEST EXTENT PERMITTED BY LAW, THE INTS2 PARTIES WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF DATA OR ACCESS, PROFITS, REVENUE, CONTRACTS, GOODWILL, FACILITY CLEARANCE STANDING, OR SECURITY RATING, OR FOR COSTS OF RE-CREATING DATA OR PROCURING SUBSTITUTE SERVICES, HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, EVEN IF ADVISED OF THEIR POSSIBILITY.

9.3 Cap. THE INTS2 PARTIES' TOTAL LIABILITY ARISING OUT OF OR RELATING TO THIS AGREEMENT OR THE SERVICE WILL NOT EXCEED ONE HUNDRED U.S. DOLLARS (US $100), AND IN NO EVENT WILL IT EXCEED THE TOTAL AMOUNT YOU PAID INTS2 FOR THE SERVICE (WHICH, FOR A FREE BETA, IS ZERO).

9.4 Exceptions. Sections 9.2 and 9.3 do not limit liability that cannot be limited under applicable law, including liability for gross negligence, willful misconduct, or fraud.

9.5 Your indemnity. You will defend, indemnify, and hold harmless the INTS2 Parties from any third-party claim, government inquiry, loss, or expense (including reasonable attorneys' fees) arising from (a) Tester Data, including prohibited data you enter in violation of Section 3.2; (b) your breach of this Agreement; or (c) your use of the Service or its outputs in violation of law.

10. Term, Termination, and Survival

10.1 Term. This Agreement starts when you accept it and continues until the Beta Period ends, unless terminated earlier.

10.2 Termination. Either party may terminate this Agreement at any time by written notice (email is sufficient – admin@fsoconsole.com). INTS2 may suspend or terminate your access immediately if you breach Sections 3.2, 4, or 5.

10.3 Return and destruction. When this Agreement ends, or on INTS2's request, you will stop using the Service and, within ten (10) business days, export any Tester Data you wish to keep, uninstall and delete all copies of the software from your environment, and return or destroy all Confidential Information and Derived Materials in your possession, including notes, screenshots, and electronic copies, and confirm this in writing on request.

10.4 Duration of confidentiality. Your obligations under Section 4 continue for five (5) years after this Agreement ends, except that for any Confidential Information that is a trade secret, they continue for as long as it remains a trade secret under applicable law.

10.5 Survival. Sections 1, 3.3, 3.4, 4, 5, 6.3, 7.3, 7.7, 8, 9, 10.3 through 10.5, and 11 survive termination or expiration.

11. Remedies and General Terms

11.1 Equitable relief. A breach of Sections 4 or 5 would cause INTS2 irreparable harm for which money damages would be inadequate. INTS2 may seek injunctive relief and specific performance without posting a bond or proving actual damages, in addition to any other remedy. The prevailing party in an action to enforce Sections 4 or 5 may recover its reasonable attorneys' fees and costs.

11.2 Defend Trade Secrets Act notice. An individual shall not be held criminally or civilly liable under any federal or state trade secret law for the disclosure of a trade secret that (a) is made in confidence to a federal, state, or local government official, either directly or indirectly, or to an attorney, solely for the purpose of reporting or investigating a suspected violation of law; or (b) is made in a complaint or other document filed in a lawsuit or other proceeding, if such filing is made under seal. An individual who files a lawsuit for retaliation for reporting a suspected violation of law may disclose the trade secret to the individual's attorney and use the trade secret information in the court proceeding, if the individual files any document containing the trade secret under seal and does not disclose the trade secret except pursuant to court order (18 U.S.C. § 1833(b)). Nothing in this Agreement limits any person's right to report to DCSA, an Inspector General, or any other government authority.

11.3 Export compliance. You will comply with all applicable U.S. export control and sanctions laws in using the Service and will not permit access by any person or from any country prohibited by those laws.

11.4 Governing law and venue. This Agreement is governed by the laws of the State of Texas, without regard to conflict-of-laws rules. The state courts located in Williamson County, Texas, and the United States District Court for the Western District of Texas, Austin Division, have exclusive jurisdiction, and each party consents to personal jurisdiction there, except that INTS2 may seek injunctive relief in any court of competent jurisdiction.

11.5 Entire agreement; order of precedence. This Agreement is the entire agreement about the beta and supersedes prior discussions about it. It survives, and is not superseded by, any later subscription or license agreement unless that agreement expressly references and replaces this Agreement by name.

11.6 Changes. INTS2 may update this Agreement for future testers. Changes will not apply to your current Beta Period without your consent.

11.7 Miscellaneous. You may not assign this Agreement without INTS2's written consent; INTS2 may assign it to a successor or affiliate. If any provision is held unenforceable, it will be enforced to the maximum extent permitted and the rest remains in effect. A waiver is effective only in writing. Notices to INTS2 go to admin@fsoconsole.com; notices to you go to the email on your account. Electronic acceptance has the same effect as a handwritten signature.

Acceptance

Name: ____________________ Title: ____________________

Organization: ____________________ CAGE (optional): __________

Email: ____________________ Date accepted: __________

Appendices — Production Agreement Forms

Appendices A through C are forms for the production release of FSO Console™. They are not part of the Beta Agreement above and do not bind Testers during the Beta Period.

Appendix A — FSO Console™ End User License Agreement

This End User License Agreement ("EULA") is between INTS2, Intelligence Support & Services, LLC, a Texas limited liability company with its headquarters in North Carolina ("INTS2" or "Licensor"), and the company that obtains an Authorization Code for FSO Console™ ("Customer"). Customer accepts this EULA by installing, activating, or using the Software.

A1. Definitions

A2. License grant. Subject to this EULA and payment of applicable fees, INTS2 grants Customer a non-exclusive, non-transferable, non-sublicensable license during the License Term to install and run the Software in Customer's own environment, and to permit its Users to use it, solely to manage Customer's own industrial-security compliance. A part-time FSO may use one Instance for multiple client companies only where each client holds its own Authorization Code or has authorized that use in writing.

A3. Perpetual data-access license. Regardless of expiry, non-payment, or termination, Customer retains a perpetual, royalty-free license to run the Software solely to view and export Customer Data. This survives any end of this EULA.

A4. Restrictions. Customer will not, and will not permit anyone to: (a) reverse engineer, decompile, or disassemble the Software, except to the extent applicable law expressly permits despite this restriction; (b) copy, modify, or create derivative works of the Software, other than one backup copy; (c) sell, rent, lease, or provide the Software to third parties as a service bureau or hosted offering; (d) circumvent, disable, or tamper with license verification or the Software's clock checks; (e) remove proprietary notices; or (f) use the Software to store or process classified information, or Controlled Unclassified Information unless the Documentation expressly states that the Software supports it.

A5. Ownership and Feedback. INTS2 and its licensors own the Software and all related intellectual property. No rights are granted except as expressly stated. Customer grants INTS2 a perpetual, irrevocable, royalty-free, worldwide license to use any feedback or suggestions Customer provides, without obligation.

A6. Customer Data. Customer owns Customer Data. Customer Data resides only in Customer's environment, and INTS2 has no access to it. Appendix C describes data handling in more detail and forms part of this EULA.

A7. Customer responsibilities. Customer is solely responsible for: (a) its environment, infrastructure, security, backups, and recovery; (b) granting, approving, and removing User access through its Owner and Alternate; (c) the accuracy, legality, and lawful use of Customer Data, including any notices to or consents from individuals whose information it enters; (d) the self-attested accuracy of its CAGE Code, UEI, and clearance information; (e) installing updates; and (f) its compliance with 32 CFR Part 117 and all contract and reporting obligations.

A8. Not an authoritative system; no verification. The Software is a management aid, not a system of record. It does not verify identity, entity status, or clearance against SAM.gov, DISS, NISS, or any other source. It is not developed, endorsed, or certified by DCSA or any government agency. Scores and ratings it displays are unofficial. Nothing in the Software is legal or compliance advice.

A9. Updates and support. INTS2 will make updates available through its designated release channel, and Customer chooses when to install them. INTS2 provides email support at admin@fsoconsole.com during its normal business hours. Because INTS2 has no access to Customer's Instance, support is limited to guidance, documentation, and updates. INTS2 supports each major release for twelve (12) months after the next major release.

A10. Limited warranty. For ninety (90) days after Customer first receives a paid release, INTS2 warrants that the Software will perform substantially as described in its Documentation. Customer's exclusive remedy, and INTS2's sole obligation, for breach of this warranty is for INTS2 to use reasonable efforts to correct the nonconformity, or, if it cannot, to refund the fees paid for the affected License Term. This warranty does not apply to free or trial Authorization Codes, modified Software, or problems caused by Customer's environment.

A11. Disclaimer. EXCEPT FOR SECTION A10, THE SOFTWARE IS PROVIDED "AS IS." INTS2 DISCLAIMS ALL OTHER WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND ANY WARRANTY THAT THE SOFTWARE WILL BE ERROR-FREE OR THAT DATA WILL NOT BE LOST.

A12. Limitation of liability. NEITHER PARTY IS LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR LOST DATA, PROFITS, CONTRACTS, FACILITY CLEARANCE STANDING, OR SECURITY RATING. EACH PARTY'S TOTAL LIABILITY IS LIMITED TO THE FEES CUSTOMER PAID FOR THE SOFTWARE IN THE TWELVE (12) MONTHS BEFORE THE CLAIM. THESE LIMITS DO NOT APPLY TO A PARTY'S INDEMNITY OBLIGATIONS, CUSTOMER'S BREACH OF SECTION A4, OR LIABILITY FOR GROSS NEGLIGENCE, WILLFUL MISCONDUCT, OR FRAUD.

A13. Indemnities. INTS2 will defend Customer against any third-party claim that the unmodified Software infringes a United States patent, copyright, or trade secret, and pay resulting damages and costs finally awarded or agreed in settlement. INTS2 may modify or replace the Software, obtain a license for it, or end the license and refund prepaid fees for the unused term. This obligation does not cover claims arising from Customer Data, modifications, or combinations INTS2 did not provide. Customer will defend INTS2 against third-party claims and government inquiries arising from Customer Data or Customer's breach of this EULA. Each indemnity requires prompt notice, sole control of the defense, and reasonable cooperation.

A14. Confidentiality. Each party will protect the other's non-public information with at least reasonable care and use it only to perform this EULA. Confidentiality obligations last five (5) years after termination, and as long as information remains a trade secret.

A15. Term and termination. This EULA lasts while any Authorization Code issued to Customer is in effect. Either party may terminate it on thirty (30) days' written notice if the other materially breaches and fails to cure within that period. On expiry or termination, Customer will stop creating new records except as Appendix B allows, and Section A3 continues to apply.

A16. Government end users. The Software is "commercial computer software" and its Documentation is "commercial computer software documentation" as those terms are used in FAR 12.212 and DFARS 227.7202. Government end users acquire only the rights stated in this EULA.

A17. Export compliance. Customer will comply with all applicable U.S. export control and sanctions laws.

A18. General. This EULA, Appendix B, Appendix C, and any order form are the entire agreement on this subject. Texas law governs, and the state courts in Williamson County, Texas, and the U.S. District Court for the Western District of Texas, Austin Division, have exclusive jurisdiction. Customer may not assign this EULA without INTS2's consent, except to a successor of its entire business that is not a competitor of INTS2. Notices to INTS2 go to admin@fsoconsole.com. If any term is unenforceable, the rest remains in effect.

Appendix B — Authorization Code and Subscription Terms

These terms explain how Customer obtains, uses, and renews the Authorization Codes that enable FSO Console™. They form part of the EULA in Appendix A. If they conflict with the EULA, the EULA controls, except on fees and License Terms.

B1. How Authorization Codes work. An Authorization Code is a license digitally signed by INTS2. The Software verifies it against a public key built into the Software. Verification happens entirely inside Customer's Instance, with no connection to INTS2, so the Software works in isolated environments, and this is unchanged. The only outbound connection the Software makes for licensing is the optional automatic renewal check in Section B5, which, when enabled, sends only the current Authorization Code to INTS2 to retrieve the next one. Because an Authorization Code is verified offline, INTS2 cannot remotely revoke, extend, or change an Authorization Code once it is issued; a renewal is delivered as a separate, newly issued Authorization Code, not a change to one already issued.

B2. Types of Authorization Code.

Type How obtained License Term Renews Warranty and support
Paid Subscription Purchase under an order form or invoice The term stated in the code — annual (12 months) or month-to-month (one calendar month); see B3 Automatically renews until canceled (Section B5) Appendix A, Sections A9 and A10
Trial or Beta Issued by INTS2 for evaluation Stated in the code (Beta: 30 days) Does not auto-renew None; governed by the Beta Agreement or trial terms
Promotional or Complimentary Issued by INTS2 at its discretion Stated in the code Does not auto-renew unless INTS2 states otherwise in writing None, unless INTS2 agrees in writing

B3. License Term. Each License Term starts on the start date encoded in the Authorization Code and ends on its encoded end date. The Software measures time using the clock of Customer's environment. Paid Subscriptions are offered on an annual or month-to-month basis:

B4. Fees and payment. Fees are stated in the order form or invoice and are payable in advance in U.S. dollars, within thirty (30) days of invoice unless stated otherwise. For an auto-renewing Paid Subscription, fees for each renewal term are billed in advance to the payment method Customer has on file, at the then-current price, until Customer cancels under Section B5. Fees exclude taxes, which Customer pays, other than taxes on INTS2's income. Except as stated in Appendix A, Sections A10 and A13, fees are non-refundable.

B5. Automatic renewal; cancellation. A Paid Subscription renews automatically for successive License Terms, each equal in length to the prior term, until Customer cancels. Before each renewal, INTS2 issues Customer's next Authorization Code for the upcoming term. Customer's Instance obtains that code in one of two ways:

Either way, Authorization Codes remain fixed-term and are verified offline inside Customer's Instance.

Renewal notice. INTS2 will email Customer's billing contact a renewal notice before each end date — at least sixty (60) days before for an annual subscription, and at least five (5) days before the end of the then-current month for a month-to-month subscription. INTS2 will give notice of any price increase before it applies to a renewal — at least sixty (60) days for annual, and at least five (5) days for month-to-month.

Cancellation. Customer may cancel automatic renewal at any time, effective at the end of the then-current term, through Customer's FSO Console account, or by notice to admin@fsoconsole.com — received at least thirty (30) days before the end date for an annual subscription, or at least five (5) days before the end of the then-current month for a month-to-month subscription. On cancellation, no further charge is made and no further Authorization Code is issued; the current Authorization Code runs to its end date, after which Section B7 applies. Trial, Beta, and (unless INTS2 states otherwise in writing) Promotional or Complimentary Authorization Codes do not auto-renew.

B5a. The automatic renewal check — how it works and what it sends. When enabled, the automatic renewal check:

INTS2 receives no Customer Data through the renewal check and maintains no central store of Customer Data; the design of Appendix C is otherwise unchanged.

B6. Expiry warnings. The Software displays escalating warnings inside the Instance as the end date approaches. Customer is responsible for watching for them and for keeping its environment's clock accurate. The warning schedule is scaled to the length of the License Term, so that a shorter-term code—such as a 30-day beta or a month-to-month subscription—begins warning proportionally earlier rather than only at or near expiry, and a longer term (such as an annual subscription) receives correspondingly earlier notice.

B7. What happens at expiry. After an Authorization Code ends without renewal, the Software may restrict creating or editing records. The restriction may also cover sending or uploading content and queued deliveries, and takes effect only after a brief read-only grace period. Expiry never restricts Customer's ability to view Customer Data or to use the full-data export, and INTS2 never deletes Customer Data, which remains in Customer's environment. Entering a new Authorization Code restores full use. A new Authorization Code is installed on the Software's in-app license screen and restores full use immediately upon a successful, verified installation.

B8. Permitted use of codes. Each Authorization Code is for the Customer and Instance named in it. Customer will not share, sell, transfer, or publish an Authorization Code, alter it, generate its own codes, or change its environment's clock to extend a License Term.

B9. Lost or exposed codes. If an Authorization Code is lost or exposed, INTS2 will issue a replacement for the remaining License Term at no charge on request to admin@fsoconsole.com. Since INTS2 cannot revoke a deployed code, misuse of an exposed code is addressed under the EULA.

B10. Changes to these terms. INTS2 may update these terms for future Authorization Codes. Changes do not apply to an Authorization Code already issued.

Appendix C — Data Ownership and Handling Statement

Customer owns all Customer Data, it stays in Customer's own environment, and INTS2 has no access to it. This statement forms part of the EULA in Appendix A.

C1. Where data lives. FSO Console™ runs as an isolated Instance in Customer's own Google Cloud or Google Workspace environment. All Customer Data is stored there. INTS2 does not host Customer Data, receives no copy, and maintains no central store of customer data.

C2. INTS2 is a software licensor, not a host or processor. INTS2 does not process Customer Data on Customer's behalf. Hosted-service commitments such as uptime guarantees, sub-processor lists, hosted-data breach notification, and data return at termination therefore do not apply to INTS2. Customer's agreement with its cloud provider governs those matters.

C3. No vendor access. INTS2 has no remote administrative connection, backdoor, escrow, or recovery key for any Instance. INTS2 cannot read, change, recover, or delete Customer Data, and cannot grant, revoke, or restore any User's access. The Software sends no usage data, telemetry, or Customer Data to INTS2. The optional automatic renewal check in Appendix B5a sends only the current Authorization Code and no Customer Data.

C4. Portability. The Software includes a one-click full-data export that produces a complete, re-readable copy of Customer's records and stored documents. It is available before, during, and after any License Term, regardless of license status. Controlled content is excluded from exports by design.

C5. Separation between companies. Within an Instance, each company's data is separated from every other company's data. Users see only companies for which their membership is approved. Owners and Alternates approve all memberships.

C6. Email. Email the Software sends or receives uses Customer's own connected mailbox and mail transport. INTS2 is not in the mail path.

C7. What INTS2 does hold. INTS2 holds only: Customer's account, billing, and contact information; order and Authorization Code records; support communications; and feedback Customer chooses to send. INTS2 uses this information only to provide licenses, support, and billing, and protects it with commercially reasonable safeguards.

C8. Support communications. Customer will not send INTS2 classified information, Controlled Unclassified Information, Social Security Numbers, or other sensitive personal information in support requests or screenshots. If INTS2 receives such information, it will delete it once the support matter is resolved.

C9. Who is responsible for what.

Responsibility Customer INTS2
Hosting, availability, and backups of the Instance Yes No
Security of Customer's cloud environment and email Yes No
Approving and removing User access Yes (Owner and Alternate) No
Account recovery and break-glass codes Yes No
Accuracy of CAGE, UEI, and clearance information Yes (self-attested) No
Notices to individuals whose data is entered Yes No
Installing updates Yes No
Secure development of the Software, with no hidden access No Yes
Publishing fixes for known vulnerabilities No Yes
Issuing and replacing Authorization Codes No Yes
Protecting account, billing, and support information INTS2 holds No Yes

C10. Vulnerability notice. If INTS2 learns of a security vulnerability in the Software that could expose or alter Customer Data, INTS2 will notify Customer's designated contact within seventy-two (72) hours and make a fix or workaround available when one exists.

C11. Changes. INTS2 will give Customer thirty (30) days' notice before any change to this statement that would reduce Customer's protections. No change will give INTS2 access to Customer Data without Customer's express written consent.