Last Updated: June 1, 2026
This document details how we handle database object strings collected via school instances. In accordance with strict COPPA and GDPR safety directives, minor students have no individual autonomous account footprints; all minor identifying data fields (Names, birthdates, course enrollment records) are stored secondary to a primary verified parent/guardian data profile instance.
We process information submitted during instance registration: Administrative Emails, Guardian telephone entries, structural currency targets, system translation parameters, and uploaded application setup image properties configuration tokens.
Financial metrics, validation hashes, and address checks are shared safely directly with our authorized merchant of record, Paddle.com, to ensure secure handling and fraud protection monitoring during active checkout executions.
Users can invoke structural data erasure configurations. When an adult profile is deleted, all linked minor student tracking variables, historical invoices, and attendance logs are cleared immediately from production caches to safeguard data integrity.