Tracking Technology Information

This document explains how Nyqorth Zyr collects information through various digital tracking mechanisms when you visit our educational platform. We believe in transparency about the technologies we use and want you to understand both the practical benefits they provide and your choices regarding their use.

Our platform relies on several different types of tracking technologies to deliver personalized learning experiences, maintain course progress, and continuously improve our educational offerings. While some of these technologies are essential for the basic functioning of our website, others help us understand how students interact with course materials so we can make informed decisions about content development and platform enhancements.

Why We Use Tracking Technologies

Tracking technologies are small data files and scripts that websites place on your device or use to recognize your browser when you visit. Think of them as digital bookmarks that help websites remember who you are and what you were doing during your last visit. For an online education platform like ours, these technologies serve multiple purposes—from something as simple as keeping you logged in between sessions to more complex functions like adapting course content based on your learning pace and preferences.

The most basic category we use consists of strictly necessary technologies that make our platform functional. Without these, you wouldn't be able to log into your account, navigate between course modules, or complete assessments. When you start a video lecture and then navigate away to take notes, these technologies remember your playback position so you can resume exactly where you left off. They also maintain your shopping cart if you're browsing course offerings, ensure that form submissions work correctly when you submit assignments, and enable our platform to recognize whether you're a registered student or a visitor browsing our course catalog.

Beyond essential functions, we deploy technologies that enhance your overall learning experience through personalization and preference management. These remember your interface settings—like whether you prefer dark mode for late-night studying, your chosen subtitle language for video content, or how you've organized your course dashboard. If you've customized your learning path or bookmarked specific lessons for later review, these technologies preserve those choices across sessions. They also power features like recommended courses based on your completed classes and learning history, which many students find helpful for discovering relevant content they might otherwise miss.

Our analytical technologies collect aggregated data about how students interact with our platform, which directly informs our development priorities and content improvements. We examine patterns like which course sections students replay most frequently (suggesting those topics need clearer explanation), where students commonly drop off in longer video lectures (indicating we should break that content into shorter segments), and which assessment formats correlate with better learning outcomes. This information helps our instructional designers refine course materials and guides our technical team in identifying performance bottlenecks that might frustrate learners trying to access content.

For certain features, we use customization technologies that allow us to present educational content in ways that match individual learning styles and goals. If you've indicated an interest in data science careers, for example, our platform might highlight relevant case studies within your current coursework or suggest complementary courses in statistics or programming. These technologies also support A/B testing—where we show different versions of course presentation formats to different student groups to determine which approach produces better educational outcomes before rolling changes out platform-wide.

The data we gather through these various technologies benefits both you and our educational mission in concrete ways. Students get a smoother, more intuitive learning experience with features that adapt to their needs, while we gain insights that directly improve course quality and platform reliability. When we notice through analytics that mobile students struggle with a particular assignment format, we can redesign it for better touchscreen compatibility. When preference data shows us that most students in a particular region access content during specific hours, we can schedule server maintenance to minimize disruption.

Restrictions

You have substantial control over how tracking technologies function on your device, backed by various data protection frameworks including GDPR in Europe and similar regulations worldwide. These frameworks recognize your right to know what data is collected, why it's collected, and to make informed decisions about which non-essential technologies you'll accept. Educational platforms like ours must respect these rights while explaining the practical trade-offs involved in certain choices.

Most modern browsers give you direct control through their settings menus. In Chrome, you'll find these options under Settings > Privacy and Security > Cookies and other site data, where you can block third-party trackers or clear existing data. Firefox users should navigate to Settings > Privacy & Security and select from several strictness levels for tracking protection. Safari on Mac offers controls under Preferences > Privacy, including an option to prevent cross-site tracking by default. Edge users can access similar settings through Settings > Cookies and site permissions. Each browser also lets you view and selectively delete existing stored data, and you can typically set exceptions for specific sites you trust.

On our platform itself, we provide a preference center where you can manage technology categories independently. When you first visit our site, you'll see a banner allowing you to accept all technologies or customize your choices. Through the customization interface, you can enable essential functions while declining analytics or personalization features. We've designed this system to remember your preferences across sessions, though you can return to modify your choices at any time through the privacy settings link in your account dashboard.

Rejecting certain technology categories will affect your experience in specific ways. If you disable functional technologies, you'll lose personalized features like saved course preferences, customized dashboard layouts, and your history of recently viewed content—meaning you'll need to manually navigate to courses each time rather than seeing them highlighted based on your progress. Blocking analytical technologies won't affect your ability to access course content, but it prevents us from identifying technical problems you might encounter or understanding which teaching approaches work best. Refusing customization technologies means you won't receive personalized course recommendations, though you can still browse and enroll in any course through our catalog search.

