Private by default
Golden Queries, Golden Answers, customer records, receipts, uploaded files, wallet details, support material, and preserved packets remain private unless a separate public-safe record is intentionally approved.
Privacy is part of the architecture
Golden Bridge is designed to preserve accountable work without turning private customer material into public content. Records, receipts, Golden Queries, Golden Answers, uploaded files, and support references are private by default; only deliberately redacted, public-safe anchors belong on the public ledger.
Core privacy boundary
Do not submit passwords, API keys, private keys, payment secrets, confidential business documents, personal health information, legal secrets, or other highly sensitive material unless Golden Bridge has explicitly arranged a suitable intake path with you.
Golden privacy map
The governing rule is simple: collect only what the service needs, keep customer work private, and publish only redacted references.
Golden Queries, Golden Answers, customer records, receipts, uploaded files, wallet details, support material, and preserved packets remain private unless a separate public-safe record is intentionally approved.
Public ledger cards are reference anchors. They may confirm that work happened and preserve safe metadata without exposing private prompts, private answers, payment details, files, or infrastructure secrets.
Selected query content may be sent to an activated AI provider only when that route is used. Parked routes remain unavailable, and provider credentials are never public.
Eligible records may be reviewed for access, correction, export, restriction, or deletion through a written customer request, subject to operational, accounting, security, and legal retention needs.
Ledger boundary
A timestamp, public-safe status, custody reference, route or provider label where appropriate, file count or type, and a safe credit receipt summary.
Raw prompts, private answers, uploaded files, wallet identifiers, payment details, admin notes, support details, and private infrastructure information.
A public ledger card proves custody, order, preservation, and scoped status. It does not automatically prove that every claim inside a Golden Answer is factually true.
Information categories
These categories support authentication, governed AI work, payment accounting, preservation, customer access, and system reliability.
Sign-in email address, authentication state, account references, access records, and security-related events.
Questions, prompts, selected privacy level, selected route, answers, summaries, record metadata, and preservation references.
Wallet balance, held and settled credits, order references, receipt records, transaction records, and support references.
Timestamps, route status, error messages, rate limits, checkout status, provider labels, and troubleshooting references.
Files and media
Uploaded files are treated as private by default. When a public-safe reference is appropriate, it should expose only limited information such as file count, general file type, or processing status.
Audio and video should also remain private by default. Future handling should favour controlled access, redaction, and transcript-first processing where appropriate.
Provider routing
When a customer chooses an activated AI route, selected query content may be sent to the approved provider required to complete that work under the active Golden Bridge privacy and provider rules.
Parked or unactivated routes remain gated. Provider keys, backend secrets, raw payment credentials, and private infrastructure details are never public.
Customer control
Customers may contact Golden Bridge in writing to request review of eligible private records. Some information may need to be retained for receipts, payment history, credit accounting, security, support, legal compliance, dispute handling, or public-ledger custody.