Privacy & data use

What we collect

For signed-in use, we collect the adult account email and display name provided through Firebase Authentication. For each child profile, we store only the nickname entered by the adult and activity records such as answers, emotions selected, attempts, response times, timestamps, and session summaries.

For guest use, Firebase Authentication assigns a random guest UID without asking for an email. After the responsible adult agrees, guest nicknames, profiles, and activity results are stored under that UID in Firestore. Existing browser progress is imported using its original activity IDs to avoid duplicate results. The browser keeps a local copy and queues results while offline.

Each full website load adds one to an aggregate Firebase visit count. We also assign this browser a random identifier (UUID) to count returning browsers once. Firebase stores that identifier and its first registration time, plus an aggregate unique-browser count. Neither traffic counter is linked to an account, child nickname, or activity answers. A different browser, private browsing session, or clearing site data may count as another visitor.

Do not enter a child’s full legal name, diagnosis, school, address, date of birth, or contact details.

Why we use it

We use activity information to show progress reports and generate requested data exports. Signed-in information also supports saving across devices. The traffic counts help us understand how often the website is opened and how many browsers return. Reports describe educational patterns only and must not be treated as a diagnosis or medical advice.

Storage and sharing

Authentication is provided by Google Firebase. Guest and adult profiles, activity history, and browser traffic records are stored in Project Little Bridge’s Cloud Firestore database. The browser retains the guest sign-in credentials. Clearing browser data or losing the device may remove access to the guest account, even though its cloud records remain. We do not sell child or account data. Firebase processes cloud data as our service provider, and authorized Project Little Bridge administrators may access cloud data only when needed for security, support, or system maintenance.

Adult control

• Download a child’s complete activity history as an English or Thai CSV from Progress & History.
• Delete a child profile and all of its saved activity history from the account panel.
• Use Manage profile to delete a guest profile and its results, or Delete all guest profiles to remove all guest profiles and results from Firebase and this browser. Deletion needs an internet connection.
• Stop future activity collection by deleting the relevant data and not using tracked activities.

Guest and adult data remain online until deleted through the app or with help from Project Little Bridge. Clearing browser storage alone does not delete cloud records. The legacy local source is removed only after its upload is acknowledged; an updated browser copy remains. Guest and adult accounts are separate: signing in does not transfer guest results into an adult account. The separate random visitor identifier remains after deleting profiles to prevent duplicate traffic counts. Browser registration records are retained for counting repeat visits; clearing site data removes the identifier from your browser but does not remove an earlier registration from Firebase.