Privacy Policy
Last updated October 20, 2026
Who we are and what this covers
Texas Fish & Water is developed and operated by REIGN Fishing. This policy describes information handled through the Texas Fish & Water website and through app versions that link to this policy. It does not describe separate REIGN Fishing events or other websites. Privacy questions and requests: contact@texasfishandwater.com.
Information you provide
A lake request includes the lake name and nearby city or county. An official source link, notes and a reply email are optional. We save the request, a request identifier, its submission time and review status. Public fishing information can be browsed without a TFW account. The request form uses a temporary security session and a request identifier to validate submissions and handle retries. We store a hashed session identifier with the request. A keyed hash of the connecting IP address is used for submission limits; temporary rate-limit records are removed after expiry by scheduled maintenance. Operator review uses separate password-protected access. Email correspondence may contain the contact details and information you choose to send. Please do not include passwords, payment details, medical information, private addresses or children’s personal information in requests.
Contact messages and optional email updates
The contact form collects your name, email, topic and message. We save these with the submission date and use them to respond and manage inquiries. Sending a contact message does not subscribe you to email updates. New email-update choices are made separately through your account. Earlier contact-form choices retain the wording and scope recorded when submitted; they are not automatically converted into new subscriptions. This does not subscribe you to a separate REIGN Fishing list. No automatic mailing-list integration is currently connected; opted-in records may be transferred manually to our chosen email service. You can withdraw marketing permission by emailing contact@texasfishandwater.com and through unsubscribe options in marketing emails. Withdrawal does not prevent a necessary response to your inquiry. Contact and consent records follow the retention and privacy-request practices below.
Device notifications and optional TFW updates
Enabling device notifications connects this browser or installed web app to your account for your selected Water Watch updates. Browser permission and a successful saved subscription are both needed. We store the push endpoint, subscription public key and authentication secret, account link, registration dates and delivery state in Supabase. A local browser record identifies this device registration. A push-only service worker receives messages; it does not cache the website for offline use. Push providers operated by Google, Mozilla or Apple, depending on your browser, process subscription and delivery information under their own practices. Optional TFW updates are a separate, unchecked-by-default account choice for occasional site news and new-feature announcements on your connected devices. We record that choice, its wording, version and date, including later changes. Water Watch enrollment alone does not enroll you in site announcements. This news choice does not authorize merchandise offers or other promotional campaigns. New email-update choices have the same limited news purpose and are separate from push and analytics. A signed-in account is needed to manage these choices. There is no automatic email campaign sender in this release. Authorized operators may compose announcements, preview them and send a requested private delivery test to a specifically selected device. Notification text can appear on a lock screen. Signing out does not revoke a connected device subscription. To stop all TFW notifications on a device, block TFW notifications in that browser or device's site/app notification settings; this does not delete your account or saved waters. You may change the optional TFW updates choice in your account without changing Water Watch. We disable device subscriptions reported as expired or invalid by a provider. Device records remain until removed through account deletion, administrative cleanup or a verified privacy request. Pending announcement deliveries expire within 24 hours; private test jobs expire within ten minutes; Water Watch jobs follow their source validity and queue expiry. Announcement records include content, timestamps and aggregate queue/provider outcomes, not confirmation that a person saw a message. Consent history remains linked to the account until account deletion, subject to provider backups and logs. Delivery can be delayed or missed and is not an emergency-warning or navigation service.
Optional user accounts
Accounts are intended for adults age 18 or older. Registration collects your email address and password through Supabase Auth, which manages authentication and password protection. Supabase stores your account identifier, email, authentication/security records and saved preferences. We also submit the account-terms version and your adult attestation; these are self-declarations, not identity verification. Your browser stores an authentication session, including tokens used to stay signed in. Signing out clears this browser’s login session and restores guest saves; it does not delete your account or revoke other devices’ sessions. Supabase and our hosting email service process confirmation and password-reset emails. Account creation is not marketing consent. Use Delete my account in account settings for self-service deletion. Email contact@texasfishandwater.com from your account email for access, correction, export or help; we verify requests before acting. Deleting an account removes its linked saved-preference row, while provider logs and backups may remain under their own retention schedules. Account records are retained while the account is active and for necessary operational or legal reasons until a verified deletion request is completed. Account saves are protected by rules restricting access to the authenticated account owner.
Water Watch and account deletion
Optional Water Watch stores up to ten freshwater, coastal and weather alert settings per account in Supabase, including selected public NOAA measurement stations or NWS marine zones. Coastal thresholds use measured wind/gusts or station water levels, not tide predictions. New marine-alert notifications follow an initial baseline and record the issue and expiry time of official NWS alerts. Source requests use public station/zone identifiers without intentionally including your account identity. Saved notifications may describe conditions or warnings that have since changed or expired. Paused, edited or resumed settings establish a new baseline. Shared dated official readings are compared with your settings; notifications are kept for 30 days and capped at 50 per account. Initial readings and edited or resumed alerts set a baseline rather than generating a past-event notification. Checks are periodic, may be delayed and cannot observe crossings between readings. These are not emergency, navigation or access warnings. Notifications appear in your account and may also be sent to a device when you separately enable device notifications. This release sends no Water Watch alert emails. Delete my account requires your current password and explicit confirmation, verified by our server through Supabase Auth. The password is used only for verification, never saved in notification records or application logs. Deletion removes your Auth account and linked account preferences, permission records, follows, community reports, meetup links, alerts and notifications. Messages previously submitted through public forms remain for operator review, and provider backups/logs follow provider retention. Previously viewed or copied meetup information cannot be recalled.
Form spam protection
Contact Us and Request a Waterbody use Google reCAPTCHA v3. Its script loads when either form opens so verification can initialize before submission, rather than across normal browsing. A fresh token is generated when you submit. Google may process network, browser/device information and interaction signals under its Privacy Policy and Terms of Service to assess abuse. We send the verification token to our server and then to Google for verification using a secret kept on the server; we do not include your message, email address or marketing choice in that verification request. Tokens and scores are not saved with your submission. Spam protection is separate from optional Google Analytics and marketing permission; rejecting analytics does not disable form verification. Verification can fail or reject legitimate submissions. If you cannot submit, email contact@texasfishandwater.com.
Aggregate site activity
When you allow the updated optional analytics choice, our HostGator backend also records aggregate page-view and Lake DNA selection counts by day and public page or waterbody. These counters store no account ID, email, full query URL or cross-page visitor identifier. They start when reporting is enabled and do not count earlier visits or rejected/blocked tracking. Counts are retained for up to 90 days. A short-lived keyed hash of an IP address is used for abuse rate limiting and expires after approximately two hours. Administrators can review registered accounts, recorded permissions, messages, community submissions and dated feed health through protected server access. Admin login attempts, export starts and message-status changes are logged for up to 90 days; passwords and authenticator codes are not included in those logs. Account email exports and original contact-form permissions remain separate; unsubscribe/suppression lists and withdrawal requests must be honored before marketing imports.
Temporary trip links
Signed-in users can create meeting links containing a lake or bay, precise meeting coordinates, a place label, optional time and note, and expiration. Supabase stores these with the creator’s account ID. Anyone who receives or forwards the unguessable link can view its meeting details without an account while it is active; it is not restricted to a named recipient. We do not include the creator’s account name or email in the shared response. The pin is manually chosen, not live location tracking. Opening the optional OpenStreetMap map sends the map area and network information to its provider. Directions links pass the selected coordinates to your chosen mapping provider. Expiry and cancellation prevent future retrieval through the public lookup; they cannot erase screenshots or copies already made. You can cancel links in My meetup links. Records remain visible to their creator until account deletion or operator removal; deleting the account removes linked meetup records, subject to provider backup/log retention. Do not enter sensitive information. Meetup pages and link tokens are excluded from our analytics page views and search indexing.
Installation reminders
We store your choice to dismiss the install banner in this browser so it is not shown again unless site data is cleared. A session-only page counter delays the suggestion until you have browsed a few pages. These preferences are not sent to analytics or used for marketing. You can still open installation instructions from the footer.
Optional profile preferences
You may add a display name and choose bank/pier, boat/kayak or both as your fishing style after signing in. Supabase stores these choices as account metadata. They are not included in public catch summaries or sent to analytics, and they do not subscribe you to marketing. You can edit or clear them in your account. These choices do not confirm access conditions or change fishing regulations. Deleting your account removes the profile metadata, subject to provider backup and log retention.
Account agreements and email choices
At signup we record your account agreement and 18+ self-attestation with the wording version and server timestamp. The separate optional email choice is unchecked by default. New choices labeled TFW site news and new-feature updates authorize those messages, not merchandise offers or other promotional campaigns. Earlier choices retain their original recorded scope. Existing records are not rewritten when wording changes. We record its exact wording, version, timestamp and subsequent account choices in Supabase, including withdrawal history. Signing up or confirming an email does not enroll you in optional email updates or TFW push announcements. Each requires its own affirmative choice. You can change your choice in My account, use an email’s unsubscribe link or contact us. We may export only currently opted-in, confirmed account emails to our chosen email service. Contact-form consent is recorded separately on HostGator; contacting us can also withdraw that permission. We retain permission and withdrawal records as reasonably necessary to honor choices and resolve disputes. Account-linked consent records are removed when the account is deleted; email-service suppression records may remain to avoid contacting people who unsubscribed. Manual exports do not automatically update a separate email service. We honor its unsubscribe and suppression records and do not use a new import to override them.
Community catch reports and species follows
Catch reporting is optional. When signed in, you may submit a report for a species listed for the selected lake or bay. Supabase stores your account ID, water, species and server timestamp. Public summaries identify the water and species and count distinct reporting anglers over seven days; names, emails, account IDs, exact fishing spots and fish quantities are not published. Even an aggregate summary reveals that a species was reported at that water. Reports are unverified community submissions, not proof of current fish presence or biting activity. Reports remain stored after leaving the recent summary and can be removed through your account. Private species follows store water/species choices under your account, require a saved water and do not subscribe you to email. Comparison choices are temporary in this browser. Deleting an account removes its linked reports and follows. Guests may save two waters on a device; signed-in members may save more and sync preferences. We may remove abusive or misleading reports.
Private water notes
Optional notes are stored in Supabase with your account ID, water ID, note text, version and save time. They are private to your account and are not published in catch reports, comparisons or shared collection links. Operators and service providers may access stored information for support or administration; notes are not end-to-end encrypted. Unsaved edits remain in memory in the current tab. You can edit or delete notes on the water page or Saved waters. Removing a saved water does not delete its note. Account deletion removes linked notes, subject to provider backups and logs. Do not enter sensitive information or children’s personal information.
Collections, snapshots and contextual reports
Private collections store names, ordered water entries, optional labels and dates, version identifiers and save times in Supabase under your account ID. Operators and providers may access them for support or administration; they are not end-to-end encrypted. Changes sync only after a successful save. Delete a collection to remove its entries. Account deletion removes linked collection records, subject to provider backups and logs. Water snapshot JPEGs are generated on your device and are not uploaded to a snapshot database. Saved notes are included only when you choose them. Anyone receiving an image can read it; TFW cannot recall saved or forwarded copies. Snapshots retain their creation and source dates and do not update. Requests for date-specific coastal products may contact NOAA or NWS from your browser using public station IDs, reference coordinates and dates; these requests do not intentionally include account IDs, private labels or notes. Contextual correction links carry public page, section and optional source/reading details in a URL fragment. The initial page request does not include that fragment. Submitting the contact form includes those public details in your message, but does not attach private notes or collections or enroll you in email updates.
Shared collections & failure reports
Publishing a collection creates a readable snapshot containing its name, waters, labels and dates. Anyone holding the link can read that shared snapshot until it expires or you revoke it; it is not restricted to named recipients. Private notes and account details are excluded. Revoking a link cannot recall copies already saved. With analytics permission, TFW records coarse failure-category counts by broad page area and release for seven days. Reports exclude error messages, account identifiers, private notes and exact locations. Short-lived hashed network addresses help limit abuse and are not shown in the dashboard. Counts are incomplete and do not identify unique visitors.
Saved waters and device storage
Your optional display name is used on your private Home and account pages, not public reports or shared meetup pages. Your optional freshwater/saltwater/both preference is stored in Supabase account metadata with your existing profile preferences and selects initial filters; it does not change your Home Water, current trip, rules or access rights. Your favorites, home water and selected fishing water are stored in your browser’s local storage, together with a cache of dated water observations. They persist until changed or cleared and are specific to that browser and device. Without an account, up to two saved waters stay in this browser. Setting a home water requires a free account. If you sign in, saved waters and your home water are stored under your account and synchronized through Supabase. Guest saves stay separate unless you choose to import them. Your current fishing trip and dated feed caches remain device-local. The latest successful account save replaces earlier account preferences; concurrent edits across devices may overwrite each other. Weather information is held temporarily while the page is open. Clearing site data in your browser removes locally stored choices; it does not delete a request already submitted to us.
Location and weather
Choosing a lake or bay tells our server which water’s weather or water information to request. Weather uses a predefined water or station reference location, not your phone’s precise GPS location. The Nearby waters button can request browser location permission to sort waters locally by approximate distance. Precise device coordinates are not intentionally uploaded by this feature. We do not continuously track your location. Browser or hosting restrictions may prevent this optional feature from working. Selecting “I’m fishing here” records a choice locally; it is not live location sharing. Our server retrieves official information from sources including the National Weather Service and Texas Water Development Board. These requests use the selected water, station or marine-zone reference and do not intentionally include your request-form contact details.
Coastal observations and forecast audio
Coastal station and marine-zone choices are stored on your device. NOAA observations and NWS forecasts and alerts are requested through our server using the selected public station or zone, without intentionally including your account or contact details. These source requests and retained dated caches do not establish safe navigation or continuously monitor conditions for you. Selecting Read marine forecast aloud passes the displayed public forecast text to your browser’s speech service. The browser or operating-system voice provider may process that text; we do not request microphone access or record your voice. Following official-source links opens those providers’ sites, which have their own privacy practices. Generated bay scenery is illustrative, not a location photograph or current-condition observation.
Technical information and hosting
When you access an online service, hosting, delivery and security providers may process technical information such as IP addresses, browser or device information, request URLs, timestamps and security or diagnostic logs. This website is hosted on HostGator. Lake requests and dated feed caches are stored on the hosting account, with request records outside the public website folder. HostGator may process technical logs, backups and email delivery information according to its own practices. Fonts are loaded from Google Fonts, which may receive technical connection information such as IP address and browser details. Email notifications, when enabled, pass request information through our hosting email service for operator review. We do not claim that hosting providers collect no data or that their logs are controlled by the app’s local-storage settings.
How we use information
We use requests to assess proposed public fisheries, verify sources, maintain the guide and, if you supply an email, respond about your request. We use technical information as needed to deliver the service, diagnose failures, protect it against abuse and meet legal obligations. We may use the non-personal water name, location and verified source information to develop a public water profile. Submitted contact details and notes are not published as a public request feed. Supplying a reply email does not subscribe you to marketing messages; optional account email updates require a separate affirmative choice.
Sharing and advertising
Service providers and authorized people assisting REIGN Fishing handle information to operate the service. We may disclose information when legally required or to protect rights and security. We do not sell submitted contact details or share them for targeted advertising. Google Analytics 4 is optional. Its script loads only after you select Allow analytics, and eligible public page views are measured only while that choice remains allowed. You can reject it or reopen Privacy choices in the footer. We send page names and clean guide paths, without query strings or fragments; we do not intentionally send account emails, names, passwords, form contents or authentication tokens. Account, saved-water, contact, request and operator pages are excluded from our page-view measurements. Google may process IP/network, browser, device and usage information under its own practices; this is not a promise of anonymous processing. Advertising storage, Google signals and advertising personalization are disabled in this implementation. There is no AdSense or behavioral advertising integration in this release. We will update this policy and choices before introducing new tracking or advertising practices.
Cookies and other choices
Essential storage includes the temporary request-form security cookie, browser authentication session and saved-water preferences and feed caches. These support features you choose to use. A separate local-storage record remembers your analytics choice, its version and date. If you allow analytics, Google Analytics can use first-party _ga cookies to distinguish visits; these commonly last up to two years, subject to Google settings and your browser. Rejecting analytics stops this implementation and removes accessible first-party _ga cookies. You can also clear cookies and site storage in your browser. Doing so may sign you out and remove local preferences; it does not delete records already submitted to us. Optional analytics is separate from email marketing permission. We do not currently set advertising cookies.
Retention and security
Lake requests and contact messages remain in server storage during review and follow-up. The current request system does not automatically expire submissions. We retain information only for operational, security or legal needs and review removal when it is no longer needed or when you make a deletion request. Provider logs and backups may follow separate retention schedules; this policy does not promise an unverified deletion date for them. Access to contact messages, consent records and the request-review endpoint is restricted to the operator. We use reasonable safeguards appropriate to the information, but no online service can guarantee complete security. Avoid submitting sensitive information.
Access, correction and deletion requests
Email contact@texasfishandwater.com to ask what request information we hold, correct it or request deletion. Include enough information to locate the submission, such as the lake name and approximate submission date; do not send identity documents unless a necessary verification method has been discussed. We may verify your relationship to a request before disclosing personal information. We will respond in accordance with applicable law, including any applicable access, portability, correction, deletion, appeal or response-time requirements. Rights and exceptions depend on the law that applies. If you disagree with our response, reply to the same address and ask for review. You may also contact your relevant privacy regulator. Requests about a provider’s independently controlled logs or records may also need to be directed to that provider.
Children’s information
Texas Fish & Water provides general fishing information that may be browsed without an account. Accounts and contact/request forms are intended for adults age 18 or older. Do not create an account for a person under 18 or submit children’s personal information through these forms, private notes, meetup links, collections or community reports. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information, email contact@texasfishandwater.com so we can investigate, restrict further collection or account access where appropriate, and remove the information as required. Please identify the affected account or submission without sending additional sensitive information about the child. The signup age declaration is a self-attestation, not independent age verification.
External sources and policy changes
Official-source links take you to another operator’s service, where that operator’s privacy practices apply. This policy describes current behavior, not a promise that every future feature will collect the same information. We will revise it when data practices materially change and provide additional notice or obtain consent where required. The date above identifies this version. Please contact us before submitting information if you need clarification.