What the current Givessa prototype records, why it records it and what it deliberately does not ask for.
The finder can process browser language, timezone-derived market, structured answers, recommended directions and structured feedback. It does not need a name, email, telephone number or exact address. Do not enter personal or sensitive information; the current flow has no free-text profile field.
Research permission is a separate, optional choice. Without it, finder events are not eligible for a research dataset. With it, only a reviewed snapshot may be prepared; collection does not mean automatic training, publication or transfer to an external AI provider. The same browser can delete its finder sessions while it retains their private deletion keys.
A wishlist stores a random public share token, a one-way hash of the private edit token, the chosen language, expiry time and selected gift concept codes. The private edit token is returned once and kept in your browser. No name or account is attached. Anyone with the public link can view the list.
Data is used to run the requested finder or wishlist, protect the service, diagnose failures and improve reviewed product rules. Finder sessions have a 30-day expiry and wishlists a 365-day expiry. The public application rejects expired records and an automated daily retention job deletes them from the operational database.
Hosting, database, cache and security logging providers may technically process request metadata such as IP address, timestamp and user agent. Givessa does not currently embed advertising trackers or third-party analytics on public pages.
A formal privacy request channel is not published in this prototype. Before a public or commercial launch, the responsible operator, contact channel, applicable jurisdiction and legally required rights procedure must be added and reviewed.