Privacy · Updated 5 October 2026
This notice covers this portfolio website and describes the data categories represented in the public code of the related products below. The products are separate applications: the data and providers involved depend on the application and features you use.
The portfolio identifies its author as David Minguela. For questions or requests about personal data described here, contact: minguela9109@gmail.com.
Where Google sign-in is enabled, Clerk handles authentication using the OpenID Connect scopes openid, email and profile. They support sign-in and basic account details such as an account identifier, email address, name and profile image when supplied by Google. The reviewed application code does not request Gmail, Drive or Contacts access. Not every related application currently exposes the same sign-in provider; the sign-in screen shown by each product determines what is available. Google OpenID Connect scopes.
Analytics preference for this browser. Turning analytics off stores a local preference; it does not remove data already reported.
The following categories come from the applications’ public data models and flows. They describe what a product can handle, not a claim that every feature or provider is enabled in every deployment.
Shopping lists and lines, quantities, selected products and offers, saved carts, and authorization metadata for the browser extension. Carrefour catalog services and Empathy are used to search and return product or offer information.
The repository still includes Better Auth and optional Clerk integration; the active identity provider depends on deployment configuration.
Menu and recipe data, ingredients, shopping lists, nutrition targets and profile fields such as name, age and sex. When used, submitted menu images and OCR text are processed for menu entry; the optional Telegram bot receives Telegram account/chat identifiers and messages or images sent to it.
The code contains a Neon migration target and legacy Supabase modules; the active database, image store and OCR provider are deployment-specific. Telegram is used for bot messages and files.
Account profile, recurring services or contracts, providers, amounts, renewal dates, notes, attachments, reminder settings and payment-method or bank-account fields entered by the user.
Reminder channels in the code include Telegram, email and WhatsApp; delivery vendors are used only when configured.
Job applications, companies, contacts and their details, application stages and events, salary ranges, notes, follow-ups and CV/resume files.
Clerk and Neon are present in the app code. Reminder email delivery through Resend requires a configured service key.
Training plans and routines, schedules, exercise sessions and sets, progress/history, timezone and user-created exercises or uploaded exercise media.
The code uses Clerk, Neon and private Vercel Blob storage for exercise media; Vercel Web Analytics is also integrated.
Trips, dates and destinations, place names and coordinates, itineraries, reservations and locators, participants, invitations, travel documents, expenses and equipment. Mapbox provides map/routing features; Open-Meteo provides forecast data for itinerary locations.
The app code also uses Clerk, Neon, private Vercel Blob storage and Vercel Web Analytics.
The code references Clerk for authentication, Neon for database-backed features, Vercel for hosting/analytics, and the product-specific services named above. Menu Planner also retains legacy Supabase code; notification and OCR delivery providers vary by configuration. Each provider processes information needed for its function under its own terms. Provider activation, storage locations and transfer arrangements must be checked for the specific deployed application.
The public repositories do not establish one retention period, legal basis or deletion workflow that applies to all products. I therefore do not state a fixed period here. To ask about data held by a product or request access, correction, deletion or restriction where applicable, email the contact above and name the application. You may also contact the relevant data-protection authority; in Spain, the AEPD publishes information about these rights. AEPD: data protection rights.
This page is a factual summary of the reviewed public code, not a statement that every listed application or integration is live. For the active provider or configuration of a product, use the contact link above.