Information Emergence and Capture

Details arrive at Fymtron through three distinct pathways, each tied to a specific stage of your interaction with our Unreal Engine mobile game development programs.

Registration and Account Formation

When you decide to join one of our learning programs, we ask for identifying elements necessary to establish your participation. You provide a full name, email address, and phone contact. This intake happens during signup and gets stored immediately in our learner management infrastructure.

The email becomes your primary communication channel. We send course updates, schedule adjustments, and administrative notices through it. Your phone number serves as a backup contact method when urgent coordination is needed.

Payment Processing

Enrollment in our courses involves financial transactions. We obtain billing address and payment confirmation details, though sensitive card numbers never touch our servers directly. External payment processors handle that layer, and they operate under separate agreements.

What we do receive: transaction identifiers, payment dates, amounts transferred, and invoice references. This record-keeping serves both operational needs and Romanian accounting requirements.

Learning Activity Records

As you progress through coursework, our platform automatically captures participation patterns. Login timestamps, module completion status, assignment submissions, and forum contributions all generate records that help instructors gauge your engagement level.

These activity logs don't require explicit input from you. They emerge naturally from platform usage and feed into progress tracking systems that shape how we support your development.

Purpose Alignment and Functional Dependencies

Every category of information we gather connects to specific operational requirements. Nothing gets collected purely for potential future utility.

Instructional Delivery

Your contact information makes it possible for instructors to send personalized feedback on projects, notify you about live coding sessions, and coordinate one-on-one technical consultations. Without these details, the interactive dimension of our programs collapses.

Activity records inform how instructors adjust pacing. If completion patterns suggest certain Unreal Engine concepts are causing widespread confusion, curriculum gets modified. Your usage fingerprint contributes to that adaptive mechanism without requiring direct survey participation.

Administrative Continuity

Program enrollment depends on accurate billing. Payment records verify your active status and determine access windows for course materials. When disputes arise, transaction logs provide the reference point for resolution.

Your address enables invoice generation that meets Romanian VAT reporting standards. Tax authorities expect geographic precision, and compliance failures create legal exposure we can't accept.

Technical Support Operations

When you submit help requests about platform access issues or content delivery problems, support staff pull your account details to diagnose root causes. Login history reveals whether authentication is failing. Device information shows compatibility gaps. Response effectiveness depends entirely on having this diagnostic context available.

Information Movement Beyond Organizational Boundaries

Certain operational necessities force information to leave our direct control, though always through carefully structured channels.

Payment Infrastructure Partners

Transaction processing requires collaboration with external payment gateways. When you pay course fees, your billing details flow to these processors who validate cards and authorize transfers. We select partners based on their security certifications and contractual commitments to restrict usage.

These entities can't repurpose your payment information for unrelated marketing. Agreements explicitly prohibit that, and we audit compliance periodically.

Romanian Legal Obligations

Tax authorities may request enrollment and billing records during audits. When legal demands arrive through proper channels, we comply by disclosing only the specific details required by the formal request. Broad fishing expeditions get challenged through appropriate legal procedures.

Service Continuity Providers

Our learning platform runs on third-party hosting infrastructure. Server operators technically can access stored information, but contracts impose strict confidentiality duties and usage restrictions. They function as data processors under our instruction rather than independent controllers.

Email delivery services transmit course communications. These providers see recipient addresses and message content but face the same contractual limitations as hosting partners.

No marketing aggregators, advertising networks, or data brokers receive anything. We don't monetize learner information through sales to external parties.

Retention Duration and Disposal Triggers

Information doesn't accumulate indefinitely. Different categories have distinct shelf lives based on their purpose.

Active Enrollment Period

While you're participating in a program, all collected details remain accessible. Instructors need full visibility into your progress, and you need continuous platform access.

Post-Completion Window

After program completion, your account enters an extended retention phase lasting eighteen months. This window accommodates alumni who want to revisit course materials or request certification verification.

During this phase, login credentials stay valid but marketing communications cease unless you explicitly opt back in.

Legal Retention Requirements

Romanian tax law mandates seven-year retention of financial records. Even after we delete your learning activity logs and contact details, billing documents persist in isolated accounting archives. These records contain minimal personal specifics—mostly transaction amounts and dates.

Deletion Process

When retention periods expire, automated purge routines remove records from production databases. Backup systems get cleared during subsequent rotation cycles. The entire elimination process completes within ninety days of the retention deadline.

If you request early deletion, we initiate removal immediately for categories not subject to mandatory retention. Financial records stay until legal minimums are satisfied.

Control Mechanisms and User Authority

Multiple intervention points exist where you can examine, modify, or restrict how we handle your details.

To exercise these controls, email help@fymtron.com with your request and account identifier. We verify identity through security questions before processing sensitive changes.

If you believe we've mishandled your information or violated applicable regulations, Romanian data protection authorities provide an escalation path. You can lodge complaints with ANSPDCP, which has jurisdiction over organizations operating within Romania.