Privacy policy
This notice explains how the BouquetBrowse project handles information in its private research pilot and on this public information site.
BouquetBrowse is operated by the project administrator reachable at viethoangtran.ds@gmail.com. The public information site and private application have different functions; publishing this notice does not open the research application to the public.
Information we process
- Public site visits. Cloudflare hosts these pages and processes request information, such as IP addresses and browser details, to deliver and protect the site. These pages have no advertising, analytics scripts, forms, application login, or tracking cookies added by BouquetBrowse. See Cloudflare's privacy policy.
- Invited pilot participants. When the private application is enabled, we process account identifiers, email addresses, access roles, and authentication/session information to manage invited access. Password authentication is handled by the configured authentication provider rather than stored as plaintext by BouquetBrowse.
- Permitted catalog records. We may process seller business names, social account identifiers, profile and post links, captions, permitted photos, publication dates, advertised prices and fulfillment claims, source-access permissions, and derived catalog attributes, embeddings, and review records. We do not assume that public visibility grants unrestricted collection or reuse.
- Support and operations. We process information you send with a correction or deletion request, together with minimal job, security, and administrative audit records. We do not intentionally collect personal search histories.
Why we use information
We use it to operate the private pilot, display attributable permitted listings to authorized testers, search and compare bouquets, review extraction accuracy, maintain source permissions, protect access, and handle correction or deletion requests. An extraction review does not verify seller inventory or product availability.
Platforms, service providers, and AI
Meta APIs are used only where the required permissions and applicable use authorization are available. We do not use them to publish posts, send messages, or manage comments for this catalog workflow. We do not sell personal information or use Meta-derived data for advertising audiences.
The pilot is designed to use managed database, authentication, and private storage services from Supabase and application hosting infrastructure. When API-based AI enrichment is enabled, permitted captions and selected images may be sent to OpenAI to extract structured attributes and create search embeddings. OpenAI extraction requests are configured with storage disabled where supported; this does not guarantee zero provider retention. Local image processing may also generate derivatives and embeddings. Demonstration mode uses fictional data. Live provider use depends on configuration and source permissions.
Service providers process information according to their applicable terms and controls. Hosting or processing can occur outside your country. We do not claim that a production location, international-transfer arrangement, or live processing deployment has already been established.
How long we keep information
Pilot defaults are up to 30 days for raw source payloads and operational logs, 90 days for permitted media and vectors, and 12 months for accepted catalog facts. Shorter source requirements or valid deletion requests override those defaults. Account data is kept while needed for authorized access, and request/audit records may be retained where needed to document handling or meet applicable obligations. Backup copies require separate expiry or deletion handling; removal records must be replayed before restored data is returned to use.
Your choices and requests
You can contact viethoangtran.ds@gmail.com to request access, correction, deletion, or withdrawal from the pilot. Include only the account or source links needed to locate the relevant information. We may ask for proportionate evidence that you control the affected account or content. Do not send passwords, API tokens, or identity documents unless a justified verification method has first been agreed.
Follow the data-deletion instructions to disconnect a Threads connection and request removal of retained data. Revoking a platform connection stops the authorization but does not, by itself, delete information already retained by the project. Requests are handled by the project operator; this site does not submit requests automatically.
Security and changes
The private pilot uses restricted access, role-based administration, private media storage, and source-linked review and removal workflows. No system can guarantee absolute security. We update this page when the project's data practices change and revise the date above. Contact viethoangtran.ds@gmail.com with privacy questions.