Cookies Policy

Last updated: 23 September 2026.

What cookies and similar technologies are

Cookies are small text files placed on your device when you visit a website. They store information such as your preferences, login details, or browsing behaviour. Similar technologies include web beacons, pixels, and local storage that can access or store data on your device. These tools help websites function properly and gather insights without requiring you to re-enter information each time you visit.

Why the site uses them

codezenly uses cookies to deliver programming course materials reliably, remember user progress through lessons, analyse traffic patterns for course improvement, and support essential commercial operations. Without these technologies the platform could not maintain secure sessions, personalise learning paths, or measure how learners interact with tutorials and exercises.

Strictly necessary, functional, analytics, advertising, and social-media categories

Strictly necessary cookies enable core functions such as logging into course accounts and navigating between modules. Functional cookies remember preferences like language or video playback speed. Analytics cookies track completion rates and popular lessons to refine content. Advertising cookies may measure campaign effectiveness for programming bootcamps. Social-media cookies allow limited sharing of course achievements when users choose that option.

First-party versus third-party cookies

First-party cookies are set directly by codezenly and stay within our domain. They handle authentication and course progress. Third-party cookies come from external providers such as analytics services or payment processors that support our commercial activities. These may be used to verify transactions or gather aggregated usage statistics while learners access programming resources.

Session versus persistent cookies and retention

Session cookies exist only while your browser is open and are deleted when you close it. Persistent cookies remain on your device for a set period, often between thirty days and two years, depending on purpose. For example, authentication tokens may last thirty days while analytics identifiers can persist up to twenty-four months to track long-term learning trends.

Data handled and purpose of each category

Necessary cookies process identifiers and session tokens to keep you logged in. Functional cookies store settings such as theme or subtitle preferences. Analytics cookies collect page views, time spent on exercises, and device type to improve course quality. Advertising cookies may record referral sources without creating individual profiles. All data handling follows Malaysia’s Personal Data Protection Act 2010.

Consent or exemption basis for each category

Strictly necessary cookies operate under the legitimate interests exemption because they are essential for the service. Functional, analytics, and advertising categories require consent under PDPA principles. You may grant or refuse consent through the site-wide cookie banner. Withdrawal of consent does not affect prior lawful processing but stops future collection in those categories.

Cookie or provider table

auth_token – first-party, necessary, 30 days, maintains login sessions.
pref_lang – first-party, functional, 90 days, stores language choice.
_ga – third-party analytics, 24 months, measures course engagement.
payment_ref – third-party, necessary, session only, processes course fees.

How the consent manager works

The cookie banner appears on first visit and allows you to accept all, reject non-essential, or customise choices by category. You can reopen the banner from the footer at any time to change or withdraw consent. Changes apply immediately and are stored in a first-party cookie for twelve months.

Browser-level controls

Most browsers let you block or delete cookies through settings menus. Disabling necessary cookies may prevent login and course access. Blocking analytics cookies limits our ability to improve content but does not stop core functionality. Instructions for popular browsers are available on their official support pages.

International transfers

Some third-party providers may store data outside Malaysia. Transfers occur only with appropriate safeguards such as contractual clauses. Details appear in the Privacy Policy.

Policy changes, contact route, and last-updated date

We may update this policy to reflect legal or operational changes. The revised version will carry a new date. For questions contact codezenly via the Contacts page form, email [email protected], phone +603-2116 5778, or visit Suite 33-01, 33rd Floor, Menara Keck Seng, 203 Jalan Bukit Bintang, 55100 Kuala Lumpur, Malaysia. This document was last revised on 23 September 2026.