Kilasec Beta Program Agreement

This Beta Program Agreement (the "Agreement") is between Kilasec ("we", "us") and the organization on whose behalf you accept it ("Customer", "you").

1. Definitions

• "Service" — the Kilasec cloud console and APIs at kilasec.com and its subdomains.
• "Software" — the Kilasec collector container and any other Kilasec components we make available to you, including installers, SDKs, directory agents, identity connectors, and associated documentation.
• "Beta Period" — from your acceptance until the earlier of (a) general availability of a commercial release, (b) termination under Section 10, or (c) our discontinuation of the beta program.
• "Customer Data" — data you or your network transmit to or through the Software or Service, including inspected traffic metadata, policy events, and audit records.
• "Feedback" — suggestions, bug reports, feature requests, or other input about the Software or Service that you provide to us.

2. Beta License

Subject to this Agreement, Kilasec grants Customer a limited, non-exclusive, non-transferable, non-sublicensable, revocable license to install and run the Software on infrastructure Customer owns or controls, and to use the Service, in each case solely for Customer's internal evaluation during the Beta Period. Customer may run a reasonable number of collector instances consistent with its approved beta scope.

3. Restrictions

Customer will not, and will not permit anyone else to:

1. redistribute, sell, rent, lease, sublicense, or host the Software or Service for any third party, or operate it as a service bureau or managed offering (MSPs evaluating on behalf of a client must get our written approval first — email ops@kilasec.com; we generally say yes);
2. reverse engineer, decompile, or disassemble the Software, except to the extent applicable law expressly permits despite this restriction;
3. remove or alter proprietary notices;
4. publish benchmarks, performance comparisons, or evaluation results without our prior written consent;
5. use the Software or Service to build, train, or improve a competing product;
6. use the Software or Service in violation of applicable law, or attempt to probe or bypass its security other than good-faith testing on Customer's own tenant (which we encourage — report findings to ops@kilasec.com).

4. Network Interception Authorization

The Software's core function is to intercept, decrypt, inspect, and act on network traffic, which may include the content of employee and system communications with AI model providers. Customer represents and warrants that:

1. Customer owns, or is expressly authorized by the owner to administer, every network segment and system on which it deploys the Software;
2. Customer has full legal authority to intercept, decrypt, and inspect traffic on those networks;
3. Customer has given all notices to, and obtained all consents from, its network users (including employees and contractors) that are required by applicable law — including, as applicable, wiretap and electronic communications privacy laws, employee-monitoring notification laws, and data protection laws such as the GDPR and CCPA;
4. Customer will scope TLS decryption only to endpoints appropriate for inspection and will use the Software's scoping controls to exclude traffic it is not entitled to inspect.

Customer is solely responsible for its compliance with this Section, and will indemnify, defend, and hold harmless Kilasec from any third-party claim arising out of Customer's breach of it.

5. Customer Data and Privacy

1. Processor role. Kilasec processes Customer Data on Customer's behalf and under Customer's configuration. Customer controls what is inspected, what is redacted, and retention settings.
2. What we store. The Service stores traffic metadata, policy decisions, audit events, and — where Customer's policies capture it — inspected request content. The collector buffers events locally if the Service is unreachable and drains them when connectivity returns.
3. No training. We do not use Customer Data to train machine-learning models.
4. Safeguards. We protect Customer Data with reasonable administrative and technical safeguards. The beta Service is not yet SOC 2 certified (we are on the readiness track); do not route data into the beta that your own compliance obligations prohibit placing with an uncertified processor.
5. Telemetry. The Software reports operational telemetry (version, health, and usage metrics) to the Service so we can operate the beta, including offline-collector alerting.
6. Deletion. On termination, we will delete Customer Data from the Service within 30 days of your written request, excluding backups that age out on our standard cycle.

6. Feedback

Customer grants Kilasec a perpetual, irrevocable, worldwide, royalty-free license to use Feedback for any purpose, without obligation or attribution. Feedback is voluntary; we may develop features similar to any tester's suggestions independently.

7. Confidentiality

"Confidential Information" means non-public information disclosed by either party in connection with the beta, including (for Kilasec) the Software, unreleased features, documentation, and pricing, and (for Customer) Customer Data and Customer's network and security configuration. Each party will use the other's Confidential Information only for the beta, protect it with at least reasonable care, and not disclose it to third parties except to employees and advisors under equivalent obligations. These obligations survive for three (3) years after termination and do not apply to information that is or becomes public through no fault of the recipient, was known before disclosure, or is independently developed.

8. Beta Nature of the Product

Customer acknowledges that the Software and Service are pre-release:

1. they may contain defects, and features may change, break, or be removed without notice;
2. no service level, uptime, or support commitment applies;
3. stored data may be lost — keep your own copies of anything you need;
4. the Software must not be relied on as Customer's sole or primary security control. It is an additional enforcement layer; Customer remains responsible for its own security program, and for the conduct of its users and AI agents;
5. if the Service is unreachable beyond the collector's buffering limits, or the subscription lapses, the collector behaves as documented (fail-open pass-through by default for non-scoped traffic; documented fail-closed semantics for workload-identity rules). Customer is responsible for choosing the failure mode appropriate to its network.

9. Fees

The beta is free of charge. We will give at least thirty (30) days' notice before any feature you are using becomes paid, and you are under no obligation to purchase anything. Customer remains responsible for its own costs, including the third-party AI provider fees of traffic that transits the Software.

10. Term and Termination

This Agreement runs for the Beta Period. Either party may terminate at any time, for any reason, on written notice (email suffices: ops@kilasec.com). We will give at least thirty (30) days' notice before discontinuing the beta program, except where required sooner for security or legal reasons. On termination: the license in Section 2 ends, Customer will stop using the Service and uninstall the Software, and Sections 4–8 and 11–14 survive.

11. Warranty Disclaimer

THE SOFTWARE AND SERVICE ARE PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTY OF ANY KIND. KILASEC DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND ANY WARRANTY THAT THE SOFTWARE WILL DETECT, REDACT, OR BLOCK ANY PARTICULAR DATA OR THREAT. NO DETECTION TECHNOLOGY IS PERFECT; FALSE POSITIVES AND FALSE NEGATIVES WILL OCCUR.

12. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW: (a) NEITHER PARTY WILL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUE, OR DATA; AND (b) KILASEC'S TOTAL LIABILITY UNDER THIS AGREEMENT WILL NOT EXCEED ONE HUNDRED U.S. DOLLARS (US $100). THESE LIMITS DO NOT APPLY TO CUSTOMER'S OBLIGATIONS UNDER SECTIONS 3 (RESTRICTIONS) AND 4 (INTERCEPTION AUTHORIZATION) OR EITHER PARTY'S BREACH OF SECTION 7 (CONFIDENTIALITY).

13. Governing Law

This Agreement is governed by the laws of the State of California, excluding its conflict-of-laws rules. The exclusive venue for disputes is the state and federal courts located in El Dorado County, California, and each party consents to personal jurisdiction there.

14. General

This Agreement is the entire agreement about the beta and supersedes prior discussions. Customer may not assign it without our consent; we may assign it in connection with a merger, acquisition, or sale of assets. A waiver must be in writing. If a provision is unenforceable, the rest remains in effect. We may update this Agreement for future beta periods by posting a new version at kilasec.com/beta-terms.html and notifying active testers by email; continued use after notice is acceptance. Notices to Kilasec: ops@kilasec.com.

---

Questions about these terms: ops@kilasec.com