Raw private text is not public proof
Reports, website language, and delivery evidence use receipt markers, route status, hashes, and redacted summaries instead of publishing private messages.
Trust proof
Private by design means the boundary is visible.
MindReply is used for sensitive professional communication, so the trust claim has to be inspectable: what is stored, what is redacted, when memory is allowed, and which routes are actually configured.
Receipts are narrow on purpose
The receipt shape is limited to source, timestamp, risk, confidence, action kind, input hash, and rawContentRedacted status.
Memory requires explicit approval
Growth and Pro can describe memory only as an approved lane. Sensitive context is not claimed as persistent until the user chooses what should carry forward.
Human handoff uses the public route
Public support and package requests use info@mind-reply.com, the contact form, or the checkout/invoice route. Personal inboxes stay out of public pages.
Claim discipline
No borrowed trust badges. No invented proof.
Testimonials and compliance badges are useful only when they are real. Until then, MindReply shows the operational boundary and keeps unsupported claims out of public copy.
No customer count, revenue, staff, compliance badge, payment status, or integration status is stated without evidence.
Slack, email, memory, MCP, and payment routes are described as active only when credentials, permissions, and workflow proof exist.
The Website Completion Package keeps scope, price, and invoice/payment route visible before private context is reviewed.
Security and owner decisions stay in private, redacted reports; public pages explain boundaries without exposing sensitive data.
Inspectable surfaces
The proof is spread across public routes buyers can check.
Privacy page
Explains raw-input restraint, receipt shape, review, and derived memory.
Contact route
Handles human follow-up, package requests, billing details, and security owner routing.
Checkout route
Shows GBP 600 fixed price, direct-payment readiness, and invoice fallback.
Package page
Shows deliverables, buyer proof checklist, and invoice-first paymentPath receipt.
Next step