> trust --plain-language

Trust

AI and Digital Literacy runs lessons for children, so trust is a precondition, not a feature. This page says what the platform holds, where it lives, who can see it, and how it leaves. The same statements, in fuller form, are in the Data Retention Policy and the Data Processing Agreement that accompany a school’s licence.

Where data lives

Every school’s data lives in a PostgreSQL database hosted by Supabase in ap-south-1 (Mumbai), and the application runs in Mumbai too. Connections to the database travel over TLS verified against a pinned certificate authority. Inside the database, row-level security is forced per school: no school can read another school’s rows, and that rule is enforced by the database itself, not merely by the application in front of it.

During a lesson the platform is offline-first. Marks are recorded on the teacher’s device and held there until they sync, so teaching carries on when the connection does not.

What we hold about a child

Below Grade 9 a pupil has no account: no email address, no password, no photograph. A pupil joins a lesson by typing a six-digit room code from the board — the code is the whole sign-in.

The roster holds the pupil’s name as the school wrote it, an optional school reference, an optional access note, and the dates of enrolment. That is the complete list. Beside it sit the assessment records the school’s own staff create: observations against the curriculum’s rubrics, any amendment recorded with its reason.

School data is processed only to operate the platform for the school — never for advertising, profiling, or model training.

Who can see what

Staff sign in with a school email and a password stored only as a scrypt hash — never in a readable form — and two-factor authentication is available to every staff account.

Within a school, roles decide reach: exporting the school’s data, for instance, is held by the School Leader and School Administrator roles. Across schools there is no reach at all — the database’s row-level security sees to that.

Skill2Success itself touches a school’s data only for support, and each access is time-boxed, carries a stated reason, and is audited — with the school’s administrator able to see that it happened.

The audit trail

An append-only trail records every access-relevant action: who, what, when, and — where the platform demands one — why. Entries are added, never edited or removed, and the trail is retained for six years as the defensibility record behind marks and access.

The trail references pupils by roster id rather than by name, so when a roster is deleted the trail keeps its shape but loses the child.

Protecting the curriculum

The curriculum is Skill2Success’s licensed property, and the platform treats it that way. Staff read curriculum documents through a view-only reader carrying a Skill2Success watermark; the original files never leave Skill2Success.

The curriculum is licensed, not sold, and is never part of a school’s export.

Backups and deletion

Roster and assessment records are held for the licensed academic year plus one further academic year — so a September report can look back at July — and are then deleted.

If a licence ends without renewal, the school receives its full export, and school data is deleted 90 days after the licence’s final day; a signed request from the school’s administrator shortens that to as soon as practicable.

Backups follow the host’s schedule, and deleted data leaves the backups as the backup window rolls over — at most 30 days behind live deletion.

Your rights: export and deletion

A school can take out everything it put in — roster, assessment records, documents — as one JSON document, at any time. The export asks for a stated reason and writes itself to the audit trail.

A parent’s deletion request goes to the school; the school’s administrator raises it with Skill2Success. The request and its execution are both audited actions, and deletion follows the retention windows above.

The full detail is in the Data Retention Policy that accompanies a school’s licence agreement.

Accessibility commitment

The platform is built for a bright lab, a phone held in one hand, and every pair of hands in the room: no interactive target smaller than 44 pixels, every control operable from the keyboard with a clearly visible focus ring, and reduced-motion preferences honoured throughout — the design works static.

If anything here puts a barrier in your way, report it to aivico.dev@gmail.com and it becomes our bug to fix.

Contact

Data questions go to aivico.dev@gmail.com (Skill2Success). Parents should start with their school’s named administrator — the first contact for data requests, who can raise anything with us.