Skip to content
Last updated · September 20, 2026

Cookies

The cookies and similar technologies String's site and application use — and the ones we don't.

What this page covers

"Cookies" here covers traditional cookies and similar browser-storage technologies (such as local storage and session storage). This page describes two products: the string.education website you are reading this on, and the String application that schools and teachers use. They differ a great deal, and each has its own section below.

On this website

This website's pages are static: there is no account and no login. It sets no cookie of its own, uses no analytics tool, and knows your language from the page's address (/ar/ or /en/) rather than from anything saved. What it stores in your browser is two things:

What is storedWhenFor how long
Your place on the family app waiting list, with your emailWhen you finish joining the list, not before. The same number is sent with the form.Until you clear your browser data
A mark saying you have just sent a requestWhen a form is sent, so the thank-you page knows the message actually arrived.Read once then deleted, and gone when the tab closes

Cloudflare Turnstile — the check that confirms a form is being sent by a person — sets storage of its own on any page that carries a form. That check is required to send a form at all, and it is there to stop automated submissions rather than to track you across sites.

In the String application

The String application — the one teachers, schools and students use — is a different product with an account and a login. These are the categories of what it stores:

CategoryPurposeExamples
Strictly necessaryLogin and secure session. The application does not function without these.Session cookie, authentication token
PreferencesRemembering choices like language (Arabic/English).Interface language
AnalyticsUnderstanding platform usage to improve it, in aggregate rather than per person.Google Analytics, PostHog

What we don't use

Why the application uses analytics tools

Inside the application we use Google Analytics and PostHog to understand how it performs — which screens get used, where someone gets stuck — so we can improve it. This is product measurement, not building a marketing profile of any individual. Both tools operate under data-processing agreements with their providers, and are covered by the same retention and deletion terms stated in the Privacy policy. Neither of them runs on this website.

Third-party service providers

On this website there are exactly two: Cloudflare, which checks that a form is being sent by a person, and Brevo, through which the form's email reaches us and your confirmation reaches you. Neither does anything until you send a form, and neither appears on a page without one.

In the application, the only two tools that set analytics cookies are Google Analytics and PostHog. Each of these providers has its own privacy policy describing how it processes data at its own level; this page describes how we use them, not how they operate internally.

Cookies and student accounts

Student accounts follow the same rule with no exception: no targeted advertising, and no marketing profile, on any student account — regardless of the student's age.

Managing your preferences

You can control and clear cookies directly from your browser's settings. Clearing this website's data loses your waiting-list number — it is kept in your browser alone — but it reached us with your form, so write to us and we will tell you what it is. In the application, disabling strictly necessary cookies will prevent you from logging in, and disabling analytics will not affect how it works.

Changes to this page

If we add a new analytics tool or change a cookie category, we update this page and the "Last updated" date at its top — we do not change the practice silently.

Questions about this page