Privacy Policy for Minikiz

Effective Date: July 7, 2026

1. Introduction

Minikiz is a preschool education management ecosystem designed for institution administrators, teachers, and parents. We are committed to protecting the privacy of our users, especially children. This policy explains what information we process, why we process it, and how we protect it while delivering preschool communication, reporting, and institution management features.

2. Information Collection and Use

To provide our services, Minikiz may process the following categories of information:

• User Account Data: Names, usernames, contact details, role information, institution assignments, and account status for administrators, teachers, and parents created or managed by the institution.
• Student Data: Student names, class assignments, linked parents, attendance records, absence notices, and related institution-scoped identifiers.
• Daily Care and Development Data: Meal, sleep, mood, toilet, observation notes, developmental entries, year-end development reports, and similar educational follow-up records.
• Learning Records: Learning evidence / portfolio items, EDE observations, skill tags, behavior and context notes, and teacher-entered educational documentation.
• Media Content: Photos, videos, captions, comments, reactions, gallery approval status, and student tags used in class flow or portfolio-related experiences.
• Communication Data: Secure messaging between parents and teachers, reminders, announcements, appointment records, and related read / unread status data.
• Health and Care Data: Medicine definitions, dosage and schedule details, medicine administration outcomes, health notes, and selected consent-related health declarations where enabled by the institution.
• Consent and Authorization Data: Digital consent form templates, parent responses, pickup authorization / handover records, and other workflow confirmations required by the institution.
• Billing and Payment Data: Fee plans, invoices / installments, payment status, parent payment claims, optional receipt uploads, and administrator approval / rejection notes for billing workflows.
• Location or Pickup Data: Pickup-related records and optional location-based workflow data only when the relevant institution feature is enabled and used.
• Technical and Notification Data: Device tokens for push notifications, app preferences, theme settings, and operational logs necessary to keep the application functioning securely.

3. Children’s Privacy and Access Control

Because Minikiz is used in environments that serve children, we apply role-based and institution-scoped access controls designed to limit visibility to authorized adults only.

• No Public Access: Student-related data is not public and is only visible to authorized institution users such as the child’s parents, assigned teachers, and institution administrators with appropriate permissions.
• Institution Scope: Institution administrators can only access records belonging to their own institution. Cross-institution access is restricted to specially authorized system-level roles where applicable.
• Feature Controls: Institutions can enable or disable modules such as messaging, gallery, AI-assisted features, billing, digital consent forms, appointments, and other optional workflows.
• Purpose Limitation: Information is processed to support preschool education, care communication, administrative operations, and parent updates. It is not processed for advertising to children.

4. Technical Data, Permissions, and Security

• Push Notifications: We use Firebase Cloud Messaging (FCM) for real-time alerts such as messages, attendance updates, reminders, gallery activity, medicine actions, fee reminders, and related workflow notifications. Users can manage notification preferences through app settings where supported.
• Security: The application uses role-based access, authenticated APIs, and institution-scoped server-side validation to protect records from unauthorized access.
• Device Permissions: Depending on the features used, the app may request access to camera, photo library, or file storage for uploading photos, videos, documents, and payment receipts.
• Session and Preference Data: We may store authentication sessions, push tokens, and user interface preferences required for secure sign-in and app usability.

5. Data Sharing and Transparency

• Service Providers: We may use third-party services such as Firebase Cloud Messaging for notifications and Gemini-powered AI assistance for selected teacher or reporting workflows when enabled by the institution.
• No Sale of Data: We do not sell student, parent, teacher, or institution data to third parties.
• Authorized Visibility: Parents can view data related to their own child or children through the parent-facing application areas made available by the institution.

6. Contact

If you have questions about this privacy policy or about how Minikiz handles data, please contact us at minikizapp@gmail.com.