School and municipal assessment

Municipal report

Documentation for the school owner's assessment of 321school. Choose a short report with links or a full package of Trust Center documents and DPA annexes A–D.

Recipient and note are used only in this report view and are not saved by the report feature.

Review draft v0.12. Content revised: November 12, 2026.

321school Trust Center · Short report

Report for municipality/school owner

Review draft v0.12. Content revised: November 12, 2026.

Fjord Service · 968 400 789

Review draft. The short report includes selected summaries with links to document texts and annexes.

Information for schools and school owners

Schools, school owners, teachers, students and parents can find information here about how 321school works, the personal data it processes, and ongoing privacy and security work. The documentation distinguishes the current service, tested improvements and matters to clarify before agreed school use.

Internal control and documented progress

Fjord Service works systematically on internal control, privacy and information security as an ongoing part of operations. Access controls, private file handling, participant-link approval, school boundaries for invitations, time-limited substitute access and daily backups are deployed and checked. Data-flow mapping, provider clarifications, retention procedures and documentation continue to be maintained, with clear responsibility and verification for each measure.

Access controls, private file handling and participant-link approval went live on 28 October 2026. Firestore/Storage rules and application flows were checked with synthetic accounts, a dedicated test room and rejection of unauthorised access. Old direct download tokens were revoked for the entire mapped set of 128 audio files, rechecked on 29 October. Files, submissions and memberships were preserved. The school boundary for new invitations was deployed on 6 November and time-limited substitute access on 7 November 2026, both with documented functional checks. The evidence covers the flows and file set examined.

The school boundary for new co-teacher and observer invitations to school rooms was deployed and checked on 6 November 2026. Invited teachers must have an active affiliation with the same school. The school administrator role does not itself grant access to individual student answers or the right to invite on behalf of the room owner.

Time-limited substitute-teacher access was deployed and checked on 7 November 2026. A school administrator can grant a teacher with an active affiliation with the same school access to a specific school room, including during teacher absence. The substitute can read assignments and student answers and provide written feedback through a dedicated, scoped view. Access can be revoked and expires automatically. Grants, expiry deadlines and revocations are logged. This does not grant ordinary room administration rights or general access to the school’s other rooms.

Since 11 November 2026, a platform administrator can disable AI feedback suggestions for Lessons answers and AI help in writing activities across Space rooms linked to one verified school, including new rooms. Rooms may apply stricter settings; a room cannot override the school's restriction. These settings are not automatically enabled for every school. Rooms without a verified school link are outside their scope. Other AI features and school-owner-wide controls are not covered by these two restrictions.

Checks using synthetic accounts and test rooms confirmed rejection across the school boundary, continued ordinary student and co-teacher access, and that revocation and expiry block further substitute access. Existing student work was preserved. The evidence covers the flows tested.

Analytics and retention

Google Analytics and application product analytics are disabled in the published code policy for all roles, deployed on 28 October 2026. This was checked in source and tests and on a selected public page view. Necessary operational/security logging and educational results are described separately. Any later activation of product analytics requires a separate assessment and documented change.

The draft agreement proposes target periods to be agreed with the school owner: student work and related audio/files during active teaching, deleted within 90 days of the agreed end; operational/error logs 30 days and security logs 90 days. School instructions, earlier deletion and return are agreed in annex D. Specific incident evidence may be retained separately with a documented basis and review date. Enforcement has not been fully verified in operation; procedures, export, copies and provider periods are completed separately.

Municipal topic

1. Privacy notice

321school is the service brand. The legal supplier is Fjord Service Jan Hogne Christiansen (Norwegian sole proprietorship/ENK), referred to below as Fjord Service.

  • For municipal school use, the intended agreement assigns purposes and legal bases to the municipality/school owner, with Fjord Service processing school data on documented instructions. Separate supplier purposes, such as billing and managing its own customer relationships, must be described separately.
  • Students can participate by code/QR without a private email or personal Feide login. Participation is linked to a technical user ID, chosen display name, room membership and submitted work. These may be personal data; anonymous authentication does not mean anonymised work.

Municipal topic

2. DPA – draft

This is a general draft agreement with annex material for assessment by the school owner. The parties, processing scope and annexes must be clarified and legally reviewed before any signing.

  • The draft covers instructions, confidentiality/security, assistance, breaches, sub-processors, audits and exit. Annexes A–D cover processing, security, providers/transfers and retention/deletion.

Municipal topic

3. Personal data

The school overview describes data about teachers, students using accounts or personal codes, and school administrators, along with student work, media and technical data.

  • Account/role: ID, name/display name, email or school identity where relevant, login metadata, membership and timestamps.
  • Work: tasks, answers, results, teacher/AI feedback, audio, podcast segments, images and attachment metadata. Infrastructure/analytics may process technical request/event data.

Municipal topic

4. Storage, providers and transfers

321school uses Google Cloud Firestore and Firebase Storage in project skole-c09b8. Firestore database (default) and Storage bucket skole-c09b8.firebasestorage.app are both located in europe-west1 (Belgium). The bucket uses regional storage. Fjord Service checked the locations in Firebase Console and Google Cloud Console on October 18, 2026.

  • Daily backups are established for Firestore, Firebase Authentication accounts and finalised stored files, with storage in Belgium. Auth and file copies are verified separately. Failures or a missing health check trigger alerts to the operator and a designated backup contact. The first scheduled automatic Auth/file cycle completed and was independently verified on 4 November 2026. Incomplete file uploads are excluded from the file backup.
  • Vercel Pro: checked production resources show Functions region Frankfurt (fra1) in Germany; its Pro DPA includes SCCs. Resend’s DPA was obtained from the account and reviewed; primary processing is in the US, with SCCs and stated DPF participation. Google documents US processing for Firebase Authentication and DPF for relevant EU/EEA–US transfers, with SCCs where applicable under the agreement. Google customer registration and explicit acceptance are being clarified before new acceptance. Other processing and subprocessors are assessed per service.

Municipal topic

5. Purpose and users

321school supports teachers in planning, teaching and following up student work through learning resources, digital class and group rooms, and Live activities. Teachers and students use the teaching features, while school administrators manage their own school's use. The links below explain AI and other feature choices.

  • Agreed role policy: school administrators manage only their own school's teachers within its licence and receive aggregate school statistics. That role alone must not grant access to individual answers, AI feedback or teaching rooms. Administrators who also teach use separate teaching permissions.
  • In the school-use model, AI provides translation, vocabulary support and reading aloud, alongside limited help in process-oriented activities such as writing and podcast workshops. Its purpose is to support students' understanding, learning and their own work.

Municipal topic

6. Feide and shared information

The service is registered in the Feide customer portal as Innlogging 321skole, service ID 2196690, listing Fjord Service as provider and OpenID Connect as authentication type. Sign-in uses Firebase Authentication. Registration is documented in console images from 25 October 2026. Each school owner’s activation and actual sign-in are checked before Feide is used there. Licences, roles and room access are managed in 321school.

  • The Feide portal shows three attribute groups/scopes: names (userinfo-name), organisation user identifiers (userid-feide) and email (email). Stated purposes are recognition, correct account linking, secure sign-in, account administration and necessary communication. Actual disclosure depends on the organisation directory and configuration. The account flow can store names and email from Firebase. Any connected data-source sharing and actual field use are checked separately.