Sabonex
Apps Approach About
EN DA
SchoolOpS ↗
Privacy / SchoolOpS

Privacy in SchoolOpS.

This notice describes the current SchoolOpS V1 direction: school information is processed locally, the user reviews the result before saving, and only approved structured information is retained.

Last updated 27 September 2026 Contact info@sabonex.com Publisher Steffen Aspe Brand SABONEX
Scope Local data & purposes Import & OCR Calendar, tasks & timetable Permissions & device access Tracking & security Retention Deletion Rights & contact Changes
01 / Scope

Who is responsible and what this notice covers.

This privacy notice applies to the SchoolOpS iOS app published by Steffen Aspe under the SABONEX brand. In this notice, references to SABONEX mean Steffen Aspe operating under that brand.

For personal data that SABONEX actually receives or otherwise controls — for example support correspondence — Steffen Aspe is the data controller. SchoolOpS V1 itself is local-first, requires no SchoolOpS account, and has no SchoolOpS backend or cloud synchronization of the user's school data.

Visits to this page or the wider SABONEX website are covered separately by the SABONEX website privacy notice.

02 / Local data & purposes

Approved planning data is stored locally for specific app functions.

SchoolOpS can store the following structured information in app-owned local files and settings:

  • Child profile name and optional class label — used to identify profiles and connect approved planning items and timetables to the correct child.
  • Local adult names — used only where the app needs to show or assign practical responsibility inside the household workflow.
  • Approved events, tasks, packing lists and history — used to provide the in-app planning, task, packing and history features.
  • School timetables — used to show the weekly timetable and current/next lesson for the relevant child.

Child relationships use stable local identifiers, so renaming a child does not reassign existing data. The current V1 architecture does not send a server copy of this structured SchoolOpS data to SABONEX.

03 / Import & OCR

Photos, PDFs and source text are temporary working material.

You can choose to import school information from the camera, photos/screenshots, PDF files or pasted text. OCR and interpretation run locally on the device using Apple platform frameworks, including Vision and PDFKit.

Raw images, PDF content, full OCR text and pasted source text are working data during import and mandatory review. They are not sent to a SchoolOpS server or external cloud-AI service.

Only after you review and approve an import does structured planning information become authoritative. The raw image/PDF/full OCR or pasted source is not persisted as part of the approved case. Cancelled or replaced import sessions use cancellation/generation safeguards so late asynchronous results cannot repopulate abandoned raw working data.

04 / Planning

Calendar, tasks and timetables stay in SchoolOpS.

The SchoolOpS V1 calendar and tasks are internal app features. They are not sent to Apple Calendar or Apple Reminders.

Active OS notifications/reminders are not part of the current V1. School timetables are imported, reviewed and stored locally in the app.

05 / Permissions & device access

SchoolOpS asks for access only when a chosen feature needs it.

If you choose to photograph school information or a timetable, SchoolOpS asks for camera access. The camera usage description states that the image is processed locally on the device.

Photos and files are selected through Apple's system picker interfaces. The current Xcode configuration does not request location access, Apple Calendar access, Apple Reminders access or notification permission for V1.

06 / Tracking, services & security

No advertising, behavioural tracking or cloud-AI fallback.

SchoolOpS V1 has no advertising network, behavioural tracking, child accounts, SchoolOpS backend, external analytics SDK or external cloud-AI service for processing school material. The current Xcode project has no external package dependency for such a backend or analytics service.

Approved structured data is kept inside the app's local container in app-owned files/settings. Protection therefore relies on iOS app sandboxing and the security of the user's device. Depending on the user's Apple device and backup settings, Apple device backup/restore may include app data; such backups are handled by Apple and are not received or controlled by SABONEX.

07 / Retention

Retention follows the type of information.

Raw import material: source images, PDF contents, full OCR text and pasted source text are temporary working data and are not retained in an approved case.

Approved structured data: child profiles, planning items and timetables remain in SchoolOpS's local storage until you edit or delete them or use the delete-all-local-data function.

Device backups: copies that may exist in an Apple device backup are governed by the user's Apple backup settings and Apple's own retention processes.

Support email: correspondence is kept while a matter is active and afterwards only while there is a reasonable need for follow-up, security, documentation, dispute handling or legal obligations. Messages are deleted when those purposes no longer apply.

08 / Deletion

V1 supports targeted deletion and a durable delete-all flow.

SchoolOpS supports permanent deletion of items including tasks, case content, packing lists, complete cases, individual lessons and complete school timetables.

The app also includes a controlled function to delete all SchoolOpS-owned local user data. The reset uses a durable recovery design so an interrupted reset or relaunch continues toward the empty state instead of silently restoring old local data.

Because the current V1 architecture has no SchoolOpS backend copy of these local data, there is no corresponding SchoolOpS server profile for SABONEX to erase remotely.

09 / Rights & contact

Your privacy rights and choices.

You control SchoolOpS's locally stored data through the app's edit and deletion functions. Because SABONEX does not receive a server copy of those local app data, SABONEX cannot remotely access, export or delete them on your behalf.

For personal data that Steffen Aspe/SABONEX actually holds, such as support correspondence, applicable privacy law may give you rights including access, correction, deletion, restriction, objection and, where applicable, data portability.

Support correspondence is processed to answer the request, troubleshoot the app and keep necessary follow-up or records. Depending on the context, this may be based on steps requested by you or performance of an agreement, legitimate interests in providing and securing support, or a legal obligation.

Privacy questions or requests can be sent to info@sabonex.com. You may also have the right to complain to the competent data protection authority where you live or work, or where an alleged infringement occurred. In Denmark, the supervisory authority is Datatilsynet.

10 / Changes

If SchoolOpS changes its data handling, this page will be updated.

This notice describes the current V1 architecture. If a later version adds accounts, backend/cloud sync, cloud AI, external integrations, analytics, advertising, payments or other material data sharing, the privacy notice and relevant App Store information will be updated accordingly.

SchoolOpS is still in development, and this page must be reviewed again before public release.

Sabonex

SchoolOpS · iOS · Privacy

© 2026 SabonexSchoolOpSWebsite privacyEmail