Last updated: 25 August 2026

Privacy Policy

How LittleBlueCup collects, stores, and uses information for Searches and Search requests.

In plain English

The short version, before the more detailed bits.

We collect only what we need

We try not to collect unnecessary information.

We do not sell personal information

LittleBlueCup does not sell personal information.

We protect user privacy

Email addresses and private details are not automatically shared with other users.

We use information to run LittleBlueCup

Information is used to review Search requests, operate Searches, support messaging, moderate safely, and respond to enquiries.

Information we may collect

Different parts of LittleBlueCup need different information to work properly.

Account information

  • name
  • email address
  • login details
  • account preferences
  • account status

Search information

  • Search request details
  • item details
  • Self Search activity
  • Search updates
  • quantity information

Uploaded content

  • photos
  • video clips
  • audio recordings
  • documents
  • written content

Platform activity

  • messages
  • moderation actions
  • reports
  • safety records
  • consent choices
  • audit records

Information about the person who needs the item

A Search may include information about the person the item is for. This might be the Searcher, a child, another family member, or someone the Searcher supports.

  • the person's name or public name
  • their age, approximate age, or birth-month details where supplied
  • their relationship to the Searcher
  • general location or region
  • why the item matters
  • private notes the Searcher says should not be shared publicly
Private notes, raw contact details, and information marked as not for sharing are not meant to appear on the public Search page.

Sensitive and disability-related information

Some Searches may include information about disability, health, sensory needs, communication, routine, safety, vulnerability, or family circumstances.

LittleBlueCup only needs this kind of information when it helps explain the Search, review safety and suitability, or protect the people involved.

Public Search wording should use only what has been reviewed as suitable, necessary, and safe to share.

Why we collect information

We collect information so LittleBlueCup can work as a Search, review, messaging, moderation, and safety service.

  • receiving and reviewing Search requests
  • inviting someone to complete full Search details
  • creating, managing, reviewing, publishing, updating, and closing Searches
  • supporting Self Search steps and wider Search activity
  • checking consent and media permissions
  • enabling account-backed messaging
  • protecting users and investigating reports
  • preventing misuse, scams, pressure, or unsafe contact
  • responding to contact, privacy, accessibility, press, and media enquiries
  • keeping staff audit, moderation, and safety records
  • operating and improving the website

Messaging

Messages help Searchers, finders, and LittleBlueCup communicate without automatically exposing contact details.

Messages are stored by LittleBlueCup and may be reviewed by authorised staff.

Messages may be reviewed when necessary for:

  • user protection
  • scam prevention
  • abuse investigations
  • moderation
  • safety checks
Messages are not automatically visible to everyone and are not end-to-end encrypted.

Photos, videos and audio

Media can help explain a Search, but it can also reveal private details about people, homes, routines, voices, children, disability, or location.

  • Searchers can upload photos, videos, audio, documents, and written descriptions.
  • Uploaded media is reviewed before it is used publicly.
  • Public media selection depends on consent, safety, review status, and whether the media is suitable for the public Search.
  • Staff may download or remove media where authorised and necessary for review, privacy, safety, or consent reasons.
Public use of media depends on the permission and consent settings selected by the Searcher, staff review, and public-safety checks.

You can read more on the Content and Media Permissions page.

Who can see information

Visibility depends on the type of information, the person looking at it, and what they need to do safely.

Public visitors

May see approved public Search information, public-safe updates, and approved public media.

Searchers

May see their own Search request, Search details, media, messages, and progress information.

Finders

May see the public Search and their own account-backed message thread when they use messaging.

Staff and moderators

May access additional information needed to review requests, manage Searches, respond to enquiries, investigate reports, and keep users safe.

Administrators

May access system-level information required to operate LittleBlueCup, manage access, audit activity, and maintain the service.

Email addresses

LittleBlueCup does not automatically expose user email addresses to other users.

Account-backed messaging and staff-reviewed contact forms are used so people can help with a Search without being given each other's direct email addresses by default.

