Privacy notice

1. Two separate places for progress

Device mode and account mode store progress differently. Choosing a device learner does not sign you into KEYBAKI. Signing into KEYBAKI never merges a device learner’s records on its own. After signing in on a computer that has device learners, the learner may choose their own device profile, once, to move its progress into their account; that profile is then removed from the computer.

This draft describes the Labs application code and controls. It is not a complete inventory of production hosting, access logs, backups or external providers. Those deployment details still need owner confirmation.

2. Learning on this device

Device mode saves learner names or nicknames, preferences, activity progress, practice results and skill-check records in browser storage. The selected learner and those records are available to other people who use the same browser profile.

The app can also cache its pages, learning files and media for offline use. Browser storage and cached files can be removed by browser settings, device cleanup or private-browsing behaviour.

A backup downloads learner records to a file you control. Restoring a backup adds or merges its records into device learning storage. Downloading or removing a learner in the app does not delete copies of backup files you saved elsewhere.

3. Learning with a KEYBAKI account

KEYBAKI handles account sign-in and checks whether the signed-in user may access Labs. The handoff gives Labs a canonical account identifier, display name, access context and session information. Labs does not ask for your password, PIN or verification code.

When connected, Labs stores the account learner’s preferences, progress and results on its server, separated by account and access context. It also records activity needed for account-data housekeeping. The browser holds account work in memory while the page is open instead of putting it into the device learner store.

Account pages require a current session and an online connection. If authorization changes or the connection fails, the workspace can lock and unsaved changes can be lost. A school or family relationship does not by itself give another browser user access to these records.

4. Sessions, cookies and supporting features

Labs uses session cookies to recognise account sessions and to connect a sign-in return to the browser that started it. The account cookies are designed to be inaccessible to page scripts; production cookies require a secure connection. The reusable server-side grant is not stored in a browser URL or browser storage.

Short-lived browser session-storage markers remember choices such as device mode and the activity to return to. Device mode uses persistent browser storage for learner records and preferences. Public pages do not require choosing a learner.

Narration can use prerecorded clips and the browser’s speech-synthesis voices. Voice availability and handling depend on the browser and selected voice. This draft does not promise that every voice operates offline. The landing-page welcome is played only on request and selects an installed local voice; it never asks for microphone access. Its written transcript is always available.

Separate school or service integrations may exchange records under their own authorised configuration. Signing into Labs does not itself enable every integration or import a school roster.

Anonymous usage counts: to see how the lab is used, the browser sends KEYBAKI’s statistics service (cbe-api.keybaki.com, shared with KEYBAKI’s CBE Challenge game) short events such as which section of the lab was opened, that an activity was started or finished (its learning area and Show me, Guide me or Let me try), that a skill check was passed or not yet, a tour with Tcha, a share and the channel chosen, whether the visitor was signed in, the kind of device (phone, tablet or computer) and the site the visit came from (its domain only). The service adds the country of the connection and keeps only daily totals. No account identifier, name, progress, typed text, answers or full web address is sent, and the connection address is not kept with the counts.

While the lab is open, the browser also sends a random number made for that visit about once a minute, so the service can count how many people have the lab open. It is not stored in the browser, not linked to anything else, and deleted about 90 seconds after the last one; only the highest number in each hour is kept. Counts are not sent when the browser asks sites not to track (Do Not Track), or when they are switched off for this browser.

5. Your controls and requests

• For device learners: choose or switch the learner, change the displayed name, download a backup, and use the available remove-learner control. Browser settings can clear the site’s local data; this may remove every learner stored in that browser, so back up anything you need first.
• Usage counts: switch them off for this browser in Settings (Privacy) or with the button at the end of this notice; events not yet sent are then discarded. The browser’s Do Not Track setting also stops them.
• For account learning: use account controls to retry saving or sign out. Signing out ends access from that Labs session; it does not erase previously saved server progress. Sign out of the parent KEYBAKI service too on a shared computer.
• To ask about access, correction, export or deletion of account learning records, contact the KEYBAKI data-protection contact below and identify Digital Labs explicitly. The required identity verification and request workflow need confirmation for this standalone service.
• Do not assume deleting a KEYBAKI account immediately erases every Labs record or backup. The cross-service deletion process and backup lifecycle must be confirmed before a final policy makes that promise.

6. Children and shared learning

A nickname in a device learner profile is not a verified child account or a record of guardian consent. Adults supporting learners should explain who can see the shared browser’s profiles and help them avoid entering sensitive personal information into practice activities.

KEYBAKI manages account registration and guardian-approval flows. The owner must confirm how those approvals cover standalone Labs and how schools, parents and guardians can make requests for a learner. No new approval or consent is collected by these draft pages.

7. Retention and operational details to confirm

The implementation expires sign-in transactions and account sessions and includes account-data erasure and inactivity housekeeping. An expired session is not the same as deletion of saved learning progress.

This draft intentionally makes no promise about retention durations, backup expiry, hosting countries, specific subprocessors, legal bases or response deadlines. The owner must verify deployed configuration and operations, complete the data inventory and approve the final policy before publication.

Changes to these draft pages do not change the parent KEYBAKI consent records. A final policy still needs an approved version, effective date and any required notice or acceptance process.

Questions and requests

The parent KEYBAKI legal documents identify WEBFLEG SOLUTIONS LTD, P.O. Box 8138-00300, Nairobi, Kenya, as the operator. They list hello@keybaki.com for general questions and dpo@keybaki.com for data-protection requests. The owner must confirm that these details also cover standalone Digital Labs before this draft is published.

For a request about Labs records, say whether you used a device learner or a KEYBAKI account. Never send a password, PIN, verification code or session link.

Read the parent KEYBAKI Terms (opens in a new tab) and KEYBAKI Privacy Policy (opens in a new tab). This Labs draft does not resolve or replace those documents.