This page supplements our Privacy Policy. It describes food-profile and related information that may be consumer health data under applicable US state laws, including Washington’s My Health My Data Act and Nevada’s consumer-health provisions. Applicability and available rights depend on the law and processing involved. A general food preference is not automatically a medical diagnosis.
Categories and sources
You may choose to record allergies, intolerances or food restrictions and other preferences that reveal a health-related need. Locally derived restriction matches may also reveal such a need. The current app stores profile entries and performs profile matching on your device; the profile is not intentionally sent in a cloud-analysis payload.
Photos, support messages or corrections you submit can themselves contain health information. Technical identifiers can connect a submitted item with a pseudonymous installation. Sources are your entries/selected material and the service’s processing of that material. We do not obtain medical records from healthcare providers, connect to HealthKit/Health Connect, or intentionally infer a new medical diagnosis from your shopping activity.
Purposes and recipients
We use this information to provide preferences and product explanations you request, operate the chosen photo analysis, handle support and protect the service. Local profile fields are not intentionally shared with AI or advertising providers. When you opt into remote analysis, Google/Firebase handles selected images/operational records and OpenAI interprets the prepared image; visible sensitive information in that image can reach them. Support email providers handle material you choose to send to support. Authorized operational access is restricted to the relevant purpose. There are no affiliated companies receiving consumer health data in this release; Vladyslav Kravchenko is the individual operator, not a group of unnamed affiliates.
We do not sell consumer health data, disclose it for targeted advertising, or use it to advertise health-related products to you. We do not use precise location or health-facility geofencing. Any legally required disclosure must have an applicable basis.
Consent and control
Optional profile processing and optional cloud analysis require distinct choices before you use those features. Profile permission covers the sensitive profile details used for local product matching; it does not authorize sending the profile to AI. AI photo permission separately identifies the selected photos and processing providers. Accepting general Terms is not blanket consent to collect or share consumer health data. Where the law requires additional collection or sharing permission, that permission is needed before the processing can occur. Refusing optional cloud analysis leaves the relevant local features available.
You may withdraw future permission and request access, confirmation, correction where applicable, a list of relevant recipients, deletion or another applicable right. Contact support@rialza.app with subject “Nibavo health privacy request”. We use proportionate verification; do not include a full medical history. We handle rights requests and lawful extensions within the applicable legal periods.
If we deny a request, we explain the reason and any available appeal route. To appeal, email the same address with subject “Nibavo privacy appeal”; if the appeal is denied, we provide information about contacting the relevant authority where required. We do not unlawfully discriminate against you for exercising these rights.
Retention and contact
The retention categories, provider limitations and security-record criteria in Privacy section 6 also apply here. Deleting a profile is different from deleting photos, technical account records, support messages or provider-held copies. We communicate which categories a completed request covers and any lawful residual retention.
Operator: Vladyslav Kravchenko, Ukraine. Contact: support@rialza.app, identifying Nibavo.