Little Gift List Privacy Policy

The information depends on the features you choose to use. It can include your account email, internal account or pseudonymous guest identifiers, guest/account state, and the people and gift-planning information you enter.

Planning information can include recipient names or labels, birthdays or age group, relationship or pronouns, budgets, gift ideas, prices, purchases, retailer links, wrapping and storage status, notes, return information, previous or received gifts, wishlists, occasions, traditions, household/co-planner information and sharing choices.

Optional recipient profiles can include likes, dislikes, interests, gift hints, favourite brands, favourite colours and sizes. Profile preference fields, general notes and Quick Notes are for gift planning. Little Gift List does not provide a dedicated health or allergy field, and please do not use those free-text fields to store unnecessary health, medical or other sensitive information. If you nevertheless enter health or medical information in free text, it is handled as part of that user-generated content until you edit or delete it. Current deployed production does not send profile-preference text to an external AI gateway.

Product features can process product links, barcode numbers, product details, search queries, selected product options and photos you deliberately add or share into a supported planning/import flow.

If you share or save an image or photo into a supported gift-planning or import flow, the image can be uploaded to private storage and linked to the relevant planning record. It remains subject to the same access, deletion and account controls as the feature that stores it.

Little Gift List is a gift planner, so information you enter can be about someone other than you. This can include recipients, gift givers, household members and people you invite to collaborate or view a wishlist.

A recipient profile may concern a child if you are planning a gift for a child. Keep information about other people proportionate to gift planning, use optional fields only when useful, and avoid entering sensitive information that the app does not need.

This information normally comes from the person using Little Gift List rather than directly from the recipient. Invitation information can also come from the person who starts the invitation. Shared-planning information can come from other household members or people who use a sharing feature.

On devices where a system contact picker is available, you can deliberately select one contact to prefill a recipient name. Little Gift List requests only the selected name, not your address book. The name becomes cloud planning data only if you then save that person.

The Android app requests camera access when you choose barcode scanning. Camera frames are used on the device to detect a retail barcode; the detected barcode value can then be processed for product lookup rather than uploading a continuous camera feed.

Android share-receiver features can receive text, links or images that you deliberately share into Little Gift List so the app can help create or enrich a gift record.

Information is used to provide and sync the guest/account and planning features you choose to use, keep private plans separated between users, remember gift history and preferences, support household/wishlist sharing, process product links and barcode lookups, operate Price Watch when you explicitly choose it, preserve the compact tracked saving for a watched gift you later buy, provide backups/restore features where available, answer support/privacy requests and protect the service.

It can also be used for optional reminders or notifications that you enable. Planning reminder text is designed to avoid putting recipient names, gift names, prices, purchase details or reminder notes in Android lock-screen notification text. The locked Price Watch design itself does not send price-drop notifications.

UK data-protection law requires a lawful basis for each purpose. The basis depends on what the information is being used for; Little Gift List does not rely on one blanket basis for everything.

Contract: when you create a permanent account, the registration screen asks you to agree to the Terms of Use. Processing that is necessary to create and operate that account and provide the core account/planning features you request can rely on Article 6(1)(b) UK GDPR.

Legitimate interests: Little Gift List relies on Article 6(1)(f) for proportionate processing needed to operate the guest experience, handle private recipient/invitee information entered for gift planning, provide bounded first-party analytics, protect and troubleshoot the service, support user-requested Price Watch and its limited catalogue operation where appropriate, and temporarily retain the paused migration rollback copy. The interests are providing a useful private gift-planning service, improving/reliably operating it, protecting users and preserving a controlled migration rollback position. These uses are subject to documented necessity/balancing assessments and safeguards such as minimisation, access controls and retention limits.

Legal obligation: where processing is necessary to comply with data-protection rights, regulatory or other legal duties, the applicable legal-obligation basis may apply.

Where a future optional technology legally requires consent, Little Gift List will ask for that consent separately rather than treating ordinary use of the app as blanket consent. Device permissions such as camera or notification permission are also requested through the device/platform when the relevant feature needs them.

The current production analytics table records a limited set of first-party events to understand whether important planning/product features are working and being used.

Depending on the event, a row can include an internal user ID and household ID, event name, platform, occasion, whether it relates to an affiliate feature, and the event time. The current analytics table does not contain names, email addresses, gift text, search text or retailer URLs.

The controlled-experiment platform currently has no active seeded treatment. For an explicitly approved controlled product experiment, a signed-in internal user ID can be used server-side to keep a stable variant assignment across sessions and devices. When that assigned version is actually shown, analytics can record bounded experiment and variant labels. Assignment is not based on recipient or gift content, household planning content, an ADHD diagnosis, demographics or other sensitive targeting.

Raw analytics events are automatically removed after 90 days. Little Gift List does not use these events to build sensitive advertising profiles. You can contact us using the privacy form below if you want to object to legitimate-interests analytics processing.

Little Gift List records limited first-party client and server operational error telemetry so production failures can be detected and fixed. This can include an error type or category, coarse route, operation or feature context, platform where applicable, a non-content fingerprint and limited rate-limit state.

These diagnostics are designed not to contain raw error messages, stack traces, email addresses, gift text, retailer URLs, search text or raw share tokens. The main client/server/extraction diagnostic tables are cleaned after 90 days by the configured retention process. Short-lived operational queues and rate-limit records are kept only for processing, reliability and security purposes and are subject to continuing retention review.

Product lookup can use public retailer/catalogue information, product URLs, barcodes, selected options and the search terms needed for the request. Verified public product facts and catalogue price observations can be reused without storing which user a catalogue product was originally found for.

If you choose Find matching gifts from a Quick Note, that note is handed into the existing product-search flow and its text becomes the product-search query. Current deployed production does not send that note to an external AI gateway.

