HAL SUPREME
Menu
Effective October 27, 2026

Privacy Policy

This policy explains how the HAL SUPREME website, One HAL account, chat, music service, and optional paid memberships process information, including what HAL stores and what payment information stays with PayPal.

Who operates HAL

HAL SUPREME is operated under the public creator identity Unite And Create For Life. Privacy questions can be sent to opportunities@halsupreme.com.

Chat and public website data

On your device

Conversation history

The public chat interface keeps conversation history in local browser storage so it can reopen on the same device. It is stored in your browser until you clear chats or browser data.

To produce a reply

Message processing

Messages you send are transmitted to HAL's edge service and to the AI model providers selected to create the response. Do not send passwords, access tokens, financial account details, or information you are not permitted to share.

Reliability and abuse prevention

Operational records

HAL's structured edge log can record route, response status, mode, authentication type, degraded state, and elapsed time. That structured log does not include message content or IP addresses. Cloudflare can process network identifiers for delivery, security, rate limiting, and human-verification checks under its own terms.

One HAL account, sync, and creator tools

HAL supports a signed-in account for account sync and membership entitlements.

Depending on which sign-in method is configured and chosen, HAL can store an internal user ID, provider type, provider-specific identifier, display name, avatar URL, handle, hashed passcode material, passkey public-key data, and hashed session tokens. OAuth access tokens are not stored as your HAL session credential. Session cookies are HTTP-only and the stored session record uses a token hash.

When account sync is used, HAL can store favorites and the chat-history body associated with that HAL user. Account sync uses a bounded service limit and is not sold as a premium storage entitlement. Local browser history can still exist separately on a device. HAL-managed hosted services can use short-lived operational counters and hashed network identifiers for fair-use, abuse prevention, reliability and capacity protection; these controls do not contain prompt or reply text. Earlier membership builds may have recorded aggregate daily request counters, also without prompt or reply content. For paid managed-compute accounting, HAL can store a membership compute-period identifier, plan tier, included/used/reserved internal cost amounts, and idempotent usage-event metadata such as an event ID, compute source category, cost-evidence category, provider/model identifiers and observed hosted cost. The compute ledger does not need prompt or reply text. Work executed through user-controlled local, connected or self-hosted compute is not treated as a paid daily membership-message counter and does not debit Managed Compute Credits. Music jobs store the user ID, requested mode, duration and text inputs needed to run the job, operational status, queue metadata, the membership tier used when the job was admitted, and the retention allocation captured for that job. Temporary voice clips and generated audio are stored with bounded retention by the music service.

Membership payments

Optional web memberships use PayPal for recurring billing. PayPal collects and processes the payment method and payer information under PayPal's privacy practices. HAL does not need or store your card or bank-account number.

To attach a PayPal subscription to the correct HAL account and deliver the purchased service allocation, HAL stores limited payment metadata such as the PayPal subscription ID, PayPal plan ID, membership tier and status, current billing-period information when available, the payer email returned with the PayPal subscription for account support/reconciliation, verified webhook event IDs, and payment event amount/currency metadata. HAL also uses short-lived account-bound checkout tokens to prevent a subscription from being attached to the wrong user.

PayPal webhook messages are authenticated before membership state changes. Payment/subscription metadata may be retained as reasonably necessary for account support, fraud/security controls, accounting, dispute handling, and legal obligations. Android digital purchases, if offered inside an Android app, require their own Google Play Billing entitlement and disclosure flow.

Your choices

You can clear local chat history from HAL's settings or your browser, sign out of the HAL account, and cancel an active membership from the signed-in membership panel. The account deletion page explains the account-data deletion process and the separate need to stop recurring PayPal billing before account deletion is finalized. You may contact us to ask what HAL-associated data exists for you, request correction or deletion where applicable, or raise a privacy concern.

This service is not directed to children under 13. Material changes will be posted with a revised effective date before they apply.