How consent is given
Consent version 2026-09-10-v1 is given by a separate explicit action: the user actively selects an unchecked checkbox before creating an account. Merely continuing registration, opening a page, or using the site is not treated as this consent.
Data covered by registration consent
Account data: name, email, generated username, settings, and account identifier.
Learning data: selected route, progress, quiz answers, task submissions, assessment results, and related learning states.
Technical data necessary for account operation, security, and abuse prevention: session identifiers, technical logs, and account-linked security events to the extent required for those purposes.
Purposes
Creating and maintaining the NativePath account, authentication, and account recovery.
Providing courses, preserving learning progress, assessing tasks, and presenting the next learning step.
User support, account security, abuse prevention, and compliance with the operator's legal obligations.
Processing operations
For these purposes the operator may collect, record, organize, accumulate, store, update, retrieve, use, disclose to authorized processors where a lawful basis exists, block, delete, and destroy personal data by automated and non-automated means.
Consent evidence
When a new account is created, NativePath stores a server-side record containing the user identifier, document version 2026-09-10-v1, confirmation method «explicit_checkbox», registration surface, language, and server record time. The account and this record are created in one transaction.
Withdrawal and requests
Consent may be withdrawn by contacting the operator at the legal email shown on this page. Withdrawal does not invalidate processing that has another lawful basis after withdrawal, while processing based specifically on consent must stop to the applicable extent.