Trust

Data processing agreement draft

Effective date: 24 September 2026 ยท Version 1.0

1. Parties and roles

The institution is the controller and EGEROBOT is the processor. EGEROBOT processes personal data only on the institution's documented instructions.

2. Subject matter and duration

The subject matter of the processing is the evaluation of access data from the institution's gates and the live presence, attendance, notification and emergency functions based on that data. The duration of processing is the term of the contract.

3. Categories of data

Identity data, access event records, class and guardian relationships, contact details and application usage logs.

Data subject groups: students, guardians, staff, visitors and contractor personnel.

4. Prohibition of biometric data

The parties agree that no biometric data is processed in any version. The data schema has no such field, the API rejects it and the adapter strips it out.

5. Security measures

Data is encrypted in transit and at rest, access is role-based, administrative actions are written to an immutable audit trail and card numbers are transmitted as an institution-specific salted hash.

6. Sub-processors

If a sub-processor is to be used, the institution is notified in advance, and the sub-processor is bound by the same obligations.

7. Assisting with data subject requests

EGEROBOT provides the institution with technical assistance in meeting the access, rectification, erasure and objection requests it receives.

8. Breach notification

When a data breach becomes known, the institution is notified without delay; the notification includes the number of affected records and the measures taken.

9. Return and destruction

On termination the data is returned or destroyed at the institution's choice; destruction is recorded and deactivation does not count as destruction.

10. Audit

The institution may audit compliance at reasonable intervals; the scope of the audit is agreed in writing beforehand.

11. Hosting location

The institution may choose local hosting. Where the cloud is chosen, the hosting location is notified to the institution in writing.

12. The nature of this text

This text is a draft and does not replace the contract to be signed; it is finalised together with the institution's legal team.

Change history

This is the first draft of this document.

Contact

You can send questions about this document and your data subject requests to the controller, EGEROBOT, through the support form.