Branch boundaries
Users belong to a network and branch context so later academic, finance, and student records can be scoped safely.
Privacy
Student records deserve careful systems from day one.
Jibar School ERP stores the operational information needed to run a school network: accounts, branches, roles, billing records, payment state, demo requests, and audit history. Student data for later modules is designed to stay inside explicit tenant, branch, and permission boundaries.
Role checks
Permissions are evaluated against the active branch so staff only see the workflows they are trusted to operate.
Payment records
Paynow credentials stay with the provider. Jibar stores references, poll URLs, statuses, and redacted event payloads.
Audit trail
Security-sensitive actions create audit entries that support investigations and school accountability.
Legal
Operational Privacy Notes
Demo and contact submissions are used to respond to school rollout requests, understand branch seat needs, and plan onboarding. Operational logs may include IP address, user-agent, route, and timestamp metadata for support, abuse prevention, and security review.
Payment status is verified through Paynow poll URLs and result callbacks. We avoid storing payment provider secrets in public-facing records and redact payloads before they are shown to school administrators.
As the ERP expands into admissions, attendance, academics, LMS, finance, and parent workflows, each module should continue to follow the same network, branch, role, audit, and data-minimization principles.