Legal

Privacy Policy

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 StatusPrivacy draft

The privacy policy explains contact-intake data, pilot workspace materials, analytics, retention, subprocessors, and customer-requested deletion for readiness review.

Document Sections

Contact intake

The public form validates required fields and can forward submissions to a configured CRM or intake webhook.

Pilot materials

Markets, competitors, URLs, prompt priorities, and source notes are used to scope answer evidence and readouts.

Analytics

Public site analytics uses a privacy-conscious analytics provider once production tracking is configured.

Choices

Prospects and customers can request export, correction, or deletion through the sales/security contact flow.

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 Privacy 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 PacketPrivacy draft

Collection map

Contact forms, analytics, pilot materials, workspace inputs, emails, and webhook/CRM forwarding receive distinct explanations.

privacy

Use boundary

Markets, competitors, prompts, URLs, and source notes are used for answer evidence and scoped readouts, not broad resale claims.

use

Choice path

Export, correction, deletion, and contact-preference requests use a clear intake and follow-up route.

rights

Analytics posture

Public site analytics stays privacy-conscious and discloses provider, purpose, and retention once configured.

analytics

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

Contact intake

The public form validates required fields and can forward submissions to a configured CRM or intake webhook.

Pilot materials

Markets, competitors, URLs, prompt priorities, and source notes are used to scope answer evidence and readouts.

Analytics

Public site analytics uses a privacy-conscious analytics provider once production tracking is configured.

Choices

Prospects and customers can request export, correction, or deletion through the sales/security contact flow.

Review ArtifactsPacket build

Data map

Collection point, data category, purpose, destination, retention, and deletion path.

Webhook inventory

CRM, notification, analytics, and email destinations used by the contact intake flow.

Rights request runbook

How a prospect or customer requests export, correction, deletion, or contact preference changes.

Pilot privacy note

How answer-market materials are used during evaluation before authenticated production workspaces exist.

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.