This policy explains how KidsMeal handles information when a parent or caregiver uses the KidsMeal mobile application. KidsMeal is published by Onat Software, an individually owned business operated in Türkiye (“we”, “us”).

Information the app uses

• Account information. If you create or use an account, Firebase Authentication processes your email address, account identifier, sign-in provider, and authentication/session information. Sign-in options include email and password, Google, and Apple. Passwords are handled by Firebase Authentication; KidsMeal does not receive your plaintext password.
• School meal plan requests. The app requests published meal plans using a school and school-section identifier and the requested month. The service also receives ordinary connection information needed to answer the request, such as IP address, request time, and technical request metadata.
• On-device app data. The app may cache published menu text and menu images on your device for faster access and offline viewing. The app also displays a configured child label/grade and school section. The current meal-plan request sends the school/section and month; it does not send the child label or child ID.
• AI requests. When you ask for meal alternatives or a shopping list, the relevant menu text is processed by an AI model on your device. KidsMeal does not send that prompt or generated result to the KidsMeal API. On Android, the app uses the on-device Gemini Nano model through Android AICore. On iOS, the app can download a Gemma model from Hugging Face and run it on the device. Downloading a model involves a network request to the model host; that host may receive connection metadata. The device platform and model provider have their own privacy terms.

How information is used

We use account information to provide sign-in and account recovery; school and period identifiers to return the published meal plan you requested; and locally processed menu text to generate the feature you requested. We do not use the child profile to create a child account or for advertising.

Service providers and sharing

Firebase Authentication and Google Cloud/Firebase infrastructure support account authentication, the published meal-plan service, and storage of meal-plan content. These providers process information on our behalf to deliver their services. Google and Apple may also process information when you choose their sign-in service. We do not sell personal information or use KidsMeal menu prompts for advertising. We may disclose information when required by law or to protect the service and its users.

Retention and deletion

Authentication information is retained while the account is active. Published meal plans are retained as service content. Menu cache files remain on the device until removed by the app, cleared through device storage settings, or removed when the app is uninstalled. To request deletion of your KidsMeal account and associated information, follow these instructions. We may retain limited information where required by law or necessary to resolve security, fraud, or legal issues.

Children and family information

KidsMeal is intended for parents and caregivers, not for children to create accounts. Do not enter a child’s sensitive information, health information, or allergy details into the app. Meal alternatives and shopping lists are suggestions and are not medical, allergy-safety, or nutrition advice.

Security and international processing

We use Firebase/Google Cloud and the device platform’s services to operate KidsMeal. Information may be processed in locations where those providers operate, subject to their safeguards and terms. No method of transmission or storage is completely secure; we take reasonable measures to protect information used by the service.

Your choices and contact

You can sign out, stop using the app, remove locally cached files by uninstalling the app, and request account deletion. For privacy questions or requests, contact bekironat@onatsoftware.com.

Changes

We may update this policy as the app changes. We will update the effective date and publish the new version on this page.