Privacy Policy

Information in the current boundary

HUATRA.ai, Pridicta ReviewPack, Zeravue ProofPack, and Sonolock RecordPack may process limited authentication and session metadata, tenant, organization and case metadata, payment and provider-reference metadata, artifact and delivery metadata, technical and security logs, timestamps, non-sensitive interface preferences, and contact information voluntarily sent through an official channel. Controlled product workflows may process only the categories authorized by their product-specific intake and access boundaries.

Purposes and minimization

Current purposes are site operation, security, troubleshooting, controlled access, inquiry response, review preparation, and required governance records. Do not submit passwords, tokens, payment credentials, private keys, confidential customer records, or regulated material unless a separately approved secure intake and written agreement applies.

Product-specific boundaries

Sonolock is metadata-only in the current authority: it does not retain raw audio, create voiceprints, identify speakers, perform biometric identification, verify identity, or make automated determinations. Zeravue does not determine ownership, infringement, or face identity. Pridicta does not certify compliance or approve or deny a launch.

Retention and data requests

The canonical C20 governance values retain a DSAR request for 90 days and its DSAR audit record for 365 days. These are HUATRA product-governance values, not universal statutory periods, and they do not authorize automatic destructive deletion. Other product, payment, provider, and incident retention periods remain subject to an approved retention schedule and applicable obligations.

Access, correction, deletion, restriction, objection, or other requests are reviewed subject to applicable law, identity verification, security, and preservation duties. Send requests to contact@huatra.ai; no public page performs an automatic deletion or provider action.

Service providers and transfers

Hosting, database, authentication, payment, email, analytics, error-monitoring, and security services are treated as separate provider gates. A package or configuration reference does not prove that a provider is production-active. Provider identity, processing location, transfer mechanism, and legal adequacy require human confirmation before commercial launch.

Cookies, analytics, and diagnostics

The current repository does not enable an external analytics vendor in the public application source. Limited first-party preferences, privacy-minimized operational events, or redacted diagnostics may be used in controlled contexts. They must not include secrets, tokens, payment data, raw provider payloads, or customer material. Any future non-essential analytics activation requires an updated disclosure and approval before use.

Security, contact, and version

HUATRA uses technical, administrative, and organizational safeguards, including server-derived authority, fail-closed access boundaries, structured redaction, and human review. No internet service can guarantee absolute security. Contactcontact@huatra.ai for privacy questions. Draft revision: August 23, 2026. Effective date: pending founder and counsel approval. Status: controlled-launch draft, version 1 review candidate, not an approved commercial privacy notice.