Legal

Support Policy

Support Policy 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 StatusSupport draft

The support policy gives pilot and production customers clear paths for implementation questions, data issues, report updates, and security concerns.

Document Sections

Pilot support

Pilot Map customers have a named contact, scheduled review points, and a readout handoff.

Operator support

Workspace questions route by account, market, source issue, engine coverage, or integration concern.

Security reports

Security reports use the responsible disclosure route and include reproduction details.

Escalation

Enterprise escalation paths are agreed during implementation planning.

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 Support Policy 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 PacketSupport draft

Pilot coverage

Named contact, review cadence, scope questions, report updates, and readout handoff stay clear for every Pilot Map.

pilot

Workspace support

Questions route by account, market, prompt set, source issue, engine coverage, or integration concern.

workspace

Security channel

Responsible disclosure reports include reproduction details, scope, contact path, and coordinated resolution language.

security

Escalation model

Enterprise escalation is agreed during implementation rather than implied by the public summary.

escalation

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

Pilot support

Pilot Map customers have a named contact, scheduled review points, and a readout handoff.

Operator support

Workspace questions route by account, market, source issue, engine coverage, or integration concern.

Security reports

Security reports use the responsible disclosure route and include reproduction details.

Escalation

Enterprise escalation paths are agreed during implementation planning.

Review ArtifactsPacket build

Support intake fields

Account, workspace, market, issue class, urgency, affected artifact, and reproduction notes.

Pilot calendar

Kickoff, evidence review, mid-pilot correction, final readout, and next-scope decision.

Escalation tree

Pilot owner, implementation lead, security contact, and future enterprise support owner.

Known-boundary note

What is included during pilots versus what waits for production support operations.

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.