Preview terms that stay honest about beta risk.

These Beta Terms apply only to Preview Features. They are meant to sit beside the Main Agreement as a surgical preview-risk layer rather than quietly rewriting the entire service contract.

Unless AgentAlly expressly says otherwise in writing for a particular Preview Feature, the Main Agreement still governs the rest of the service. If these Beta Terms conflict with the Main Agreement, these Beta Terms control only for the specific Preview Feature at issue.

Current repo truth supports a curated design-partner launch posture rather than a broad self-serve beta. These terms are written so they work for a founder-led cohort now while still supporting later limited preview programs if product truth changes.

The most important boundary in this draft is that Feedback, Operational Customer Content, and Usage Telemetry are not treated as the same thing. Different rights and different risk rules apply to each category.

Feedback is a voluntary participant contribution about the product. Operational Customer Content is the business and workflow material that customers run through AgentAlly. Usage Telemetry is the technical and operational signal generated by product use.

Preview Features include anything AgentAlly labels or otherwise presents as beta, preview, pilot, early access, limited release, experimental, evaluation, in development, non-production, or similar language indicating that the feature is still being tested or has not reached the general-availability baseline.

A Preview Feature may contain bugs or errors, may be incomplete, may behave inconsistently, may depend on unstable provider or model paths, may materially change without notice, and may be unsuitable as the sole basis for critical workflows.

AgentAlly is not promising that any Preview Feature will reach general availability, remain available for any minimum period, or continue in its current form.

Preview Features are provided on an as-is and as-available basis to the maximum extent permitted by law. They may have reduced stability, incomplete functionality, missing safeguards, degraded performance, limited compatibility, or heightened change risk compared with the generally available service.

Preview behavior may be affected by evolving prompts, models, vendors, provider limits, integration changes, feature flags, migration work, or other internal product changes that would not ordinarily be surfaced as a general-service commitment.

Participants should not rely on a Preview Feature as the sole basis for time-sensitive, legally sensitive, housing-sensitive, communication-critical, or compliance-sensitive workflows. Preview outputs and behavior may be wrong, incomplete, stale, or inconsistent even when the general service is functioning normally.

If a Preview Feature touches outbound communications, approval-gated sends, lead handling, housing-sensitive recommendations, or other higher-risk workflows, the participant remains responsible for verifying content, recipients, timing, consent, disclosures, and applicable compliance obligations before use.

Nothing in these Beta Terms creates a commitment to launch, maintain, or roadmap any Preview Feature for general availability.

Preview support may be limited, founder-guided, best-efforts, scheduled, or unavailable at times. AgentAlly does not promise any minimum support level, response time, bug-fix timeline, uptime commitment, service credit, or compatibility guarantee for Preview Features unless those commitments are stated separately in writing.

A high-touch design-partner experience or founder-led support loop may exist in practice for a curated cohort, but that operational posture should not be read as a formal SLA or continuity commitment for Preview Features.

Preview participation does not create any warranty that a bug will be fixed, that a workflow will remain available, or that a feature will graduate into the generally available product.

AgentAlly may add, remove, relabel, replace, limit, pause, suspend, or discontinue a Preview Feature at any time. That includes changes to workflows, prompts, models, integrations, UI, eligibility, access level, quotas, and cohort participation.

AgentAlly may also withdraw or restrict an individual participant's access to a Preview Feature if reasonably necessary for product, security, safety, abuse-prevention, legal, third-party, or launch-readiness reasons.

If a Preview Feature is discontinued, AgentAlly is not obligated to maintain the preview-only functionality or to make the feature generally available. Handling of related Customer Data remains subject to the Main Agreement, Privacy Policy, and applicable retention realities rather than an implied promise of indefinite preview continuity.

If a participant voluntarily provides Feedback, AgentAlly may use that Feedback to operate, evaluate, improve, market, and support the service without obligation, attribution, accounting, or compensation to the participant.

Participants are not required to submit Feedback, and AgentAlly is not required to implement any particular suggestion. The purpose of this clause is to preserve a conventional market feedback-rights posture, not to claim broader rights in operational customer content.

Operational Customer Content remains governed by the Main Agreement and Privacy Policy. Beta participation alone does not grant AgentAlly any additional right to use prompts, outputs, staged communications, approval logs, workspace records, uploaded materials, or other operational content for unrelated analytics, marketing, product improvement, model improvement, or training purposes.

AgentAlly may still process Operational Customer Content as reasonably necessary to provide, secure, maintain, support, troubleshoot, and evaluate the Preview Feature for the participant, subject to the same general data-handling posture that otherwise applies to the service.

If AgentAlly ever wants a separate right to use Operational Customer Content for evaluation, safety review, model improvement, training, or another broader purpose, that right must be described separately and precisely in writing and aligned with the applicable privacy disclosures or other written agreement.

Usage Telemetry and troubleshooting diagnostics may be used to improve preview performance, reliability, and abuse resistance, but those operational analytics are not a back door for converting general Operational Customer Content into unrestricted training material.

AgentAlly may monitor Preview Feature usage to evaluate performance, understand adoption, prioritize fixes, support users, investigate incidents, and prevent misuse or abuse. That monitoring may include logs, diagnostics, feature-usage events, quality signals, approval-state transitions, support interactions, and related Usage Telemetry.

Preview monitoring is intended to keep the product honest and usable, not to erase the distinction between telemetry and Operational Customer Content. Operational oversight should remain aligned with the narrower privacy and approval posture already described in the Main Agreement, Privacy Policy, and AI Policy.

If AgentAlly expressly designates a Preview Feature or cohort as a Private Beta Program, participants may be asked not to publish non-public screenshots, benchmark claims, feature details, roadmap information, or launch timing without AgentAlly's prior written approval.

If AgentAlly does not expressly designate the Preview Feature as private, confidential, or non-public, this section does not create a blanket gag rule by implication. Participants may still share truthful internal evaluation with their own professional advisers or internal stakeholders subject to ordinary confidentiality obligations.

Preview access may be free, discounted, deposit-backed, paid, credit-based, or bundled with another commercial offer if AgentAlly states that separately in writing. AgentAlly is not obligated to continue any free or discounted preview access for any minimum period unless it expressly agrees to do so.

Any preview-specific fees, deposits, pilot credits, refunds, or conversion pricing should be stated in the applicable order form, offer letter, pricing surface, or design-partner materials rather than implied by these Beta Terms alone.

Unless AgentAlly expressly discloses otherwise in writing for a specific Preview Feature, Preview Features remain subject to the same baseline privacy, security, approval, and data-use posture described in the Main Agreement. Beta status alone does not mean that customer content can be used for training, that the security baseline disappears, or that human approval controls no longer apply.

If a specific Preview Feature has a different privacy, security, vendor-routing, retention, approval, or data-use profile, AgentAlly should disclose that difference clearly before the participant uses the feature. Hidden deviations are exactly what this beta layer is meant to prevent.

Any Preview Feature that materially changes outbound communications, approval-gated sending, fair-housing-sensitive logic, compliance-sensitive workflows, or the way operational content reaches vendors or model providers should receive separate review under the G3 and G7 governance tracks before rollout.

AgentAlly may update these Beta Terms or feature-specific preview notices from time to time to reflect product changes, legal needs, or lessons from the preview program. Material changes should be communicated through the product, by email, or through another reasonable notice method before they take effect, unless earlier changes are required for security, abuse-prevention, or legal reasons.

Questions about these Beta Terms or launch-review issues can be sent to ben@getagentally.com. If a preview program ends or a participant is removed from it, these Beta Terms stop applying to future access to that Preview Feature, but the sections that should survive by their nature continue to apply.