Bloom App Privacy Policy

Applies to parents and guardians using the Bloom app to stay connected with their child's Nursery. The Nursery is the controller of your personal data; Bloom is the processor, acting on the Nursery's instructions. Data about your child specifically and the separate consent that governs it, is covered by the Child Data Privacy Policy, not this one.

4.1 What we collect about you.

• Account basics: full name, email, phone, profile photo.
• Your relationship to your child(ren) (e.g. mother/father/other) and, where applicable, whether you're authorized to pick your child up.
• Messages you send to staff, comments you post on announcements, likes on classroom photos.
• Device push-notification token, for notifications (e.g. new messages, daily report published) not used for location tracking.
• Basic product-usage analytics (Firebase Analytics) to understand how the app is used and improve it.

Crash and error reports. When the app or website stops working, it may automatically send a technical report to our service providers (Google Firebase Crashlytics for the mobile app, and Sentry for the websites) so we can find and fix the problem. These reports include technical information such as the app version, device model, operating system and the place in the code where the error happened. They are not designed to include names, phone numbers, emails, photos or children’s information, and we do not attach your account identity to them. Reports are kept for a limited period (about 90 days for Crashlytics and about 30 days for Sentry) and are processed outside Egypt, in regions we select with appropriate safeguards.

4.2 How it's used.

To give you access to your own child's information within the app (attendance, daily reports, assessments, photos, announcements), to let you message your child's Nursery staff, and to send you relevant notifications.

4.3 Who can see it.

Your child's Nursery staff who have a legitimate reason to (e.g. your child's assigned Teacher, the branch's Director/Owner). Other parents never see your personal data. Bloom's own staff can access it only as needed to provide support or maintain the service.

4.4 Consent and acceptance.

You're asked to acknowledge this policy the first time you sign in after being invited (alongside a separate, specific consent for your child's own data, see the Child Data Privacy Policy), and again whenever a materially updated version is published. Each acceptance is recorded and kept as a permanent record.

4.5 Ending your account.

You can delete your own account at any time from your account settings in the app. You confirm the request and your account is closed after 30 days. During those 30 days you can't use the app, except to cancel the deletion from the screen you'll see when you sign in. After 30 days your profile is anonymized (name, email, phone and photo removed or replaced) and your login is disabled. The Nursery's Owners and Directors are told when you request deletion or cancel it. One safeguard: if you're the only registered guardian of a child who is still enrolled or on pause, you can't request deletion until another guardian is added or the child's status changes, so a child is never left without a responsible adult on record. Deleting your account never deletes or changes your child's own record.

4.6 Your rights.

You have the right to ask for access to the personal data we hold about you, to have it corrected or deleted, to restrict how it is used, and to object to how it is used. Write to privacy@bloommena.com and we will respond within 30 days. Because your Nursery is the controller of this data, we may refer your request to the Nursery. You can also delete your own account in the app (see 4.5).

4.7 Security.

