B2U Privacy Policy
Draft for product and UK legal review. Legal identity, contact details and launch arrangements remain placeholders; this is not a final production policy.
Version: 0.1
Effective date: [insert date]
Last reviewed: [insert date]
This policy explains how B2U handles personal information when you visit our website, use the B2U consumer service, report or claim an item, communicate with us, or interact with a B2U partner workflow. It also explains your privacy rights.
Current pilot and demonstration
This website currently provides pilot account registration and staff-controlled reviewer access. Recovery cases and provider events in the demonstrations are fictional and browser-local. Live identity checks, delivery bookings, payment processing, insurer connections and AI processing are not enabled. Descriptions of those services below apply only if they are subsequently enabled and their arrangements are confirmed. B2U is not an insurer and makes no underwriting, policy or claims decisions.
1. Who is responsible for your information?
The B2U service is operated by [full legal name of B2U entity], registered in [jurisdiction] under company number [number], with its registered office at [address] (“B2U”, “we”, “us” or “our”). B2U is the data controller for personal information it uses to operate its own consumer accounts, case service, support, security and website, unless this policy or a case-specific notice says otherwise.
Contact our privacy team at [privacy email] or write to [postal address]. [Add DPO contact details if a Data Protection Officer is appointed or legally required; otherwise do not describe the privacy contact as a DPO.]
Partner cases
A venue, transport operator, insurer or other organisation may decide why and how it uses information in its own lost-property system. That organisation may be a separate controller. B2U may act as its processor when it provides software under its instructions. For some shared recovery workflows, B2U and the partner may each determine purposes and means, or may be joint controllers. The actual arrangement depends on the workflow and will be set out in the partner agreement and, where needed, a case-specific privacy notice.
If you are dealing with a partner directly, read that organisation’s privacy notice too. Contact us if you are unsure which organisation is responsible for a particular part of your case.
2. Personal information we may handle
The information we handle depends on the feature you use and whether B2U or a partner created the case. It may include:
| Category | Examples |
|---|---|
| Account and contact details | Name, email address, telephone number, account identifier, preferred contact method, account verification status and accessibility or language preferences. |
| Lost and found case details | Item category, description, date and approximate place lost or found, route or venue information, case reference, case status and case timeline. |
| Item images and evidence | Photographs, receipts, serial or IMEI details, distinctive marks, proof of purchase, device or account association and other evidence you choose to submit. These may reveal information about you or another person. |
| Identity-check information | Verification provider, session or transaction reference, check status, assurance level and outcome. B2U is designed to receive a provider result rather than raw identity documents wherever possible. The provider may collect identity documents or biometric information under its own notice. |
| Location information | A place you enter in a report and, only if you choose to use it, a device location shared for a specific case. We do not need continuous background location to provide the core service. |
| Communications | Messages, support requests, complaint details, case notes and attachments. We may record call details where we tell you that we do so. |
| Collection and delivery details | Recipient name, delivery address, contact number, delivery instructions, carrier reference, tracking events and confirmation or exception evidence. We request an address only when it is needed for an agreed delivery. |
| Reward and transaction status | Reward offer and eligibility, amount and currency, payment-provider reference, transaction status, refund or dispute event. B2U does not intend to store full payment-card numbers. |
| Partner and organisation data | Organisation and venue records, staff account and role information, item inventory, custody events, partner API activity and webhook events. |
| Technical and usage information | Device/browser data, IP address, security events, diagnostic logs, consent and preference records, and cookie or similar technology information as described in our Cookie section. |
Please do not send us passwords, full payment-card details, unnecessary identity documents, or sensitive personal information that is not needed for the case.
3. Where information comes from
We may obtain personal information:
- directly from you when you create an account, make a report, submit evidence, message us or request support;
- from a finder, recipient or person acting for you;
- from a venue, transport operator, insurer or other partner that records or handles the item;
- from an identity-verification provider, courier, payment provider or communications provider when you use that service;
- from a person or organisation we contact during a human-reviewed search for an item, including publicly available business contact details; and
- automatically from your device or browser when you use our website or application.
If we receive information about you from someone else, we will provide privacy information as required by law, including at the first relevant communication or disclosure where applicable. We will not reveal a claimant’s personal details to a non-partner organisation as part of an initial search unless the disclosure is necessary, lawful and approved for the case.
4. Why we use information and our legal bases
UK data protection law requires us to have a lawful basis for each purpose. The exact basis depends on the feature, the organisation involved and whether you are a consumer, partner contact or person mentioned in a case. We document the basis for each live workflow.
| Purpose | Typical information | Likely lawful basis |
|---|---|---|
| Create and secure an account; provide the case service you request | Account details, report, case status, messages and evidence | Contract, or steps taken at your request before entering into a contract. |
| Search for possible items and coordinate a recovery case | Report details, location or venue context, found-item records, candidate references and case events | Contract where the processing is necessary to provide a service you requested; otherwise legitimate interests where appropriate and balanced against your rights. |
| Review claims and coordinate an authorised handover | Ownership evidence, identity-check result, custodian decision and release event | Contract and legitimate interests in preventing mistaken or unauthorised release; legal obligation where one applies. Any special-category or criminal-offence data requires an additional legal condition and will not be used unless separately approved. |
| Arrange delivery or process a reward | Delivery details and provider transaction status | Contract, steps taken at your request, and legal obligation for relevant accounting or transaction records. |
| Provide support, manage complaints and keep the service reliable | Communications, support and technical records | Contract, legal obligation where applicable, and legitimate interests in operating and improving support. |
| Protect users, items, systems and case integrity; detect misuse | Security logs, account activity, case events and limited risk indicators | Legitimate interests, and legal obligation where applicable. Risk indicators are reviewed proportionately and do not by themselves prove misconduct. |
| Send service messages | Contact details and case/account status | Contract or legitimate interests in delivering essential service and security notices. |
| Send optional marketing | Contact details and marketing preferences | Consent or another lawful basis permitted by law. We follow applicable PECR rules and provide an easy opt-out. |
| Use non-essential cookies or similar technologies | Cookie identifiers and usage data | Consent where required by PECR; some limited technologies may fall within a legal exception. We will identify the technologies and choices in the cookie controls. |
| Meet legal, regulatory, accounting and legal-claim requirements | Relevant case, transaction and audit records | Legal obligation and, where appropriate, legitimate interests in establishing, exercising or defending legal claims. |
| Measure and improve aggregate service performance | Pseudonymised or aggregated usage and outcome data | Legitimate interests where an assessment shows that our interests are not overridden; consent where required for the technology used. |
We do not treat consent as the basis for essential case processing when another legal basis applies. Where we rely on consent, you can withdraw it at any time. Withdrawal does not affect processing that already took place lawfully or processing that has a different legal basis.
5. Location, images and sensitive evidence
Entering a location in a loss report is part of describing where an item may have been lost. Device-based location sharing is optional, limited to the case purpose and controlled by your device settings. We will not continuously track you in the background as part of the core service. You can deny or later withdraw device location permission; this may make a location-based search less precise.
Images and evidence are private by default and available only to people who need them to review or progress the case. We may use image-analysis tools to describe or compare item features if that feature is enabled and disclosed. We do not use face recognition to identify people for item matching. We will not send raw identity documents, home addresses, payment-card data or unrestricted private evidence to an AI provider unless that specific use, provider, retention arrangement and legal basis have been reviewed and clearly explained.
If an identity provider processes biometric information to uniquely identify you, that provider must explain its own processing. B2U will not add biometric identification to its workflow without a separate legal, security and privacy assessment and the required additional legal condition.
6. Matching and automated processing
Matching may use case descriptions, category, time and location, distinctive item features, permitted images, partner inventory and other case evidence to rank possible candidates. A score or suggestion is only a lead; it is not proof of ownership.
B2U’s intended workflow uses human review for ownership, identity, release, fraud, insurance, payment and dispute decisions. We do not intend to make a significant decision about you solely by automated means. If this changes, we will update this policy before the change takes effect and provide the information and safeguards required by law, including an explanation of the decision and a way to make representations, obtain human intervention and contest it where those safeguards apply.
We may use service providers to host or analyse limited data on our instructions. We require appropriate contractual and security protections. We do not permit an AI provider to use private case information to train a general model unless we first disclose that use and establish a lawful basis and any required consent.
7. Who may receive information
We share only information needed for the stated case or service purpose, with access controls appropriate to the recipient’s role. Depending on the case, recipients may include:
- the venue, institution or organisation holding or reviewing the item;
- a caseworker or B2U support specialist assigned to help with the case;
- a courier or delivery provider, after delivery is selected, with the details needed to complete it;
- an identity-verification provider, with the details needed for the requested check;
- a payment provider, with the details needed to process an authorised transaction;
- an insurer or claims partner, only for the information and purpose you have authorised or that another lawful basis permits;
- hosting, storage, email, SMS, security, customer-support and analytics providers acting under appropriate contracts;
- professional advisers, auditors, regulators, courts, law enforcement or other public authorities when disclosure is required by law or reasonably necessary to protect rights and safety; and
- a successor organisation if B2U undergoes a business sale or reorganisation, subject to appropriate confidentiality and legal safeguards.
We do not sell personal information. We do not give a partner blanket access to all consumer cases. Partner access is limited by organisation, role, case assignment and the applicable agreement.
8. International processing
Some providers may process information outside the United Kingdom. Before a restricted international transfer, B2U will use a transfer mechanism permitted by UK data protection law and assess whether the information will remain appropriately protected. The actual countries, providers and safeguards depend on the live hosting and integration setup.
Provider and transfer details: [publish an up-to-date sub-processor/provider list, processing locations, transfer mechanisms and contact route here before launch].
9. How long we keep information
We keep information only for as long as needed for the case, service, legal obligations, security and dispute handling. The UK GDPR does not set one universal retention period for all records. We will maintain a record-type retention schedule, review it, and delete or anonymise information when it is no longer needed, unless a legal hold or other lawful reason requires longer retention.
The following is a proposed schedule for B2U to approve and implement, not a statement of currently configured system behaviour:
| Record | Proposed default retention | Important qualification |
|---|---|---|
| Account profile | While the account is active, then up to 24 months after closure | Keep a minimal suppression/security record only if needed to honour an opt-out or prevent abuse. |
| Open case and case timeline | Until the case is closed | Keep longer only for a defined legal, dispute, partner or audit purpose. Unresolved property may remain subject to the custodian’s separate policy. |
| Closed case details and ordinary messages | Up to 24 months after closure | Delete or anonymise sooner if no longer needed; preserve only records required for a live complaint, legal claim or documented partner obligation. |
| Private ownership evidence and attachments | Until the decision/dispute is final, then up to 90 days | Longer storage needs a specific documented reason. Do not retain raw ID documents by default. |
| Identity-verification references and outcome | Up to 24 months after the related case closes | Provider retention is governed by that provider’s notice and contract; B2U should retain only the minimum result/reference needed. |
| Delivery address and delivery instructions | Delete or restrict within 90 days after confirmed delivery or case closure | Retain longer only for an active delivery dispute, legal claim or payment/accounting requirement. |
| Payment and accounting records | For the period required by applicable law | Store provider references and transaction records, not full card details. Confirm the applicable accounting schedule with advisers. |
| Support, security and access logs | Up to 12 months, unless an incident or legal hold requires longer | Restrict access and avoid logging evidence or unnecessary personal details. |
| Marketing preferences | Until withdrawal or the relevant inactivity review date | Keep only the minimal suppression record needed to respect an opt-out. |
| Cookies and device data | As stated in the cookie controls | Set and disclose actual lifetimes before deployment. |
If you request deletion, we will assess the request under applicable law. Deleting an account may not immediately remove information that we must retain for a legal obligation, a live dispute, security, another person’s rights or a documented lawful purpose. Where full deletion is not appropriate, we will restrict use and explain why where required.
10. Security
We use technical and organisational measures designed to protect personal information, including role-based access, restricted evidence storage, access logging, secure transmission, provider review and incident handling. No online service can promise absolute security. If a personal-data breach occurs, we will assess it, take appropriate steps and notify affected people or the regulator where the law requires.
Access to identity-related evidence and sensitive case material should be limited, time-bound, reason-coded and audited. Do not send full evidence through ordinary email unless we specifically provide a secure method.
11. Your rights
Depending on the circumstances, you may have the right to:
- ask for a copy of your personal information;
- correct inaccurate or incomplete information;
- request erasure;
- ask us to restrict processing;
- object to processing based on legitimate interests or direct marketing;
- receive certain information in a portable format;
- withdraw consent where consent is the basis; and
- ask for information about a decision made using automated processing and, where applicable, request human intervention or contest it.
These rights are subject to legal conditions and exceptions. To exercise a right, contact [privacy email] and include enough information for us to identify the relevant account or case. We may need to verify your identity. We will respond within the period required by law and explain if an extension or exception applies.
You can complain to the UK Information Commissioner’s Office (ICO) at https://ico.org.uk/make-a-complaint/ or by contacting the ICO through its published channels. We would appreciate the chance to address your concern first, but you are not required to contact us before complaining to the ICO.
12. Cookies, browser storage and site analytics
Website analytics
Page visits, time on page, page speed, errors and clicks are recorded for every visitor to the published site. The editor preview is not counted. No consent banner is currently connected to these analytics. The analytics uses no cookies, stores nothing on the visitor’s device, does not keep IP addresses and does not identify visitors or recognise returning visitors.
It records the pages visited, where visitors came from, country, browser, operating system and device type, how long visitors stay, how fast pages load, errors, and clicks on buttons and links. The application can also forward error reports; it does not currently send separate custom interaction events. Detailed data is kept for 90 days and daily summaries for a year.
Lovable collects this data for us. Lovable's privacy policy explains how it handles it.
Sign-in, preferences and demonstration storage
Account sign-in uses browser-local authentication storage and sends account details to our hosted authentication service. Reviewer access uses an encrypted, secure, HTTP-only session cookie lasting up to eight hours; sessions can be revoked sooner. The emergency shared-password gate uses a separate encrypted cookie lasting up to eight hours, and changing availability settings invalidates it. Shared access does not replace a reviewer’s individual permissions.
Theme preference and fictional reviewer-scoped demonstration cases are stored in local storage until cleared or replaced. The reviewer identifier used to scope a demo is also stored in session storage. These records are not stored by the analytics script.
Our hosted platform provider, Lovable, supplies the website infrastructure and hosted account and access records. Account profiles, pilot registrations (including terms acceptance and separate marketing choice), reviewer credentials stored as hashes, grants, session records, workspace page visits and staff audit actions are available only to authorised people. Reviewer visit logs record page and timestamp, not verified engagement duration. Copy and right-click events are not measured.
Password-attempt protection uses a hashed request-network identifier and attempt counts for the emergency gate; the application does not store a raw IP address in its reviewer visit log. No automatic deletion schedule for account, reviewer, audit or attempt records has yet been configured. Proposed retention periods elsewhere in this draft are not statements of deployed behaviour.
Google Fonts receives requests to load Geist and Geist Mono, which may include the visitor's network address and ordinary request headers. No advertising pixels, third-party tracking embeds, live payment/identity/courier integrations or AI provider calls are currently loaded by the app. Provider locations and international-transfer arrangements remain to be confirmed before production launch.
13. Marketing and service messages
We may send you service messages about your account, case, security, support or an action needed to complete a recovery. You cannot opt out of messages strictly necessary to provide a service you requested, though you can close the account or case where available.
We will send optional marketing only where permitted by law. You can unsubscribe using the link in the message or contact [marketing/privacy email]. Unsubscribing from marketing does not stop case-related service messages.
14. Information about other people
If you submit another person’s contact details, photograph or other personal information, do so only where you have a lawful reason and it is necessary for the case. Tell that person about the relevant privacy information where appropriate. B2U may contact a person or organisation as part of a human-reviewed search, using a minimal message that does not reveal unnecessary claimant or item details.
If you believe someone has used your information improperly in a B2U case, contact [privacy email] and provide the case reference if known.
15. Changes to this Policy
We may update this Policy when our service, providers, processing or legal obligations change. We will post the new version with a revised effective date. If a change materially affects how we use information in an active case, we will provide additional notice where required.
16. Contact
B2U legal entity: [full legal name]
Privacy email: [privacy email]
Support email: [support email]
Postal address: [registered or service address]
Company number: [number]
ICO registration number, if applicable: [number or confirm not applicable]