Privacy Policy
Last updated: November 14, 2026
Buddyzz is a storytelling app for children and families. This policy explains what information is processed on the website and in the Android and iOS apps, why it is needed, and whom to contact. The sign-in account, parent PIN and purchases are intended for a parent or guardian. Both apps offer the digital scarf model, but their parent accounts are separate, and features and purchases may vary by version and country.
Who is responsible for the information and who this policy is for
The service and apps operate under the Buddyzz name. For questions about privacy, personal information or account deletion, contact us at ayala@buddyzz.com. Apple, Google, the app stores and hosting providers also operate independent services governed by their own policies.
Buddyzz does not ask for a child account or require a child to provide a name, email address or payment details to view open content. On Android, parent Google sign-in is required for remote downloads and account and wallet actions. On iOS, parent Sign in with Apple is optional, including for free book downloads, scarf purchases and exchanges; parent approval and store payment checks still apply. Technical authentication and wallet identifiers may be created when protected services are used, even without an Apple profile.
Parent account and identity verification
On Android, parents sign in with Google. On iOS, the wallet is associated with an Apple-verified App Store identity using signed app-transaction information and a keyed identifier derived from it. Firebase Authentication may create an anonymous technical session when a download or wallet operation needs authentication. These sessions and wallet identifiers can be linked to purchases and are not anonymous information for privacy purposes.
A parent may link an Apple sign-in profile to the existing iOS wallet. Firebase Authentication then processes information supplied by Apple, such as an email address or display name when available. Linking or unlinking that optional profile keeps the same wallet, balance and book rights; it does not create or merge another wallet. The optional Apple sign-in profile and the App Store purchase account serve different purposes. For deletion of a linked Apple profile, Firebase also processes a fresh Apple authorization code to revoke the Sign in with Apple permission before the deletion request is submitted.
On iOS, compatible devices using the same App Store Apple account can resolve the same wallet through the verified app transaction identity, without parent Sign in with Apple. A new installation may need the restoration option in Parent Profile; ownership and network checks apply. This differs from Android, where the Google parent sign-in identifies the account. Downloaded files, parent PINs and device preferences are local and are not synchronized by linking an Apple profile. Access through a parent Apple profile on a device using a different App Store account is not currently offered and remains a possible future feature.
Sign in with Apple is optional and will enable access to future account benefits, when offered. It links a parent profile to the existing iOS wallet and lets Buddyzz recognize that linked profile; Apple may provide a name or email address, including a private relay address. It is not required to buy scarves, exchange them for books or recover a wallet using the same App Store identity. No free scarf or other benefit is currently granted automatically for signing in; any future offer will state its eligibility and conditions.
The four-digit parent PIN is a local approval mechanism on the device; it is not a Firebase account password and is not sent to the wallet server. iOS wallet ownership is verified using Apple transaction and app/device integrity checks without requiring parent Sign in with Apple. Deletion and recovery follow the verification steps described below.
For a forgotten parent PIN, an iOS wallet without a linked Apple profile can use system biometric or device-passcode authentication; a linked profile uses Apple reauthentication. Buddyzz receives the system authorization result, not biometric templates or the device passcode.
Android uses the parent’s Google account, while iOS uses its verified App Store wallet identity with an optional Apple sign-in profile. Android and iOS wallets remain separate even when the same parent or email address is involved. Balances, purchase and exchange history, and book rights do not sync or transfer between the platforms. Linking an Apple profile within the existing iOS wallet does not link it to an Android wallet or merge two wallets.
Digital scarves, purchases and entitlements
When the scarf store is available, a parent can buy a pack of one or three digital scarves through Google Play on Android or the App Store on iOS. Once the server verifies the transaction, the balance is recorded in the parent account used for the purchase. Exchanging one scarf for an eligible book is recorded separately, reduces the balance and gives that account access to the selected book. The balance, scarf units, purchase and exchange history, book identifiers and entitlements are stored on the server to provide the service, prevent duplicate charges or use, and handle errors and refunds. Entitlements from earlier direct book purchases, if any, are handled separately.
To verify purchases with the store and bind them securely to an account, we process the store type, product and transaction identifiers, Google Play purchase tokens or Apple transaction identifiers where relevant, account-binding identifiers, payment and verification status, timestamps, and correction or refund records. Some identifiers are retained after a transaction is completed to prevent reuse of the same purchase and investigate refunds. We receive transaction confirmation and information from the stores, but the app does not send us the full credit card number. Transaction records may indicate whether the store marked a purchase as a test transaction, for verification, operation and transaction investigation.
The final price and currency are shown by the store before approval. Scarves are credited only for completed, server-verified purchases. On iOS, opening or dismissing an incomplete purchase flow does not create a wallet purchase-attempt record, reserve scarves or create a completed purchase-history entry. Technical service/security processing and store records are separate, as described in this policy. Refunds and revoked rights may change the balance or access after store verification. No welcome scarf is automatically granted.
Books, downloads and on-device data
As of the last update, “Jemma Superstar” and “Fred and the Blue Ball” are offered free of charge. On iOS, downloading free books does not require parent Sign in with Apple; technical authentication may be used to secure remote downloads. Android retains its parent Google sign-in requirement for remote downloads. Other books may require a scarf exchange, be available through an earlier direct purchase, or be marked “Coming soon”. Availability and price depend on the catalog and version in use.
The apps store downloaded books, caches, the local parent PIN, preferences and read-news markers on the device. Read-news markers are handled locally and are not currently stored in the Firebase wallet. Downloaded book pages are stored in protected form in app storage; a file already on the device is not independent proof of entitlement to a paid book. Removal of the app or its data depends on the operating system and backup settings, and does not by itself delete server records.
On Android, optional notification permission enables a silent local notification and launcher badge for unread News. You can change that permission in device settings; the in-app unread indicator remains available. This feature uses local read markers and does not upload them as reading activity.
Technical information, the website and service providers
Firebase and Google Cloud provide sign-in, the catalog, storage, access rules, the digital wallet and server services. Google Play and the App Store process payments and provide information needed to verify and investigate transactions. These services and the website hosting provider may process IP addresses, technical device information and network requests for operation, security and troubleshooting. Email support requests are processed so that we can respond. Technical request and error information may also be processed for security and troubleshooting.
The website is hosted on Cloudflare Pages. We have not enabled Cloudflare Web Analytics, and the current website and app code does not include advertising or dedicated usage analytics tools on our behalf. The website has no user account or form for collecting details. The hosting provider may process IP addresses, network requests and security data to deliver and protect the website. If we add analytics tools or new uses of information, we will update the policy and any required choice notices.
We use Firebase App Check, Play Integrity on Android and App Attest on iOS to verify app requests and protect against misuse. Providers process technical app and device attestation data. For iOS wallet ownership verification, we also retain verification public keys, attestation receipts, counters and limited request-verification records, including hashes used to prevent replay, associated with a technical session or wallet. Limited account-registration information, account identifiers, sign-in providers, timestamps and request-origin assessments may be retained for security. Support receives the email, request and files you choose to send; do not include children’s personal information, passwords, the parent PIN, purchase tokens or card details.
Purposes, sharing and security
Information is used to authenticate service access, verify wallet ownership, deliver books and updates, verify completed purchases, manage balances and exchanges, prevent fraud and duplicate use, handle refunds and provide support. We share information necessary for these roles with sign-in providers, app stores, Firebase/Google Cloud, website hosting providers and professional support providers, subject to applicable law and arrangements. These services may process information outside Israel according to their infrastructure and policies.
Wallet and purchase records are written on the server and cannot be changed directly by the app. We use authentication, access controls and encrypted communications; no system can guarantee absolute security. We treat an encrypted or hashed identifier that can still link transactions to a person or account as linked information, not anonymous information.
Information retention and account deletion
You can request deletion of your Buddyzz account or iOS wallet and associated data from the Parent Area, after parent approval and ownership verification. On iOS, an unlinked wallet does not require adding an Apple sign-in profile to request deletion. You may also email ayala@buddyzz.com without access to the app. We will verify ownership before processing the request; contact us if deletion or paid-rights restoration fails.
On Android, in-app deletion requires the parent account, parent PIN and Google reauthentication. For an iOS App Store-backed wallet without a linked Apple profile, deletion requires parent PIN approval and fresh wallet-ownership verification. If an Apple profile is linked, Apple confirmation and revocation of that sign-in permission happen before the deletion request is sent; Store-backed wallets also verify ownership with the App Store. Older Apple sign-in accounts use their existing Apple-confirmed deletion flow. Once accepted, the account or wallet is frozen for account, purchase and exchange actions, and a server process removes the Firebase Authentication user, linked Buddyzz profiles, old account and wallet records and associated ordinary data, including active purchase and entitlement records. The old account is not reopened. Deletion is not a refund, does not delete your Google or Apple account and does not delete store-held transaction data.
For in-app deletion, the app clears the parent PIN, downloaded books, partial downloads, caches, read-news markers, local preferences and the local book-encryption key from the device where deletion was requested. Copies on other devices or in system backups are not removed by this device’s local cleanup. If cleanup fails, follow the app’s instructions or contact support; you can also clear app data through the operating system. An email deletion request does not remotely delete files from your device; for local cleanup, remove the app’s data or the app using the operating system.
After deletion, limited evidence of paid purchases, unused paid scarf balance and valid book access is retained separately. It includes purchase identifiers and secure identity bindings, including keyed identifiers derived from the App Store wallet identity on iOS or provider identity on Android. It supports ownership checks, prevention of duplicate restoration, refunds and restoration of valid rights. Necessary closure and anti-reuse markers are retained; the Store-backed recovery anchor does not permit reopening the deleted account. This is not a full copy of the old account.
Purchased scarves do not expire because of time, inactivity or account deletion. On Android, after deletion completes, sign in with the same Google identity and use Parent Area → Parent Account → Restore Paid Purchases, with additional Google verification. On iOS, ordinary reinstallation recovery uses the same verified App Store identity to reconnect the existing wallet and recorded rights; it does not require parent Sign in with Apple. After actual account or wallet deletion, explicitly request restoration in Parent Profile: ownership and retained purchase evidence are verified before rights are restored to a new account lifetime. Only unused paid scarves and still-valid book rights are restored, once; an exchanged scarf returns as book access rather than an additional scarf. Refunded or revoked rights and free promotional scarves are excluded. Contact support if recovery fails before buying again.
On iOS, restoration may be partial when the store cannot currently verify every retained purchase. Verified paid scarves and book rights can become available while the remaining rights stay unrestored and grant no balance or access. Use Restore Paid Rights in Parent Profile again later to retry those rights. Repeating restoration does not add rights that were already restored a second time. Refunded or revoked rights remain excluded.
Purchase evidence and markers that prevent duplicate use are retained separately after account deletion to restore valid rights, handle refunds and prevent fraud. As of the last update, these records have no fixed automatic deletion date; there is no automatic deletion after 30 days and paid rights do not expire with the passage of time. After identity verification, you can contact us to request a review or deletion of remaining information; we will assess the request against the information needed to preserve rights, prevent duplicate use and meet applicable obligations, and explain which records need to be retained and why.
Anonymous technical authentication does not mean that a wallet lacks an owner. A technical Firebase user or keyed recovery identifier may remain associated with a wallet or retained paid rights even when the balance is zero or an optional Apple profile is unlinked. Unlinking that profile or uninstalling the app does not request deletion of these records.
Planned temporary-account cleanup — not active in the public service as of this policy date: temporary anonymous Firebase Authentication accounts are intended to be checked on the 15th of each month, Israel time, once they are at least 30 days old. Only accounts with no associated wallet, parent profile, paid purchase, book right or retained recovery association are eligible. A zero scarf balance does not make a wallet owner eligible. This cleanup does not expire paid rights or replace the deletion-request options above.
Deleting an account on one platform does not delete the separate account on the other platform. A request concerning both accounts must explicitly specify Android and iOS; ownership of each account will be verified separately. Signing out or uninstalling the app is not a request to delete server data and is not a refund.
Removal from the active account does not necessarily mean immediate deletion from every backup and recovery copy. Database recovery versions may be retained within a recovery window of up to seven days. Service providers may retain additional backup copies and security records according to their retention policies. This information is separate from active account records and the limited purchase evidence retained to restore valid rights.
Firebase describes removal of Firebase Authentication data from its active systems and backups within 180 days after a user is deleted. This does not give a deleted Buddyzz account an additional period of activity, and does not impose a time limit on valid purchase rights. Service providers’ policies also contain information about their data retention.
Parent rights and policy changes
A parent can contact us with questions about information linked to their account, to request access to it, to correct inaccurate information or to request deletion, in accordance with applicable law. Do not email a password, parent PIN, purchase token or card details. The deletion process and its effects are explained on the deletion page linked below.
We will update the policy date when the service’s operation or handling of information changes. Material changes will be brought to users’ attention in an appropriate way, and additional consent will be requested when required; a policy update alone does not remove rights already lawfully granted.
Account and data deletion
You can request deletion of an account and its associated data from the Parent Area, or by email even without access to the app, after ownership verification. The deletion process removes the account and its ordinary data from active systems, while retaining limited evidence of valid purchase rights and preventing duplicate use separately. Recovery copies and service-provider data may be deleted according to the timeframes described above. Instructions for submitting a request are available here: Delete your Buddyzz account.
Firebase privacy and data-retention information
Contact us
For questions about the service, privacy or account-related requests, email us: ayala@buddyzz.com.