Your data is scoped by row-level security so only people with a legitimate reason (your child's own Nursery staff) can see it, and access is logged. Your session is stored encrypted on your device.

4.8 Contact.

If you have questions about this policy or how we handle your information, contact us at privacy@bloommena.com

4.9 Changes to this policy.

We may update this policy from time to time; material changes require you to re-acknowledge the new version before continuing to use the app.

Applies to the personal data of children enrolled at a Nursery using Bloom. This is the most sensitive category of data the app handles, and the only one gated by its own explicit, per-child, withdrawable guardian consent; separate from every other acceptance in this document set. The Nursery is the controller of your child's data; Bloom is the processor, acting only on the Nursery's instructions and this consent.

5.1 What we collect about your child.

• Identity: full name, date of birth, profile photo, enrollment date, enrollment status.
• Any allergies recorded by the Nursery (a short list, e.g. "peanuts," "dairy").
• Attendance: daily check-in/check-out records.
• Daily reports written by staff: mood, nap duration, meals eaten, a teacher's note.
• Developmental assessments: a point-by-point rubric completed by staff, roughly monthly, plus an optional teacher's note.
• Photos taken by staff and shared to the classroom's photo feed.
• Guardian and emergency-contact information linking your child to you and any other authorized adults (relationship, and for anyone besides a registered guardian an ID document, for pickup authorization).

5.2 Consent, how it works.

Before any of the above (other than your child's basic enrollment record) is created for your child, a guardian must give explicit, signed consent through the app a typed name, not a pre-filled signature, against a specific version of this policy. Until consent is given: your child's record exists but is excluded from staff pickers/rosters, and no classroom assignment, attendance check-in, daily report, or assessment can be created for them. Any one registered guardian's consent is enough to unlock your child's record. It doesn't require every guardian to consent separately.

5.3 Withdrawing consent.

Any registered guardian can withdraw consent for their child at any time from within the app, with a plain-language explanation of what that means before confirming. Withdrawal is absolute: it immediately re-locks the same actions listed in §5.2 for that child, even if a different guardian had given consent the most recent action (given or withdrawn), by any guardian, is what governs. Withdrawing does not delete anything already recorded, and does not remove your child from their classroom it only stops new attendance/report/assessment entries from being created until consent is given again.

5.4 What withdrawn/no consent looks like to Nursery staff.

While consent is pending or withdrawn, your child's name is shown to staff only as masked initials, and no photo is shown this applies to every staff role, including the Owner and Director, not just teaching staff. This is enforced by the system itself, not just hidden in the screen design, so it can't be worked around by, say, a screenshot of an unmasked view. This masking does not extend to your own view as the guardian you always see your own child's real name and photo. It also does not extend to the Nursery's billing/finance records, since a subscription fee is tied to your child's enrollment regardless of this consent.

5.5 Who can see your child's data.

Nursery staff whose role and classroom/branch assignment give them a legitimate reason to (subject to the masking in §5.4), the child's own registered guardian(s), and Bloom's own staff only as needed to provide support or maintain the service. Other parents never see another family's child's data.

5.6 Age of the child and who may consent.

Egypt's PDPL is understood to require explicit guardian consent for a child under 15, with a child aged 15–18 able to consent themselves or via a guardian, via a consent mechanism that itself needs regulatory approval. The consent system described above does not currently vary by the child's age, it treats every enrolled child the same, gated on guardian consent regardless of age.

5.7 Your rights, and what this policy does not promise.

This policy and the consent flow it describes control what the app does with your child's data day to day. They are not, by themselves, a guarantee of full erasure on request. To have your child's record deleted, contact your Nursery, which controls it.

5.8 Security.

Your child's data is protected the same way as everywhere else in Bloom, scoped access per role/branch/classroom, logged access, encrypted session storage plus the consent-based masking in §5.4, which is a real access restriction enforced by the system, not a display-only convenience.

5.9 Contact.

If you have questions about this policy or how we handle your information, contact us at privacy@bloommena.com

5.10 Changes to this policy.

We may update this policy from time to time; a material change requires a fresh guardian consent, following the same re-acceptance mechanism as every other policy here a previous consent is never altered or reused for a new version.

Applies to Owners, Directors, Supervisors, and Teachers using the Bloom app on behalf of a Nursery. Your Nursery is the controller of your personal data as your employer; Bloom is the processor, handling it only to provide the app on the Nursery's instructions. This policy explains what Bloom itself does with your data. It does not cover your employment relationship with the Nursery, which is between you and your employer.

3.1 What we collect about you.

• Account basics: full name, email, phone, profile photo.
• Role details: your role (Owner/Director/Supervisor/Teacher), which branch(es)/classroom(s) you're assigned to, job title, joining date.
• Optional profile fields your Nursery may ask you to fill in: years of experience, certificate, university, graduation year, gender, birthdate, marital status, home address.
• Documents your Nursery's Owner/Director uploads about you (e.g. certificates), up to 5 files.
• Activity you create in the app: attendance check-ins you record, daily reports and assessments you write, messages you send, announcements/comments you post.
• Device push-notification token, so the app can notify you (e.g. new messages), not used for location tracking.
• Basic product-usage analytics (Firebase Analytics) to understand how the app is used and improve it.

Crash and error reports. When the app or website stops working, it may automatically send a technical report to our service providers (Google Firebase Crashlytics for the mobile app, and Sentry for the websites) so we can find and fix the problem. These reports include technical information such as the app version, device model, operating system and the place in the code where the error happened. They are not designed to include names, phone numbers, emails, photos or children’s information, and we do not attach your account identity to them. Reports are kept for a limited period (about 90 days for Crashlytics and about 30 days for Sentry) and are processed outside Egypt, in regions we select with appropriate safeguards.

3.2 How it's used.

To run your account and give you the access your role needs; to let your Nursery colleagues and (where relevant) parents identify and reach you within the app; to record your work (attendance, reports, assessments, messages) as part of the Nursery's own operational records; to send you in-app and push notifications relevant to your work.

3.3 Who can see it.

Other staff at your Nursery, scoped by role and branch/classroom assignment, e.g. a Teacher only sees what their own classroom access allows, an Owner/Director sees more broadly. Parents can see your name and photo where you're the assigned teacher of their child's classroom. Bloom's own staff can access it only as needed to provide support or maintain the service.

3.4 Consent and acceptance.

You're asked to acknowledge this policy the first time you sign in after being invited, and again whenever a materially updated version is published. Each acceptance is recorded and kept as a permanent record; an earlier acceptance is never altered when you accept a new version.

3.5 Leaving the Nursery.

If your access is removed (offboarded), your past activity records (attendance you logged, reports you wrote, etc.) stay in the Nursery's records, since they're the Nursery's own operational history. Removing your access doesn't erase what you did while employed.

You can delete your own account at any time from your account settings in the app. You confirm the request and your account is closed after 30 days. During those 30 days you can't use the app, except to cancel the deletion from the screen you'll see when you sign in. After 30 days your profile is anonymized (name, email, phone, photo and address removed or replaced) and your login is disabled. The Nursery's Owners and Directors are told when you request deletion or cancel it. Historical records you created keep a reference to your (now anonymized) account rather than being deleted, since removing them could break the Nursery's own records (e.g. an attendance log). If you are an Owner, you can delete your account only while another active Owner exists on the Nursery, so the Nursery is never left without an Owner. The other Owners are notified.

3.6 Your rights.

You have the right to ask for access to the personal data we hold about you, to have it corrected or deleted, to restrict how it is used, and to object to how it is used. Write to privacy@bloommena.com and we will respond within 30 days. Because your Nursery is the controller of this data, we may refer your request to the Nursery. You can also delete your own account in the app (see 3.5).

3.7 Security.

Every piece of staff data is scoped by row-level security so it's only visible to people with an actual reason to see it, and access is logged. Your session is stored encrypted on your device.

3.8 Contact.

If you have questions about this policy or how we handle your information, contact us at privacy@bloommena.com

3.9 Changes to this policy.

We may update this policy from time to time; material changes require you to re-acknowledge the new version before continuing to use the app.

Covers how Bloom, acting as controller, handles the Nursery organization's own account and business data, not the personal data of individual staff, parents, or children, which are covered by the three policies below.

2.1 Scope and role.

This policy is about Bloom's direct relationship with your Nursery as our customer: your organization name, branch details, billing contact, subscription, and invoices. For staff, parent, and child personal data your Nursery collects and manages through the app, Bloom acts as your processor, not controller. You remain responsible for your own lawful basis and obligations toward those individuals (see §1.8 of the Terms, and the Staff/Parent/Child Data policies).

2.2 What we collect about your Nursery.

• Organization details: nursery name, logo, branch name(s), address(es), governorate, operating days/hours.
• Billing details held by Bloom's own back-office: billing contact name and email, plus (if provided) phone, address, and governorate.
• Subscription and billing history: plan, billing cycle dates, invoices, payment status, any discounts applied.
• Support/operational communications between your Nursery and Bloom's team.
• A record of manual actions Bloom staff take on your account (e.g. suspending, reactivating, issuing an invoice), kept as an audit trail, separate from any log of automated system behavior.

2.3 How we use it.

To provide the service (create and run your account, bill you correctly, respond to support requests), to communicate with you about your account (invoices, payment reminders, policy updates), and to meet our own legal/accounting obligations.

2.4 Who can see it.

Bloom's own staff (Admin/Officer/Super Admin roles on our internal back-office tool), scoped to what their role needs, e.g. only Admins can change your plan or feature access. We do not sell your organization's data, and we do not share it with other nurseries.

2.5 Where it's hosted.

Your data is hosted with our infrastructure provider, Supabase, on servers in the European Union (Paris, France).

2.6 How long we keep it.

Billing and invoice records are kept while your account is active and for 5 years afterwards, as accounting law requires. Our internal record of manual staff actions on your account is kept for 24 months on a fixed schedule.

2.7 Your rights.

You may ask for a copy of the organization-level data we hold about your Nursery, and for correction of inaccurate billing or contact details. You also have the right to ask for access, correction, deletion, restriction and objection for the personal data we hold. Write to privacy@bloommena.com (see 2.9) and we will respond within 30 days.

2.8 Security.

We use role-based access controls internally, and every table in our database enforces row-level security so that no nursery's data is ever visible to another nursery. Access to your billing/account data by our own staff is logged.

2.9 Contact.

If you have questions about this policy or how we handle your information, contact us at privacy@bloommena.com

2.10 Changes to this policy.

We may update this policy from time to time. Material changes will be presented to you for re-acceptance the next time you log in. Your previous acceptance of an earlier version stays on record and is never altered.