Some privacy-conscious students prefer to use browser extensions or VPN services alongside selective technology acceptance. This approach can work well if you enable essential and functional categories on our platform while using browser-level tools to block third-party trackers from other sites. You might also consider using privacy-focused browsers like Brave, which block many tracking mechanisms by default while still allowing first-party functionality necessary for websites to work properly.

Making these decisions involves balancing your privacy preferences against the learning experience you want. A student who values comprehensive privacy might accept only essential technologies and navigate some inconveniences like re-entering preferences or missing personalized recommendations. Another student might prefer the smoother experience that comes with accepting most technologies, particularly if they're primarily concerned about third-party advertising networks rather than their educational platform's own analytics. We encourage you to experiment with different settings to find the balance that feels right for your situation—you can always adjust these choices as your needs or comfort level changes.

Further Considerations

Our retention approach varies depending on the type of information and its purpose. Essential session data typically expires when you close your browser or after a set period of inactivity (usually 30 minutes to maintain security). Preference data that remembers your interface customizations may persist for up to one year, after which you'd need to reset your choices if you return. Analytical data gets aggregated and anonymized within 90 days, at which point we can't connect it back to individual users even if we wanted to. When you request account deletion, we remove all associated tracking data within 30 days, though we may retain minimal information in aggregated form for historical statistics.

We protect collected data through multiple security layers including encrypted transmission protocols (TLS 1.3 or higher), encrypted storage for sensitive information, and strict access controls limiting which team members can view raw data. Our technical infrastructure undergoes regular security audits, and we've implemented monitoring systems that alert us to unusual access patterns. On the organizational side, all staff members with data access receive privacy training and sign confidentiality agreements, while our data handling procedures are documented and regularly reviewed by our compliance team.

Sometimes we combine tracking data with other information sources to create a more complete understanding of the learning experience. For instance, we might correlate course completion patterns (from tracking data) with assessment scores (from our learning management system) to identify whether students who watch lectures at certain times of day perform differently on quizzes. We also integrate tracking data with support ticket information to understand whether students reporting technical issues share common browsing patterns that might point to underlying platform bugs. Any such integration happens only with data you've already provided to us through various aspects of using our service.

Our data practices comply with multiple regulatory frameworks depending on where you're located. For European students, we adhere to GDPR requirements including lawful basis for processing, data minimization principles, and your various rights around access and deletion. Students in California benefit from CCPA protections, which grant similar rights regarding data transparency and control. Educational records containing personally identifiable information receive additional protections under laws like FERPA in the United States. We regularly review our practices against emerging regulations in other jurisdictions to ensure broad compliance.

International students should know that our servers are located in multiple regions, and your data may be processed in a country different from where you're accessing our platform. For data transfers outside your home jurisdiction, we rely on approved mechanisms like Standard Contractual Clauses (recognized under GDPR) and conduct transfer impact assessments to verify adequate protection. Students in regions with particularly strict data localization requirements may find their data processed on region-specific servers—we'll indicate this during account creation if it applies to your location.

External Technology Providers

We work with several categories of external service providers who may deploy their own tracking technologies through our platform to deliver specialized functions. These include content delivery networks that cache course videos for faster playback worldwide, analytics services that help us understand aggregate usage patterns with more sophisticated tools than we could build internally, payment processors who handle secure transaction processing for course enrollments, and customer support platforms that power our live chat and ticketing system. Each provider category serves specific purposes that enhance the educational experience or enable core business functions.

The data collected by these partners varies by their function. Analytics providers typically gather information about page views, session duration, navigation paths through our site, device characteristics (like screen size and browser type), and general geographic location at the city level. Payment processors collect transaction details and may use fraud detection technologies that analyze purchase patterns—though sensitive payment information never passes through our servers directly. Content delivery networks log technical details about video playback including bandwidth usage, buffering events, and playback quality to optimize streaming performance. Support platform providers can see your conversation history with our team and may note which pages you were viewing when you initiated contact.

These external providers process data according to their service agreements with us, which strictly limit how they can use information collected through our platform. Our contracts prohibit them from using your data for their own marketing purposes or sharing it with other companies. When you watch a course video delivered through a content network, for instance, that provider optimizes delivery but can't build an advertising profile about you or sell insights about your viewing habits to third parties. We periodically audit our providers' compliance with these restrictions and maintain the right to terminate relationships if we discover misuse of data.

You have some control over external provider technologies through the same mechanisms described earlier—browser settings and our preference center. Blocking third-party technologies in your browser will typically prevent external analytics and marketing tools from functioning, though it might also interfere with content delivery or payment processing that relies on external services. Our preference center lets you reject analytics providers while still accepting those necessary for core functions like video playback and payment processing. For specific providers, we can often provide direct opt-out links if you want to block a particular service across all websites that use it, not just ours.

