Version 15.11.2026
Vitensti data processing agreement
Agreement basis under GDPR Article 28 for a specific processing assignment. Both parties must complete and sign it. This is not general approval of school use or an agreement with all visitors.
1. Parties and roles
The customer in the signature section is controller for the assignment. Skjld Labs AS, registration number 937 025 955, hello@skjldlabs.com, is processor for that assignment. This agreement and documented instructions apply together; this agreement prevails in a conflict about personal data. Skjld Labs is separately controller for its own open-service purposes, which cannot rely on this agreement.
2. Subject matter and duration
The purpose is to provide, secure and maintain the agreed Vitensti service and report agreed aggregate usage figures. Processing may include technical transmission, temporary sessions, access management, aggregation, storage, restoration and erasure. Data subjects may include pupils, teachers and customer administrators. Duration follows the completed assignment until return and erasure are finished.
The MVP has no pupil accounts, name lists or server-stored individual pupil answers. Individual answers and logs remain in the browser. Data categories are limited to necessary technical connection/session data and agreed aggregate subject/grade/topic/language figures and results. Article 9 special categories, national identity numbers and pupil profiling are prohibited. New categories, recipients, accounts or integrations require documented instructions and a new risk assessment before introduction.
3. Instructions and lawfulness
The customer determines purposes and lawful basis, informs data subjects and assesses privacy impacts, particularly for children. The processor acts only on documented instructions, including transfers, unless law requires otherwise. Legal requirements are disclosed beforehand unless notice is prohibited. Instructions considered contrary to data protection rules are reported immediately; disputed processing is suspended pending clarification. Data must not be used for marketing, the processor’s own pupil profiles or other independent purposes.
4. Confidentiality and security – operations annex
Only authorised employees with a service need may access data and must be bound by confidentiality. Access is reviewed and removed when no longer needed. Risk-appropriate Article 32 measures are documented: HTTPS, an isolated tenant, private storage outside the web root, secure sessions, password hashing, login and event rate limits, validation, CSRF/XSS controls, security headers and dependency checks.
The server and both rolling backups are held by Skjld Labs in Sandefjord, Norway. The detailed address is not published. Nobody outside the company has administrative access. Vitensti’s nginx log includes IP addresses, timestamps, requested paths and browser information and is not anonymous. The operator declares one-year log retention and up to one year for two rolling backups; active statistics are retained for 90 days. Parties must document necessity and the balancing assessment and agree shorter periods or anonymisation where appropriate. Recoverability, actual erasure and log contents must be checked regularly.
5. Subprocessors and transfers
No other processors are declared for hosting, operations or backups. New subprocessors require specific prior written customer approval and an updated register of entity, task, country and data categories. They must have at least equivalent obligations. Skjld Labs remains responsible to the customer.
Processing and administrative access must take place in Norway/the EEA. Third-country transfers or access require documented customer instructions, a valid GDPR Chapter V mechanism and assessment of necessary supplementary safeguards before transfer. This agreement alone does not approve a new reporting integration.
6. Rights, assistance and audit
The processor assists with access, rectification, erasure, restriction, portability and objection and forwards rights requests without undue delay. Necessary assistance with security, risk assessments, DPIAs and any prior consultation under Articles 32–36 is provided considering the processing and available information.
The processor supplies documentation needed to demonstrate compliance and allows and assists audits and inspections by the customer or an independent auditor it appoints. Audits must protect security and others’ confidentiality without limiting legally required access. Findings and agreed remediation are followed up in writing.
7. Security breaches and contact
The processor notifies the agreed customer contact without undue delay after becoming aware of a personal data breach. Initial notice must not wait for a complete investigation. It describes known facts: nature, affected categories and approximate scale, likely consequences, contact point and completed or planned measures. Further information follows as available.
The customer decides notification to authorities and affected people. The processor assists compliance with any applicable 72-hour Article 33 deadline and Article 34 obligations. The Skjld Labs incident and recovery contact is hello@skjldlabs.com. Incidents, assessments and remediation are documented.
8. Return, erasure and termination
At termination the customer chooses return or erasure of personal data processed on its behalf. Active copies are erased after return or documented erasure instructions unless retention is legally required; the requirement and scope are disclosed. Skjld Labs documents completion.
Residual backups are restricted from ordinary use and erased at the agreed rotation, within one year at most unless a shorter period is agreed. After restoration, prior erasure instructions and active retention limits are reapplied before normal use. The customer manages local pupil data on its devices; the processor assists through features and guidance. Pupil accounts and individual reports must not be assumed to exist in this MVP.
Completion and signatures
Complete the customer, term, instructions, contacts and any different erasure deadlines before both parties sign. Visiting the website does not sign an agreement.
- Controller customer – legal name and registration number
- __________________________________________________
- Customer contact and incident contact
- __________________________________________________
- Assignment, duration, instructions and special terms
- __________________________________________________
- Date and signatures of both parties
- __________________________________________________
Legal basis and guidance
Norwegian Personal Data Act including GDPR · Datatilsynet: data processing agreements · Datatilsynet: cookies and consent