Data Use Notice
Last updated: 21 September 2026
A short, plain-English explanation of the main ways data is used in the current production app. For lawful bases, rights and the full details, read the Privacy Policy.
Account and planning data
Your account or pseudonymous guest identity and the planning information you choose to save are used to provide and sync Little Gift List. This can include recipient profiles, birthdays, budgets, gift ideas and purchases, wishlists, photos, occasions and household/shared-planning information.
Information about other people
Gift planning can include names or labels and optional details about recipients, givers, household members and invitees. Keep this information proportionate to gift planning and do not use profile or note fields to store unnecessary health, medical or other sensitive information. On supported devices, the contact picker requests only the contact name you deliberately select.
First-party analytics and experiments
Little Gift List records a small set of first-party product and funnel events. Depending on the event, this can include internal user and household IDs, event name, platform, occasion, affiliate context and event time. The controlled-experiment platform currently has no active seeded treatment. If an explicitly approved controlled product experiment is activated, a signed-in internal user ID can be used server-side to keep a stable variant assignment across sessions and record bounded experiment and variant labels when that version is shown. 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 deleted after 90 days.
Diagnostics and reliability
Limited first-party client and server operational error telemetry can record an error type or category, coarse route, operation or feature context, platform where applicable, and a non-content fingerprint so production problems can be found and fixed. It is designed not to store raw error messages, stack traces, email addresses, gift text, retailer URLs, search text or raw share tokens, and older records are removed by the configured retention process.
Camera, barcodes and imports
Camera access is used when you deliberately choose barcode scanning. Camera frames are used on the device to detect a retail barcode; the detected value can then be processed for product lookup. Text, links or images you deliberately share into the Android app can be used to help create or enrich a gift record.
Shopping links and Price Watch
When you ask Little Gift List to read a product link or barcode, the information needed for that lookup can be processed by the backend, retailer or catalogue sources. Price Watch is optional: it starts only when you choose Price Watch for an eligible linked gift. It keeps the verified price from when you started watching as the comparison baseline and checks quietly without price-drop notifications. The user-linked watch ends when you stop it, the gift is bought or deleted, its product link changes, or it otherwise becomes ineligible. If you buy a watched gift, Little Gift List can keep the baseline, the actual price you confirm and the resulting non-negative tracked saving as part of that archived purchase. Shared catalogue price history itself does not contain user IDs.
Gift recommendations
There is no active external AI gateway in deployed production. Current deployed production can create recommendation ideas from saved planning preferences without sending recipient profiles to an external AI gateway. If you choose Find matching gifts from a Quick Note, that note is used by the product-search flow as the search request rather than being sent to an external AI gateway. Older dormant source paths reference an external AI service, but they are not part of the current deployed production path. An external AI provider will not be reactivated without a fresh privacy, processor and transfer review and updated notice where required.
Sharing
Gift lists, wishlists and household co-planning are private by default unless you deliberately enable a sharing feature. The app exposes only the planning information needed for the sharing feature and the people or link recipients you choose.
Current service providers
Current production is delivered through Cloudflare and an independent Supabase project. Supabase provides authentication, database and storage services, with the primary project region in London. Google is involved only when Google sign-in is chosen. Firebase Cloud Messaging is conditional on push being configured and enabled. Awin and retailers can receive normal request/affiliate-attribution information when you choose an affiliate link. Lovable Cloud remains paused as a temporary historical/rollback copy and is not required for current production operation.
Product catalogue and archives
Verified public product facts and price observations can be kept in a shared catalogue so the backend can reuse current retailer information without keeping who a catalogue product was originally found for. Completed planning cycles can remain in your Archive. Archived gifts are not automatically pulled into new plans or used to generate duplicate-gift or historical-spending recommendations; you choose when to open old archives.
Retention
Raw user-linked analytics and the main operational diagnostics are kept for 90 days. Backup-restore receipts are kept for 180 days. Expired invitations are removed after a 30-day grace period. Resolved or closed support requests are kept for 12 months and closed privacy requests for 24 months. Active Price Watch records last only while that watch is active; the compact purchase outcome can remain with the archived gift. Active guest plans and core gift-planning records are not automatically deleted solely because of age.
Your choices
You decide which people, gift details, photos, shopping links and optional planning details to add. You also choose whether to turn on Price Watch for an eligible gift and can stop it again. You can remove planning records, control sharing, leave shared planning you do not own, export or back up where available, permanently delete your account, and contact us about your data-protection rights or an objection to legitimate-interests processing.