Cookie Policy

Cookies are small text files that a website places on your device. When you return to the site, your browser sends them back, which lets the site remember things between visits — for example, that you are already signed in, or that you prefer to read in French.

Websites can also save information directly in your browser using technologies called localStorage and IndexedDB. Unlike cookies, this data stays on the device and is not automatically sent to our servers with every request. Warshati uses this kind of on-device storage to make pages load faster and to keep a learner's in-progress creative work safe on their own device. We explain all of it on this page, in plain language, so you can see exactly what is stored and why.

We take an essentials-only approach. Cookies on Warshati do exactly two jobs:

• Keeping learners and educators securely signed in to their accounts.
• Remembering the language you have chosen — English, French, Arabic, or Spanish — so every page loads in the right language.

Just as important is what we do not do. Warshati sets no advertising cookies, no third-party analytics or audience-measurement cookies, no social media cookies, and no third-party tracking of any kind. We measure how the learning platform is used with our own first-party system — described in our Privacy Policy — which uses no cookies and shares nothing with outside companies. We do not build advertising profiles of visitors, and we never sell personal data.

You will not see a cookie consent banner on Warshati. That is deliberate: consent banners exist to ask permission for optional cookies such as advertising and analytics, and we simply do not set any. If that ever changes, we will update this policy first and put appropriate choices in place before any new cookie is used.

Warshati sets two first-party cookies, listed in the table below. The sign-in cookie, access_token, carries a signed login token and is protected with the standard safeguards: it cannot be read by scripts running on the page (httpOnly), it is sent only over secure connections in production, and it is restricted to our own site (sameSite=strict). It is deleted the moment you sign out.

The language cookie, NEXT_LOCALE, is set by our localization framework when needed to remember which of our four languages you are using. It is a session cookie, which means it disappears when you close your browser.

Beyond cookies, Warshati saves some information directly in the browser on the device a learner is using. Almost all of it stays on the device: it is not shared with advertisers, and it is never read by third parties. We use it for two things — making the platform feel fast, and keeping a learner's work safe where they made it. The one exception is a random session identifier (warshati-activity-session) that travels with the usage events our own first-party measurement records, as described in our Privacy Policy; it contains no personal details.

A point parents often appreciate: creative work made inside certain workshops, such as drawing boards, design pieces, and project boards, is saved on the device itself. In our multimedia workshops, any audio or video a learner records is stored in the browser's IndexedDB database on that device only — recordings are never uploaded to our servers.

The table below lists the main storage keys we use and what each one does. Clearing your browsing data removes them all. Account progress — pathway, level, points, completed workshops, and certificates — is safely stored in the learner's Warshati account, so clearing the browser never erases real progress; however, unfinished on-device creative work would be lost.

Storage entries beginning with workshop names (for example digital-explorer, visual-creation, or multimedia-production) hold the learner's own creations for those workshops, on the device where they were made.

We do not set any third-party cookies, and we do not allow other companies to set cookies through our site. There are no advertising networks, no analytics providers, no embedded social media widgets, and no video players from other platforms — the videos on our site are hosted by us.

In the interest of full transparency: some of the display fonts on our site are currently loaded from Google Fonts. This means your browser requests font files from Google's servers, and Google receives your device's IP address as part of that request. According to Google, the Fonts service does not use cookies, so nothing is placed on your device — but we mention it because we believe you should know about every outside service your browser talks to. Our Privacy Policy has more detail on the limited third-party processing we use.

If we ever decide to introduce a cookie from a partner or service provider, we will update this policy before it takes effect, so this page always reflects what is actually on your device.

You are always in control of cookies through your browser. Every major browser — Chrome, Safari, Firefox, and Edge — lets you view, block, and delete cookies from its privacy or settings menu, and lets you clear stored site data for individual websites.

Because our cookies are functional, blocking or deleting them has practical consequences:

• Without the access_token cookie, you cannot stay signed in — Warshati will ask you to log in again, and learner areas will not work.
• Without the NEXT_LOCALE cookie, the site may not remember your language, and you may need to choose it again.
• Clearing all site data also removes the on-device storage described above, including any unfinished creative work saved on that device.

A note for learners using a school device: computers and tablets managed by a school often have browser settings controlled by the school's IT team. If something about cookies or saved work seems different on a school device, the best first step is to ask a teacher or the school's IT staff.

We review this policy whenever the cookies or on-device storage we use change. When we update it, we will post the new version on this page and refresh the date shown at the top.

If we make a significant change — for example, introducing a new category of cookie — we will update this page before the change takes effect, and we may also inform our partner schools directly. We encourage you to check back here from time to time.