Updated
Privacy Policy
how-to-fish.net is a public fan-made How to Fish guide. It has no visitor accounts, subscriptions, or payments.
Controller and contact
The controller for this site is XU ZHENYU, an individual based in China. Email [email protected] for privacy questions or requests. You can also use the Contact page to create a private ticket without an email address, phone number, account, or login.
Email correspondence
If you email us, we receive your email address and the information you include in your message so we can review your request and respond.
Site delivery and security
Vercel hosts and delivers the site. Cloudflare may provide domain, network, or security services. These providers can process request metadata such as IP address, time, requested URL, user agent, and security signals to deliver the site, prevent abuse, and maintain service reliability. Their own retention and transfer terms apply.
Optional Google Analytics
Public pages download the Google tag library for measurement ID G-RKHYRN3KM0 even before you make a privacy choice. Downloading it sends ordinary connection metadata, such as your IP address and browser headers, to Google. This is separate from analytics measurement: the site keeps measurement disabled until you accept Analytics. Before acceptance or after refusal, the site does not send analytics events or create analytics cookies. Private feedback pages do not load the library. If accepted, Google may receive page and interaction data, device and browser information, approximate location derived from IP address, and identifiers used to distinguish visits. Consent is the basis for this optional processing. Google is the analytics recipient; advertising signals and ad-personalization signals are disabled in the site configuration.
Optional Adsterra advertising
Adsterra Native Banner advertising is loaded only after the visitor separately enables Advertising in Privacy choices. Before that consent, the site does not request the Adsterra script. If enabled, Adsterra and its advertising partners may receive the requested page, referrer, IP address, device and browser information, approximate location, advertising identifiers, and ad-view or interaction data, and may use cookies or similar storage under their terms. Consent is the basis for this optional processing.
Optional Google AdSense advertising
If Google AdSense is configured, its loader is requested only after the visitor enables Advertising and only on the site's reviewed content routes. It is not loaded on the home page, search, contact, policy pages, private feedback, or excluded content routes. Google and its advertising partners may then process the requested page, referrer, IP address, device and browser information, approximate location, advertising identifiers, and ad-view or interaction data, and may use cookies or similar storage to deliver, secure, limit, and measure ads under their terms.
Visitors in the European Economic Area, United Kingdom, or Switzerland may also receive a Google-certified consent message configured through AdSense Privacy & messaging. That regional message can collect choices required by Google's advertising framework. Enabling Advertising in this site's Privacy choices does not bypass any additional certified consent step that Google requires.
Preferences and embedded video
The browser stores separate analytics and advertising choices locally so the site can respect them on later visits. The official YouTube video uses a privacy-enhanced youtube-nocookie.com player and is not loaded until the visitor selects play. Starting the player can cause Google or YouTube to receive device, network, and viewing information under their terms.
Private feedback
When feedback is configured, the Contact page collects a category, subject, optional nickname, message, optional related-page path, and timestamps. Vercel processes the request and Neon stores the ticket and conversation. The server derives an HMAC digest from the client IP for abuse limits and sends only that 32-byte digest to the feedback database. The raw message is kept as submitted and rendered as plain text.
A secure random token is returned only when a ticket is created. The database stores its SHA-256 hash, not the token. The complete private link contains the token after the # symbol; anyone with that link can read and reply to the ticket. The private page sends the token only in same-origin POST bodies and loads no analytics, advertising, or third-party tracking.
Local feedback links and retention
After creation, this browser stores the full private link, ticket ID, subject, and local timestamps under how-to-fish-feedback-tickets:v1 so the My feedback area can reopen it without an account. These records never provide a server-side ticket list. They can be removed from My feedback or by clearing browser storage. If the link and browser record are lost, the ticket cannot be recovered.
Feedback tickets and messages are retained permanently by default, including after resolution, unless the operator performs an explicit manual deletion. Use the private conversation to request correction or deletion and keep the private link so the request can be followed.
Retention and international processing
The local consent choice and saved feedback links remain until they are removed or browser storage is cleared. Feedback tickets are retained permanently by default. Analytics cookies are configured with a maximum lifetime of 90 days, while Adsterra, Google AdSense, Google, and their partners may apply different retention periods under their terms. Because the controller is based in China and Vercel, Neon, Cloudflare, Google, YouTube, Adsterra, and advertising partners may process data in other countries, personal information can be transferred across borders. Applicable Chinese personal-information protection and cross-border transfer requirements, together with provider safeguards and contractual terms, govern that processing.
Your choices and rights
Use Privacy choices in the footer to accept or reject all optional services directly. Manage choices provides separate Analytics and Advertising controls when needed and can be used to withdraw a previous choice. Withdrawing analytics stops subsequent analytics measurement and removes accessible GA cookies. Withdrawing advertising removes the active Adsterra slot and stops future Adsterra and Google AdSense loader requests; browser controls can remove provider cookies or storage that this site cannot access. Depending on local law, visitors may request access, correction, deletion, restriction, or object to processing, and may complain to their data-protection authority.
Send your request to [email protected] or submit it through the Contact page and retain the resulting private link.