Our agreements with data processors include specific contractual safeguards that extend your privacy protections to their operations. These contracts specify the exact purposes for which providers can process data, require them to implement appropriate security measures, mandate that they delete data when no longer needed for the specified purpose, and obligate them to notify us of any data breaches promptly. For providers handling particularly sensitive information or large volumes of data, we conduct due diligence reviews of their security practices and may require third-party certification or audit reports before entering into agreements.

Alternative Technologies

Beyond traditional browser technologies, we use several supplementary methods to collect information about how students interact with our platform. Web beacons (also called tracking pixels or clear GIFs) are tiny transparent images embedded in web pages or emails that notify us when content is loaded. On our platform, we primarily use these in email communications to understand which messages students open and which links they click, helping us refine our communication strategy to focus on information students find most valuable. These beacons typically collect your IP address, the time you viewed the content, and the type of device you're using.

Local storage and session storage are browser features that let us store more complex data structures on your device than traditional methods allow. We use session storage for temporary information that shouldn't persist after you close your browser—like the current state of a multi-step assignment you're completing or the answers you've entered in a practice quiz before submitting. Local storage holds data that should survive between sessions, such as your interface customization preferences, course bookmarks, or the list of courses you've recently viewed. This data remains on your device until either our code deletes it or you manually clear it through browser settings, and unlike some older technologies, storage data can hold more detailed information about your learning activities.

Device recognition involves analyzing various technical characteristics of your device to create a probability-based identifier even without traditional tracking files. We might look at your browser version, installed fonts, screen resolution, timezone, language preferences, and graphics card specifications—individually these are common, but the specific combination becomes relatively unique. We use this technique primarily for security purposes, like detecting when your account might be accessed from an unfamiliar device or identifying bot traffic that might threaten platform stability. The accuracy of this method varies considerably, and it becomes less reliable as device configurations change with software updates.

Our web servers automatically log certain technical information whenever you connect to our platform, which is standard practice across virtually all websites. These logs capture your IP address, the date and time of your request, which page you requested, the address of the previous page if you followed a link to reach us, your browser and operating system details, and whether the request succeeded or encountered an error. We retain these logs for approximately 90 days for security monitoring and technical troubleshooting. If our platform goes down or students report errors, these logs help our engineering team diagnose the problem by showing exactly what happened leading up to the issue.

Managing these alternative technologies requires different approaches than blocking traditional browser storage. For email beacons, most email clients let you disable automatic image loading, which prevents the beacon from reporting back—though this affects all images in emails, not just tracking pixels. Local and session storage can be cleared through the same browser privacy settings where you manage other site data, and some browsers let you block storage for specific sites while allowing it for others. Device recognition is harder to control since it's based on legitimate technical information your browser shares to display web content properly, though using privacy-focused browsers or browser extensions can limit the amount of identifying information transmitted. Server logs are necessary for basic website operation and security, so you can't opt out of this logging, but the information collected is technical rather than personal and gets deleted relatively quickly.

Policy Updates

We review this document at least annually to ensure it accurately reflects our current technology practices, and we make updates whenever we introduce new tracking methods or significantly change how we use existing ones. Changes might be triggered by the adoption of new analytics tools, modifications to third-party service providers, updates to regulatory requirements in jurisdictions where we serve students, or shifts in our product features that require different data collection approaches. Our legal and privacy teams collaborate on these reviews to ensure the documentation remains both accurate and compliant with evolving standards.

When we make substantive changes to this policy, we'll notify you through multiple channels. Registered students will receive an email to the address associated with their account at least 14 days before changes take effect, giving you time to review the modifications and adjust your preferences if needed. We'll also display a prominent notice on our platform homepage and in your account dashboard when you log in. For significant changes that materially affect your rights or substantially expand our data collection practices, we may ask you to review and acknowledge the updated policy before continuing to use certain platform features.

Previous versions of this document are archived and available upon request, though we don't publish a comprehensive version history publicly due to the administrative burden involved. If you need to review an older version—perhaps because you're investigating when specific practices began or researching how our policies have evolved over time—contact our privacy team with your request, including the approximate date range you're interested in. We maintain archives going back three years and can typically provide copies within five business days.

Not all modifications warrant individual notification. Minor updates might include clarifying existing explanations without changing actual practices, updating links to external resources, correcting typographical errors, or making small wording adjustments to improve readability. More significant changes requiring notification would include adding new categories of tracking technologies, extending data retention periods, sharing data with new categories of third-party providers, or expanding the purposes for which we process your information. We use the "effective date" at the top of this document to indicate when the current version took effect, and the presence of a new effective date signals that some modification has occurred since your last review.