TAKI
Get Started

Everything a class produces, in one place

Six areas of the product, on the two surfaces a school actually uses: a phone in the classroom and a browser in the office. Every screen below is a sample, with no real class appears on this site.

Six areas, one set of records

Everything a teacher enters in the classroom is the same data an administrator opens in the browser. Pick an area to see what it looks like.

Mobile app

One tap per student, then it is done

Mark the roster during class. The summary updates as you go, and the record is written to the device immediately.

One row per class, per student, per day. The class teacher is the single writer, which is what makes last-write-wins safe when two devices sync out of order.

Never “the system flagged this student”

An indicator that cannot be checked cannot be argued with, and a teacher who cannot argue with it will stop believing it. TAKI shows the arithmetic.

The rule
Three rules, deterministic and countable: consecutive absences above 3, an absence rate above 15%, and a quarterly grade below 75.
The numbers
Every indicator records what was observed beside what the threshold was: 4 consecutive absences against 3, 22% absent against 15%. Never a score with no derivation.
The threshold
Resolved in a fixed order: a class override first, then the school default an administrator set, then TAKI’s. A school that knows its own context can move the line.
The boundary
No student record is sent to a third-party AI service. The rules run against the school’s own data, which is also why the reasoning can be printed at all.

The thresholds, their resolution order and the settings screen that configures them exist today. The nightly engine that evaluates them is still being built. TAKI has not raised an at-risk flag for anyone, and this page does not pretend otherwise.

What TAKI does with a child’s record

This product holds minors’ academic data, and the Philippine Data Privacy Act applies to every row of it. These are properties of the system, not promises about it.

Offline-first by design

Records can be created with no connectivity at all. A lost signal delays a sync; it never blocks a class.

Session expiry gates syncing and never blocks local capture.

Authorization in the database

Every table is default-deny and every query is filtered by policy, so a forgotten check hides data instead of exposing it.

20 tables, 56 policies, row-level security enabled on all of them.

Explainable monitoring

An indicator records the numbers that produced it. Copy says "5 consecutive absences against a threshold of 3", never "the algorithm flagged".

Rule-based and deterministic, so it can be explained to a parent.

No student data sent to AI services

Nothing about a student leaves the system for a third-party model. The early-warning rules run against the school’s own records.

A design constraint, not a configuration option.

Consent is a column

A guardian contact carries the date consent was given and whether it was withdrawn. Messages are not sent to a contact without it.

Required by RA 10173 and by the NTC rules on unsolicited messages.

Records are never hard-deleted

Removing something marks it removed, so a phone that was offline when it happened still learns about it on the next sync.

A vanished row cannot be reported to a device that was not listening.

TAKI claims no certification, audit or accreditation, because it holds none. What it can show is the code: read the privacy notice for what is collected and why.

Designed to fit the academic workflow

How a record travels from the room it was made in to the browser it is reviewed in, including what happens when the signal is gone.

See how TAKI works

Set up your school
in an afternoon.

Create the administrator account, add your grade levels, sections and subjects, and hand your teachers the join code. The portal is live today.

Get StartedSign In

Signing up creates an administrator account. Teachers are given the TAKI mobile app and join with a code.