Privacy Notice

Last updated: 9 September 2026.

Who is responsible

1BritsPOV is a personal, non-monetised hobby archive operated by Mathew Luby, an individual based in England. Mathew Luby is the controller for personal information processed by this website. Contact: 1britspov@gmail.com. Linked services, including YouTube, Google and X, have their own privacy notices.

What we collect

You can browse cases without an account. Our hosting and security services process the connection information needed to deliver pages and protect them, which can include your IP address, browser information, request time and requested path.

If you sign in, Supabase Auth verifies your identity through Google or an email one-time code. The website receives your verified email and provider account identifier and starts with a reader alias that you can change. We do not ask for or store a local password. Resend delivers the sign-in emails and receives the recipient address, message content and delivery information. Google handles its own sign-in interaction and the basic profile/email permission used for it. We do not request access to your inbox, contacts or Google files through the website.

We store your public display name, comments, submitted source links, corrections and their status; votes and the case they concern; moderation reports, appeals, account restrictions and necessary audit records. Your email address is not part of your public profile. Moderation reports and appeals remain private to the authorised administrator and their author where available. Standalone sighting submissions start in private review. An edited version may be published only with the author’s optional publication permission, as explained below. Please do not include home addresses, phone numbers, identity documents, private correspondence or sensitive details about yourself or other people in public text. Release one has no direct media uploads.

Historical case pages may refer to identifiable people in published records. We record the source of that information, describe allegations as allegations and assess corrections, privacy concerns and requests to reduce unnecessary identification.

Why we use it

We use account identifiers, verified email, session information and the contribution details you choose to submit to provide the account and community services you request. Our lawful basis for processing objectively necessary to deliver those services is contract.

We rely on legitimate interests for proportionate security, abuse prevention, moderation, source-led publishing and approximate case-page counts. These interests are maintaining a usable and trustworthy archive, protecting readers and considering corrections. We limit the data, use short retention for security signals, keep private reports out of public discussion and offer human review and a right to object. Historical or research context does not automatically override a living person’s privacy. Where a specific applicable law requires us to keep or disclose information, we rely on that legal obligation and limit the processing to what it requires.

Optional Google Analytics is available only after you accept analytics; its purpose, data and controls are described below. We do not sell account information or use it for advertising profiles. If our purposes change, we will update this notice and provide any legally required information or choice before the new use.

Views, security and moderation

A case’s view total estimates full case-page opens. Marker previews are excluded. Short-lived pseudonymous signals help suppress obvious bots and rapid repeat opens; counts are not a reliable measure of unique people. The implementation hashes a server secret, UTC day, connection IP and a limited browser user-agent string, suppresses repeat opens for 30 minutes and normally deletes the resulting pseudonymous signals within 25 hours through hourly cleanup. Raw IP addresses and browser strings are not stored in the site database for this count. A repeat near midnight may be counted after the daily rotation. No cross-site behavioural profile is intended.

Cloudflare Turnstile checks community submissions for automated abuse. Cloudflare describes its processing in its Turnstile Privacy Addendum. Automated moderation rules can hold or reject a contribution or temporarily hide reported content. They can be wrong. You can ask for human review through the Moderation and Appeals policy. We do not use moderation results to make decisions about employment, credit or insurance.

Optional Google Analytics

With your permission, Google Analytics measures visits to public pages, including the Coming soon homepage. It receives cookie identifiers, the public page path, visit/session information, approximate location and browser/device information. Google processes connection information to provide this service. We do not send account IDs, emails, submission text, search terms, URL query strings or fragments. The tag is disabled on sign-in, account, submission and admin pages, in private previews and during signed-in sessions. Automatic enhanced measurement of searches, forms, outbound clicks and similar interactions is switched off. Advertising storage, advertising personalisation and Google signals are disabled by this website’s tag.

The Google tag does not load before you choose Accept analytics. Reject analytics leaves the site fully usable. Cookie settings in the footer lets you change your choice or withdraw consent. Do Not Track and Global Privacy Control keep analytics off. We use consent for optional analytics; withdrawing it stops future collection through this site and clears accessible Analytics cookies, but does not undo earlier lawful processing.

The browser preference is stored as `bp_google_analytics_v1`, including the choice, wording version and decision/expiry times, for 180 days. This is necessary to remember your choice and is not sent as a visitor identifier. The older `bp_optional_analytics` preference was for Cloudflare and does not grant Google consent. Analytics uses `_ga` and `_ga_095D0CZ0GJ` first-party cookies to distinguish visits/sessions, configured to expire after 180 days without extending the original expiry on each visit. Browser restrictions or clearing storage may shorten those periods. Clearing the preference causes the site to ask again.

Google’s property settings retain event-level data for two months and user-level data for 14 months, with the user-level period reset by new activity. These controls do not set the retention period of most aggregated reports. Google can process data outside the UK, including in the United States, under the applicable data processing terms and transfer safeguards. See Google Analytics data collection, data retention and Google’s Privacy Policy. Contact 1britspov@gmail.com about analytics privacy or removal requests.

Who receives information

Cloudflare hosts the website and its D1 database and helps protect it against abuse. Supabase manages account sign-in; the primary authentication service is hosted in London, UK. Resend delivers account emails. Google receives optional analytics information only after consent. Mathew Luby, as the authorised administrator, can access information needed to operate and moderate the service. Public contributions can be read, copied and shared by other visitors.

Some provider processing takes place outside the UK, including in the United States. Resend stores email data in the United States; its Ireland sending region controls message routing, not storage. Supabase’s London setting does not mean that every support, logging or subprocessor activity takes place in the UK. The providers’ processing agreements include contractual safeguards for relevant international transfers, including standard contractual clauses and the UK Addendum where applicable. Contact 1britspov@gmail.com for information about the safeguards relevant to your data.

