School readiness
A working alpha with a clear evidence boundary. Japanily is not yet school-production approved.
Last updated 4 October 2026
Do not introduce a production cohort until your school and the service owner have approved the required evidence. This is review preparation, not a contract, certification or permission to upload student information.
Public facts reviewed · this application release 29731b44. Check current service health; a healthy server does not mean all launch gates are met.
Implemented software, with limits
Private classroom access
Approved teacher roles, class ownership and learner membership constrain classroom records. Explicitly authorised observation reviewers receive only the scoped review material.
Practice and assessment boundaries
Server-validated practice results, private attempt history and teacher observations support feedback. Completion, supported practice and learner self-report are distinct; none alone proves mastery.
Data choices
Account export, reviewed single-learner report preparation, deletion requests and guarded operator workflows are implemented. Export limits, school retention decisions and operator fulfilment still apply.
Shared-device controls
Shared/personal cookie choices, current/all-device sign-out and selective cross-tab recovery cleanup are implemented. Browser restoration and already issued access tokens have limits: sign out and follow school device-clearing instructions.
Temporary guest quizzes
Separate untimed quizzes use private invitations, generated labels, teacher admission and one-hour room access. No learner Auth accounts, private classroom access or permanent rewards. Host end deletes room data; hourly expiry cleanup can be delayed by service outages. Genuine school/device acceptance remains required.
Public versus private content
Public news, polls, quizzes and reviewed learning previews sit outside the private classroom. There is no public student directory or direct messaging. Reader submissions enter a moderation queue; submission does not publish them.
Release checks
Build, database replay, isolation, browser, accessibility and hosted checks gate releases. Automated checks are not an independent penetration test, accessibility certification or school approval.
Outstanding evidence and decisions
All 14 categories below need evidence or a named decision. “Not recorded” means this public preparation record does not establish acceptance. It is not a percentage score or an assertion that a school has failed.
School identity and sign-in — evidence not recorded
Suggested responsible role: School ICT and service owner
Choose permitted accounts, teacher verification, learner recovery and retention. Supply approved provider configuration and witness real allowed/denied sign-in, recovery and shared-device tests.
Hosted authentication protection — evidence not recorded
Suggested responsible role: Service owner and school ICT
Confirm password rules, breached-password protection, abuse controls, rate limits, administrator MFA and the selected plan. Do not treat a client password field as proof of hosted policy.
Backup and witnessed restore — evidence not recorded
Suggested responsible role: Service owner and independent witness
Approve backup/PITR coverage and retention, an isolated restore target, recovery objectives and a witnessed drill. Migration replay alone does not recover production data.
Retention and deletion operations — evidence not recorded
Suggested responsible role: School privacy lead and service operator
Approve record-specific periods, deletion exceptions and operator authority. Schedule and witness the approved cleanup; test account export and deletion without real student test data.
Privacy, school terms and subprocessors — evidence not recorded
Suggested responsible role: School procurement and qualified privacy/legal reviewers
Review notices, child-facing explanations, school agreement and processor terms; confirm actual provider locations, logs, cross-border processing and contractual obligations. No legal approval is recorded here.
Independent security and release review — evidence not recorded
Suggested responsible role: Qualified security reviewer and service owner
Review current advisor findings, privileged endpoints, tenant isolation, secrets, branch/release controls and dependencies. Supply authorised penetration-test scope, findings and verified remediation.
Independent accessibility acceptance — evidence not recorded
Suggested responsible role: Accessibility reviewer and school inclusion lead
Test assistive technology, keyboard, zoom, touch, forced colours, timing and alternatives with representative learners/devices. Automated axe results are supporting evidence, not certification.
Qualified curriculum and Japanese review — evidence not recorded
Suggested responsible role: Qualified educators and Japanese-language reviewers
Review exact versions of both sequences for language, culture, age, alignment, assessment and differentiation. All 120 units / 600 lessons remain drafts until genuine scoped review evidence supports a different state.
Authorised professional media — evidence not recorded
Suggested responsible role: Rights holder, language reviewer and service owner
Supply genuine recordings, contributor consent/licences, transcripts/captions and qualified reviews. Production briefs and browser speech are not professionally reviewed recordings; the real asset ledger is currently empty.
Assessment and family-report acceptance — evidence not recorded
Suggested responsible role: School assessment and privacy leads
Validate draft rubrics, moderation, interpretation of attempts and support, accessible family reports and approved recipient channels. Select any external integration before credentials or data sharing are introduced.
Named support and incident ownership — evidence not recorded
Suggested responsible role: Service owner and school contact
Name responsible people, escalation contacts, support hours and cover arrangements. Exercise the incident plan; public response targets are not a contracted SLA.
Authorised real-school pilot — evidence not recorded
Suggested responsible role: School ICT, teachers and inclusion lead
After entry approvals, witness classroom use on the actual school Wi-Fi and managed device mix. Test joins, live reconnects, learning, reports and accessible alternatives. Synthetic load tests do not replace this.
Commercial and procurement decisions — evidence not recorded
Suggested responsible role: Service owner and school procurement
Approve prices, trial conditions, invoices, service terms and payment provider before live charging. Record genuine pilot outcomes and permissions before publishing customer claims or case studies.
Cohort launch authorisation — evidence not recorded
Suggested responsible role: Authorised school decision-maker and service owner
Review all evidence, unresolved conditions, scope, named owners and dates. Sign the actual rollout decision outside this checklist; downloading or filling a worksheet grants no access or approval.
Take a review pack to your school
The script-free print pack and JSON contain these same public facts, release identifier, outstanding gates and blank evidence fields. No private roster, internal incident, provider secret or school identity is included. Downloading or completing it does not change Japanily’s status.
Open the HTML file and use Print / Save as PDF. Keep completed evidence in your school-approved system; do not add learner details or credentials.
School network guide
Ask school ICT to review these exact destinations and protocols under its normal policy. Do not disable security filtering globally.
japanily.comandwww.japanily.com— HTTPS, port 443, application and first-party media delivery.wjqrrrszhyqawouhvxap.supabase.co— HTTPS and secure WebSockets, port 443, account/database and live updates.- First-party cookies and JavaScript are required for current account flows. QR codes are generated locally; recording is optional and asks for permission only when selected.
- School Google/Microsoft sign-in, email delivery and provider redirects need separate approved configuration and real-device tests. A provider button or this guide does not establish school SSO support.
Check this device’s basic connection
Run on the intended school Wi-Fi. Two read-only requests go to Japanily and its existing Supabase project, without account cookies or tokens. Providers still receive ordinary request metadata such as an IP address. Results stay on this page and are not saved or sent to a support inbox.
Connection checks need JavaScript. The network guide and review pack still work.
No checks run yet.
Reachable is not school approval. These checks do not test sign-in, email delivery, WebSockets, live reconnects, microphone, accessibility or a whole classroom’s load. Complete the supervised pilot before relying on the service.
People, privacy and next steps
Supabase hosts the application database in Sydney; Netlify hosting/CDN and provider operations may involve other locations. Do not interpret the database region as an Australia-only processing guarantee. Confirm current plans, logs, retention, subprocessors and signed terms in procurement review.
Read the privacy notice, child-safety information, accessibility limitations, student access guide and service terms. Request current evidence or report a concern through support. Do not email student records, passwords or active sign-in links.
You can explore lessons without an account while approvals are being arranged. Genuine educator review, professional media, real school pilots and operational sign-off remain required; software checks cannot supply those approvals.