Privacy

CatchBadge Ltd (a company registered in England & Wales, company no. 17302327), operator of catchbadge.app, is the data controller for personal data processed via this app. For privacy questions or data requests, contact rob@catchbadge.com.

CatchBadge requires an account. The data we hold falls into four categories:

Account data

• Email address (sign-in + service notifications)
• Password (stored hashed by Supabase Auth — we never see the plaintext)
• Display name (shown on your catches + leaderboard)
• Region (used for region-filtered leaderboards)

Catch content you upload

• Photos of your catches (trophy + optional length / weight / release / location photos)
• EXIF metadata embedded in those photos — camera make/model and capture date (used to check the photo is genuine). Any GPS coordinates your camera saved are stripped from the photo when you upload it and are never stored (see below)
• Catch details you type: species, weight, length, location name, notes, date caught, disposition (kept / released)

Your location: if your camera saved GPS coordinates, they are read on your device only to pre-fill an editable, coarse place name (e.g. a town or area). The precise coordinates are stripped from the photo on upload and are never stored, transmitted, or shared — only the coarse place name you see and can edit is saved. This protects your fishing marks.

Activity data

• IP address and browser headers (Cloudflare server logs — security, rate-limiting)
• Verification status and admin actions on your catches
• AI verification verdict (see §5 below)
• Badge shares — when you share a badge we record that it happened, which method you used (e.g. copy link, native share), and which catch it was. We use this to see whether sharing is worth building on. It is stored on our own systems only and is never passed to an advertising or analytics company

Payment + shipping data (when you subscribe or order a sticker)

• Card details — handled directly by Stripe; we never see or store your card number, only a subscription or order identifier and its status
• Delivery address — only if you ask us to post a physical sticker to you. We store it solely to dispatch that sticker, which we post to you ourselves; we never use it for marketing, and it's deleted when you delete your account.

Push notifications (if you turn them on)

Push notifications. If you turn notifications on, we store a device token (and whether your device is iOS or Android) so we can send you alerts about your own activity — a catch verification result, a catch credited to you, a competition result, an award you've earned. These are service messages, not marketing. To reach your device, the token and the alert are sent via Apple (APNs) or Google (FCM); we don't keep the alert after it's sent. You can turn notifications off — by category or entirely — in Settings or in your device settings. We remove a device token when you log out, when it stops working, after about 90 days unused, and when you delete your account.

We do not collect special-category data (health, ethnicity, political views, etc.). If your catch photos incidentally show identifiable third parties (e.g. a friend in the background), please ensure you have their permission before uploading.

We rely on the following lawful bases under UK GDPR Article 6:

• Contract performance — running the service you signed up for: storing your catches, displaying your badges, processing subscriptions.
• Legitimate interests — fraud prevention (AI verification of catch authenticity), security logging, basic product analytics, and member discovery (suggesting anglers to each other — optional; see §4). Our analytics are deliberately minimal: we record when you share a badge, and how, so we can tell whether sharing is worth building on. That data stays on our own infrastructure — there is no Google Analytics, no advertising network, and no third-party tracker anywhere in CatchBadge, and we never track you across other websites. You can object to this at any time (see §10) and we will stop.
• Legal obligation — retaining tax-relevant transaction records for 6 years if you've made a purchase (UK HMRC requirement).
• Consent — for sharing your catch album with other members when you turn on “Allow members to view my album” (off by default; you can withdraw at any time by turning it back off), and for any future marketing email.
• Consent (separate and specific) — appearing on a partner’s public board. Being listed on a partner’s public shopfront page, which anyone can view without signing in, relies on its own distinct consent: the “Show me on partners’ public boards” setting. It is off by default, it is deliberately not covered by your album setting above (that one only ever applies to signed-in members), and you can withdraw it at any time by turning it back off. See §4.

Photos you upload as verified catches may be shown publicly within CatchBadge — on the leaderboard, on your public profile, and inside your badge designs. By uploading a verified catch you grant CatchBadge a non-exclusive, worldwide licence to display, resize, and render the photo within the service and on printed sticker products you order. You retain ownership of the photo.

Photos uploaded as archive entries are private to your account and not shown publicly.

