Privacy

What Anglrithm keeps, where it keeps it, and what leaves your phone. Last revised November 14, 2026.

Your log stays on your device

Your catch log, trips and photos are stored first in your browser's own database on the device you use. If you turn on catch sync in Settings, your trips and catches are also copied to your account, where only you can read them. Photos are never copied, and positions are copied only if you also tick Copy positions too. Turning sync off stops new copies; write to support@anglrithm.com to delete what was copied. Your home spot, watchlist and saved marks follow your account so they appear on each device you sign in on. Exports leave only when you save or share one. Sick Day alerts are described below.

Photos

When you attach a photo to a catch, or add a day's photos to the photo inbox, the app reads its EXIF data on the device to fill in the time and position for you, and compares the pictures with each other on the device so a burst of one fish reads as one catch. No photo is sent anywhere to be recognised; you name the fish. The stored copy of the photo has its GPS tag removed. The original in your camera roll is untouched.

Float plans

A shared float plan is encoded in the link itself, after the # sign. That part of a URL is not sent to our servers; the person you send it to decodes it in their own browser. Share it only with the people who should have it.

An overdue alert is different: it has to be on our server to work while your phone is off or out of signal. When you set one, we store with your account your name as you typed it, the trip summary you entered (the boat, where you leave from and when, where you are going), your return time and grace period, one to three shore contacts' email addresses, and the plan's link only if you chose to include it. The addresses are used for that alert and nothing else. If you have not checked in by the return time plus the grace period, each contact gets one email, and one more when you check in. Everything is deleted when you check in or cancel (after the "they are back" email if an alert went out), and in any case 7 days after your return time. Email only, through our email provider (Resend); we never contact the Coast Guard. It is a backup to the plan you leave with a person, not a rescue service.

Live position sharing

Your position stays on your phone unless you choose Share live position for one trip, on the float plan or in Running mode. It is never on by default. While a share is open, and only while Anglrithm is open in Running mode, your phone sends its GPS position about every 30 seconds to our server, with its time, accuracy, speed and course; without signal the positions wait on your phone and go when it has signal again. We store with your account when the share started and when it ends, those positions, and the float plan's details only if you ticked them: text such as the boat, where you leave from, when you are due back, how many are aboard, the VHF channel and the phone aboard, never a route, a catch or a mark.

Anyone with the link can see the boat on a chart, its trail, speed and course until the share ends, without an account, so send it only to the people who should have it. The link's key travels after the # sign, which browsers do not send to servers, and our server checks its signature and its end time before it shows anything. If you add the share to an overdue alert, the alert email carries your last shared position to the contacts you chose, only while the share is open.

A share ends when you tap Stop or at the time you picked, and never more than 24 hours after it started. Then every position is deleted from our server, and nothing is kept: no history, no copy and no record of where you went. Deleting your account deletes an open share and its positions too. Not a rescue service and not for navigation.

Sick Day alerts

For Sick Day alerts we store, with your account, the public spots you watch and their marine zones, your limits (wind, seas, the days you fish), and for each fish landed in your log its day, the fish and the conditions at the time (wind and its direction, seas, the three-hour pressure trend, water temperature, tide stage and flow, moon phase, solunar and light). Never a position, a note, a photo or a size. That is what lets us tell you, the day before, that a day looks like the days you caught fish. Email goes to your confirmed address and every email has a one-click unsubscribe; push goes only to devices where you turned it on, and turning it off deletes that device's push address.

If your Pro plan ends, we may email you on the morning a season opens, by the rules the app shows, for a fish you follow: the fish you picked in Settings, the fish of a window you watch, or a fish you have logged three times. At most two a year, never within 30 days of the last. For this we keep the fish you picked with your account, its name only and never a position. Every one has a one-click unsubscribe, and none goes to an account whose browser sends Global Privacy Control.

Signing in

Anglrithm asks you to create a free account to use the app; that is how Sick Day alerts reach you and how the trial and any plan stay with you. A shared float plan opens without one. If you sign in with Google, we receive your name and email address from Google and nothing else. Passwords are held, hashed, by our sign-in provider (Supabase), never by us; when you choose one, the first five characters of its SHA-1 hash are checked against Have I Been Pwned's list of breached passwords, so the password itself never leaves your browser. Account data sits in a database where only your account can read your rows, and deleting the account from its page removes it.

Analytics

The site uses Cloudflare Web Analytics, which counts page views without cookies and without identifying you; the Google Ads tag, described next, is separate. The app also keeps a short, anonymous list of which features were used, on the device, to decide what to build next.

We also count a few steps on our own server, with no cookie and nothing that identifies you: that a visitor without an account reached the sign-up wall, and that a sign-up was started. Once you have an account we note, once each, that it signed up and how (email, Google or Apple), that it saw the trial offer, started a trial or switched the Morning Call on.

If the link that brought you here named where it was posted, or your browser said which site you came from, we keep one coarse label for the visit: a source from a short fixed list (Instagram, Facebook, Google, a Google ad, Reddit, X, an email, a group, a partner, direct or other) and the link's campaign name, cut to letters, numbers and hyphens. The label stays in your browser tab until you close it. It is added to the counts above, to the list on your device and to your sign-up's record, so we can tell which posts bring people here. We do not keep the address of the page you came from, anything you searched for or your IP address with it, and the label is never given to Google.

Google Ads measurement

We advertise Anglrithm on Google, and the site loads the Google tag for Google Ads so we can tell which ads bring people here and whether they start a trial. On your device it can set cookies or similar identifiers, and it sends Google the pages you view on anglrithm.com, the Google ad you clicked to get here and, once we set one up, a conversion when a trial starts. We give it each page's address without the part after the ? or the # (where share links, sign-in steps and checkout sessions keep their details), a fixed title on app pages, and the origin alone of a site you came from. We never give Google your email, your name, your account id, a position or anything from your log. It does not load on a shared float plan.

We use the tag to measure ads only. Ads personalisation and remarketing are off: the tag tells Google not to use your visit to personalise ads or to build an audience to show you our ads again (ad personalisation signals off), and Google signals, which would link the visit to a signed-in Google account, are off too. Enhanced conversions are off.

If your browser sends Global Privacy Control or Do Not Track, the Google tag does not load at all; we treat either as your opt-out of ad measurement. Google uses this data under its own terms: see how Google uses information from sites that use its services and your Google ad settings, where you can turn off ad personalisation from other sites too.

No ads in the app, no sale of data

There are no ads in Anglrithm and we do not sell personal data to anyone. Apart from the Google tag described above, nothing on the site belongs to an ad network. Forecast and chart data come from public agencies and are fetched directly for your spot. When you ask for the forecast, the marine zone or the depth at one of your own marks, at the pin or along a route you drew, that position goes to the source (Open-Meteo, the National Weather Service or for a depth the NOAA services the lookup walks: nowCOAST, NCEI and THREDDS, then GEBCO) in the body of the request and nowhere else: it is never written into a web address, never kept in our edge cache and never kept in your browser's page cache. On the NOAA chart, a tap on open water or the crosshair sends that point and the chart's zoom through our relay to NOAA's chart service (the Office of Coast Survey's Maritime Chart Service) to read the chart objects charted there, in the same way.

Contact

Questions about this policy: support@anglrithm.com.