For applicants and guardians: Please particularly note school responsibility, drafts/progress recording, any document review and your individual rights.
These notices cover schulanmeldung.app, school administration, applications, additional evidence and event registrations. Sushi Dev GmbH, Wiedner Gürtel 28/6, 1040 Vienna, Austria, is responsible for its own platform accounts, contractual communications and platform operations. Privacy contact: office@sushi.dev.
The selected school or event organizer generally controls application and registration contents. It determines fields, recipients, access rights, legal bases and retention. Sushi Dev processes these data as a technical processor on documented instructions. Each school must provide its full contact details, any applicable data protection officer and additional school-specific legal information. Please also consult that school’s privacy notices. The operator’s independent security and contractual purposes are distinguished below; a school instruction does not permit arbitrary independent reuse.
Information comes from you, authorized school personnel, where relevant guardians, enabled login providers and the technical activities described here.
| Area | Data and purpose |
|---|---|
| Accounts and schools | Name, email, password hash, account status, school memberships, roles, invitations, preferences and recorded acceptance of terms: sign-in, access administration and collaboration. |
| Applications and drafts | Depending on the form: identity/contact information, date of birth, guardian and previous education details, free text, selections, photos, identity documents or certificates and confirmations: collection, saving, resuming and processing an application. Not every school requests every category. |
| Processing | Application/appointment status, assignments, internal notes, document requests, review results, communications, PDFs, file and delivery information: administration, follow-up and accountable human decisions. |
| Progress | Start, form version and step labels, first opened and successfully fully validated steps, submission and last observed activity: resuming applications, identifying problems and improving school workflows. This function does not record individual keystrokes, session video or mouse movements. |
| Events and passes | Event/participant details, booking/ticket identifiers, QR codes, check-in and pass status: registration, admission and optional wallet issuance. |
| Operations and support | Technical connection/request information, times, necessary IP/browser information, error/security events, actor, affected resource and support purpose: reliable operation, abuse prevention, troubleshooting and accountability. |
Schools may request only necessary and lawfully processable information. Required and optional fields depend on the form. Missing necessary information may prevent completion or processing; optional information can be omitted. Sensitive information should be requested and supplied only where necessary and supported by an appropriate legal basis.
Where applicable, account administration and agreed services rely on Article 6(1)(b) GDPR and legal obligations on point (c). Necessary security, abuse prevention and properly assessed product improvement may rely on point (f). Public schools may particularly rely on statutory obligations or public tasks under points (c) or (e). Each school must identify and explain its specific basis and any relevant statutory provision. An operator’s legitimate interest cannot replace the school’s basis.
Special categories, such as health information, additionally require a condition under Article 9 GDPR. Applicable school, civil and privacy law for minors, including any required guardian involvement, must be respected; this notice does not assume a universal age threshold.
Where consent is required, it must be separate, informed, freely given, specific and demonstrable. It can be withdrawn for the future without retrospectively invalidating lawful prior processing. Accepting terms, reading this notice or using the software does not replace required consent. Optional processing must not become an unjustified condition of applying. Engaging a processor does not replace the school’s legal authority or waive individual rights.
An application may be saved as a draft before submission. Information is saved to support continuation and processing. Progress recording internally links the described step metadata to that application without copying answers or documents into the progress history. Schools can see, for example, how many applications reached a step and the furthest observed step of applications not yet submitted.
Each step counts once per application; changed form versions are reported separately. Inactivity means no recently observed activity and does not prove permanent abandonment. Missing histories for older applications are not invented. Demo and test applications are excluded from normal reports. Individual school progress histories are not sent to Fathom. They are not used to judge personal suitability or build student profiles across schools.
Sign-in, sessions, protection against forged requests and any persistent sign-in use necessary cookies and browser state. Lifetimes depend on deployed session settings, persistent sign-in where applicable, logout and browser configuration; persistent sign-in can outlast a simple session. Language, display and filter preferences may be stored in the account or browser.
Form information may also be saved in browser history to restore steps and navigation. This is not a transfer to Fathom. Local availability also depends on the browser and its settings. Server erasure does not automatically remove pre-existing browser, device, export or recipient copies. Optional analytics and provider sign-in are distinct from necessary session functions; applicable requirements for access to terminal information must additionally be respected.
Where a suitable legal basis and contractual safeguards exist and AI review is enabled for the school, selected documents may undergo OCR, document-type recognition, such as identity document or certificate, and formal completeness/consistency checks for human review. This may involve selected documents and visible contents, associated field/document categories and derived findings. Unrelated documents and unnecessary information should be avoided.
Mistral AI receives selected document contents in live OCR; these may contain names, birth dates, grades and other visible information. Jev by TypeSafe AI, Inc. currently receives only reduced check states and categories. Names, emails, images, complete form answers and OCR text are not sent to Jev. Credentials and general payment/usage data are not part of this review. Disabled or simulated checks do not transmit application documents to these AI providers.
School setting and background processing: The school-level permission is technically enabled by default for Pro schools and can be explicitly disabled under Settings → AI & document review. Global restrictions take precedence; a technical default is neither consent nor an independent legal basis. The school must establish the requirements before processing real applications and otherwise disable the permission. Submitted applications and confirmed supplementary documents may trigger background review. Disabling prevents new provider calls; transfers or calls already in progress cannot be recalled. Simulated reviews are labelled accordingly.
Review results and usage records: Review findings and a cache of previously read documents are stored with protection to avoid unnecessarily transferring unchanged files again. They are erased with the associated application; processing already in progress must not restore erased content. Budget controls record provider, model, time, request status, OCR pages, token values actually reported by the provider, and reserved/calculated costs per school and calendar month. Usage records contain no document text, form answers or contact details; the link to the application is removed upon erasure. Minimal cost and audit records may remain for accountable billing, security and legal evidence under the applicable retention criteria. Settings, review jobs and usage changes are logged for these limited purposes.
Human decisions: Results can be incorrect or incomplete. Completeness values describe fulfilled checks, not the person. This integration does not make solely automated admission/rejection or comparable legally significant decisions. Responsible people must review information and evidence; individuals may request correction and human review.
Model training is not an integration purpose and is not commissioned. Before live use, any provider training must be excluded contractually or through account settings, subprocessors approved and international transfers assessed. Neither universal zero retention nor exclusively European processing is promised. TypeSafe may in particular process in the United States. Actual regions, subprocessors and retention depend on the agreed service. Any expanded data scope requires prior legal assessment and notice.
Authorized school users act within their roles. Other schools do not thereby gain access. Particularly privileged operator administrators can inspect a technical overview across schools, including drafts, submitted, accepted, rejected and test applications. The new diagnostics directory initially shows technical metadata without contact details or answers.
Personal diagnostic details require renewed password confirmation and a documented support/troubleshooting purpose. Access lasts 15 minutes for the specific application. Grants and every retrieval are logged with actor and affected resource. Diagnostics are read-only and do not alter or submit applications. A separately authorized school support session may also permit changes within its scope; access and changes remain auditable. This does not authorize arbitrary inspection by all employees.
Permitted purposes include authorized support, necessary troubleshooting, security incidents and assistance with valid privacy requests. Application contents are processed on documented school instructions. General usage analysis, curiosity, advertising and model training do not justify such access. The audit function does not automatically copy complete answers, documents or credentials; separate business communications and review records remain distinct.
Fathom Analytics (Conva Ventures Inc., Canada): If enabled, predefined usage events count activities such as successful form saves, program creation or opening the workflow report. Marketing and administration may use separate projects. These administration and marketing events contain no names, emails, application/school identifiers, free text, documents, original private URLs, search terms or access codes. Only fixed event names and sanitized page categories are forwarded, not individual application histories. Connections necessarily involve technical information such as IP address and browser information. Fathom processes these under its terms and describes its analytics as using no analytics cookies or cross-site visitor profiles. That does not itself establish an exemption from all applicable legal requirements.
The app prevents Fathom on protected applicant form/evidence-upload pages and administrative diagnostics and during privileged support sessions. Optional administration statistics exclude demo/super-admin use and saved objections. Browser Do Not Track and an existing local Fathom block are respected. Signed-in users can object under Profile → Optional usage statistics. This does not disable necessary internal workflow, progress or security records. A browser block setting is stored to enforce the selection. Reliance on legitimate interests requires a documented balancing assessment; where consent is required it must precede activation. New optional app statistics are separately configurable.
Public school portals: A school may enable a dedicated Fathom site for its public admissions and event pages. Reports include visitors, pageviews, trends, source domains, countries, devices and browsers. Sanitized page paths contain public school, program and event identifiers only; query strings, campaign values, private application links and ticket codes are not transmitted. Successful application starts and event bookings may be counted as fixed events. Form contents and contact details are excluded. Analytics is not linked to individual applications or bookings. In consent mode, Fathom loads only after acceptance; the school may disable that mode for a cookieless integration on its documented legal basis. Visitors may change their choice or object under “Analytics preferences”. The choice is stored locally without a visitor identifier for 180 days per school and browser domain. Do Not Track and Global Privacy Control prevent measurement. Private application, document-submission and ticket pages remain excluded. The school is responsible for its integration, legal basis, privacy information and provider agreements.
Support chat (Front): Only when enabled, for signed-in school users on the support page. Name, email, school association, a signed identity confirmation, technical connection information and voluntarily provided messages may reach Front. The widget is not loaded on private applicant portals or super-admin diagnostics. Use the school’s designated channels for personal application matters.
Actual disclosure depends on enabled functionality and school instructions/agreements:
Where providers are processors, suitable Article 28 agreements and proper subprocessor authorization are required. Independent controllers additionally apply their own notices. Transfers outside the EEA require assessment under Articles 44 onward, for example an actually applicable adequacy decision or standard contractual clauses and supplementary measures where needed. Choosing a storage region alone does not replace this assessment. Ask the school about recipients/safeguards in its deployment, or Sushi Dev for operator purposes.
Erasure and individual rights: Schools determine application, draft, event and communication retention based on purpose, processing state and legal obligations. Drafts do not automatically expire merely because they remain unsubmitted. The platform does not impose a universal expiry for every school. Schools must explain their specific periods and initiate required erasure.
Authorized school users can search for a person’s applications within their school and erase selected applications, including answers, progress events, notes, review results and related portal access. Storage-provider file deletion runs in the background with retries; necessary deletion metadata remain until confirmation. Minimal audit evidence may remain without answers, documents or contact information where a necessary purpose or retention obligation justifies it. Shared communications, provider periods, external copies and backups need separate consideration. Required erasures must be reapplied following restoration. Immediate universal deletion of all external copies is not promised.
Account information supports account operations and, where necessary, contractual, security and statutory evidence. Logs, support cases, backups and provider statistics must not be retained longer than their purpose or legal obligation requires. Where no fixed period can be specified, criteria include case completion, troubleshooting/abuse-investigation needs, contractual administration, evidence obligations and agreed provider/backup periods. This notice does not claim that universal automatic log purging or all provider deletions have already occurred. Concrete periods must be documented and implemented for the deployment.
Subject to legal conditions, individuals may request access, correction, erasure, restriction, portability and objection. Processing under Article 6(1)(e)/(f) can particularly be challenged for reasons related to the individual’s situation. Consent may be withdrawn for the future. Schools are the first contact for application/event data; Sushi Dev assists as processor. For independent operator processing contact office@sushi.dev. Appropriate identity checks may be necessary to avoid unauthorized disclosure. Statutory response periods and exceptions apply. Complaints may be made to a competent supervisory authority, including the Austrian Data Protection Authority.
Production uses encrypted transport and access-controlled processing. Form answers and stored AI results are encrypted at application level; searchable contact, status and operational information is access-controlled and not automatically encrypted in the same manner. Roles, school boundaries, time-limited privileged access and audit evidence limit disclosure. Absolute security cannot be guaranteed. Internal keys, credentials, network addresses and security-sensitive configuration details are not published in this notice.
New purposes, recipients and significant processing changes require appropriate prior notice and legal assessment. Wording changes do not retrospectively expand earlier consent.
Updated: 30 October 2026. Provider information: Fathom DPA, DigitalOcean DPA, Front DPA, Postmark DPA, Mistral DPA, TypeSafe DPA.