How Kenzlab’s apps and this website handle your data.
These pages use static HTML and CSS. They include no analytics, third-party fonts, or data-entry form. The email link opens your mail app; the website does not receive the message.
EduFlow keeps a local database on your device.
On your phone, your classes, students, attendance, grades, plans, and journal are kept in an encrypted database. Its key stays in the phone’s secure key storage. When you sign in, these records also sync to your EduFlow account. Student records hold what you enter or import from Massar, such as names, the Massar ID and, if you add them, parent contact details.
Glood keeps a local database on your device.
On your iPhone, Glood keeps your rides and their GPS tracks, saved routes, GPX files, and settings. Your sign-in is kept in the iOS Keychain. When you sign in, your rides with their GPS points, GPX files, profile, bikes, training zones, plans, and workouts sync to your Glood account. Sensor readings sync as ride summaries, such as average and maximum heart rate, power, and cadence.
Both apps’ Supabase projects are hosted in the eu-west-1 region.
Supabase holds your account, records, and uploaded files for both apps. Neither app includes analytics, advertising, or third-party crash-reporting tools. EduFlow error reports go to EduFlow’s own database and contain technical details, such as the error, app version, and device model. Glood also asks a few services for what it needs to show a ride. Map tiles come from OpenStreetMap, and road and elevation data from the Overpass and Open Topo Data services, requested by map area. Weather comes from OpenWeatherMap, which receives the ride’s location, but only if you add your own OpenWeatherMap key. Apple Health is used only with your permission. The web dashboard draws its maps with CARTO.
EduFlow and Glood have access rules switched on for every table in their online databases.
The database checks who is signed in before it returns a personal record, so your classes, students, rides, and plans are visible only to your own account. Some reference data is shared with every signed-in user and holds no personal records. For EduFlow, that is the curriculum, subjects, and school calendar. For Glood, it is route segments; when an account is deleted, its segments stay but lose their link to the rider. As the operator of both apps, Kenzlab can access the databases to run and support them.
An account-deletion request starts a 30-day grace period. You can cancel while the request is pending.
Choose Delete Account in the app’s account settings, or in Settings on the web dashboard. Until the 30 days are up, Restore Account in either place cancels the request. After that, a daily job removes your rides, routes, files, profile, and sign-in. You can also delete a single ride at any time.
You can archive a class or delete a student in the app. Deleted items go to a trash, where you can restore them.
EduFlow does not yet have in-app account deletion. To delete your account and its records, email [email protected].
The planned EduFlow features would use curriculum and plan structure, excluding student names, grades, and attendance. The planned Glood coach would use the rider’s own history and training plan. These features are planned and are not available today.