Skip to main content

Privacy

Last updated 2026-11-07.

This is a non-commercial fan wiki. There are no reader accounts and no sign-in, and you can read every page without sharing anything personal. We count page views without cookies and collect error reports, as described below, but none of it tells us who you are. We do not sell your data or share it with third parties for marketing.

What we store

The only data this site collects is what you choose to send through the “Send feedback” and “Suggest an edit” forms:

  • The message you write.
  • The page URL you sent it from, so a bug report is actionable.
  • With “Suggest an edit”, the type of problem you pick and, only if you fill them in, the section of the page and the source you point to.
  • An email address, only if you choose to enter one for a reply.
  • Your IP address, held briefly to rate-limit submissions and prevent spam. It is not linked to anything else and is not used to identify you.

Submissions are delivered as issues to a private GitHub repository that only staff can read, so GitHub stores them under its own privacy policy. The raw message, page URL, edit details, optional email, internal status, and staff notes are visible only to staff. There is no promise of a timely response or of acting on any particular submission.

Optional publication

Feedback is private by default. The publication opt-in checkbox is optional and unchecked by default. If you leave it unchecked, the submission stays private. Existing submissions made before this option was introduced also remain private and are not treated as consent.

If you opt in, staff may prepare a separate public excerpt for the reader corrections board. Staff may moderate, shorten, or redact that public copy, reject it, unpublish it later, or delete the submission. Opting in does not guarantee publication.

Your optional email and the original message are never public. A public entry can include only the moderated excerpt, an optional safe link to a page on this site, and its publication date. We perform no identity verification, so publication does not confirm who submitted a message or any identity claimed in it.

Services that handle reader data

Each service below receives only what is listed here and keeps it under its own privacy policy.

Railway and Cloudflare (hosting and network)

Railway runs this site and Cloudflare carries its traffic. Like any web host, both see every request: your IP address, your browser details, and the full request URL, including any search query you type. Their request logs hold these for as long as each provider keeps logs. We use them only to keep the site running and to stop abuse.

Cloudflare R2 (images)

Images come from our image host on Cloudflare R2, which receives your IP address, your browser details, and the address of each image. It is told which site asked for the image, but not which page you are reading.

Umami (page-view counts)

On this site's public address only, each page view is counted with Umami. Umami receives the page address with any search query and #fragment removed, the address of the page that linked you here (shortened the same way), the page title, and your screen size and language. Your browser's request also carries your IP address and browser details, which Umami uses to estimate your country and to count visitors without cookies; Umami says it does not store IP addresses in its analytics records. A successful feedback submission is counted as one event with nothing attached. Umami keeps this data for 6 months.

If your browser sends Do Not Track, nothing is sent to Umami at all.

Sentry (error reports)

When a page or the server hits an error, a report goes to Sentry: the error message and where in the code it happened, your browser and operating system, and the page address with any search query removed. Browser reports pass through this site first, so Sentry never sees your IP address. Reports are set up to leave out feedback text, email addresses, search terms, and cookies. Sentry keeps them for 30 days. Do Not Track does not turn off error reports.

GitHub (feedback)

Feedback submissions are stored as issues in a private GitHub repository, as described above.

YouTube (videos)

Nothing loads from YouTube until you press play on a video. The player then loads from youtube-nocookie.com, YouTube's privacy-enhanced mode, and YouTube receives your IP address and browser details under Google's privacy policy.

Buy Me a Coffee (one-off tips)

Nothing on this site loads from Buy Me a Coffee. It is contacted only if you follow a support link. If you leave a tip, Buy Me a Coffee and its payment processor, Stripe, handle the payment under their own privacy policies, and we never see your card details. We see only what Buy Me a Coffee shows creators about a tip, such as the name and message you choose to enter.

Patreon (monthly support and ideas)

Nothing on this site loads from Patreon. It is contacted only if you follow a link to it. If you become a member, Patreon handles the payment under its own privacy policy, and we never see your card details. We see only what Patreon shows creators about their members.

The feedback post on Patreon is public. Comments there appear under your Patreon name and are covered by Patreon's privacy policy. They are separate from the private feedback forms on this site.

BreezeWiki (optional ad-free Fandom links)

Nothing on this site loads from BreezeWiki. It is contacted only if you follow an ad-free Fandom link, from the Useful sites page or, with the ad-free setting on, from a page's sources. The BreezeWiki mirror, antifandom.com, then receives your request, and your browser loads the article and its images from Fandom, under each service's own privacy policy.

Game content

Genshin Impact text, names, and imagery belong to HoYoverse. How this project reuses that material is described on the terms page and in the project's licensing notes.