WHAT CROSSES
THE HORIZON.

Who operates AVORBYSS

ACN 700220784 PTY LTD (ACN 700 220 784; ABN 77 700 220 784) operates AVORBYSS and applies privacy controls aligned with the Australian Privacy Principles.

Minimum matter for the chosen passage

• Authentication identity handled by the sign-in and hosting platform.
• Prompts submitted to the public Nexus and the resulting event state.
• Pseudonymous HMAC identity, prompt/evidence digests, timestamps, runtime class and security events.
• Before a hosted return—including the free First Aperture or a paid Creator return—is released, AVORBYSS stores a server-encrypted exact-return record bound to the authenticated recipient and request coordinate. This permits byte-exact recovery if delivery drops, without repeating model work or consuming the request allowance twice, including while admission of new work is sealed.
• On a refresh or reopen, the signed-in browser may ask for at most one latest unacknowledged coordinate belonging to that exact principal. Discovery returns only opaque request and session identifiers plus an operational timestamp; it does not return or persist prompt, conversation history, answer, digest or ciphertext.
• After the browser displays that answer, it acknowledges delivery; AVORBYSS erases the server-side answer ciphertext and encryption nonce, retaining only the minimum delivery tombstone, digests, byte count and operational timestamps.
• Separately, the browser automatically creates an encrypted recipient capsule and attempts to store its ciphertext and minimum routing metadata; the Horizon Vault is not intended to receive plaintext. The capsule decryption capability exists only in that browser session and is not recoverable after refresh or closure. A still-unacknowledged hosted exact return may be recovered through the separate recipient-bound process just described. Copy work you need before leaving the session.
• A pseudonymous Nexus coordinate and two-letter country code when binding your account.
• For controlled Creator checkout, Stripe collects the billing name and address and may collect a tax identifier. AVORBYSS receives the signed billing country and related customer, subscription, invoice and tax evidence needed for the selected route. Australian checkout uses GST evidence; United States checkout uses billing-location and tax evidence; the UK business-only route also receives the registered legal entity name, GB VAT ID and provider-verification state. Stripe holds payment-card details.
• Provider customer, subscription, invoice, refund and dispute references when you use paid billing.
• Your account email and message when you deliberately contact support or a published AVORBYSS role address.
• Feedback only when you deliberately submit it under the displayed consent scope.

Sovereign inference stays in the compatible browser

When Device Mode is offered and selected, the local model and runtime are downloaded to the device. A local prompt is not sent to a model API merely to perform inference. Authentication, asset delivery, optional receipt registration, save, support and hosted features remain separate network operations.

Provide, secure and prove the service

Data is used to authenticate passage, perform the selected event, retain user-chosen continuity, issue evidence receipts, prevent abuse, diagnose faults and comply with law. Customer content is not sold.

The label is separate from the conversation

When you deliberately rate an answer, the control sends the selected outcome label, opaque event coordinates and the evaluation scope you chose. It does not automatically attach your prompt, reply or conversation. Shared aggregate evaluation is a separate opt-in. Founder reporting releases only cohort-suppressed totals, never customer text or identities.

Minimise the permanent field

Local prompts remain within the device session or local browser storage unless you select a networked feature. A hosted exact-return record remains replayable only until acknowledged delivery; acknowledgement erases its answer ciphertext and nonce. Separately stored recipient-capsule ciphertext may persist after its browser-only decryption capability is gone, but that persistence does not make the capsule answer recoverable. Registry, delivery tombstone, billing, support and security evidence is retained only for operational, contractual, fraud-prevention, accounting, security and legal needs. Provider retention and deletion settings follow the service configuration and applicable obligations.

Separate passages, bounded purposes

OpenAI Sites supplies hosting and authenticated identity; configured model providers process only prompts sent through their hosted mode; Stripe processes checkout and billing. When a published AVORBYSS email address is used, the disclosed mail provider routes that correspondence. Each provider may process data in other countries under its own contracted security and privacy terms.

Control the passage

Do not submit sensitive or confidential material unless needed and authorised. You may avoid hosted features, clear local browser storage, decline optional feedback, manage billing through the authenticated portal and use the protected support route for access, correction or deletion requests.