Contact submissions are stored so LittleBlueCup can review and respond. Authorised staff access depends on the enquiry type; safety, complaint and privacy information may need more restricted handling. After a platform contact record has been dealt with, it may be permanently deleted from LittleBlueCup’s records. A separately delivered email copy can remain in the LittleBlueCup email system until it is deleted there.

Newsletter choices

LittleBlueCup and Still Fighting are separate optional newsletters. An account can choose either, both or neither, and can later withdraw each choice separately. Newsletter choices do not affect account access, transactional service email, Search review, Search priority or permission to feature a particular Search.

When an account holder chooses Subscribe or Subscribe again, the exact publication-specific wording shown beside that action is recorded against the verified account. An earlier LittleBlueCup update preference may be retained as historical evidence, but it does not create a newsletter subscription.

After that optional action, LittleBlueCup shares the verified account email with Beehiiv for the named publication. Beehiiv manages the email subscription and confirmation process, including unsubscribe and resubscribe state. Newsletter choices remain separate from Postmark transactional service emails and are not required to use LittleBlueCup.

Cookies and analytics

If you allow it, LittleBlueCup can count visits through its own Search and official-post links. It keeps only limited click totals and whether a request appeared automated or opted out. It does not use an outside analytics service, identify anyone or treat a click as proof that a platform caused a result. You can switch this off in Cookie Settings and the links will still work.

The current website uses essential sign-in/session storage, cookie-consent preferences, and a small amount of browser storage needed for account setup or interface preferences.

  • essential sign-in and security cookies
  • cookie consent preferences
  • limited browser storage for account setup choices
  • staff interface preferences
  • optional Metricool anonymous website analytics on eligible public pages

If you allow Metricool anonymous website analytics, it can load only on approved general public pages on the official LittleBlueCup website. It stays off staff, sign-in, account, form, private and individual Search pages. It also stays off whenever the web address or previous-page address contains extra details after a question mark or hash, or points to a private page.

Metricool does not set cookies or save information in your browser. Metricool says it does not create a unique visitor identifier. For an eligible visit, it receives the public page address, a page-view signal, the browser window size and, when it is safe, only the website the visit came from, not the full previous-page address. Metricool says it can use the connection IP address to estimate a country but does not store that address.

Switching analytics off prevents future Metricool requests immediately and does not require a page reload. It cannot take back aggregate information already sent while analytics was enabled. The marketing loader remains inactive.

Where information is stored and processed

LittleBlueCup currently uses external infrastructure and email providers to run the service.

Vercel

Hosts and serves the website. Technical request, device, and service log information may pass through Vercel when someone visits the site.

Vercel Privacy Notice

Firebase Authentication

Provides account sign-in and session support. It may process email addresses, login identifiers, authentication state, and related security information.

Firebase Privacy and Security

Firestore

Stores account, Search, Search request, contact, message, consent, moderation, safety, staff feedback/roadmap, and audit records used by LittleBlueCup.

Firebase Privacy and Security

Firebase Storage

Stores uploaded media and files such as images, videos, audio, documents, message attachments, staff-reviewed media assets, and private staff feedback screenshots.

Firebase Privacy and Security

Postmark

Sends service emails for contact messages, Search review requests, invitations, staff feedback alerts and other service notifications when email delivery is configured.

Postmark EU Privacy

OpenAI

Provides optional drafting only after an authorised staff member or owner reviews the selected information categories, confirms the current notice and deliberately asks Bluebell to create an editable draft.

OpenAI Data Processing Addendum

Metricool

Provides optional aggregate website analytics for eligible clean public pages after analytics consent. Metricool says its tracker does not use cookies, store the connection IP address or create a unique visitor identifier.

Metricool tracker and cookie information

Metricool's terms say it acts as a processor for website analytics, may use subprocessors and applies data-processing safeguards to international transfers. Its help material says disconnecting a website does not automatically remove its analytics history. LittleBlueCup must complete the account-level data-processing and retention review before the separate live connection step.

Some services may process or store information outside the UK. This policy does not say that all information remains in the UK.