Member album visibility (optional). By default your album is private. If you turn on “Allow members to view my album” in your profile settings, other signed-in CatchBadge members can view your verified catches — species, the approximate place (town/area only, never exact coordinates), the date, the weight or length, and the catch photos. This sharing relies on your consent; you can withdraw it at any time by turning the setting back off, after which your album is private again. Archive (personal) catches are never included.

Profile bio (optional, off by default). Your profile bio is private by default. If you turn on “Show my bio on my profile”, the text you write is shown to other signed-in CatchBadge members — never to logged-out visitors or the public web. You can turn it off at any time, which removes it from your profile.

Partners’ public boards (optional, off by default). A verified partner — a charter skipper, tackle shop, fishery, club or brand — can choose to publish a shopfront page showing catches landed with them. Unlike everything else in CatchBadge, that page can be viewed by anyone on the internet, without signing in, and may be found by search engines.

You are never included on such a page unless you turn on “Show me on partners’ public boards” in Profile → Privacy. It is off by default, and it is a separate setting from your member album visibility — turning on album sharing does not put you on any public board.

If you do turn it on, a public board shows only: your display name, your founder number if you have one, and for your single biggest catch credited to that partner, the species and the weight. That is all. It does not show any photo of you or your catch, your email, the date of the catch, where you caught it, your other catches, or any account identifier. Only verified catches count; archive (private) catches are never included.

Withdrawing. Turn the setting back off and you are removed from every partner’s public board straight away — the boards are built fresh each time someone loads them, so we serve no cached copy of you. A partner switching their own shopfront off has the same effect. Please note that anything already published may have been copied, screenshotted or cached by third parties outside our control, which we cannot recall.

A board also shows counts of verified catches and anglers. Those counts cover only anglers who have turned the setting on — if you have not opted in, nothing about you appears on the page, not even as part of a total.

Social links (verified creators + partners). If you’re a verified creator or partner, any social links you add are shown on your CatchBadge profile or shopfront — to other members (creators) or to anyone, including the public web (partner pages) — so people can find your channels. Add or remove them at any time; removing a link takes it off your page.

Finding other anglers (optional, on by default). To help members connect, CatchBadge can suggest anglers to each other in two ways — “anglers in your area” (other members in your region) and “people you might know” (anglers who share a connection with you). A suggestion shows only your display name and avatar and a link to your profile — the same details already shown on the leaderboard. It never shows your catches, and it uses only the broad regionyou set (a town or county), never your device’s precise or GPS location.

You control this. In Profile → Privacy, switch off “Show me in member discovery” and you will no longer be suggested to other members. We do this on the basis of our legitimate interest in helping anglers find each other (see §3), and turning the setting off is how you object to it. “People you might know” is worked out from shared connections but never reveals who those connections are — not to you, and not to anyone you’re suggested to.

Photos are stored in a private Supabase Storage bucket. Access is mediated by short-lived signed URLs (1 hour or less). We do not embed your photos in advertising and we do not sell them.

To deter faked catches, your verified-catch photos are sent to Anthropic's Claude Vision API for automated assessment. Claude returns a structured verdict (species match, weight plausibility, red flags) that we store alongside the catch. Archive entries are not sent to AI.

Before any photo is sent, its GPS location data is stripped — Anthropic never receives your precise coordinates. The camera make/model and capture date are preserved so the authenticity check still works.

Anthropic processes the photos under its own privacy and data-handling commitments — see anthropic.com/legal/privacy. Anthropic does not use API inputs to train its models, and holds them for up to 30 days.

Public-photo safety check. If you choose to show a catch photo on a partner’s public page, we also send it to the same AI provider (Anthropic) to check for faces and possible under-18s before it can appear publicly. This is a safeguarding step, and a member of our team always makes the final decision on whether a photo is shown. The photo is processed under the same terms as above — not used to train models, and held by the provider for up to 30 days.

Where the AI confidence is high and no red flags are raised, your catch may be auto-approved without human review. For an ordinary catch, a length photo is a supporting signal only — the catch can be verified even when the measuring tape can’t be read clearly, and “verified” means the catch itself is confirmed, not that its exact length was AI‑read. A record or competition claim still requires a clear length read. You have the right under UK GDPR Article 22 to request a human review of any verification decision — email rob@catchbadge.com with the catch ID.