Price Watch does not start merely because you save an unpurchased gift. If you deliberately start Price Watch, Little Gift List links your user ID, item ID and catalogue ID to the fixed verified baseline price and timestamps needed for that feature. The active watch ends when the gift is bought or deleted, its product link changes, or an unfinished old-cycle gift moves to Needs sorting. Catalogue price observations themselves do not contain user/account identifiers in the current schema.

If you buy a watched gift, Little Gift List can keep a compact outcome containing the original baseline, your recorded purchase price/date and any non-negative tracked saving so the completed occasion can show an accurate money summary. A later correction to the purchase price updates that outcome. These finished-plan outcomes remain tied to the original occasion and are not automatically mined to build future gift or spending recommendations.

Current deployed production can create recommendation ideas from saved planning preferences without sending recipient profiles to an external AI gateway. Older dormant source paths reference an external AI service, but that endpoint is blocked from the current production deployment and the current Christmas AI-inactivity setting has no enabled/consented users. Little Gift List will not reactivate an external AI provider without a new processor, transfer, lawful-basis and privacy review and updated notice where required.

Current production is delivered through Cloudflare and an independent Supabase project. Supabase provides authentication, database and storage services; the primary Supabase project region is London. The private gift-photo bucket is not public.

Cloudflare provides the production application/edge and security infrastructure. Google is involved when you choose Google sign-in. Firebase Cloud Messaging is only relevant if push delivery is configured and enabled; current push-device storage is designed to contain only the device-registration data needed for delivery.

Awin and retailers can receive the normal request and affiliate-attribution information needed when you deliberately follow an affiliate link. Product lookup can also contact retailer/catalogue sources needed to answer the lookup you requested.

Lovable Cloud is no longer required for current production. It remains paused as a temporary historical/rollback copy while the post-migration assurance programme is completed. Data still held there remains within Little Gift List's retention and data-rights responsibilities while that copy exists.

The primary Supabase project is in London, but infrastructure/service providers may process limited information from or in other countries as part of their global services. Where UK law treats this as a restricted transfer, Little Gift List uses the provider's applicable contractual transfer safeguards and carries out transfer/data-protection assessments where required.

Gift lists and recipient planning are private by default unless you choose a sharing or household feature. When you deliberately share a wishlist/list or invite a household co-planner, the app makes the information needed for that feature available to the people or link recipients you selected.

Only share links with people you trust. Leaving a household removes your access but does not delete a planning space owned by someone else.

Little Gift List does not intentionally collect special-category information for its gift-planning purposes and the former dedicated allergy/health field has been removed. If you put health, medical or other sensitive information into a free-text field, it can be stored as part of that user-generated text until you edit/delete it. Please do not add sensitive information the app does not need.

Little Gift List does not make solely automated decisions that produce legal or similarly significant effects about you. Gift recommendations, product matching and Price Watch are planning tools; they do not make legally significant decisions about a person.

Little Gift List uses technical and organisational safeguards appropriate to the service. These include HTTPS/TLS network connections, authentication and access controls, restricted server-side administrative operations, private storage for gift photos, database row-level security and bounded retention/diagnostic controls.

No internet service can promise absolute security, so these safeguards reduce risk but cannot guarantee that information will never be exposed or misused.

Core account-owned or guest-owned planning information is generally kept while the relevant account/guest plan exists unless you delete records earlier. Active guest plans and core gifts, recipients or households are not automatically deleted solely because they are old. Existing deleted-recipient recovery uses a 30-day recovery window where that product flow applies.

An active Price Watch exists only while that user-requested watch remains relevant. It is removed when the gift is bought/deleted, the product changes, or an unfinished old-cycle gift reaches Needs sorting. A compact tracked-saving purchase outcome can remain with the corresponding gift/finished-plan history so that the archived money summary stays accurate; deleting the related account/item removes it through its database relationship.

Raw user/household-linked analytics are automatically deleted after 90 days. The main client/server/extraction diagnostics are kept for 90 days. Backup-restore receipts are kept for 180 days. Expired household/wishlist/occasion invitations are removed after a 30-day grace period.

Support requests remain while open; resolved/closed support requests are automatically removed 12 months after their last update. Privacy/data-rights requests remain while unresolved; closed privacy requests are automatically removed 24 months after their last update.

When you permanently delete an authenticated Little Gift List account, the authentication account and account-owned planning spaces are deleted and related records configured with deletion relationships are removed. If you are a member of another person's household, deleting your account removes your membership/access without deleting that other person's household or gifts. Authenticated analytics attached to deleted account/household records and private experiment assignments attached to the deleted user are removed through the same database relationships.

Privacy enquiries and support requests matching the authenticated account email are also removed as part of the current account-deletion process after authentication deletion succeeds. Privacy enquiries and support requests that are not removed through authenticated account deletion remain subject to the retention rules above and any applicable legal, security or fraud-prevention obligations.

Verified public product-catalogue facts can remain because they are stored as reusable public product information rather than as account-owned planning records. The paused Lovable rollback copy is reviewed periodically and is not authorised for indefinite retention merely because it exists.

Depending on the circumstances, UK data-protection law can give you rights to be informed, access personal information, correct inaccurate information, request erasure, restrict processing, receive portable information, and object to certain processing. Some rights depend on the lawful basis and are not absolute in every case.

Where Little Gift List relies on legitimate interests, you can object to that processing. We will assess the objection against the specific purpose and the applicable UK GDPR rules. You can also ask about information that concerns you even if another user entered it into a private recipient or sharing record.

You can use the privacy-enquiry form below for a rights request. You also have the right to complain to the UK Information Commissioner's Office if you are unhappy with how your personal information has been handled.