Privacy
How the handbook handles questions, contributions and browser preferences.
Updated 29 October 2026. This independent fan handbook is operated by its maintainer, Jordan.
Reading and browser storage
The guide, map, planner and search run in your browser. Browser storage remembers preferences, map pins, planner builds and widget placement. You can clear these through your browser. A planner share link contains the build you choose to share. We do not run advertising or analytics scripts.
Cloudflare hosts the website and receives ordinary connection information, including your IP address. Google Fonts receives a request when fonts load, including connection and browser information. These providers handle their own service records under their policies: Cloudflare privacy and Google privacy.
Questions and AI
Searching for quoted guide passages happens in your browser. Asking for a generated Archivist answer sends your question and relevant handbook passages to Cloudflare Workers AI. Do not send passwords, account details or other sensitive information. Generated answers may be wrong. We do not save a separate question history in the handbook database; provider processing and service logs are governed by Cloudflare.
Feedback and contributions
Submitting a missing question, correction or manuscript sends its contents and any optional contact information to the maintainer's private Cloudflare KV queue. New records expire after 30 days. Older records may retain the previous retention period of up to 180 days. Contributions are reviewed before publication; accepted article text may remain published under the contribution terms. Optional contact details are not published by default.
The backend hashes the connection IP into a pseudonymous client key to enforce shared request limits. Daily and monthly quota counters expire at the end of their window and are cleared on later admission. Feedback retains a shortened client key for its retention period. These keys are not anonymous. Cloudflare can retain service/security information independently; application deletion does not promise deletion of provider logs.
Contact, correction or deletion
Use the DFO community Discord to request contact with the handbook maintainer, or send an optional contact address with a private correction. For deletion, identify the submission ID and approximate date without posting sensitive contents publicly. We may need enough information to locate and verify the request. Please do not submit other people's personal information.