We use a Supabase Auth cookie / localStorage token to keep you signed in (strictly necessary, exempt from consent requirements under PECR). We may also set a short-lived Cloudflare bot-protection cookie (__cf_bm). No third-party tracking cookies, no advertising cookies, no Google Analytics.

The following providers process data on our behalf, each under a written processor agreement and their own published privacy policy:

• Supabase (authentication, database, storage) — supabase.com/privacy. Hosted in the EU (Frankfurt).
• Cloudflare (hosting, CDN, security, Turnstile bot protection) — cloudflare.com/privacypolicy.
• Anthropic (Claude Vision — AI verification) — anthropic.com/legal/privacy.
• Stripe (subscription billing + sticker shop checkout, when live) — stripe.com/privacy.

We do not sell or rent your data to anyone.

Who else can see your data. Processors aside, almost everything in CatchBadge is visible only to you or to other signed-in members. The one exception is a partner’s public board (§4): if — and only if — you switch that setting on, the limited details listed in §4 become visible to the general public, with no account or sign-in needed. No new company processes your data as a result; what changes is the audience. That setting is off unless you turn it on.

• Account + catch data: retained until you delete your account.
• Server logs (Cloudflare): up to 7 days.
• Tax-relevant transaction records: 6 years from the end of the tax year (HMRC requirement).
• Photos: stored as long as the parent catch exists; removed within 30 days of catch deletion or account deletion.

You can delete your account at any time via Profile → Delete my account. Deletion is immediate and irreversible.

If you create a linked business account through "List my business", it is a separate account with its own login. Deleting your personal account does not delete the linked business account — it stays active until you delete it separately by signing into it. We keep them separate so that a business's competitions, and catches other anglers have logged with it, aren't removed without the business's own owner deleting it.

Some processors (Cloudflare, Stripe, Anthropic) operate global infrastructure. Where personal data leaves the UK or EEA, we rely on UK ICO-approved International Data Transfer Agreements / Standard Contractual Clauses to ensure equivalent protection.

If you joined from another member’s invite link or QR code, we record which member invited you — a single private link between your account and theirs. We use this to run our invite and recruiter-reward programmes (for example, crediting the member who introduced you). Our basis is our legitimate interest in growing CatchBadge and rewarding members who bring in active anglers. This link is private — it’s never shown publicly or to other members. It’s deleted if you delete your account, and you can object at any time via Settings or by contacting us.

You have the right to:

• Access any personal data we hold about you (Profile → Export my data downloads a full JSON dump)
• Correct inaccurate data
• Request deletion ("right to be forgotten")
• Object to or restrict processing
• Data portability — your export is provided in machine-readable JSON
• Withdraw consent where consent is the basis
• Request human review of an AI verification decision (Article 22)
• Lodge a complaint with the Information Commissioner's Office (ICO)

To exercise any of these rights, email rob@catchbadge.com. We aim to respond within one calendar month as required by UK GDPR.

CatchBadge is an 18+ service. You must be 18 or over to create an account, and we do not knowingly collect data from anyone under 18. If you believe we hold data about someone under 18, please contact rob@catchbadge.com and we will delete it promptly — you do not need to give a reason, and we will not ask the child for anything further.

We know younger anglers fish too. We would rather support them properly — with age-appropriate defaults and protections designed in from the start, as the ICO’s Age Appropriate Design Code expects — than admit them to a service built for adults. That work is planned; until it is done, CatchBadge is for over-18s only.

Being listed on a partner’s public board (§4) means being named on a page anyone can see without signing in. Because that is the most exposing thing the service does, it carries its own separate 18+ confirmation on top of the account-level requirement above — belt and braces, and it stays that way.

All traffic is encrypted via HTTPS. Authentication uses Supabase's hashed-password storage and Cloudflare Turnstile bot protection. Photos are stored in a private bucket with row-level security policies preventing cross-user access. We follow industry practice for keys, secrets, and access control.

We may update this policy as the service or law evolves. The "last updated" date at the top reflects the latest material revision. Material changes affecting your rights will be notified via in-app banner or email.

Privacy questions, data requests, or complaints: rob@catchbadge.com. If you are not satisfied with our response, you can contact the ICO at ico.org.uk or 0303 123 1113.