Student information deserves heightened care. FobsSMS is designed around school-controlled access, role separation and the principle that people—not automated systems—remain responsible for educational decisions.
Roles and instructions
For school records, the school decides the purpose and authorized use, and FOBS acts as its service provider or processor. FOBS follows documented instructions, confidentiality commitments and the signed school agreement, except where law requires otherwise.
Access and least privilege
Accounts receive role- and school-specific permissions. Owners, academic staff, finance staff, teachers and parents are shown different information. Schools must review assignments, remove leavers promptly and avoid shared credentials. Administrative actions may be logged for accountability and investigation.
Technical and organizational safeguards
Safeguards include authentication controls, password hashing, encrypted network transport, tenant and school scoping, authorization checks, backups, logging, environment separation, updates and restricted operational access. Measures are reviewed in proportion to risk and service evolution.
Children and family information
The school must collect and disclose student and guardian information lawfully and provide required notices. Parents access only children properly linked to their account. Teachers and staff may use information only for authorized professional duties. FobsSMS does not sell or advertise against student records.
Artificial intelligence and human review
Where AI-assisted import, timetable or analytical features are used, outputs are suggestions or prepared data. An authorized person must review material results before they affect official records or decisions. School data is not made public merely because it is processed by an AI-assisted feature.
Incidents and continuity
We maintain response processes to investigate suspected loss, misuse or unauthorized access, limit harm, restore service and notify the responsible school or authorities when required. Schools should promptly report suspicious activity and maintain their own operational continuity procedures.
Requests, exports and end of service
FobsSMS supports reasonable access, correction, export and deletion workflows, subject to school authority, contractual scope, secure verification and retention duties. When a service ends, the school should arrange export within the agreed period; remaining copies are deleted or expire from backups under the applicable schedule.