Key Point
Beta features may be incomplete, unstable, or removed entirely without prior notice.
Loading...
Pre-Release Addendum
Additional rules for Kairois while the product is invite-only, experimental, or pre-general-availability.
Key Point
Beta features may be incomplete, unstable, or removed entirely without prior notice.
Key Point
Users should not rely on Kairois beta outputs for critical or irreversible decisions.
Key Point
Beta usage generates high-value feedback, telemetry, and improvement data that Kairois may freely use.
During the beta stage, some or all of Kairois may be invite-only, limited-capacity, experimental, pre-release, or non-public. Features may not be complete and may contain bugs, data-quality issues, incorrect outputs, availability gaps, or changes that break prior behavior.
Beta access is a revocable privilege, not a guaranteed service level or long-term entitlement. We may grant, deny, pause, or revoke beta access at any time for any reason.
You must not rely on beta outputs as your sole source of truth for time-sensitive, safety-sensitive, medical, legal, transportation, employment, or financially material decisions. Maintain your own backups, records, confirmations, and independent judgment.
We do not promise continuity of APIs, models, workflows, fields, settings, integrations, or stored workspaces during beta. Features may be reset, migrated, or deleted.
Because beta is used to evaluate product behavior, we may collect expanded logs, telemetry, qualitative feedback, route/performance traces, interaction data, experiment assignments, and other diagnostics beyond what may exist in later commercial tiers.
We may use beta interactions, Submitted Data, outputs, and observations to test, compare, improve, train, debug, commercialize, and document the Service and related products, subject to our Privacy Policy and applicable law.
If you participate in surveys, interviews, pilots, or evaluation programs, you grant us the unrestricted right to use your feedback, ratings, suggestions, and evaluation results. Unless we separately agree otherwise in writing, we may reference the fact that you participated in beta in aggregate or anonymized form.
We may provide support, migration assistance, feature previews, or access accommodations during beta, but we are not obligated to do so. Beta support channels, turnaround times, credits, and uptime commitments are entirely discretionary unless expressly stated in a separate signed agreement.
These Beta Terms supplement the Terms of Service. If there is a conflict between the two, these Beta Terms control for beta-specific matters to the extent of the conflict.
Pre-Release Addendum
Additional rules for Kairois while the product is invite-only, experimental, or pre-general-availability.
Key Point
Beta features may be incomplete, unstable, or removed entirely without prior notice.
Key Point
Users should not rely on Kairois beta outputs for critical or irreversible decisions.
Key Point
Beta usage generates high-value feedback, telemetry, and improvement data that Kairois may freely use.
During the beta stage, some or all of Kairois may be invite-only, limited-capacity, experimental, pre-release, or non-public. Features may not be complete and may contain bugs, data-quality issues, incorrect outputs, availability gaps, or changes that break prior behavior.
Beta access is a revocable privilege, not a guaranteed service level or long-term entitlement. We may grant, deny, pause, or revoke beta access at any time for any reason.
You must not rely on beta outputs as your sole source of truth for time-sensitive, safety-sensitive, medical, legal, transportation, employment, or financially material decisions. Maintain your own backups, records, confirmations, and independent judgment.
We do not promise continuity of APIs, models, workflows, fields, settings, integrations, or stored workspaces during beta. Features may be reset, migrated, or deleted.
Because beta is used to evaluate product behavior, we may collect expanded logs, telemetry, qualitative feedback, route/performance traces, interaction data, experiment assignments, and other diagnostics beyond what may exist in later commercial tiers.
We may use beta interactions, Submitted Data, outputs, and observations to test, compare, improve, train, debug, commercialize, and document the Service and related products, subject to our Privacy Policy and applicable law.
If you participate in surveys, interviews, pilots, or evaluation programs, you grant us the unrestricted right to use your feedback, ratings, suggestions, and evaluation results. Unless we separately agree otherwise in writing, we may reference the fact that you participated in beta in aggregate or anonymized form.
We may provide support, migration assistance, feature previews, or access accommodations during beta, but we are not obligated to do so. Beta support channels, turnaround times, credits, and uptime commitments are entirely discretionary unless expressly stated in a separate signed agreement.
These Beta Terms supplement the Terms of Service. If there is a conflict between the two, these Beta Terms control for beta-specific matters to the extent of the conflict.