Inside the desktop app
Student, guardian, staff, fee and assessment records are stored in the installation’s local SQLite database. The current app does not automatically upload that database to this website or provide cloud synchronisation. If your school uses a shared host, staff browsers access that host over the configured school network.
Access is controlled by application accounts, roles and campuses. This does not replace Windows account permissions, device encryption or the security of the host computer. Someone with administrator access to the computer may be able to read its files.
Licensed release activation
The licensed release contacts the shared Keystone service for initial activation and computer replacement. It sends the CampusNivo activation key, a locally hashed computer identifier, a computer label and replacement details when requested. The service also handles software purchase references and buyer contact details. It does not receive school student, fee, payroll or result records. A saved signed certificate enables normal offline operation.
Your backup copies
Portable .schoolbackup exports are encrypted with your chosen passphrase. The application does not store or recover that passphrase. The live database and raw automatic snapshots are not encrypted by the app. Protect the computer and backup device, and keep recovery keys separately.
You choose where backup copies go and who can access them. This website does not accept school database uploads.
On this website
This website provides product information, documentation and a Windows download. Its purchase and recovery pages use an HttpOnly purchase cookie and store software-buyer details, order/payment references, a hashed private recovery key and an encrypted activation code. Checkout is currently closed. It has no advertising integration or application-added analytics cookies. Copy buttons use your browser’s clipboard only when you press them.
The hosting provider may process technical request information such as IP addresses, browser information and access logs to deliver and protect the site. Where access requires sign-in, the hosting platform also handles that authentication. These hosting functions are separate from the local school database.
Product screenshots show fictional demonstration records. They do not show real students or school customer data.
When asking for help
Share the app version and a description of the problem. Remove student details from screenshots and never send passwords, backup passphrases or an unredacted database. For the pilot, use the contact who provided the software to your school; a public support contact has not yet been announced.
This page describes the implemented pilot as of 5 October 2026. It is not a claim of regulatory certification or a promise of zero data loss.