Privacy

Encode Wiki serves static documentation and articles. Reading its public pages does not require an account. The homepage also links to Ask Encode Wiki, a separate public service at ask.encode.wiki. Submitting a question there contacts the Ask service; following the homepage link does not submit a question automatically.

The production domain uses a self-hosted Umami analytics service at u.servers.moe to understand aggregate site usage. The local analytics loader injects the tracker only when the browser hostname is exactly encode.wiki, and the tracker itself is also restricted to that domain. Local development and dev.encode.wiki therefore do not contact or record production analytics. No analytics API or administrative credential is included in the site.

Pages may include social-post components for X, Bluesky, or LinkedIn. Each displays a local placeholder and direct link by default; no resource from the social platform is requested unless the reader chooses Load post. When selected, the component loads that platform’s official embed. X’s widget uses its do-not-personalize option. The resulting connection is governed by the selected platform’s privacy and cookie policies. Declining an embed does not prevent access to the rest of the page.

Repository and release cards for GitHub, GitLab and Forgejo are different: their public API metadata is fetched by a maintainer-run refresh script, committed to the repository and rendered as first-party static HTML. A reader’s browser does not contact the forge merely by viewing a card. Following the card’s link opens the forge in the usual way. Private forge addresses and credentials are not supported.

The hosting and analytics servers necessarily receive ordinary network request data such as IP addresses, user-agent headers, requested URLs, timestamps, and error information. Encode Wiki does not use advertising cookies or sell reader data. The separate Ask service is described below; linking to it does not submit a question from a wiki page.

Ask Encode Wiki

The public Ask app does not require an account. Its development preview at ask-dev.encode.wiki remains protected by Cloudflare Access and requires an approved session. Public wiki reading remains available without using either app.

When a reader submits an enabled chat question, the Ask server receives that question and a bounded portion of the conversation history. It retrieves relevant wiki excerpts and sends the assembled context to the configured model provider. The selected live configuration uses OpenCode Zen / GLM 5.3 Flash; the actual provider/model is shown by Ask. Do not submit secrets or material you are not authorized to share. Provider processing and retention depend on its Zen privacy terms and account configuration; this wiki does not promise zero retention by a third party.

The current Ask UI holds messages in the browser tab’s memory and provides a new-conversation control. Its application database stores rate-limit counters under a keyed hash of the network address (IPv6 addresses share a /64 bucket), plus aggregate token/cost counters. The application does not write question/answer transcripts into that database. Operational chat logs record request identifiers, timings, provider/model, corpus/source identifiers, usage, and error status; the model error handler deliberately omits prompt bodies. Access, proxy, host, and provider systems can process additional request/authentication information under their own configurations. These implementation facts are not a claim of anonymity or a fixed retention schedule.

See the Ask architecture, chat handler, and provider adapter for the reviewed behavior. This description was checked against the October 2026 deployment code; future provider or storage changes require an updated notice.

Questions or privacy concerns can be reported through a confidential issue in the project’s GitLab repository.