AI drafting

Authorised staff may use Bluebell and OpenAI to help draft public Search wording, short and long voiceover scripts, and posts for one or more channels. The Owner may also use them for general campaign drafts.

Before each request, the person using Bluebell sees the exact categories selected for that draft and deliberately confirms the current OpenAI notice. Depending on the request, these categories may include approved public Search wording, item and quantity details, a permitted public name, an approved public quote, public-safe media descriptions, consent and safety warnings, approved writing guidance, drafting preferences, Distribution destinations, or the campaign brief, links, audience, available-media description and selected platforms. Voiceover requests do not include media descriptions.

Bluebell deliberately excludes media files, private messages, contact details, addresses, staff notes, moderation bodies and report bodies. The selected text categories are sent only after that deliberate action. OpenAI creates a draft; successful generated drafts are saved privately before human review so they can be edited or rejected. Nothing is published automatically. It does not publish a Search, change visibility, moderate users, make decisions, or send social posts, and it does not schedule content.

LittleBlueCup keeps a limited activity record so this feature can be used safely. It can include the categories used, the staff member who made the request, the time, the versions of the notice and choices, a request reference, its status and the amount of use. This activity record does not contain the source wording, prompt or generated text. LittleBlueCup may keep the private editable draft and its review history under its own retention practices.

What OpenAI keeps is separate from what LittleBlueCup keeps. OpenAI may ordinarily keep submitted API content for abuse monitoring for up to 30 days. Approved data controls may change this. OpenAI says it may keep information for longer when required by law or when reasonably necessary to protect its services or another person or organisation from harm. OpenAI may therefore keep this information. LittleBlueCup does not save a second untouched copy of OpenAI's full response, but it does privately save the usable draft as described above.

How long information is kept

LittleBlueCup keeps different records for different reasons. Some records are short-term working information. Others may be needed for safety, moderation, audit, history, or legal reasons.

  • Search requests and Search records may be kept while they are being reviewed, operated, updated, closed, archived, or needed for history.
  • Messages, reports, safety records, moderation notes, consent records, and audit logs may be kept where they are needed to protect people, investigate issues, or explain decisions.
  • Private staff feedback reports may include the reporting staff member, a safe page context and deliberately attached screenshots. They are retained as internal product-development records and may be redacted where appropriate while keeping a minimal audit record.
  • Uploaded media can be hidden from Searchers or removed from public use when appropriate; authorised staff also have limited permanent deletion tools for media that should no longer be kept.
  • There is no fixed automatic deletion timetable confirmed in the current implementation.
Where practical, people can ask for updates, corrections, review, or removal.

Your rights and choices

You can contact LittleBlueCup about privacy or data questions. Depending on the situation, you may be able to:

  • ask what information LittleBlueCup holds about you
  • ask for inaccurate information to be corrected
  • ask for information to be updated or removed where appropriate
  • ask about consent choices for public Search content or media
  • object to or query how information is being used
  • make a privacy or data request through the contact form
LittleBlueCup does not promise deletion where information still needs to be kept for safety, moderation, audit, operational, legal, or safeguarding reasons.

If you are unhappy with how a privacy concern is handled, you can also contact the Information Commissioner's Office.

Safety, reporting and disclosure

Privacy is part of safety, but it is not the only part.

Some information may be reviewed, restricted, kept, or shared where necessary to:

  • investigate reports
  • protect Searchers, finders, families, staff, and public visitors
  • prevent abuse, scams, pressure, unsafe contact, or misuse
  • support moderation, safety holds, and staff review
  • comply with safeguarding, legal, or serious safety responsibilities where they apply

Changes to this policy

This policy may change over time as LittleBlueCup evolves.

The latest version will always be published here.

Questions about privacy?

Use the contact form for privacy or data requests. Choose the privacy or data request option where it is available, and include enough detail for LittleBlueCup to understand what you are asking about.

LittleBlueCup exists to help people find important things. Protecting the people behind those Searches matters just as much.