Privacy
Document text is shown in its published language.
- Version
- Local-use draft
- Scope
- For local use; not publicly operated
- Operator
- To be confirmed by the user before public launch
- Access and correction
- Local feedback page and administrator
1. Data stored in your browser
Bookmarks, reading history, light or dark appearance settings, recent searches (up to 10 terms), changelog read status, and feedback drafts are stored in your current browser. List position, scroll position, and expanded sections are kept only in the current tab's session storage and are cleared when that tab closes. None of these are sent to the server. They are removed when you clear browser data and do not sync across devices. You can export and import bookmarks, reading history, and appearance settings on the Saved page.
2. Feedback
Feedback, an optional email address, the page URL, and screenshots you choose to attach are stored in a local database or file volume for the administrator to review. Feishu and external notifications are disabled during this initial stage; feedback is not automatically forwarded to external groups. The framework processes an anti-abuse identifier. Do not submit sensitive well-site information, identity documents, account passwords, or production credentials.
3. Server and network logs
No third-party analytics, CDN, or public proxy is currently connected. Applications running in Docker may record operational logs such as requests, times, paths, network addresses, and errors. Administrator authentication uses a local session cookie, and session and audit records are stored. Do not share logs or backups publicly. Before public launch, confirm retention periods, access controls, and deletion procedures.
4. Third-party content
The site displays summaries and links to third-party sources. When you follow an original-source link, you visit that provider's website and its privacy policy applies.
5. Contact us
During local use, report issues through the feedback page; an administrator can review feedback and content corrections in the admin console. Before public launch, add working contact details and procedures for access, correction, and deletion requests. No external email address or compliance commitment is represented here.