Trust & Security

This page is maintained by the NutriLabel AI team to answer common security and privacy questions about NutriLabel AI. It describes the controls we have enabled today and is provided as editable, app-owned content — not an independent certification or audit.

Authentication & access

  • Sign-in is handled exclusively through Google OAuth — we never store passwords.
  • All authenticated endpoints require a valid session token, verified server-side on every request.
  • Administrative actions are scoped to a single designated owner account.

Data handling

  • Recipes, generated labels, and account profile data are stored in our managed backend database.
  • Row-level security policies restrict every record to the user who created it.
  • We do not sell or share your recipe or lab-report content with third parties for marketing.

Subprocessors & integrations

  • Backend, authentication, and database hosting via the Lovable Cloud platform.
  • AI nutrition analysis via the Lovable AI Gateway.
  • Payments processed by Razorpay; we never see or store full card details.
  • Google OAuth for sign-in.

Retention & deletion

You can request deletion of your account and associated data at any time by contacting us at the address below. Once processed, your profile and generated label history are removed from our active systems.

Shared responsibility

NutriLabel AI relies on the Lovable Cloud platform for hosting, database, and authentication infrastructure. Platform-level operational controls are provided by Lovable; application-level configuration, access policies, and content accuracy are maintained by the NutriLabel AI team. Customers are responsible for safeguarding their Google account credentials.

Security contact

To report a security concern or request data deletion, please email girigrey00@gmail.com. We aim to acknowledge reports within a few business days.

This page is app-owned editable content and does not represent an independent certification or audit. Compliance, certification, and regulatory claims are only made when explicitly stated with supporting documentation.