Providers, storage and transfers

Authentication and account identity, including guest and Feide login.

User/provider ID, available name/email, login metadata and password-related authentication data for password accounts. Provider security may use IP/device data.

Google documents US processing for Firebase Authentication. The Cloud DPA and transfer terms have been reviewed; Google states DPF applies to relevant EU/EEA–US transfers, with SCCs where applicable under the agreement.

Technical sub-processor. The contracting party, customer registration and documented agreement acceptance are being reconciled with Google. This is an open documentation point, not a conclusion that existing agreement coverage is absent.

Database for accounts, rooms, tasks, work, feedback and administration.

Profile/role data, Space membership, submissions, text/results, feedback, content/admin data, events and timestamps.

Database (default) in project skole-c09b8: europe-west1 (Belgium). Fjord Service checked the storage location in Firebase Console and Google Cloud Console on October 18, 2026.

Technical sub-processor. Contract terms, other processing and support access are assessed separately from the confirmed storage location.

Storage of student audio, podcast segments, images and attachments.

File bytes, object metadata and user/room/activity/submission links. Historical references and access links require assessment.

Bucket skole-c09b8.firebasestorage.app in project skole-c09b8: regional storage in europe-west1 (Belgium). Fjord Service checked the storage location in Firebase Console and Google Cloud Console on October 18, 2026.

Technical sub-processor for files. Private file handling is deployed. Old download tokens for the mapped audio set are revoked and checked. Daily copying of finalised stored files is active. Retention, other processing and support access are assessed separately from storage location.

School-controlled authentication and agreed identity attribute disclosure.

Attributes listed in the Feide portal: userinfo-name includes givenName, sn, norEduPersonLegalName, displayName and cn; userid-feide includes eduPersonPrincipalNamePrior, eduPersonPrincipalName, uid, eduPersonTargetedID and eduPersonUniqueId; email includes mail. These are configured requested fields, not proof that every field is received or stored. Feide identifiers must be distinguished from the Firebase UID.

Norwegian identity service. Current Sikt agreement, locations and roles must be checked with the school owner.

Identity service when used; its contract chain is not automatically Fjord Service's sub-processor chain.

Web hosting, delivery and server processing of application requests.

IP, browser/request metadata and logs; server routes also process submitted text, file bytes and feedback for relevant features.

Production Vercel Functions run in Frankfurt (fra1), verified during deployment on 28 October 2026. The move does not automatically change processing locations for Firebase Authentication, OpenAI, Resend or other services, nor does it confine all logging, CDN, build and support processing to the EEA.

The Pro DPA includes SCCs. Other processing countries and relevant subprocessors are recorded in the provider annex.

Selected AI features: content, feedback, text/image and speech tools.

Prompts, task/reading text, answers, results and relevant context. Image/audio data depends on the feature. Teacher-requested feedback may process student data.

Project Residency Global is confirmed in an account image. This specifies neither one country nor EU-only processing. Responses, files, cache and security logs have separate retention rules.

321school uses OpenAI Platform/API. The owner reports a DPA signed on 23 October 2026. Account images show all three sharing options disabled, API call logging Enabled per call and Project Residency Global. OpenAI states API data is not used for training without opt-in. Global is neither an EU restriction nor a single processing country. Response storage, Files, prompt caching and security logs have different rules; no general zero-retention guarantee is given. Explicit store:false in the selected text calls was deployed on 28 October 2026. This does not change the other retention rules.

Transactional email, invitations and account messages.

Recipient address, message content, invitation/account context and delivery metadata. Answers must not be included as default email content.

The reviewed DPA states primary processing in the US, incorporates SCCs and states DPF participation. Account-specific periods for message and log categories are checked separately.

The DPA was obtained from the account and reviewed. Its wording makes it binding through acceptance of the service agreement or execution; the customer’s exact acceptance date has not been checked. Relevant certification scope is checked when relying on DPF.

Payments, subscriptions and billing.

Paying customer name/email, customer ID, subscription, payment/billing information. Not a general recipient of all student work.

Entities, contract, countries and onward payment processing must be checked for the payment setup.

Provider for paid customer relationships; role and relevance are separate from student data.

Previous page/product analytics; disabled in the published code policy.

When previously active: page/event and technical user/device data. Historical retention is assessed separately.

Google infrastructure; account-specific processing, transfers, contract and retention not fully documented.

Google Analytics and application product analytics are disabled in the published service, regardless of role. Necessary operational/security logging and educational statistics are separate purposes and are not disabled by this measure. Aggregate statistics are not necessarily anonymous, especially in small groups.

External instructional videos when opened or embedded.

Technical viewing/connection data depending on playback/embed configuration.

External service locations, cookies and terms require assessment for the selected use.

External content; not automatically a sub-processor under the school agreement.

Optional video/course features if used.

Participant/session identifiers, connection metadata and any media for the chosen feature.

School use, setup, countries, retention and contract must be confirmed before inclusion.

Optional; not documented as part of the municipality's agreed scope.