Privacy at LFN

Who to contact

LowFlyingNuts (LFN) is a personal hobby website for aircraft photography and daily games, operated by Alex Jones. Alex Jones is responsible for the personal information processed by LFN. Questions about the website or your information can be sent to lowflyingnuts@gmail.com. Please do not send passwords, sign-in codes or other secrets.

Google sign-in

Signing in is optional. You can use the photography pages and play as a guest.

If you choose Google sign-in, Google supplies basic account information to LFN’s Supabase authentication service: an account identifier, email address, name and profile-picture information. Supabase maintains the account record, authentication metadata and sessions. LFN uses this connection to establish and check your sign-in.

Your Google password stays with Google. This integration does not request access to your Gmail inbox, messages, Drive files or contacts. The current site does not display your Google name, email or picture publicly, and does not upload your browser’s game saves. You can separately choose and reserve one callsign. Account-saved play uses the main games page, stays separate from guest saves and requires an explicit start.

Google data is not used by this site for advertising, sold to advertisers or sent to an AI-training service. Google and Supabase also process information to operate their services under their own policies: Google privacy policy and Supabase privacy policy.

Email sign-in codes

If you choose email sign-in, you provide an email address you control to Supabase. Requesting a code creates or finds a private account; entering a valid one-time code establishes your session. No new password is requested. Supabase sends the requested code through Resend, which processes the recipient address, message content and delivery metadata. Your email provider also processes the delivered email. These messages are for sign-in, not marketing.

LFN does not separately save the pending form address or the code in browser storage, put the code in a URL, or display either publicly. The verified session uses the existing sign-in storage described below. A failed or uncompleted request can still leave an unconfirmed Supabase account or delivery record. The account-retention and manual deletion process below applies. Never share sign-in codes, including with LFN support.

Use your existing account’s email to return to its callsign. A different address can create a different account; LFN does not offer automatic account merging or callsign transfers.

Callsign reservations

After signing in, you can explicitly confirm and reserve a callsign. Supabase stores your internal account ID, chosen callsign and the time it was reserved. LFN does not copy your email, Google name or picture into the callsign record. Signing in or browsing the list does not automatically reserve a name.

The saved name is shown on your own account page. Reserved callsigns are public by default in the roster described below, unless a saved visibility choice hides them. Others may discover that a name is taken, but not which sign-in account owns it. If a ranked score is published, your callsign appears with it as described below. One callsign belongs to one account; this page cannot rename, transfer or release it. Signing out does not release it. The linked reservation is kept while your account is open and included in the manual account-closure process below.

Ranked games and leaderboard entry

Guest saves are not imported. If you sign in, reserve a callsign and submit your first guess, skip or reveal on the main games page, Supabase stores your internal account ID, UK game date, puzzle edition, guesses, skips, reveals, calculated scores, completion state, automatic-entry mode, revision and record timestamps. These records allow one run per account per day, resuming on another signed-in device, and server calculation rather than accepting browser-supplied totals. No Google email, name or picture is copied into these game records.

New account runs started with the automatic-entry notice join the public leaderboard as soon as all four games are finished. Runs started under the older private-until-published wording remain private unless you choose to publish them; they are not converted automatically. Publication makes your callsign, game date, per-game points, total, weekly completed-day count and rank available to anyone viewing the shared leaderboard. Raw guesses and internal account IDs are not included in that public response. Public information may be copied by visitors. You can remove today's entry from your scorecard; contact LFN for removal of older entries. Removing an entry does not erase the private run or give another attempt that day.

Ranked history is kept while your account is open and included in the manual account-closure process. Active linked game records are removed when the account is deleted; provider logs and recovery copies have the separate limits described below. Opening the games page or selecting a game does not start a new run. Your first submitted guess, skip or reveal starts account-saved play automatically when you are signed in with a callsign. Choose “Play as guest” before playing to keep progress on this device instead. You can play as a guest instead of starting an account run. New account runs enter the leaderboard automatically on completion; older private runs keep their original publication choice. Removing a published entry does not automatically re-add it. The existing sign-in storage also supports the main games page; no new score-storage cookie or local score upload is added.

Callsign roster and “Who’s about?”

