School and Institutional Data Processing Agreement Version 2026-10-01 Effective 2026-10-01T00:00:00.000Z School and Institutional Data Processing Agreement Souf at School Version October 1, 2026 This Agreement governs personal information that Souf at School processes on a school or institution's documented instructions to provide the educational service. It includes the processing details, security measures and subprocessor arrangements below. It applies when incorporated into an accepted institutional order or separately accepted in a durable written or electronic record, before pupil processing begins. 1 Parties and scope The Controller is the legal organization identified as the institutional customer in the accepted order. Its authorized contract representative is its initial instruction and data-protection contact unless it designates another contact in writing. The order reference and acceptance record identify the organization and relevant service without requiring a separate blank signature schedule. The Processor is Soufiane Boudarraja, sole proprietor trading as Souf at School, Waldstr. 74, 65451 Kelsterbach, Hesse, Germany. Data-protection and incident contact: general@soufatschool.com; telephone +49 152 2717 9992. The General Data Protection Regulation and other applicable data protection laws govern processing within their scope. The Terms and Conditions govern the service, fees and licenses. This Agreement takes priority over an inconsistent service term concerning processing on the Controller's behalf. Mandatory transfer clauses and applicable law take priority over this Agreement. This Agreement does not cover processing for which the Processor independently determines a lawful purpose, such as its adult contract contacts, invoicing, statutory records and its own legal claims. Those activities are described in the Privacy Policy. A role follows the actual processing, not merely the label in an account. A different allocation, including joint control where applicable, must be documented before that different processing begins. 2 Processing details Subject matter and purpose. Providing the licensed educational account, staff and class administration, authorized pupil access to selected reading, coloring and games, permitted customization, saved work and progress, synchronization, retrieval, support, security and return or deletion of institutional records. Pupil information must not be used for independent advertising, commercial profiling, sale, public publication or independent AI training. Nature of processing. Receiving and recording profiles and instructions; organizing records by institution and class; storing and displaying permitted activities; recording, updating and retrieving creations and progress; synchronizing authorized devices; maintaining restricted service backups; assisting with rights and incidents; exporting and erasing records. People concerned. Pupils and participating children, authorized teachers and institutional administrators, and individuals appearing in lawfully supplied customization material where that material is necessary for an approved use. Staff records in this scope are limited to administration and use of the institutional service. Information. Pupil aliases, preset avatars, internal profile identifiers, institution and class associations, staff identifiers and permissions, assigned titles, activity permissions, active or archived status and dates, saved drawing states and thumbnails, selected creative versions, reading progress, resumable game states, game results, device and synchronization identifiers, timestamps, and security records needed for the service. A custom Assembly image can be embedded in a saved game state. Excluded information. The service does not require pupil email addresses, passwords, exact dates of birth, home addresses, health records, formal educational assessments, biometric identification or criminal-offence information. The Controller must avoid special-category data and unnecessary real names or identifiable photographs. Any materially different or sensitive-data use requires a written assessment and agreed safeguards before collection; this Agreement does not automatically authorize it. Duration. Processing continues for the contracted service and the limited return, deletion and protected backup periods in section 9. The Controller may give lawful earlier deletion instructions. PDF-only institutional licensing without pupil records does not itself require creating pupil profiles. 3 Controller responsibilities and instructions The Controller determines and documents the lawful basis for its educational use, gives required notices, establishes any necessary parental authority or consent, and restricts staff access to authorized people. Where school authorization can lawfully support children's privacy requirements, it is limited to the institution's educational purpose. If it cannot, the necessary parental process must be completed first. The accepted order, this Agreement, authorized configuration choices and later written instructions form the documented instructions. The Controller may send instructions through its verified administrator or to the Processor's data-protection contact. Routine configuration choices do not authorize an incompatible purpose, public disclosure or new recipient. The Processor processes personal information only on those instructions, including regarding transfers, unless applicable law requires otherwise. If legally required to process differently, it informs the Controller beforehand unless prohibited for important public-interest reasons. It promptly informs the Controller if an instruction appears to infringe applicable data protection law and may suspend the affected instruction while the concern is resolved. The Processor does not acquire ownership of pupil creations. The Controller does not gain a right to use another institution's or household's information. A departing staff member cannot transfer institutional records to a personal account merely because they administered them. 4 Confidentiality and access People authorized by the Processor to handle institutional information must be bound by confidentiality and receive instructions appropriate to their role. Access is limited to the necessary task and revoked when no longer required. Parents using household accounts are checked against the relevant family. Within institutions, teachers are limited to their assigned classes and authorized records; institutional administrators are limited to their institution. Child or student mode is restricted to the selected authorized profile. These checks must be enforced by the server on reads, writes, downloads and synchronization, not only by hiding interface controls. Archiving or reassigning a place must not reveal the previous child's records to a new child. Cross-account transfers, family exports and requests from a person outside the authorized institution require an independently verified lawful instruction or right. 5 Security measures The Processor implements and maintains measures appropriate to the information and risk. The following measures form contractual requirements for the service, rather than a representation that no incident can occur. Service and account protection. Encrypted communications in transit; managed platform security; restricted service credentials; verified adult email and applicable authority checks; proportionate reauthentication before sensitive administration; multi-factor authentication for the operator and privileged collaborators wherever the platform supports it; prompt removal of unnecessary collaborator and application permissions. Data separation. Administrative-only direct access to the principal profile and activity CMS collections, with controlled application access through server authorization; institution and class checks; separation of household and school records; private or access-controlled delivery of personal files. A hidden page or an obscure public URL is not sufficient protection for a personal file. Data minimization. Nicknames and preset avatars; no compulsory child contact details or exact birth date; no collection unrelated to the requested educational activity; no child-content attachments in routine notification emails; no child data in advertising, session replay or independent AI-training tools. Devices and synchronization. Adult selection of eligible offline content; clear save status; authorized synchronization; rejection of inactive, erased or unauthorized profiles; replay and stale-version safeguards; removal instructions on reconnection. Locally stored encryption keys do not amount to protection against a person controlling the device. The Controller manages its devices, browser profiles, exported files and physical access. The Processor does not promise remote erasure of a device that never reconnects. Operations and recovery. Restricted logs, monitoring of failed legal-request and deletion operations, controlled releases, proportionate vulnerability handling, recoverable service data where appropriate, tested restoration procedures, an erasure register kept separately from restored content, and reapplication of erasures before restored records become accessible. Evidence and review. Maintain the relevant access, authorization, deletion and incident records; review privileged access at least quarterly and on role changes; review retention and provider access at least annually and on material service changes. Security details whose disclosure would create a material risk are supplied through an appropriately confidential channel. Wix's platform measures are described at https://support.wix.com/en/article/wix-security-measures-overview. They supplement, and do not replace, the Processor's responsibilities for its application and configuration. 6 Subprocessors The Controller gives general written authorization for the subprocessor arrangements in section 13, subject to this section. Before a subprocessor receives information, the Processor binds it to data protection obligations appropriate to the delegated processing and no less protective in substance than the applicable obligations here. The Processor remains responsible to the Controller for its subprocessor obligations as required by law. For a new direct subprocessor or a material replacement, the Processor gives at least 30 days' advance notice where reasonably practicable and, in all cases, a meaningful opportunity to object before the new processing. For Wix's downstream changes, the Processor subscribes to Wix notifications and forwards relevant notices without undue delay. Wix's published notice period can be seven days, so a uniform 30-day notice for every downstream change is not promised. The Controller may object on reasonable data-protection grounds. The parties seek a lawful alternative before affected processing proceeds. If an objection cannot be resolved, the affected processing is suspended or the affected service may be terminated without penalty for the unused portion, with a proportionate refund of prepaid affected service fees. Urgent security substitutions are communicated promptly with the reason and safeguards; they do not remove statutory authorization and objection rights. The institution's approval of a platform subprocessor does not authorize every installed Wix application to receive pupil information. Payment, fulfillment, analytics and other unrelated applications are excluded from institutional pupil processing unless separately authorized for a defined necessary purpose. 7 International processing Service data is processed through Wix's international infrastructure and service arrangements. No Germany-only or EEA-only hosting promise is made. Locations and safeguards must be assessed for the actual service, rather than inferred from a supplier's headquarters or the website's locale. For a transfer subject to GDPR Chapter V, the Processor uses a valid adequacy basis or appropriate safeguards, including the applicable standard contractual clauses and necessary supplementary measures. It provides relevant information to the Controller on request. Acceptance of this Agreement is not blanket consent to an otherwise unlawful transfer and this Agreement is not itself a set of international-transfer standard contractual clauses. A new transfer or materially different location requiring additional safeguards is not activated until those safeguards and required instructions are in place. If a lawful transfer arrangement cannot be maintained, the parties restrict or suspend the affected processing and arrange return or deletion as appropriate. 8 Assistance incidents and requests The Processor assists the Controller with access, correction, erasure, restriction, portability and objection requests, taking account of the processing and available information. It promptly forwards a request concerning Controller-controlled records and does not disclose those records to an unauthorized requester. It normally responds to the Controller's assistance request within five business days, or sooner where needed to meet a known legal deadline. Taking account of the processing and information available, the Processor assists with security duties, breach assessment, data protection impact assessments and prior consultation. It provides information reasonably needed to demonstrate compliance and does not condition necessary breach notification on payment of an extra fee. On becoming aware of a personal-data breach affecting the Controller's information, the Processor notifies the Controller without undue delay, with an initial notification within 24 hours where reasonably possible. Initial notice is not delayed until every fact is known. It supplies available details about the nature, affected categories and approximate numbers, likely consequences, measures and contact, and provides updates as facts become available. The Controller determines its notices to individuals and authorities, with assistance. The Processor also meets any independent legal reporting duties and coordinates communications where lawful. The agreement does not postpone a statutory deadline or prevent either party from contacting a competent authority. 9 Return retention and deletion During the service, the Controller may export or request return of its records and give lawful deletion instructions. Archiving is a retention state, not erasure. The default is to review an archived pupil record after 12 months and give the Controller at least 30 days to retrieve it or document a continuing lawful need; without such an instruction, it is erased at the end of that notice period. Any longer instruction must identify its purpose and a review or deletion date rather than indefinite retention. At the end of the service, the Controller chooses return or deletion, subject to law. Unless it instructs earlier deletion, the Processor offers a 30-day return period and then deletes active-system pupil records within the following 30 days. Return is in a commonly usable electronic format appropriate to the record, including machine-readable profile and progress data and available image exports. Return or deletion does not require purchasing a further subscription. The Processor aims to complete an authorized erasure instruction within seven days, with a normal maximum of 30 days, unless an applicable legal deadline requires faster action or a legally justified exception is explained. It disables further affected synchronization promptly and includes the linked profiles, assignments, saved work, versions, progress, game records and relevant personal files. Required adult contract or legal records are isolated and retained only for their separate lawful purpose. Backups controlled by the Processor are restricted from ordinary use and removed within 90 days after active-system deletion. Provider infrastructure copies follow the contracted deletion process; the Processor submits necessary instructions, tracks them and does not represent the 90-day operator-controlled period as a universal Wix infrastructure guarantee. Deleted information must not be restored into active use. Erasure markers are kept only as long as needed to prevent restoration or stale-device re-upload, with a normal three-year period and a documented extension only for an older recoverable copy. The Processor confirms completion, identifies any lawful retained exception and describes outstanding provider-backup handling. The Controller manages offline devices and independent exports in its possession. The Processor applies supported local-removal instructions when a device next connects and blocks unauthorized re-upload. Copies on disconnected devices are not represented as remotely erased. 10 Demonstrating compliance and audits The Processor makes information available to demonstrate its obligations under this Agreement and allows and contributes to proportionate audits, including inspections, by the Controller or its mandated independent auditor. Relevant documentation and platform assurance reports should be considered first, but do not remove an inspection right where necessary. For routine audits, the parties arrange reasonable notice, confidentiality, safety and protection of other customers' information. Ordinarily one routine audit in 12 months is sufficient; additional audits remain available following an incident, material concern or authority requirement. An approval condition, charge or frequency limit must not prevent a legally necessary audit. Any exceptional additional service fee must be agreed in advance and does not cover correcting the Processor's own noncompliance. 11 Liability and ending affected processing The liability provisions in the Terms and Conditions apply only so far as consistent with applicable data protection law. Nothing here reduces an individual's statutory compensation rights or either party's duties to authorities. There is no general obligation for the Controller to indemnify the Processor for all claims regardless of responsibility. If a material data-protection breach cannot be promptly corrected, or lawful processing cannot continue, the parties restrict the affected processing and may terminate the affected service under the applicable contract and law. The confidentiality, return, deletion, assistance and accountability obligations continue for as long as relevant information remains held. 12 Acceptance and changes The Controller's authorized representative accepts this Agreement through the institutional order or a separate recorded acceptance identifying this version. The Processor supplies a durable copy. No pupil records may be activated before the necessary agreement and authority are established. Material changes to processing scope or this Agreement require the appropriate documented agreement or lawful change process. A later website edit does not silently replace a previously accepted agreement. The parties retain evidence of the applicable version and instructions. 13 Authorized service arrangement Direct platform subprocessor. Wix.com Ltd. and the relevant Wix entities acting under the Wix user Data Processing Addendum provide managed hosting, CMS storage, account functions, media delivery and necessary transactional processing for the institutional service. Scope is limited to the information needed for those functions. The Processor must ensure that the contractual arrangement covers its use of Wix on behalf of an institutional controller. Wix data processing terms: https://www.wix.com/about/privacy-dpa-users. Downstream platform providers. The applicable Wix subprocessor list is provided at https://support.wix.com/en/article/list-of-wixs-sub-processors. It includes infrastructure, content delivery, communications, support and security providers. The list applicable at acceptance is retained with the agreement record; relevant updates follow section 6. Listing a provider as potentially used by Wix does not establish that every listed provider receives this institution's records. Headquarters are not treated as proof of a processing location. Service communications. Routine institutional notices contain adult recipient details and an account or case reference, not attached pupil drawings or full activity records. Wix delivers transactional notices. Ordinary business email may pass through Microsoft infrastructure. Pupil files are handled through the protected institutional service; a materially different email or support processing arrangement requires the applicable authorization and safeguards before routine use. Excluded recipients. Printful, Printify, Prodigi, Lulu Direct, payment providers and independent analytics applications are not authorized under this Agreement to receive pupil profile or activity collections merely because an application is installed or a school also buys physical goods. Any separately agreed personalized physical order must identify the necessary recipient and data scope before transfer.