How Details Arrive in Our Systems
Information reaches us through distinct channels. When you complete an enrolment form for one of our financial modelling courses, you provide identifying elements directly — name, email address, phone number if you choose to share it, and sometimes your current role or industry. This occurs at the moment you submit that form.
Beyond that initial interaction, we derive additional context from how you move through our platform. If you browse course syllabi, download sample materials, or watch introductory videos, those actions generate technical markers: IP address, browser type, the time you accessed certain pages. These markers emerge automatically from the interaction between your device and our servers.
Payment details arrive when you purchase a program. We don't hold full card numbers — those pass through our payment processor's infrastructure. What remains with us is transaction confirmation data: purchase date, amount paid, and a reference identifier that links back to your enrolment record.
Some details come to us through correspondence. When you email our support team or fill out a feedback form after completing a module, that communication contains whatever you've chosen to include — questions about Excel techniques, concerns about pacing, requests for additional resources. Those messages stay in our support system until the matter is resolved, and sometimes longer if they inform how we improve course content.
Operational Necessities Behind Data Handling
Every piece of data serves a function tied to delivering financial modelling education effectively. Your email address allows us to send enrolment confirmations, course access credentials, and updates when new modules become available. Without it, we couldn't provide you with what you've paid for.
Technical markers tell us which parts of our platform cause confusion or friction. If many participants abandon the registration process at a particular step, that pattern — visible through aggregated session data — signals a design flaw we need to address. Individual browsing paths help us understand whether our content structure makes sense or creates unnecessary obstacles.
Payment records fulfill legal obligations around taxation and financial reporting. They also protect both parties if disputes arise about what was purchased or when. Transaction histories provide an audit trail that Australian tax regulations require us to maintain.
Communication records exist so that when you contact us about a technical issue or curriculum question, whoever responds has context. If you emailed us two weeks ago about difficulty accessing a particular spreadsheet template, the person handling your follow-up inquiry can see that history and avoid making you repeat yourself.
Movement Beyond Our Direct Control
Certain operational requirements force data to leave our immediate environment. Payment processing happens through a third-party financial service provider. When you enter card details, that information travels directly to their secure systems — we never see the complete number. They return a confirmation token we store instead.
Email delivery relies on an external messaging platform. When we send you course materials or notifications, your email address and the content of that message pass through their infrastructure. We've selected providers who operate under strict confidentiality agreements, but the data does physically reside on their servers during transmission and for a short retention period afterward.
Hosting our learning platform requires cloud infrastructure. The servers storing course videos, downloadable templates, and your progress records sit in data centers operated by a hosting company. Those facilities are located in Sydney, and the company managing them adheres to Australian privacy standards, but they technically have access to the stored information even though contractual terms prohibit them from examining it.
Legal demands occasionally compel disclosure. If a court order arrives requiring us to produce records related to a specific enrolment, we must comply. This has happened twice in our operating history, both times involving financial disputes unrelated to our educational services but where our transaction records served as evidence.
We don't sell participant lists to marketing firms, we don't share enrolment data with recruitment agencies, and we don't provide your contact details to other educational organizations. Those practices would violate the trust underpinning your decision to learn with us.
Protection Measures and Remaining Risks
Our systems employ encryption both for data traveling between your device and our servers, and for sensitive information at rest in our databases. Access to participant records is restricted through role-based permissions — course administrators see enrollment details, but technical staff maintaining server infrastructure work with anonymized identifiers during troubleshooting.
Backups run automatically, creating copies stored separately from production systems. If our primary database suffered corruption or loss, we could restore from those backups. But that redundancy means your information exists in multiple locations, increasing surface area for potential exposure.
Despite these safeguards, risk persists. A sophisticated intrusion could bypass our defenses. A staff member might accidentally misconfigure access permissions. A backup drive could be physically lost during a data center migration. We work to minimize these probabilities through training, audits, and careful vendor selection, but absolute security remains impossible.
When security incidents occur elsewhere in our industry, we study them. After a major education platform experienced a breach in late 2024, we audited our authentication protocols and added additional verification layers for administrative access. Continuous improvement happens, but so does the evolution of threats.
Your Influence Over Held Information
You can request a copy of what we hold about you. That request goes to our support address, and we typically fulfill it within seven business days. You'll receive a structured document listing your enrolment details, payment history, support communications, and any notes our team has added to your account record. Technical logs get summarized rather than delivered in raw form since they contain system noise that wouldn't mean much out of context.
Corrections work similarly. If your professional circumstances change and you want your listed job title updated, or if we've misspelled your name, tell us and we'll amend the record. Some details can't be altered retroactively — payment amounts and dates stay fixed because they reflect historical transactions — but identifying information remains flexible.
Deletion requests present complexity. If you've completed a course, we need to retain proof of that completion for credential verification purposes. Prospective employers sometimes contact us to confirm that a candidate genuinely finished our financial modelling program, and we can't provide that confirmation if we've purged all records. But we can suppress your contact details, removing your email address and phone number while preserving the fact that someone with your name completed specific coursework on certain dates.
If you're currently enrolled and want everything removed immediately, we can do that, but it will terminate your access to course materials. We'll issue a prorated refund according to how much content you've consumed, then scrub your account. That action is irreversible — reënrolling later would mean starting fresh rather than picking up where you left off.
Marketing communications carry separate controls. At the bottom of every course update email or newsletter, there's a link to adjust preferences or unsubscribe entirely. That change takes effect within 48 hours. You'll still receive essential transactional messages — receipts, access credential reminders, notifications about platform maintenance that might affect your ability to access materials — but promotional content stops.
Retention Duration and Eventual Removal
Different data categories follow different schedules. Active enrolment records — the information needed to deliver your current course — persist for as long as you have access to that course, typically twelve months from purchase date. After that access period expires, if you haven't reënrolled or purchased additional content, the account enters a dormant state.
Dormant accounts retain core identification details and completion records for seven years. This duration aligns with Australian financial record-keeping requirements and allows for credential verification if you need proof of completion years after finishing a program. Contact information gets purged after three years of inactivity unless you've specifically opted in to ongoing communications.
Payment records stay for seven years regardless of account status. Tax compliance demands this. Transaction details older than that threshold get archived to offline storage, then eventually deleted once they age beyond any conceivable audit or dispute window.
Support correspondence follows a shorter cycle. Once a query is resolved, the thread stays accessible for six months in case the issue resurfaces. After that, we extract any insights that might improve our materials or processes, then remove the personal elements while retaining anonymized summaries. "Participant reported confusion about discount rate calculation in Module 4" becomes a note in our content improvement backlog; your name and email address disappear from the record.
Technical logs get purged aggressively. Session data typically survives only 90 days unless it's flagged for security analysis. Server logs older than a year get deleted entirely. We keep these windows short because the operational value diminishes rapidly, and longer retention just increases exposure with no corresponding benefit.