Reserved callsigns are listed on the public roster by default. Recent-activity visibility is also on by default; a visible page visit or interaction can update one latest-activity time, at most once a minute. Both can be switched off separately in your account. Existing saved choices, including hidden/offline settings, are preserved. These defaults apply to accounts with no saved visibility choice and replace the earlier private-default version. Existing saved choices are not reset.

Anyone can browse and search visible callsigns. The footer lists callsigns active within the past 15 minutes, not everyone signed in. Multiple tabs count as one member. No activity is invented for existing reservations. Guest visitors are not tracked for this list. Public responses contain callsigns and counts, not account IDs, emails, real names, activity timestamps or page histories. A callsign is still linked to an account and is not a guarantee of anonymity. Visitors may copy public names/activity. Total reserved callsigns includes hidden reservations without identifying their owners.

Supabase stores the visibility settings, your internal account link, the date a setting/default was recorded, notice version, revision and (only while online visibility is enabled) one latest-activity timestamp. An initial activity record can apply the defaults without being a record of consent. That timestamp is replaced by later activity or cleared when online visibility is switched off. The 15-minute display window does not automatically erase the stored timestamp; it remains private until replaced, switched off or the account is deleted. LFN does not keep a browsing-history log for this feature. Hosting and account providers still receive normal request information as described below.

Untick either setting and save to hide it. “Appear offline” in the footer disables online visibility without changing the roster setting. Lists refresh about once a minute; copies already made by visitors cannot be recalled. Closing a page or signing out stops new updates from that browser, but a name can remain visible until its 15-minute window expires. Hiding does not release your callsign or remove separately published scores. Settings remain until changed or the account is closed; deleting the linked account removes the active community records.

The existing sign-in storage restores your account to apply these settings on normal LFN pages. There is no new browser identifier or tracking cookie. Privacy and terms pages load only public data and do not initialise sign-in or send activity updates. You can browse and play as a guest without a public callsign.

Why we use information

• Optional accounts: our legitimate interest in providing and checking the Google sign-in or email-code sign-in you request. LFN does not use the provider’s basic profile metadata to build a public profile. The same account purpose includes saving the callsign reservation you explicitly request, recording the ranked games you choose to start, and providing the callsign rankings described above.
• Website delivery and security: our legitimate interests in serving pages, protecting the service and investigating faults or abuse.
• Support: our legitimate interest in answering messages you choose to send and resolving the issue raised.
• Photography credits: our legitimate interest in identifying contributors and crediting their work.
• Community callsigns: our legitimate interest in providing the requested callsign-based community roster and recent-activity list, with no public sign-in identity, no visit history and separate hide/offline controls. You can object or switch either setting off without losing your reservation or access to games. Existing saved privacy choices are respected; a default setting is not consent.
• Optional Instagram feeds: your consent to load embeds and the associated sharing with Meta. You can withdraw it using Instagram settings.
• Legal responsibilities: compliance with applicable legal obligations, including handling data-protection requests, where those obligations apply.

You do not have to supply account information to browse or play as a guest. An email address is needed for email-code sign-in; Google account information is needed for Google sign-in. LFN does not use this information to make automated decisions with legal or similarly significant effects.

What stays in this browser

• Sign-in session: the account, ranked and optional community features use the existing sign-in service, which stores authentication tokens and may store provider account metadata in browser storage so Supabase can restore your session. Signing out of this browser removes its active LFN session; it does not delete your account record.
• Guest games: progress, results and streaks are saved locally. They are not shared standings and do not automatically move to another device. Ranked runs are separate server records as explained above.
• Instagram preference: an allow/block choice applies across LFN in this browser and expires after 90 days. You can change it sooner in the footer’s Instagram settings.
• Temporary interface state: some session-only preferences last for the browser session.

You can remove local saves and preferences through your browser’s site-data controls. This may lose game progress and sign you out, but does not itself delete server-side account records. The site has no automatic expiry configured for all local game saves.

Optional Instagram feeds

Instagram embed code is kept off until you allow feeds. Allowing them connects your browser to Meta/Instagram, which may receive your IP address and browser information and use cookies under the Meta/Instagram privacy policy.

