What Kaku currently does with data.

Real learner information is not yet authorised

Do not enter or upload a real learner’s name, contact details, school identifier, goals, observations, evidence, session notes, or other personal information.

Use only information that cannot identify or be connected to a real learner, family, practitioner, school or case.

What the account product holds today

Kaku stores the information needed for verified adult accounts and organisation operations, including adult account details, memberships, invitations, product access, onboarding state, and minimised operational history. It also stores learner workflow records created within the current non-identifying-data boundary.

The pre-launch product has not completed a production deployment review or legal review for use with real learner information.

Current data controls

A verified adult can download their account profile, organisation memberships, and onboarding state from account data controls. An organisation owner or admin can download a bounded operational export containing organisation settings and adult operational records. They can also separately download one exact configured learner record as bounded JSON from that learner’s record or lifecycle page, or the minimized row history for one confirmed import from import history.

The organisation-wide export excludes learner records, rosters, goals, evidence, sessions, and methodology content. The separate learner download includes the selected learner’s IIPs, rubrics and immutable artifact versions, and excludes peer learner content. Import history contains only row numbers, finite outcomes, created record identifiers, booleans, counts, and timestamps—never uploaded cells, source references, filenames, or file hashes. An issued learner or import-history download prevents automatic deletion of every learner included in that copy because Kaku cannot recall the delivered file. These signed-in controls are not parent self-service or a verified public rights-request workflow.

Important protections are still unfinished

Kaku has not yet built the persistent encrypted identity store or application-level field protection required for real learner identities. A storage provider protecting its own disks is not a substitute for those product controls, and this page does not claim that it is.

Deactivation is not deletion

Account deactivation closes sign-in access and suspends active organisation memberships. Account, membership, and operational records may remain to preserve access history, security, and system integrity.

There is not yet a public or parent-facing route for requesting deletion of a learner record. An authenticated owner or administrator can delete an eligible archived learner from the configured live database, including exact learner-owned approved reports, individual-session history, and one-learner ungrouped import history. Multi-learner or grouped imports, group history, ambiguous or under-indexed aggregates, and other shared-history cases are refused, and retained backups are not covered. Kaku also does not yet provide organisation closure, automatic retention execution, or backup-aware re-purge. Those missing controls remain among the reasons Kaku is not ready for real learner use.

Questions and help

Self-serve account, invitation, recovery, and data-control guidance is available on the support page. Direct staffed support and a public support contact are not yet activated, so Kaku does not publish a support address or response-time promise.