castline.

Privacy

Updated September 24, 2026

Castline provides fishing forecasts, water information, and a private catch journal. This page explains what the app uses and stores.

Sign-in

When you sign in with Google, Google sends Castline a verified account identifier. Castline requests only the OpenID sign-in scope, not access to Gmail, Drive, contacts, or other Google data. On iPhone you may instead sign in with Apple; Apple sends Castline a verified identifier, which is kept as a separate journal account from Google. Castline does not use the optional Apple email address to combine accounts. Browser sessions use a signed cookie and mobile sessions use a signed token kept in the phone’s secure storage. Sessions last up to seven days.

Your journal

If you save a catch, Castline stores the details you enter, which may include species, size, time, location, weather notes, bait, comments, and an optional photo. Saved waters are also stored. Journal records and photos are kept in the app’s hosted database and file storage, and access is limited to the signed-in account. You can delete individual catches in the app. The mobile app’s Delete my account data control removes that account’s saved catches, photos and waters from Castline and invalidates its existing Castline sessions. You can also request removal using the contact below.

Forecasts and location

Castline uses the water or place you select to request weather and fishing information from public data providers. If you choose “Use my location,” your browser or phone asks permission before sharing your location with Castline for a county lookup. The mobile app does not track your location in the background. Map tiles and external links may send your browser’s IP address and normal browser information to their providers. Your chosen county and water may be stored in your browser so the website can restore them later.

Sharing and retention

Your journal is not published to other users or used to train Castline’s forecasts. Castline does not sell journal information. Records and photos remain until you delete them or request their removal. Website session cookies and mobile tokens expire after seven days. Signing out removes the local session. The mobile app can create a short-lived, one-use website link so you can open the same journal in a browser. Hosting and data providers may process technical request information needed to operate their services.

Optional usage analytics

If usage analytics is configured, Castline asks before loading Google Analytics. With your permission it counts page visits, forecast views, successful water and catch saves, public sharing actions, and return visits. Analytics receives page paths and predefined regional campaign labels, not your search terms, Google account identifier, catch details, photos or precise personal fishing locations. Google may process technical connection information and analytics cookies. Browser storage remembers your consent and, when allowed, the date of your first forecast visit to measure a return within seven days. Use the analytics control at the bottom of the page to change your choice. Declining does not limit forecasts or journaling.

Feedback

If you send feedback, Castline collects the category and message you provide, plus your name and email address only when you choose to include them. The submission is checked by Cloudflare Turnstile to reduce spam and delivered through Resend to Castline’s email inbox. Castline does not add feedback submissions to its journal database. The message may remain in Castline’s mailbox and Resend’s normal delivery records until it is deleted under those services’ retention practices.

Support payments

The “Support Castline” link opens Ko-fi, an independent payment service. Castline does not receive or store your card or bank details. Ko-fi and the payment processor you choose handle the transaction under their own privacy policies.

Contact

For privacy questions or a data removal request, email [email protected].