These Beta Terms apply to a ContextCloud beta or pilot offering (“Beta Offering”) that Customer expressly accepts from Oshyn Inc (“Oshyn”). They are the standard Beta Terms for both new and existing pilots. The applicable Order identifies the Beta Offering and its scope and duration. An existing pilot may accept these terms in the Service for continuation of its existing Beta Offering without making a new purchase; that acceptance does not itself create or amend an Order, authorize new charges, or elect a standard paid plan. Capitalized terms have the meanings given in the Customer Terms of Service.
Acceptance. These Beta Terms take effect for Customer when a person authorized to bind Customer expressly accepts the identified version through the Service or an Order. Oshyn records the accepting person's identity, the Customer represented, the accepted document versions and text hashes, and the actual time of acceptance. The Customer Terms and AUP must also be expressly accepted if they do not already apply. Previous pilot use, silence, or possession of an administrator account does not by itself establish acceptance or authority to bind Customer.
Existing pilots and previously supplied data. If a pilot began before acceptance, these terms govern continued use and Oshyn's subsequent handling of Customer Data already supplied to the pilot from the actual acceptance date. They do not deem any terms accepted at an earlier date, impose a newly agreed charge for past use, release an accrued claim, or apply a new disclaimer, indemnity, or liability limit to an act or event predating acceptance. Earlier applicable agreements and mandatory law continue to govern those earlier matters; acceptance does not validate an unauthorized prior act.
Customer's acceptance does not establish a Member's or Guest's individual acceptance or reduce protections already applicable to personal-space content. A change affecting existing content remains subject to the applicable individual terms, required express acceptance, and mandatory law.
These Beta Terms supplement the Customer Terms and control only conflicts specific to the Beta Offering. A separately signed agreement remains controlling as provided in section 1 of the Customer Terms. These Beta Terms do not override an executed DPA or mandatory data-transfer safeguards, authorize model training with Customer Data, or displace the express confidentiality, security, and data-handling obligations applicable to the Beta Offering.
1. Nature and changes to the Beta Offering
A Beta Offering is pre-release and may contain defects, produce unexpected results, or change during evaluation. Oshyn may change or withdraw beta features, limits, models, and integrations without advance notice. Customer is not purchasing a commitment that a beta feature will become generally available or remain available in its current form.
Feature changes do not eliminate the agreed process for ending the Beta Offering or the applicable review, export, retention, and deletion rights. Customer should maintain appropriate independent copies of information it needs and use the oversight appropriate to the consequences of an automated action. The automated-action provisions of the Customer Terms apply during beta.
2. Warranties and liability
Except for express commitments in a controlling signed agreement, Oshyn does not provide a beta uptime, response-time, or fitness commitment. Beta availability and durability are not guaranteed; this does not negate an express retention, security, confidentiality, or other obligation preserved by these terms. The warranties, disclaimers, excluded damages, and exceptions in sections 15 and 16 of the Customer Terms otherwise apply.
Beta liability provision. Subject to section 16.3 of the Customer Terms and any controlling signed agreement, Oshyn's aggregate liability to Customer arising from the Beta Offering is limited to the fees Customer actually paid for the applicable beta plan, which may be zero. This beta-specific amount replaces the ordinary amount in section 16.2 for beta claims; it does not remove the exceptions in section 16.3 or liabilities that applicable law does not permit the parties to limit.
3. Support access and credentials
For human inspection of Customer Data to diagnose a reported defect or provide beta support, Oshyn will obtain an authorized Organization administrator's consent for the specific incident. Access must be limited to what that incident requires and must comply with the Customer Terms, the applicable personal-space addendum, any executed DPA, and applicable law. Administrator consent does not bypass a separate inspection notice, access restriction, or other protection applicable to the affected data. Security processing and legally required processing remain governed by the applicable provisions of those agreements.
Credential protection and authorized processing are described in section 7 of the Customer Terms. Stored secret values are encrypted and ordinary views mask them, but the Service can decrypt credentials for authorized operations, and authorized exports can contain encrypted credential records. Beta participation does not mean that secret values are technically inaccessible to the Service or that every staff action is recorded in an Organization audit log. Any specific logging or audit commitment must be expressly agreed. Separate administration work remains subject to section 10 of the Customer Terms.
4. Feedback and Customer Data
Customer may voluntarily provide nonconfidential suggestions about the Service's features, design, or performance (“Feedback”). Oshyn may use that Feedback to improve the Service without compensation and without identifying Customer or its users. This permission does not transfer ownership of Customer Data or grant rights in another person's material.
Feedback does not include underlying workspace content, prompts, credentials, personal data, confidential information, or support files and screenshots merely because they accompany a suggestion or defect report. Providing those materials does not reclassify them or expand Oshyn's permitted use. Applicable confidentiality, privacy, and processing restrictions continue, and Oshyn will not use Customer Data to train AI models.
5. Fees, coupons, and paid-plan election
The Order states the beta charges, metering rules, and any coupon's coverage and expiration, including the service charge percentage applied to Managed Inference and whether charges above included credits require Customer's authorization. A coupon covers the charges expressly identified with it; Oshyn may not charge other amounts unless they were disclosed in and accepted with the Order. Managed Inference may be metered and displayed even where a coupon covers the charge. Charges to Customer's independently contracted providers remain governed by Customer's agreements with them.
A coupon's expiration does not, by itself, authorize undisclosed charges or enrollment in a standard paid plan. Charges after expiration must already be authorized by the accepted Order or require Customer's acceptance of the applicable paid terms. Moving from the Beta Offering to a standard paid plan requires Customer's affirmative election and acceptance of the applicable subscription arrangements; silence does not constitute that election.
6. Ending the Beta Offering
Either party may end the Beta Offering on 30 days' notice. Customer's cancellation rights and the parties' rights to suspend or terminate under the Customer Terms remain available. The notice identifies the beta end date. Continuing on a standard plan requires the paid-plan election described in section 5; ending beta access does not close an Organization while another Order continues to authorize its operation.
When Oshyn notifies Customer that the applicable Beta Offering has become generally available, these Beta Terms cease to govern new activity from the date identified in that notice; the Customer Terms and the applicable subscription arrangements continue to govern. This lapse does not amend an agreed Order, authorize new charges or a paid-plan election, or require re-acceptance merely to remove the beta-specific terms. Any ending of beta access remains subject to the notice rule above. The accepted beta version remains part of the historical agreement, and the obligations and risk allocation that apply to activity during beta continue as provided below.
If no other subscription arrangement authorizes continued operation, the beta end date is treated as the cancellation date under section 5 of the Customer Terms: 30 days of read-only access for review and export, followed by closure and the default 365 days of retention for reinstatement or export. The Customer Terms' qualifications govern throughout, including protective restrictions, earlier binding return or deletion duties, legally required records, and backup handling. These Beta Terms do not create a separate or unconditional retention promise.
Ending the Beta Offering does not extinguish accrued rights, applicable fee or refund obligations, confidentiality duties, or the risk allocation applicable to activity during beta.
7. Confidentiality and permitted statements
Nonpublic information about unreleased features and the Beta Offering is Oshyn's Confidential Information under section 12 of the Customer Terms. Customer may truthfully state that it uses ContextCloud unless Oshyn asks Customer to stop making that statement. This limited permission does not authorize disclosure of Confidential Information, an endorsement claim, or other use of Oshyn's branding. It does not authorize Oshyn to identify Customer in publicity.
Contact
Oshyn Inc
privacy@contextcloud.works