Use Instagram settings in the footer to switch feeds off. This stops future embed loading and refreshes a page that already loaded Instagram code. It cannot remove cookies Meta has already set; use your browser’s controls for those. Opening an external social-profile link also takes you to that provider.

No LFN advertising or analytics scripts are included in this preview.

Photographs and contributor credits

LFN displays contributor names, public social handles and profile links supplied for photography credits. These are separate from private Google sign-in details. Credits are kept while the relevant work or contributor feature is displayed. Contact LFN if a photograph or credit raises a privacy concern, or you want a correction or removal considered.

Reports and support messages

The game report form only prepares text for you to copy. It does not automatically send or save your report. If you email LFN, Google’s Gmail service delivers your address, message and any information or attachments you include. Social-media messages are delivered through the service you choose. Leave personal information out of game reports where possible.

Routine correspondence is kept while dealing with your enquiry and necessary follow-up, then removed when no longer needed. Relevant parts may be kept longer for a specific unresolved complaint, security incident or legal requirement; only for as long as that reason applies.

Accounts and deletion

LFN keeps your basic account record while your account is open. To close your account and request deletion of its information, email lowflyingnuts@gmail.com. Alex Jones handles these requests manually. No self-service deletion button or automatic account-deletion schedule is currently configured.

Signing out, clearing browser storage or revoking Google access does not close your LFN account or delete its server-side record. You can clear your browser’s local game saves separately; they are not uploaded to the account service. Closing an LFN account does not delete your Google account.

Provider security logs and recovery copies can have different retention from the active account record. Their duration depends on the service and its operational, security, recovery or legal needs; there is no single deletion period covering every provider copy. On an erasure request, LFN checks the relevant records and provider arrangements, takes the necessary deletion or restriction steps, and explains any exception or delayed removal from backups. Account deletion is not a promise that every provider copy is erased immediately.

Service providers and international processing

Cloudflare hosts and delivers the website. Requests to it include technical information such as your IP address, the requested URL and browser request headers. Supabase provides authentication and stores account records; its configured account-service database is in Frankfurt, Germany. Google provides sign-in and delivers email sent to the LFN Gmail address. Meta receives embed information only after you allow Instagram feeds; visiting an external profile also connects you to that service.

These providers and their subprocessors may process information outside the UK and European Economic Area, including in the United States and Singapore. The Frankfurt database location does not mean all processing stays there. Cloudflare and Supabase publish data-processing terms with contractual transfer safeguards, including Standard Contractual Clauses and the UK Addendum where applicable. You can ask LFN about the safeguards relevant to your information or request a copy.

• Cloudflare Data Processing Addendum and Cloudflare privacy policy.
• Supabase Data Processing Addendum and data locations, transfers and retention.

Google and Meta also use information for their own services under the policies linked above. LFN does not sell your personal information or use Google account data for marketing.

Your choices and rights

You can browse as a guest, sign out, clear local site data, switch Instagram off or remove LFN access in your Google Account connections.

Contact lowflyingnuts@gmail.com to ask for access, correction, erasure or restriction. You can object to processing based on legitimate interests. Rights have legal conditions; portability applies to qualifying automated processing based on consent or contract, not to legitimate-interests processing. Withdrawing Instagram consent stops future loading, not processing already carried out. You can separately hide community visibility in your account; public copies already made by visitors cannot be recalled.

LFN normally responds without undue delay and within one calendar month. Where the law allows more time, LFN will explain why. Proportionate identity confirmation may be needed; never send your password or sign-in codes.

You can complain to the UK Information Commissioner’s Office, whether or not you contact LFN first.

Resend delivery and retention

Resend delivers the requested sign-in emails. The configured sending region is Ireland, but Resend says message content, delivery logs and account data are stored in the United States. Its published standard email/log retention is 30 days, with separate backup and legal/security exceptions. This is a provider policy, not a promise that closing an LFN account immediately erases all provider copies.

Resend publishes contractual transfer safeguards, including Standard Contractual Clauses and the UK Addendum. See its Data Processing Addendum, privacy policy and data locations and retention. LFN uses this connection for requested authentication emails, not an LFN marketing list.

Changes to this notice

This notice covers the features described here. It will be reviewed when LFN changes how it handles information, including before adding public account profiles, advertising or new providers. See also the website terms.