See Cloudflare’s processing agreement and subprocessors, Supabase’s processing agreement and subprocessors, and Resend’s processing agreement, data handling and subprocessors. Their Cloudflare, Supabase and Resend privacy notices also explain provider account, security and legal processing. Google’s own privacy policy applies when you choose Google sign-in.

We share other information only where necessary for a stated purpose, such as responding to a valid legal request or protecting someone from a credible threat, after considering necessity and the applicable law.

How long we keep information

The website automatically removes expired sessions and rate-limit records hourly, view signals older than 24 hours, and site moderation audit records older than 365 days. Deleted or rejected contribution text and links are redacted after 90 days. Unpublished sighting records, including hidden reports and reports waiting in the publication queue, are deleted 180 days after their last update. Published sighting records are retained while needed for publication and review, unless withdrawn or removed. These jobs depend on successful scheduled runs; an hourly job normally processes eligible records within the following hour.

Account details, votes and block preferences remain while the account is active. Published contributions remain while relevant to the case. You can remove your own contributions or request account closure. After verifying a closure request, we remove the sign-in identity and the account’s website contributions, sightings, votes, reports and block records, and minimise related audit references. We normally handle a rights request within one calendar month, subject to the applicable legal exceptions and extensions described below.

Held or hidden material and open reports or appeals are kept while needed for review. The administrator reviews resolved reports and appeals for deletion within 12 months of resolution and reviews continuing account restrictions at least annually. These are manual reviews, not automatic expiry dates. Support and privacy correspondence is reviewed for deletion within 12 months after resolution. Any necessary longer retention must have a documented reason, limited scope and a review date.

The current Cloudflare D1 plan provides seven days of recovery history. Any manual database exports are kept privately and reviewed for deletion within 30 days. If a backup is restored, previously completed removals must be reapplied before the restored data returns to ordinary use. Resend retains email content and delivery logs for 30 days on its free plan, with a separate seven-day backup cycle. Supabase’s free dashboard exposes one day of API/database log history; that is an access window, not a guarantee that every provider security or legal record is erased after one day. Supabase’s optional database copy of authentication audit logs is disabled. Cloudflare’s optional stored Worker logs and traces are currently disabled.

Providers may separately retain account, security, support, billing or legal records under their published policies. Closing an individual website account does not terminate the site’s provider contracts. We consider proportionate removal requests and explain any information we must retain. ICO: storage limitation.

Your choices and rights

Email 1britspov@gmail.com to request access, correction, deletion, restriction, or portability where applicable. You may object to processing based on legitimate interests, including by explaining your particular circumstances. Rights depend on the processing and are not all absolute. We will ask only for proportionate information to verify a request, explain any refusal and tell you about available complaint routes. Rights requests are normally answered within one calendar month, subject to lawful extensions or other applicable timing rules. ICO: individual rights.

For a data-protection complaint, use the same email with “Privacy complaint” in the subject if convenient. No special wording is required. We aim to acknowledge it within three working days, investigate without undue delay, keep you informed and explain the outcome. You can also complain to the ICO. A complaint and a rights request are handled on their respective timelines. ICO: handling complaints.

Children and changes

The archive can be browsed without an account or age confirmation. Community accounts are for people aged 18 or over, and sign-in requires an adult self-confirmation. We do not ask for a date of birth or identity document. Self-confirmation does not prevent younger people from browsing or prove their age. If you believe a child has created an account or shared personal information, contact 1britspov@gmail.com without repeating sensitive details publicly. We will review the concern and take appropriate steps, which may include restricting the account and removing unnecessary information. We review audience and privacy risks when the service changes and explain material changes to this notice.

Sighting submissions and publication

We store your account identifier, selected topic, observation date, general location, description, optional evidence URL, review timestamps and status. We also record your publication choice, when you gave it and the wording version you accepted. The original submission remains visible only to you and the authorised administrator. Submitted evidence links are not fetched automatically by the website server.

Publication is optional. With your consent, the administrator may edit your description, remove identifying details, review the evidence link and publish a Community sighting or a clearly labelled user-submitted archive case. The public version can include the edited description, observation date, general location, an approximate map pin and the reviewed evidence link. It does not expose your email or account ID. Other visitors may copy public material.

You can remove publication permission in My account. This cancels queued publication and removes public versions controlled by this website; your original remains in private review. Withdrawing the submission also removes its description, observation date, location and evidence link from the active private record. A minimal receipt and duplicate-prevention digest remain until scheduled deletion. Withdrawal does not undo processing that was lawful before it, or erase copies independently made by other visitors.

Public disclosure of an optional sighting relies on your consent. Necessary account and review processing follows the other purposes and lawful bases in this notice. Do not include private addresses, contact details or unnecessary information about other people. Permission to publish your description does not authorise publishing another person’s private information.

Approved-source updates

The website checks selected public source feeds for new report entries each week. AARO/DVIDS entries use attributed official information; BFRO entries use limited factual metadata, original summaries and links. Each entry identifies its source and preserves the available date precision. Publication dates may differ from observation dates. These imports do not verify a sighting, establish an extraordinary explanation or guarantee new entries every week.

Public activity and YouTube

The home and video pages can highlight published website discussions with their public display names and dates, and aggregate case evidence votes. Private submissions, appeals and held discussion do not appear in these activity panels. Individual voter identities are not exposed in the activity feed.

The YouTube Data API feed is currently disabled. Playlist and video links take you to YouTube, which handles your visit under its own terms and privacy policy. The website does not automatically load a YouTube player or social tracking script. We will update this notice before materially changing external data collection or tracking.