Security

Updated 23 October 2026

Akshar’s security model starts with not having a central database to breach.

No central server

School records never pass through a Teclusion AI server. There is no single database of many schools for an attacker to target.

Signed changes

Each device has its own signing key. Every batch of changes it writes to Drive is signed, and receiving devices verify the signature, the device’s grant and the person’s role before applying anything. Tampered files are rejected.

People and permissions

  • Individual profiles and PINs for every staff member.
  • Roles: Principal, Admin, Teacher and Accountant each see only what they need.
  • Approvals for sensitive actions such as fee reversals.
  • The Principal can revoke a lost or departed staff member’s device.

Shared responsibility

Google Drive sharing decides who can read the school folder, so share it only with staff. Use two-step verification on Google accounts and keep devices locked and updated.

Reporting a vulnerability

Found a security issue? Email sales@teclusion.ai with "Security" in the subject. Please give us reasonable time to fix it before disclosing it publicly. We do not take action against good-faith research.