FAHCE Machine Data Handling Policy
FAHCE / AI Repair is operated by Max R.O.I. LLC under the Kingan Logic brand, an Alabama limited liability company, Alabama Entity ID 001-160-677. Company, billing, privacy and security contact: logan@kinganlogic.com.
Ingress and analysis. JSON request bodies, headers and network metadata pass through Cloudflare. The total request ceiling is 524288 UTF-8 bytes, including JSON overhead. Requests may contain at most 12 evidence items, each with at most 200000 UTF-16 code units; the aggregate byte ceiling takes precedence. The current machine path executes a local deterministic engine without model-provider or training requests.
Private content. Generated determinations can include submitted candidate text, evidence excerpts, labels and analysis. Private response JSON and integrity hashes are stored in D1. This machine path does not upload raw input files to R2. Separate authenticated human workflows may use other storage and integrations; a machine purchase grants no access to them.
Purchase and financial metadata. D1 stores server-owned purchase identifiers, authorization and input hashes, operation, timing, delivery state, scoped recovery verifiers and separate append-only financial events. Original raw payment signatures and plaintext recovery credentials are not stored as reusable login secrets. Financial state can remain pending until authoritative evidence is reviewed. The origin does not manufacture gateway receipts or settled-charge confirmations.
Telemetry and subprocessors. Cloudflare supplies edge, compute, D1, network and invocation telemetry and backup services. Application logging uses bounded operational fields rather than logging raw machine bodies, payment credentials or generated output. The separate human website uses Datadog browser monitoring. Read-only refund verification uses Base mainnet RPC infrastructure, including mainnet.base.org, to check public chain and destination-signature information; it does not sign transactions. Applicable provider processing and backup lifecycles remain separate from application deletion.
Retention and recovery. New paid-machine primary private results target 30 days from purchase reservation; ordinary recovery expires at the recorded deadline. Holds and unresolved charges or disputes can preserve content for restricted review. Scheduled controls remove eligible D1 serving copies and do not delete protected historical human-workflow evidence. Provider backups are not represented as instantly erased. We retain minimal financial records for at least seven years from the end of the transaction year, extended for later relevant events, applicable law and holds. Private customer evidence is kept separate from that financial standard.
Scope and requests. A cryptographically random purchase-scoped credential authorizes nonexecuting recovery while content is available. A UUID, content hash, unverified signature or claimed address alone grants no access. Lost-first-response recovery requires separately verified original-purchase entitlement. Contact logan@kinganlogic.com for privacy or data-handling requests. We verify authority and preserve applicable rights and lawful obligations.
Effective October 14, 2026 ยท Version 1.4.0
Policy bundle hash: 1deba60d2149bae8aeb057a8198f044602a6a6bb4ee20e9d41dece64c87b2ea5