Visitor Guide privacy and usage

Visitor Guide explains the approved public AnswerUp Core documentation. It cannot access protected packages, private sources, accounts or saved account conversations. Each question stands alone. Answers can be mistaken; check citations and do not rely on Guide to authorize actions or verify execution.

Do not submit passwords, keys, personal records, confidential information or provider payloads. Your question and selected public documentation are sent to OpenAI to generate an answer; the proposed complete answer and cited documentation are sent for a second checking call. Requests use Standard processing, no tools and store:false. This setting does not establish zero provider retention. OpenAI’s standard API abuse-monitoring records may include questions and responses and are normally retained for up to 30 days, with longer retention possible for legal or safety reasons. Prompt caching can retain encrypted model state for up to 24 hours. Our specific OpenAI retention controls have not been independently verified; no zero-retention or regional-processing promise is made. Hosting services may separately retain service/security logs.

The Portal does not save visitor questions or answers in its database. The conversation exists only in this page’s memory and is cleared when you leave, close Guide or refresh. Clear this conversation removes that local display; it does not reset your allowance or delete provider/service records.

An essential signed browser cookie lasts up to 30 days. The server derives a keyed identifier from the trusted network address, grouping IPv4 /24 or IPv6 /64 networks. Guide stores those pseudonymous identifiers, UTC rate/budget counters, request IDs, timestamps, call counts, bounded token/served-setting observations and content-free failure codes. Guide does not store raw network addresses in these tables. People sharing a network share network limits. Infrastructure access logs may separately contain network information.

Quota metadata and completed request records cover the current and previous UTC months and are cleaned on a subsequent admitted request. Unresolved failed reservations retain content-free accounting metadata until reconciled. Removing a cookie cannot clear server allowance records. There is no account history to delete in visitor mode. Contact the dedicated Core support contact for privacy requests; provide no secrets.

The dedicated AnswerUp Core project uses Supabase Pro. Completed daily database backups were observed at the last operator check; Point-in-Time Recovery was disabled. Deleted Portal metadata may remain in backups or infrastructure logs until the applicable provider lifecycle ends. The exact erasure timing for every backup, service log and provider record has not been verified, and we do not claim immediate erasure. Contact Core support for a privacy request.

Visitor limits: three attempted questions per browser per UTC day, at least one minute apart; two simultaneous visitor turns across the service; 20 attempts per network per day, four per network per UTC minute and ten aggregate attempts per UTC minute. Denied valid attempts count toward rate/daily allowances. Shared conservative model allowances include both generation and checking: $150 per UTC month for Guide, a $20 visitor subpool within it, and $2 per UTC day for all visitors. A reservation can consume allowance even when an answer cannot be published. Visitor availability may stop before your individual allowance is used. No automatic paid retries occur. Public documentation stays available when limits are exhausted.

Dedicated AnswerUp Core support and privacy contact: mailto:support@answerup.ai. This contact is separate from Front Desk.

Notice version: core-guide-visitor-v3