Cookie Policy

Cookies are small text files a website stores on your device so it can remember you between requests and pages. We also use a few related browser technologies that work in a similar way.

On their own, cookies are simple key-value entries — they cannot run programs, read unrelated files, or carry a virus. What matters is the job each one does and how long it stays, which is why we group and describe them clearly throughout this policy.

Cookie

A small text file set by a website and sent back on each later request, letting the platform recognize your session and remember your choices.

Session vs persistent

A session cookie is erased when you close the browser; a persistent cookie stays for a set lifespan so a choice such as your language survives your next visit.

First- vs third-party

A first-party cookie is set by Academz itself; a third-party cookie is set by another service we embed, such as a payment gateway or a video player.

Local storage

Related browser storage (localStorage and sessionStorage) that holds small preferences on your device without sending them on every request, used only for interface state.

We keep our use of cookies deliberately narrow. Every cookie we set falls into one of a few clear purposes, and we do not use any of them to build advertising profiles or to follow you around the web.

• Keep you signed in — hold your authenticated session as you move between pages so you do not have to log in again on every click.
• Keep you safe — protect forms against cross-site request forgery and help detect suspicious sign-in activity.
• Remember your choices — store your language, text direction, light or dark theme, and similar interface preferences.
• Understand usage — measure, in aggregate, which pages and features are used so we can fix problems and improve the platform.

Strictly necessary cookies are required for the platform to work. They are set only in response to actions you take — such as signing in, submitting a form, or choosing your language — and the service cannot function correctly without them.

• Authentication session — keeps you securely signed in to your account, academy, or console for the length of your visit.
• CSRF token — protects every form and state-changing request against cross-site request forgery.
• Language and theme — remembers your chosen locale, reading direction, and light or dark appearance so pages render correctly.
• Load balancing — routes your requests to a healthy server and keeps you on a consistent one during a session.

Performance and analytics cookies help us understand how the platform is used so we can make it faster and more reliable. They gather information in aggregate — which pages are visited, which features are used, and where errors occur — and are not used to identify you personally.

• Aggregate usage — counts of page views and feature use that show us what helps and what to improve.
• Performance timing — how quickly pages and actions load, so we can find and fix slow spots.
• Error diagnostics — de-identified reports when something breaks, so we can reproduce and repair it.

Functional cookies enable convenient extras that are not essential to the core service but improve your experience. If you do not allow them, the affected features may be unavailable or fall back to a default.

• Interface preferences — remembering a collapsed sidebar, a chosen dashboard layout, or a preferred table density.
• Recently used — surfacing items you worked on last so you can pick up where you left off.
• Embedded content — letting a video player or support widget you open remember its own settings for you.
• Onboarding state — hiding a tip or tour you have already dismissed.

Like analytics cookies, functional cookies are optional. Declining them keeps the platform fully usable; you may simply need to re-set a preference from time to time.

The table below summarizes the categories of cookies we use, what each is for, and how long a cookie in that category typically lasts on your device.

Some features rely on trusted third-party services, and those services may set their own cookies when their content loads. We use them only where they add real value, and each is bound by its own privacy and cookie terms.

• Payment gateways — when you subscribe or an academy sells a course, our PCI-compliant payment providers set cookies to process the transaction securely and prevent fraud.
• Embedded video — lessons and marketing pages may embed a video player that sets cookies to stream content and remember playback settings.
• Analytics providers — our aggregate analytics may be delivered through a reputable provider that sets its own measurement cookies on our behalf.
• Support and chat — an embedded help or chat widget may set cookies to keep your conversation open across pages.

You have several ways to control the non-essential cookies we and our providers set. You can adjust them at any time, and doing so never affects your right to use the core platform.

1. Browser controls — every modern browser lets you view, block, or delete cookies, and can warn you before a new one is set; look in your browser's privacy or settings section.
2. Our controls — where we offer an in-platform choice for analytics and functional cookies, you can change it from your account or a consent prompt at any time.
3. Effect of blocking — declining analytics or functional cookies is safe; the platform stays fully usable, though some conveniences may reset or turn off.

Some browsers can send a "Do Not Track" (DNT) signal or a Global Privacy Control (GPC) signal that asks websites not to track you. There is still no single industry standard for how a site must respond to a DNT request.

Because we do not use advertising or cross-site tracking cookies in the first place, there is little cross-site activity for these signals to stop. Where the law recognizes a signal such as GPC as a valid opt-out, we honor it for the optional cookies it applies to.

How long a cookie stays on your device depends on its job. We keep lifespans as short as the purpose allows, and you can clear cookies yourself at any time from your browser.

Session cookies

Erased automatically as soon as you close your browser; used mainly for sign-in and security during a single visit.

Short-lived cookies

Expire within hours, typically for load balancing and temporary security tokens.

Persistent preferences

Last up to about a year so your language, theme, and similar choices survive between visits.

Analytics cookies

May last up to about two years to measure returning usage in aggregate, unless you clear or decline them sooner.

When a cookie expires or you delete it, the platform simply sets a fresh one the next time it is needed for an essential purpose, or leaves it unset if it was optional and you declined it.

We may update this Cookie Policy as the platform evolves, as we adopt or retire a technology, or as the law changes. When we make a material change, we will update the version and effective date at the top of this page and, where appropriate, tell you through the platform.

Your continued use of Academz after an update takes effect means you accept the revised policy. We keep previous versions on record and can provide them on request.

If you have any question about how we use cookies, or want help managing your preferences, reach our team using any of the channels below. We aim to respond promptly and to resolve concerns directly.

• Privacy & data protection [email protected]
• Legal team [email protected]
• Operated by Academz — Cairo · Riyadh · Dubai