Independent from the implementer—not independent certification.

HatchCheck compares the safe launch materials you provide with current Apple and Google guidance HatchCheck tracks, plus clearly labeled internal checks. Missing evidence stays not verified.

HatchCheck is separate from the coding tool, developer, or freelancer implementing the fix. It is not certification, Apple or Google affiliation, legal approval, or an outcome guarantee.

Never upload credentials, private keys, signing certificates, production environment files, customer or payment data, private links, raw logs, cookies, tokens, or real demo passwords.

Xuru Ren performs routine private manual beta reviews. Automation prepares evidence-linked findings, but serious findings are checked before delivery. Paid activation remains paused until a named backup reviewer and calibration record exist. Sensitive or ambiguous issues can remain marked for appropriate human or legal review.

HatchCheck does not guarantee approval, certify legal compliance, submit the app, or verify anything the checked evidence does not support.

• • Project and app profile details
• • Guided intake answers
• • Safe launch artifacts and metadata
• • Selected-file scanner summaries
• • URL check results
• • Findings, evidence items, reports, and report exports
• • Read-only integration summaries where a customer explicitly connects or provides them
• • Audit logs and security event summaries
• • Private-link access and record retention are separate. A private link can expire while limited records remain under the published policy; retention does not guarantee recovery of expired material.
• • Planned artifact retention target: 90 days unless a project/report policy says otherwise.
• • Planned report retention target: 365 days unless delivered-report policy requires retention.
• • Planned audit log retention target: 730 days.
• • Until automated retention is fully available, users can request deletion, export, correction, or account-closure support by emailing privacy@gohatchcheck.com.

• • Project access is checked on the server. Sensitive operations use safe audit metadata.
• • Selected safe files are optional. A full repository is not required.
• • HatchCheck is not SOC 2 certified and does not claim production operations are fully proven.

• • No real AI provider call is required for the current V1 checkup flow.
• • If AI assistance is added to a report step, customer content must be redacted, schema-validated, and governed by the configured provider settings before use.
• • Secrets, raw provider payloads, raw customer data, and production credentials must be excluded before AI use.
• • AI output must pass schema validation, prohibited phrase scanning, evidence requirements, and source/rule grounding before it can be treated as report-ready.
• • HatchCheck does not auto-submit to Apple or Google.
• • HatchCheck avoids write-access platform integrations in this workflow.
• • Future integrations will use minimal scopes, encrypted token references, revoke/disconnect behavior, and server-side access checks.

• • For report delivery, upload, refund, satisfaction-review, or product-quality concerns, email support@gohatchcheck.com with the project/report or order reference and a short summary.
• • Paid report support includes a draft satisfaction-review path when a report is generic or not app-specific. A later Apple or Google rejection by itself is not a refund reason.
• • Deletion, export, correction, account-closure, or upload-security concerns can be sent to privacy@gohatchcheck.com while automated controls mature.