Legal

Supplemental Terms

Supplemental Terms readiness summary for Haynechi customers, partners, and evaluators.

Legal Readiness

Document posture belongs inside the trust system.

These pages are public evaluation summaries. Production commitments stay tied to buyer scope, customer data boundaries, counsel review, and the Trust Center readiness ledger.

Trust center

Readiness StatusProduct terms draft

Supplemental terms describe feature-specific boundaries for benchmark reports, supervised agents, integrations, pilot workspaces, and AI-generated workflow artifacts.

Document Sections

Agents

Agent outputs are work drafts tied to evidence and approval gates, not autonomous publication actions.

Reports

Benchmark outputs preserve methodology, prompt sets, source traces, and sample limitations.

Integrations

Connected systems and data destinations stay scoped in the order form or implementation plan.

Evaluation use

Prospect workspaces may use sample or customer-provided data for evaluation unless otherwise agreed.

Review Path4 steps

01 Identify document

Confirm which agreement, policy, DPA, SLA, or support path fits the buyer motion.

02 Attach scope

Tie each draft to workspace boundaries, pilot data, integrations, agent outputs, retention terms, and order-form scope.

03 Review externally

Route production language through counsel before signature, launch, customer reliance, or procurement submission.

04 Update packet

Keep public summaries, trust center notes, subprocessors, security answers, and order-form scope aligned.

Readiness EvidenceCurrent packet

Static site

Headers, redirects, security.txt, generated metadata, sitemap, llms.txt, contact intake, and deployment docs.

implemented

Pilot materials

Markets, competitors, prompts, URLs, source notes, evidence snapshots, readout artifacts, and sample workspaces.

scoped

Workspace controls

Roles, approvals, audit exports, retention windows, deletion flows, SSO, SCIM, and warehouse sync.

future app

Enterprise packet

MSA, DPA, SLA, support path, supplemental terms, privacy summary, and security questionnaire posture.

draft-ready

Legal BoundariesHonest claims

Public summary only

These pages are evaluation summaries, not executed agreements or legal advice.

Counsel review path

Final language receives counsel review before signature, customer reliance, launch, or procurement submission.

Scoped compliance posture

The packet keeps SOC 2, certification, uptime, and control claims tied to completed evidence.

Order form controls scope

Customer-specific commitments belong in signed order forms, implementation plans, or counsel-approved schedules.

Procurement Packet Room

Make Supplemental Terms inspectable before anyone relies on it.

Haynechi legal pages help buyers, security reviewers, and counsel understand the document packet: drafted language, existing evidence, future-app controls, and signed customer-scope commitments.

Enterprise readiness

Document PacketProduct terms draft

Feature schedule

Benchmark reports, supervised agents, integrations, exports, and pilot workspaces carry feature-specific boundaries.

product

Agent output status

Generated briefs and source plans remain drafts until a customer owner approves use, export, or publication.

approval

Report method

Prompt sets, capture windows, source traces, sample labels, and confidence language travel with every benchmark.

method

Evaluation data

Prospect and pilot workspaces specify whether inputs are sample, public, customer-provided, or approved.

scope

Control EvidenceState ledger

Static public surface

Generated legal routes, metadata, headers, redirects, sitemap, llms.txt, and security contact are implemented for evaluator discovery.

implemented

Customer-specific terms

Order-form scope, negotiated commitments, implementation paths, and commercial remedies stay customer-specific.

scoped

Production controls

Roles, retention, deletion, SSO, SCIM, audit exports, monitoring, and workspace data flows remain future-app work until built.

future app

External review

Counsel, procurement, security, and buyer stakeholders review final language before reliance.

required

Buyer Questions4 topics

Agents

Agent outputs are work drafts tied to evidence and approval gates, not autonomous publication actions.

Reports

Benchmark outputs preserve methodology, prompt sets, source traces, and sample limitations.

Integrations

Connected systems and data destinations stay scoped in the order form or implementation plan.

Evaluation use

Prospect workspaces may use sample or customer-provided data for evaluation unless otherwise agreed.

Review ArtifactsPacket build

Feature addendum

Short schedules for Answer Map, Agent Runtime, Proof Console, integrations, and benchmark reports.

Agent approval notes

Reviewer, output artifact, evidence links, export destination, and publication state.

Methodology appendix

Prompt protocol, scoring model, source taxonomy, limitations, and sample-data labels.

Evaluation workspace rules

What can be tested, retained, exported, or deleted before production contracting.

Procurement BoundariesBuyer-ready

Readiness packet

The room shows how the packet comes together; signed agreements and counsel-reviewed terms remain the source of reliance.

Control state stays visible

Implemented, scoped, future-app, and required-review items stay separated so credibility does not outrun reality.

Evidence-backed compliance

Security certifications, uptime credits, subprocessors, and privacy commitments appear only when actually supported.

Pilot first

Enterprise-grade commitments follow a scoped Pilot Map, data inventory, implementation plan, and negotiated order form.