Who to contact
Contact BassLureFish at enquiries@basslurefish.com for privacy questions, access, corrections or removal requests. This notice describes the features supplied by this website theme. Hosting security logs and any separately installed analytics or consent services have their own settings.
Public YouTube comment archive
We use YouTube API Services to retrieve and display public comments and replies on BassLureFish videos and selected third-party videos included in this library. The archive helps people search the original discussion alongside our fishing tests. Third-party videos must contain UK bass-lure context in their available descriptions or titles; this does not establish the location of a commenter’s own experience. No special phrase, separate author opt-in or routine manual approval is required for automatic display. We do not request YouTube passwords, private account data or account-writing access.
Comments appear as source text, not as independently verified facts. Opinions, questions, corrections and disagreement are welcome. Comments from BassLureFish carry a small “Channel contribution” label so that owner contributions are not presented as independent viewer evidence. Other comments carry no username or anonymous-author label.
Author profiles, comment text and source links
We do not display or retain the author profile name, handle, profile picture or personal channel link supplied separately by YouTube. The comment text itself is preserved, including any names, links or personal information the writer included. Hiding an author profile does not make the text anonymous. Distinctive wording or the original public YouTube discussion may identify its author or other people.
Comments on BassLureFish videos keep the existing archive rules. Third-party discussions are filtered for fishing relevance, shown only after a search, and display the source video and channel names as text. Long comments can be expanded and read on this website. Older shortened records can be refreshed through our server when you choose to read the full comment. Earlier comments in a reply thread are shown locally when available. Third-party source URLs are retained internally rather than offered as public navigation links. Please avoid posting personal information and report any material that should be removed. Expandable details provide a correction/removal link.
Stored information and retention
We store comment text, internal comment/video/reply identifiers, publication and edit dates, source/publication status and refresh time. A source-role flag distinguishes channel replies from viewer contributions. Legacy review notes may remain in the private administration data. We do not retain author profile names or personal channel IDs. Source identifiers are retained for updates, deduplication and removals and can occur in links to the original discussion. We do not build public commenter profiles or combine comments into catch-rate or popularity scores.
Comments and replies refresh in batches. A complete successful scan removes missing source comments; failed requests do not trigger indiscriminate deletion. Data not refreshed within 27 days stops displaying and is scheduled for deletion. Background execution depends on the website scheduler. Source edits and deletions take effect after successful synchronisation without a separate website approval. The importer regularly revisits older videos as well as new uploads. The 27-day limit is measured from the last successful refresh, not the original posting date: older comments remain available while refreshed. Excluded or unavailable videos and locally removed contributions are not shown.
Corrections and removal requests
Use the correction/removal link beside a contribution or email us with its reference, page URL or source link. We handle deletion requests as soon as possible and within seven calendar days. We may need enough information to identify the contribution or verify a correction. Removing it here does not delete the original from YouTube. Deleting a source comment on YouTube also removes it here after a successful complete scan.
A minimal hashed suppression record prevents a locally removed contribution being imported again. We do not sell comment data, train an AI model on it or distribute it in the downloadable field-observations dataset. You can object to processing and ask for access, correction, erasure or restriction by contacting us. You may complain to the Information Commissioner’s Office.
Video descriptions and field notes
Public video descriptions refresh through the official YouTube API. Explicit sections are presented as BassLureFish source statements, separate from protected editorial corrections. The audit trail records change fingerprints and section names for up to 90 days, without keeping obsolete API descriptions indefinitely. Original editorial notes and revisions remain while useful to explain the evidence.
Cookies, optional measurement and consent
Optional BassLureFish event counts are off until you allow them using Privacy choices in the footer, or through an integrated consent manager. A preference you select is stored in your browser for up to 180 days so we can remember it; this record contains the choice and expiry, not a visitor ID. You can switch optional counts off at any time. Supported Do Not Track and Global Privacy Control signals keep them off.
When permitted, events count broad actions such as YouTube link clicks, Ebbrox discount clicks, code copies, evidence searches by a fixed topic category and reading landmarks. Counts contain a date, event type, video/page placement and broad referral category. They do not contain raw searches, drafts, IP addresses, email addresses or persistent visitor identifiers. They expire after 90 days. Counts are not unique visitors, purchases, YouTube views or subscribers.
The theme does not add a Google Analytics tag. If separate services such as Site Kit/GA4 are configured, their collection and cookies must follow the website’s consent settings. The theme’s Privacy choices cannot retrospectively block another plugin’s scripts.
Embedded media and external services
YouTube thumbnails can contact Google when a page loads. A video player is loaded only after you choose Play and is not automatically loaded on archive pages. The button explains that YouTube will process data under Google’s Privacy Policy. You can instead open the video on YouTube. Using YouTube-powered features is subject to the YouTube Terms of Service.
Ebbrox and other external services handle information according to their own policies after you follow a link. Affiliate links may allow qualifying orders to be attributed by the retailer. We receive commission information, not your payment card details.
Optional comment helper and enquiries
The comment helper formats only what you type, in your browser. It does not send or store drafts or publish to YouTube. Clipboard history, browser form restoration and extensions are outside this website’s control. You choose whether to paste and post your words on YouTube. Information you email us is used to handle your enquiry or request and retained only as needed for that purpose.
Facebook source discussions
Where available through our Facebook connection, relevant public Page posts, comments and replies may be included in search results. The source Page name appears as text, with no clickable Facebook profile or discussion link. Contributor profile names, pictures and profile links are not requested or stored. Text can still contain identifying information supplied by its author. Source and parent identifiers are retained internally for matching, updates and removals. Posts and discussions refresh in batches; a completed successful scan reconciles missing records, and material not refreshed within 27 days stops displaying and is scheduled for deletion. Connection errors do not trigger bulk deletion. The same correction, removal and suppression process applies. Facebook records are not included in public topic guides or the downloadable observations dataset.
Discovery source labels
With your optional analytics consent, this site retains a broad source label (such as Google, ChatGPT or direct/unknown) in tab-local session storage so a later YouTube click can keep the same source context. This stores no visitor identifier or full referring address. Turning optional counts off clears the label. Search events may include the number of matching original videos and a predefined topic bucket; raw search text is not sent by these theme events.
Dated catch reports and research summaries
We also extract explicit catch details from eligible source records into short, automatically composed factual summaries on catch reports and topic guides. These are identified as reported experiences, with the publisher and source publication date where available. They are kept separate from our filmed results. Commenter profiles and full comments are not reproduced in this summary layer. Its index stores selected source references; the source record is rechecked for visibility, removal and expiry before display. Existing correction and removal arrangements apply.