Giggle Pieces Privacy Policy

Almo Learning (“we,” “us,” or “our”) provides Giggle Pieces, a puzzle app designed for children and families. This policy explains what information Giggle Pieces and its service providers process, why it is used, how long it is kept, and the choices and rights available to parents and guardians.

This policy applies to the Giggle Pieces mobile app and its related support and account services. Other Almo Learning website pages may process basic hosting and contact information separately.

Information We Process

Depending on the features a family uses, Giggle Pieces processes the following information:

Account identifiers: an anonymous Firebase user ID is created so the app can save and synchronize a player’s information. If a parent saves the account, the account may also be associated with the parent’s email address or Google identity.
Player profile: the selected player age or age band and an optional player nickname chosen by a parent or guardian.
Puzzle activity: completed puzzles, progress, stars, completion times, unfinished-puzzle state, and related app settings.
Analytics: app events and screen views, such as opening a screen, selecting a level, beginning or completing a puzzle, changing a setting, or using a parent-facing feature.
Diagnostics: crash reports, error details, app state, and device or app diagnostics. Depending on the app version and configuration, diagnostic reports may be associated with an internal user identifier or account type.
Feedback: feedback or support text submitted in Parent Settings, together with an internal user ID, app version, platform, category, and submission time.
Notifications and device information: notification permission and preference, Expo push token, a custom app device ID, app version, device brand, model, manufacturer, platform, operating-system name and version, and the time the device record was last updated.
Purchases: subscription or purchase status, product and entitlement information, renewal and expiration status, and an internal customer identifier. Payment-card details are handled by Apple or Google and are not provided to Almo Learning.
Technical service information: IP address, Firebase installation identifiers, app and operating-system version, request timestamps, and security or network information automatically processed when the app communicates with online services.

Giggle Pieces does not ask a child for a postal address, telephone number, photo, camera image, microphone recording, or precise location. The app does not contain third-party advertising and does not use collected information for targeted advertising.

How We Use Information

To create and authenticate a guest or parent-managed account.
To save, synchronize, restore, and delete the player profile, settings, puzzle progress, stars, and timers.
To adjust puzzle difficulty or presentation for the selected age band.
To provide notification reminders requested by a parent or guardian.
To confirm purchases, restore access, manage entitlements, and provide subscription support.
To respond to feedback, support, privacy, and deletion requests.
To measure app use, diagnose crashes, fix errors, protect the service, and improve app reliability when optional analytics and diagnostics are enabled.
To deliver app configuration, approved puzzle content, and software updates.

We do not sell personal information, share it for cross-context behavioural advertising, or make a child’s profile, progress, or feedback public.

Optional Analytics And Crash Reporting

Google Analytics for Firebase records app events and screen views. Firebase Crashlytics processes crash reports and diagnostic information. These optional services are controlled from the gated Parent Settings area through the “Share analytics and diagnostics” setting. They are off unless a grown-up enables them. Turning the setting off stops future optional collection and removes unsent crash reports from the device, but it does not immediately erase reports already received by a service provider.

Notifications

When a parent enables remote notifications, Giggle Pieces uses the Expo Push Service and the device platform’s notification service—Apple Push Notification service (APNs) on iOS or Firebase Cloud Messaging (FCM) on Android. The Expo push token and device information listed above are used to address, secure, troubleshoot, and stop notifications for the correct app installation. Notification permission can be withdrawn in the app or device settings.

Purchases And Subscriptions

When purchases are available, Giggle Pieces uses RevenueCat to retrieve products, validate purchases, restore purchases, and determine whether premium access is active. RevenueCat receives the app’s internal Firebase user ID as its customer identifier and processes purchase and subscription information received from Apple App Store or Google Play. Apple and Google process payment details under their own privacy policies.

Service Providers

We use the following providers to operate Giggle Pieces:

Google Firebase: Firebase Authentication for anonymous, email, and Google-linked accounts; Cloud Firestore for profiles, progress, settings, device records, and feedback; Cloud Storage for approved app content; Remote Config for app configuration; Cloud Functions for account deletion and related operations; Firebase Installations for app-instance identifiers; Google Analytics for Firebase for optional usage analytics; Firebase Crashlytics for optional crash diagnostics; and Firebase Cloud Messaging for Android notification delivery.
RevenueCat: purchase validation, subscription and entitlement status, product offerings, purchase restoration, paywalls, and customer support tools.
Expo: app infrastructure and the Expo Push Service, which passes requested notifications to APNs or FCM.
Apple and Google: App Store or Google Play purchases and platform notification delivery.
Cloudflare-backed update services: delivery of approved app updates and puzzle content.

