Lentova is an invite-only nutrition-planning and self-monitoring beta for adults. It is not medical care. This notice explains the data used to provide the beta and the choices available to you.
Data Lentova uses
Lentova stores your sign-in identity; profile and goal settings; height, weight, activity, optional body measurements, and timezone; food, portion, meal, water, plan, check-in, and history records; and private ingredients or recipes you create. If you connect an AI provider, Lentova also stores the provider name, a short key hint, and an encrypted API key. The full key is not shown again or included in exports.
How data is used and shared
Data is used to authenticate you, build the plans and history you request, calculate nutrition through Lentova’s deterministic Nutrition Core, keep the service secure, and process features you explicitly run. Supabase provides authentication, database, and storage services; Vercel hosts the web application; and Google provides sign-in. Lentova does not sell personal data.
Private foods and recipes stay private unless you explicitly submit one for catalog review. Review packets contain the submitted facts and your optional note, not your email. An approved shared catalog item may remain after account deletion without retaining your account identity.
AI and imported files
PDF, CSV, text, Markdown, JSON, and pasted recipe sources are read in your browser. Unsaved recipe source text may be kept in this tab’s session storage so a navigation does not erase the queue; it is partitioned with a pseudonymous account scope and disappears when the tab session or site data is cleared. With supported on-device AI, source text stays on the device, but the structured draft is sent to Lentova’s server to match foods. If you choose a connected OpenAI, Anthropic, or Google provider, the queued source is sent to that provider only when you run the draft action. That provider’s terms, retention, region, and charges apply.
Offline data, retention, and security
A small account-partitioned browser queue may hold unsynced food additions while you are offline. Lentova does not cache authenticated pages or full diaries in its service worker. Personal data remains until you delete it or the beta owner removes it under the applicable retention policy. Access is limited to invited accounts and database access is scoped by server-side authorization and row-level security. No internet service can promise absolute security.
Your choices
Settings lets you export JSON and food-log CSV data, disconnect AI-provider keys, and permanently delete your account and user-owned data. Export first if you want a copy. Account deletion cannot be reversed. Clearing Lentova site data removes queues already stored on that device.
Contact and changes
During the invite-only beta, send privacy or security questions privately through the same person and channel that granted your access; do not include credentials or unnecessary health details. A published support contact and controller identity are required before open beta. Material notice changes will update the date above.