Ownership of every record is enforced in the database. One institution’s record cannot be linked to another’s, and even an application bug cannot return another school’s data. Automated tests check this rule.
Data security
A school management system holds some of the most sensitive data there is. In Aydora, security rules are enforced where the data lives, not just on screen.
Institution APartition A
Institution BPartition B
Institution CPartition C
Database: every record is bound to its institution
Aydora admin panel
totals onlyTeachers see their own lessons, deputy heads their own school, head office every campus. Parents see only their own children; students only themselves.
Changes to attendance, student and guardian details, permissions and announcements are recorded with who made them, when, and the previous value. The application cannot delete these records.
Absence entries, awards, disciplinary decisions, assessments and announcements are never deleted from the screen; they are cancelled or archived, with who and when kept on the record. The application has no permission to delete from these tables, so even an accidental delete is stopped by the database.
Health cards and infirmary records are special-category personal data, visible only to the nurse and authorised staff. Teachers see only the short note parents write for teachers, and every change is logged.
National ID numbers are stored encrypted and shown masked. Search uses a one-way hash, never the number itself.
Accounts are temporarily locked after repeated failed sign-ins. Passwords are stored in a form that cannot be reversed.
The panel we use to manage institutions runs with a separate database role that has no access to student, parent, attendance or payment tables; it sees only totals and administrator accounts. Our team signs in with a password and a code from their phone, and every action goes into a log that cannot be deleted.
Under Turkish data protection law your institution is the data controller; Aydora acts as a processor, only on your instructions.
Every connection between the web panel, the app and the server is encrypted with HTTPS.
The database and uploaded files are backed up every night, encrypted, to separate storage. Backups are kept for 30 days and then deleted automatically.
The same student list through five people’s eyes. Pick one; as the teacher, change a roll-call and see how the change is logged.
Students · Selin Güneş
3 / 6| Student | Today | Outstanding | |
|---|---|---|---|
| Alp Aydın · 10/A•••••••7730 | •••••••7730 | No access | |
| Efe Arslan · 10/A•••••••2964 | •••••••2964 | No access | |
| Mira Aksoy · 10/A•••••••5017 | •••••••5017 | No access |
3 students are never shown to this person; the server never sends those rows.
Change log
- Press a student’s status for today; the change lands here.
The application cannot delete these records.
The assistant opens no new door: it lets people do, by typing, what they can already do in the app, under the same rules.
- Limited to the person’s permissions
- The assistant fetches information the way the app’s own screens do, with the asking person’s session. It cannot see what they cannot, and never touches a module the institution has switched off.
- No action without confirmation
- Every job is first shown on a confirmation card with names. Unconfirmed jobs expire in 15 minutes, none can run twice, and nobody else can confirm it.
- Only the owner sees a conversation
- Neither the school office nor our team can read the questions; the admin panel shows only the number of questions per institution.
- Runs in Europe, never used for training
- The AI model runs on servers inside the European Union; questions and answers are never used to train it.
- Only if your institution turns it on
- The assistant starts switched off everywhere and is turned on only if your institution chooses it.
Let’s walk through our demo school together and prepare a quote for your size and the modules you choose.