These providers process information for the purposes described above and under their applicable agreements and privacy commitments. They may process information in countries other than the family’s country.

How Long We Keep Information

Firebase account, profile, progress, settings, feedback, and registered device records: kept while the guest or saved account remains active, and removed when the parent deletes the account or asks us to delete the information, unless a limited legal, security, or fraud-prevention exception applies.
Disabled or invalid push tokens: no longer used for notifications and removed when the associated device or account record is deleted. Expo push receipts are normally available for up to 24 hours.
Firebase Crashlytics: Google states that crash stack traces and associated installation identifiers are retained for 90 days before removal begins.
Google Analytics for Firebase: user-level and event-level information is retained for the period configured for our Analytics property, no longer than 14 months. Some aggregated reports may remain without identifying an individual user.
RevenueCat: customer and purchase-status information is kept while needed to provide or restore paid access. A parent may ask us to delete the associated RevenueCat customer record through the contact method below, subject to information Apple, Google, or RevenueCat must retain for legal, accounting, security, or fraud-prevention purposes.
Deletion-safety record: after account deletion, a record containing the Firebase user ID and deletion timestamps may remain for up to two hours to prevent an already signed-in device from restoring deleted data.

We do not retain children’s personal information for longer than reasonably necessary for the purpose for which it was collected. We securely delete it when that purpose ends, subject to the limited exceptions described above.

Deletion And Account Controls

A parent or guardian can open Parent Settings and choose the available child-data or account-deletion option. Account deletion removes the Firebase Authentication account and the account’s Cloud Firestore profile, puzzle progress, settings, registered devices, and feedback, and clears the app’s locally mirrored child data. When purchases are enabled, a parent may contact us to include the corresponding RevenueCat customer record in a verified deletion request.

Deleting Giggle Pieces data does not cancel an App Store or Google Play subscription. The parent must manage or cancel the subscription through the store account used for the purchase. A parent may also request deletion without the app through our account-deletion page or by contacting us.

Children’s Privacy And Parental Consent

Giggle Pieces is directed to children and families. Under the U.S. Children’s Online Privacy Protection Act (COPPA), personal information can include persistent identifiers such as user IDs, installation IDs, device IDs, push tokens, and IP addresses. Third-party SDK collection through the app is included in this assessment.

The grown-up gate separates parent-facing account, privacy, support, notification, and purchase controls from normal child play. The gate alone is not represented as verifiable parental consent. When COPPA requires verifiable parental consent for a collection, use, or disclosure that is not covered by an applicable exception, we provide direct notice and obtain that consent before beginning the relevant processing.

Limited persistent identifiers may be processed without prior consent when they are used only to support the app’s internal operations, such as authentication, security, network communication, maintaining a player’s session, or protecting the service, as permitted by applicable law. We do not use that exception to contact a child, for behavioural advertising, or to create an advertising profile.

Parents’ Rights And Choices

A parent or guardian may:

ask what personal information we have collected from their child and how it has been used or disclosed;
review, correct, or request a copy of that information;
ask us to delete the child’s information and related account;
revoke consent and refuse further collection or use;
keep optional analytics and diagnostics disabled;
decline notifications, remove an optional nickname, or use guest play instead of adding parent contact information; and
refuse collection beyond what is reasonably necessary for the child to participate in an activity.

We may request limited information to verify that the requester is the parent or account holder before providing access to or deleting information. Please do not send a child’s name or other unnecessary personal information in an email request.

Security

We use reasonable administrative, technical, and organizational safeguards, including encrypted network connections and access controls. No service can guarantee absolute security, so we also limit collection and access to what is needed for the purposes described in this policy.

Changes To This Policy

We will update this policy and the date above when our practices change. If a change materially affects information previously collected from a child, we will provide additional notice and obtain parental consent when required before using the information in the new way.

Contact Us

The operator responsible for Giggle Pieces is Almo Learning. For privacy questions, parental-rights requests, or concerns that a child submitted information without appropriate permission, email almokidslearning@gmail.com or use our contact page.