Details arrive through deliberate actions on your part. When you complete an inquiry form, those fields — name, email, sometimes a phone number — become part of our records. If you register for educational content or programme information, additional elements may emerge: your current financial situation context, learning objectives, perhaps professional background if you choose to share it.
Technical data accumulates passively. Your browser announces itself through standard protocols: device type, operating system, IP address, pages visited on our domain. This happens automatically during any website interaction and helps us understand traffic patterns, identify technical issues, and maintain system security.
Payment details never rest on our infrastructure. When financial transactions occur, card numbers and banking particulars flow directly to payment processors operating under their own security frameworks. We receive confirmation codes and transaction records, but the sensitive payment mechanisms themselves bypass our systems entirely.
Communication Records
Email exchanges, support ticket conversations, phone call summaries — these accumulate as part of service delivery. If you write to us asking about programme structure or financial discipline methodologies, that correspondence becomes part of your client record. The content helps us provide coherent, continuous support rather than treating each interaction as isolated.
Learning Platform Interactions
Should you enroll in structured programmes, additional data emerges. Progress through modules, time spent on resources, assessment responses — this operational information helps us understand engagement patterns and identify where additional support might prove valuable. It serves pedagogical purposes rather than surveillance objectives.