Wise Kids Academy (“WiseKids”, “we”, “us” or “our”) is an educational reading and learning service for families, teachers, schools and children. We take privacy particularly seriously where children are involved. This Privacy Policy explains what personal information we use, why we use it, how it is protected, how long we keep it and the choices and rights available to users.
Wise Kids Academy is operated by Daniel Bruno Dewes, trading as Wise Kids Academy, Brestenbergstr 14, 79211 Denzlingen, Baden-Württemberg, Germany. Email: hello@wisekids.academy.
For family accounts and the general operation of WiseKids, Daniel Bruno Dewes trading as Wise Kids Academy is the data controller. Where WiseKids is provided to pupils through a school, the school will generally act as controller for the pupil information it chooses to process through WiseKids, and WiseKids will generally process that information on the school’s behalf. The precise roles may be set out in an agreement with the school.
WiseKids may be used by parents and other adult family-account holders, teachers and authorised school staff, children using family child profiles, pupils using school-controlled access, and visitors who use parts of the service without signing in.
Children are not expected to create adult accounts or provide their own email addresses. School pupil access is intended to be managed by the relevant school or teacher.
When an adult creates or uses a WiseKids account, we may process information including email address, WiseKids/Supabase user identifier, account role and access information, device-access information used to help protect accounts, account creation and activity timestamps, and information required to manage the account and subscription.
Authentication is provided through Supabase. Passwords are submitted to Supabase Authentication. WiseKids does not store readable copies of user passwords in its normal application database.
An adult family-account holder may create child profiles. Depending on use of the service, WiseKids may process the child profile display name, the link between the child profile and the adult account, stories opened or completed, reading progress, quiz completion information, quiz attempts and scores, and relevant activity timestamps.
WiseKids currently supports up to five active child profiles per family account. We aim to minimise identifying information about children.
Where WiseKids is used through a school, we may process pupil display name, class membership, story progress, quiz attempts and scores, relevant activity timestamps, and technical pupil-access/session information.
Schools should use a pupil’s first name only wherever reasonably possible and should avoid entering unnecessary identifying information. Pupil PINs, class access codes and pupil-session tokens are stored in hashed form rather than as readable credentials.
WiseKids may process information relating to authorised teachers and schools, including teacher account information, classes, pupil membership of classes, class settings, story-completion information and other settings required to provide the school service.
Family subscriptions are processed using Stripe. WiseKids may store the WiseKids account associated with the subscription, Stripe customer identifier, Stripe subscription identifier, subscription plan, subscription status, current billing-period dates and cancellation status.
Payment-card information is handled by Stripe. We have not identified full payment-card numbers being stored in the WiseKids database. Stripe may retain payment and transaction information independently where it is required to do so for legal, regulatory, fraud-prevention or accounting purposes.
WiseKids uses Brevo for certain necessary service emails, including subscription-related messages such as trial reminders. Brevo may receive an adult account email address and the information needed to deliver the relevant message. The current trial-reminder system does not send child progress, quiz scores or other learner records to Brevo.
Depending on how WiseKids is used, locally stored information may include guest story progress, recently opened stories, favourite stories, saved life lessons, the currently selected family child profile, and cached child progress information.
Guest/browser information may remain on that device until the user clears the browser or app data. Guest data is separate from cloud-based information associated with a signed-in WiseKids family account.
WiseKids does not currently rely on behavioural advertising trackers, marketing pixels or session-recording systems for the child-facing service.
We use personal information where necessary to operate WiseKids, provide accounts and child profiles, save learning progress, provide teachers and parents with authorised information, manage school access, manage subscriptions and billing, protect accounts and the service, troubleshoot technical problems, send necessary service communications, provide support and meet applicable legal obligations.
We do not use children’s learning records for behavioural advertising. We do not use AI to make important automated decisions about individual children.
For adult account information needed to provide a WiseKids family subscription or account, we generally process the information because it is necessary to provide the service requested by the adult.
For security, fraud prevention, device management, service reliability and appropriate operation of the service, we may rely on our legitimate interests, balanced against the rights and interests of users.
For child-profile and learning information associated with a family account, we aim to process only information reasonably necessary to provide and protect the educational service requested by the adult responsible for the account. Where legitimate interests are relied upon, the additional interests and rights of children must be taken into account.
Where information must be retained or processed to meet legal, tax or accounting obligations, we may process it because the law requires us to do so. Where WiseKids processes pupil information for a school as a processor, the school is generally responsible for identifying the lawful basis applicable to its use of pupil information.
WiseKids uses the OpenAI API to help generate educational and story-related content. We aim to send only the minimum information needed for those generation tasks. The current system is designed so that ordinary educational-content generation does not require sending child names, individual quiz scores, detailed learner progress or other unnecessary pupil information to OpenAI.
OpenAI is not used to make important decisions about individual children.
Cloudflare R2 is used for public WiseKids story artwork and audio. The current R2 upload system is restricted to artwork and audio and is not intended for private pupil information.
WiseKids currently relies on Supabase for authentication and cloud database services, Render for hosting, Stripe for family subscription and payment processing, Brevo for transactional email delivery, OpenAI for educational and story-related AI generation, and Cloudflare R2 for story artwork and audio storage and delivery.
WiseKids’s current main Supabase project is hosted in the EU West region in Ireland. The current WiseKids Render service is hosted in Oregon, United States. Other providers may use infrastructure or subprocessors in more than one country.
Some providers used by WiseKids may process personal information outside Germany or the European Economic Area. Where European data-protection law requires additional safeguards for international transfers, WiseKids relies on the contractual and transfer mechanisms made available by the relevant provider, such as European Commission Standard Contractual Clauses or an applicable adequacy mechanism.
School pupils: While a school pilot is active, pupil profiles, progress, quiz attempts and associated pupil-access information may be retained while the school is actively using WiseKids. When a school pilot ends, WiseKids will delete the relevant pupil profiles, progress, quiz attempts and related pupil-access records within 30 days, unless the school explicitly agrees to continue using the service.
Family child profiles: Archiving a family child profile means its profile, progress and quiz history are retained so that the profile can be restored. Our confirmed privacy rule is that permanent deletion of a child profile should also permanently delete that child’s associated progress and quiz attempts. A dedicated self-service permanent child-profile deletion facility should not be assumed to exist until it has been separately implemented.
Family adult accounts: When an adult successfully permanently deletes their WiseKids account, associated WiseKids-side family child profiles, progress, quiz attempts, device records and account/billing mappings are designed to be deleted through the account-deletion process and database relationships. WiseKids currently prevents an adult account from being deleted while its family subscription remains active, trialling or past due. Automatic Stripe cancellation as part of the account-deletion action is not currently implemented.
Teacher and school data: Teacher accounts, class information and school configuration may be retained while the teacher or school relationship remains active. When that relationship ends, information that is no longer required should be deleted or anonymised, except where retention is reasonably necessary for legal, accounting, security or dispute-handling purposes.
Operational logs: Operational/server logs are retained only for a proportionate period required for troubleshooting, security and service reliability.
WiseKids is designed around adult-managed, parent-managed, teacher-managed or school-controlled access. We aim to collect as little child information as reasonably necessary, provide high privacy protections by default, limit access to authorised adults and teachers, avoid unnecessary behavioural tracking, avoid unnecessary collection of photographs, voice recordings and personal files, and explain privacy to children in language they can understand.
A separate short child-friendly privacy explanation is available.
For family accounts, child-profile information is intended to be accessible only to the signed-in adult account responsible for that profile. For school use, authorised teachers are restricted to pupils associated with their classes. Trusted WiseKids administrators may access information when reasonably necessary for support, troubleshooting, security or data management.
WiseKids uses safeguards including authentication through Supabase, database row-level security, server-side teacher-authorisation checks, hashed pupil PINs and access credentials, restricted administrative operations, separation of public story media from private learner information, and controlled deletion mechanisms.
No online service can guarantee absolute security. A currently known security limitation is that Supabase’s leaked-password protection feature is not available on the project’s current Free plan. This is a known hardening item for wider production and school rollout and is not evidence that a security breach has occurred.
Depending on the circumstances and applicable law, you may have rights including access, correction, deletion, restriction, objection, portability and withdrawal of consent where processing specifically relies on consent. We may need to verify your identity or authority before responding to a request.
Requests can be sent to hello@wisekids.academy.
If you have concerns about how Wise Kids Academy handles personal information, please contact us first at hello@wisekids.academy.
You also have the right to complain to an appropriate data-protection supervisory authority. For Wise Kids Academy’s operations in Germany, the relevant supervisory authority is Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg (LfDI BW), Heilbronner Straße 35, 70191 Stuttgart, Germany.
Where WiseKids processes pupil information for a school, additional contractual arrangements may apply. WiseKids intends to provide schools with a Data Processing Agreement covering relevant controller and processor responsibilities, security, subprocessors, transfers, retention and deletion.
We may update this Privacy Policy when WiseKids changes, when providers or processing arrangements change, or where legal and regulatory requirements develop. When material changes are made, we will update the date shown at the top.
Daniel Bruno Dewes
trading as Wise Kids Academy
Brestenbergstr 14
79211 Denzlingen
Baden-Württemberg
Germany
hello@wisekids.academy