Cookies and Local Storage Policy Version 2026-10-01 Effective 2026-10-01T00:00:00.000Z Cookies and Local Storage Policy Souf at School Last updated October 1, 2026 This Policy explains cookies and information stored in your browser when you visit Souf at School, sign in, buy products, or prepare activities for offline use. Our Privacy Policy explains the related personal information, recipients and rights. We use technologies needed for the service or a feature you request. We do not enable advertising, session replay or optional behavioral analytics in child activity areas. The website's current privacy choices keep optional tracking disabled; choosing Accept does not turn on additional analytics or advertising. 1 Who is responsible Soufiane Boudarraja, sole proprietor trading as Souf at School, Waldstr. 74, 65451 Kelsterbach, Hesse, Germany. Website: https://www.soufatschool.com. Email: general@soufatschool.com. Telephone: +49 152 2717 9992. You can use Privacy Request in the Policy Hub or contact us directly about device storage. A form is not the only way to exercise your rights. 2 Cookies and browser storage Cookies are small records sent with relevant later website requests. A session cookie normally lasts for the browser session, although some browsers restore sessions. Persistent cookies contain an expiry. Removing a cookie early does not necessarily remove the related server record. Local storage, session storage, IndexedDB databases and browser caches perform different functions. Local storage and IndexedDB do not have a built-in automatic expiry. Browser settings, storage pressure or private browsing can remove them. Browser storage can contain personal information even if it is not called a cookie. Deleting site data does not cancel a subscription, erase an online account or revoke a lawfully acquired PDF license. 3 When permission is needed Under section 25 TDDDG, storing or accessing device information generally requires consent unless an exception applies, including strict necessity for a digital service expressly requested by the user or transmission of a communication. This applies beyond cookies and beyond personal information. We use the exception only for the necessary part of a requested function, such as authentication, security, a selected profile, a requested display setting or an explicitly prepared offline library. Being first-party, helpful or supplied by Wix does not by itself make a technology exempt. Further processing of personal information also needs the legal ground explained in the Privacy Policy. If a future optional technology requires consent, we describe its provider, purpose and duration and obtain the required choice before activation. Rejecting an optional technology does not remove unrelated purchased access or statutory rights. Privacy choices never substitute for parental authorization. 4 Application cookies The following first-party cookies support the listed requested functions. They are not all issued to every visitor. The lifetimes are maximum configured lifetimes for an individual cookie; a new authorized session or action can issue a new cookie. Revocation, signing out or removal can end its usefulness earlier. Cookie Purpose Configured lifetime sas-privacy Signed receipt of the browser privacy choice 180 days sas_mode Selected child or student session 12 hours sas_exit Temporary authorization to leave child mode 10 minutes sas_device_lock Identification of the requested locked-device session 400 days sas_device_unlock Temporary permission to return to adult controls 30 minutes sas_device_reauth Short-lived adult reauthentication challenge 10 minutes sas-institution Selected institution for the adult session Browser session oAuthState Wix sign-in state and protection of the authentication exchange 30 minutes and removed on callback A long-lived device-lock cookie does not authorize paid content for that whole period. Entitlements, account sessions and profile authorization are checked separately. 5 Wix sign in and checkout Wix supplies authentication, request protection and commerce functions. Identified platform cookies include wixSession, XSRF-TOKEN, hs and server-session-bind, used as session cookies in our sign-in and platform integration. Wix also uses smSession and svSession as persistent authentication or session-related cookies in relevant flows. Wix sets their expiry when they are issued; the expiry shown for a particular browser is not a universal duration for every Wix integration. Wix-related browser entries can also include local storage named __wix.memberDetails and fedops.logger.sessionId, and session storage named mpaSessionId. They support account, session or platform-operation functions. Local-storage entries can remain until the relevant service or browser removes them. Optional diagnostic collection is subject to the applicable consent requirements and is not made necessary merely by its name. The selected payment method may introduce its own payment-session and security technologies. Wix Payments, PayPal and supported payment-method providers present information in their checkout flow. We do not authorize unrelated advertising or analytics simply because a customer chooses to pay. Wix information: https://support.wix.com/en/article/cookies-and-your-wix-site and https://www.wix.com/about/privacy. These descriptions supplement this Policy and do not expand our permitted purposes. The exact platform entries can vary with sign-in, payment method, browser and provider updates. 6 Settings and offline storage The local-storage item sas-theme remembers a display theme explicitly selected by the user. When signed in, that choice can also be stored with the adult account. The item sas-device-locked indicates device-lock state. These items have no general automatic expiry and remain until replaced or removed. The IndexedDB database sas-device-library holds the prepared content, profile manifest, local cryptographic key, saved pictures and versions, game results, progress and synchronization queue. The database sas-activity-drafts holds unsaved or recovery drawings and thumbnails. Where an older activity was prepared using sas-private-activities, that browser database can also remain until removed. Access expiry is not the same as erasure of the underlying local data. Cache Storage entries beginning sas-shell store the offline interface and permitted static assets. Their versioned names can change as the application is updated. A cache version number is not a personal-information retention period. These stores are created or used for the offline, saving or recovery functions requested. They have no general automatic time-based erasure. Successful synchronization can clear acknowledged pending drafts; replacing a version or clearing device data can remove other entries. The adult can clear the prepared library and local activity data using the device-data removal function or the browser's controls. Prepared response bodies use AES-GCM encryption with a key held on the same device. This does not encrypt every local activity record or protect the data against everyone with control of that device. We do not keep your account password as an offline password verifier. 7 Synchronization and removal While the application is open, connected and authorized, it attempts to synchronize local work and history, including while the device is locked in child mode. A server authorization check still applies. We do not promise synchronization while the browser is closed. Check whether work is shown as saved on the device, waiting to synchronize or saved to the account. Signing out, returning to adult controls or canceling a subscription does not automatically wipe a prepared library. Erasure or authorization withdrawal stops future affected server uploads. The application applies the corresponding local removal instruction when it next connects. A disconnected device that never reconnects, and independently exported files, must be cleared by the person controlling that device. Before clearing storage, retrieve or synchronize work you want to keep. Clearing site data, losing a device, changing a browser or browser eviction can permanently remove local-only work. We cannot restore a picture that never reached our servers. Server-retention and backup periods are set out in the Privacy Policy. 8 Your choices and policy changes The Policy Hub and footer provide access to privacy controls. At present, Accept, Refuse and Only necessary keep optional tracking off. A choice on one browser does not necessarily change another browser. Server evidence of the choice is separate from the sas-privacy cookie and follows the Privacy Policy retention schedule. You may inspect, block or delete cookies and other site data through your browser. Blocking a strictly necessary item can prevent the related requested function from working. You can still contact us directly without consenting to optional tracking. We update this Policy when technologies or purposes materially change. A new policy date does not itself authorize a new use or replace consent where consent is required. For questions, use general@soufatschool.com or Privacy Request.