Diese Hilfe gibt es auf Deutsch und Englisch.
Privacy, Security & Access
Student data deserves more than a promise — it needs protection you can follow. Mapidu does not store it in a remote cloud but encrypted on the device you control. When something is shared, further layers apply: a secured connection, proof of who sent, and a separate key for the content itself. Read the plain-language sections first; the blue-bordered boxes below are for school IT and technical staff.
Your device — multiple protection layers
Access, master key, database, and sync keys kept separate
1. Access — PIN or biometrics
Only you unlock the app. Without access, everything stays locked.
2. Master key
Stored encrypted — never in plain text on the device. Available only after you unlock.
3. Main database (SQLCipher)
Students, classes, grades, timetable — all AES-256 encrypted with the master key.
4. Communication key (Comm)
Separate key in the device secure store (Keychain). Signs messages — proves identity during exchange.
5. Data key
Second key pair: public part visible, private part encrypted in the DB with the master key.
6. Sync mailbox (separate)
Dedicated encrypted store for incoming sync messages — even while the app is still locked.
On first setup you decide who may open the app: PIN plus password or biometrics. Only then is the vault released. Your student data is not a readable file on the tablet but an encrypted database — without your unlock it stays opaque even if someone has the device in hand.
Underneath, Mapidu works with several separate keys. Think of a vault with different locks: the master key protects the local database. A communication key signs outgoing messages — like a seal on the envelope. And a data key seals the actual contents on top, whether you exchange via Wi‑Fi, file, or with a colleague.
What is protected locally
- Student records and photos
- Grades and participation (default: device where entered)
- Teaching projects, calendar, and tasks
- Teacher key and colleague contacts
When exchanging between devices or with colleagues, nothing leaves the app as plain text. First the devices negotiate a temporary session key — a shared lock for this connection only. Inside sits the message: signed with your communication key and content-sealed with the recipient's public data key.
The distinction matters: the communication key answers "Who sent this and was anything changed in transit?" The data key answers "Who may read the content?" — only the recipient, even if someone captures traffic or a relay is involved.
Data exchange — three layers of protection
Between two devices or colleagues — Mapidu never sees the contents
Device A
sends
Device B
receives
Connection encrypted (handshake → shared session key, ChaCha20-Poly1305)
Message signed — recipient verifies it really came from you (Ed25519)
Student & lesson data additionally encrypted with the recipient's public data key (X25519 + XChaCha20)
What Mapidu deliberately does not do
- No central cloud of class lists or grades
- No reading of sync contents by the operator
- No automatic upload — sync only when you start it
- No substitute for school privacy approvals — device and access code remain your responsibility
Limits — stated honestly
- Metadata (timing, device, network address) may be visible with Wi‑Fi or Mapidu assist
- Lost device: encryption helps — forced unlock remains a residual risk as everywhere