Effective date: 2026. 11. 12.
NurtureBites helps caregivers record meals, understand food responses, and explore personalized meal ideas for children with sensory-selective eating.
The service is operated by Team 8, Principles and Practices of Software Development, Seoul National University (서울대학교 소프트웨어 개발의 원리와 실습 과목 8조), comprising 김도연, 김재민, 정해찬, and 허서연 (the “NurtureBites team,” “we,” “us”). This identifies the student project team; it does not identify Seoul National University itself as the service operator or imply university endorsement.
This policy covers the NurtureBites Android and iOS apps and their supporting API. If a web version is offered, the additional photo handling described below also applies.
We receive information you enter, information stored by the app on your device, and information processed when your device communicates with our service providers.
| Category | Information | Purpose and storage |
|---|---|---|
| Account information | Name, email address, internal account ID, password hash, account creation and update times | Account registration, authentication, account management, and support; stored on the server. Passwords are processed for authentication and stored as hashes rather than readable passwords. |
| Child profile | Child name or nickname, age group, allergies, dietary restrictions, dietary pattern, familiar or safe foods, preparation and presentation notes | Maintain a child profile and personalize meal ideas; stored on the server and cached on the device. Allergies and related information can be sensitive health information. |
| Meal records | Meal date, meal type, selected meal setting, food names, ingredients, cooking methods, food and ingredient outcomes, difficulty reasons, and information you enter in supported notes fields | Record and display meal history and personalize suggestions; stored on the server and in local drafts or caches. A selected meal setting is not GPS location. |
| Suggestions and feedback | Generated suggestions, saved or dismissed suggestions, dismissal reasons, and records of trying a suggestion | Display suggestions, avoid repeating dismissed ideas, and connect suggestions to meal records; stored on the server. |
| Optional photos and photo references | Before- and after-meal photos and their URI/path references | Display meal photos. In the native mobile apps, photo files are copied to app storage on the device; photo URI/path strings are also submitted to the API and stored with the meal record. |
| Consent records | Consent category, choice, document version, and time recorded | Record the choices submitted during onboarding; stored on the server. |
| Authentication and local app data | Access and refresh tokens, cached account/profile information, unfinished records, and language preference | Maintain your session and restore your work on your device. On supported native devices, tokens use the operating system’s secure storage. |
| Technical connection and operational data | IP address, request metadata, timestamps, response status, and diagnostic information where generated or logged | Deliver API requests and maintain service security and reliability. Logging and retention depend on the deployed infrastructure; see Section 6. |
| Privacy and support correspondence | Your email address, request, and the minimum information needed to verify your authority, including information submitted through our Google Forms deletion request form | Respond to questions and rights requests. Do not submit passwords or unnecessary information about a child. |
Please use a nickname where possible and avoid entering identifying information in food names or free-text notes. We do not need a child’s exact date of birth, government identifier, medical record number, or diagnosis document for the current meal-recording features.
Adding a photo is optional. The current version does not analyze photos with AI or send photos to the recommendation model for training or inference. Native photo URI strings can contain local file-path information; they are not the photo bytes themselves.
In a web version, a photo URI can be a data URL containing the actual image. If submitted as a meal photo reference, that image data is transmitted to and stored by the API. The mobile-only statement that photo bytes remain on the device does not apply to those web submissions.
Photos may contain personal information such as faces, documents, or location metadata. Avoid including people or identifying details. We do not promise that all embedded metadata is removed.
We use the information described above to: