Cookie Policy
This page lists the cookies and similar technologies we use, and gives you a way to change your mind about them.
The short version. Strictly necessary cookies always run — without them you could not sign in. Everything else runs only if you accept it. You can open Cookie settings at any time from the footer of any page, switch categories on or off, and your choice takes effect immediately.
English in Games LLC
- Address
- ul. Jana Dantyszka 18, 02-054 Warsaw, Poland
- [email protected]
- Contact form
- https://elang.app/contacts
- Last updated
- 21 August 2026
1. What a cookie is
A cookie is a small file a site stores in your browser so it can recognise the browser on a later request. This policy also covers the technologies that do a similar job — local storage, pixels, software development kits in our mobile apps, and device identifiers.
We use the word "cookie" for all of them.
2. When we ask, and when we don't
Storing anything on your device that is not strictly necessary requires your consent. So:
- Strictly necessary cookies run as soon as you arrive. They are what makes sign-in, security and the site itself work, and there is no way to offer the Service without them.
- Everything else — preferences, statistics, marketing — stays switched off until you accept it in our banner.
Your choice is stored for 6 months, after which we ask again. We store it in a cookie called elang_consent, together with the date, so we can show that we asked and what you answered. If we change the categories or the providers inside them, we ask again straight away.
Where a browser sends a Global Privacy Control signal, we treat it as an objection to advertising cookies in the jurisdictions that recognise it.
3. Changing or withdrawing your choice
Withdrawing is as easy as consenting. Use the Cookie settings link in the footer of any page, change the switches, and save. Turning a category off stops the corresponding tags immediately, and we delete the cookies we set under it.
You can also delete cookies in your browser settings, and set your browser to refuse them. If you block strictly necessary cookies, sign-in and other core features stop working.
4. The categories
Strictly necessary — always on
Keep you signed in, protect against abuse and cross-site request forgery, balance traffic between servers, and remember your cookie choice.
| Set by | Purpose | Typical lifetime |
|---|---|---|
| eLang | Records your cookie choice (elang_consent) | 6 months |
| Google Firebase | Keeps your sign-in session valid | Session to 1 year |
| DigitalOcean | Routes requests and serves the site's media | Session |
Preferences — optional
Remember choices that change how the Service looks and behaves, so you do not set them again each visit: interface language, learning language pair, study and display settings.
| Set by | Purpose | Typical lifetime |
|---|---|---|
| eLang | Interface language and study settings | Up to 1 year |
Statistics — optional
Tell us which pages and features people actually use, which ones fail, and where the Service is confusing. We use this to decide what to build and fix.
| Set by | Purpose | Typical lifetime |
|---|---|---|
| Google Analytics 4 | Aggregate website and product analytics | Up to 2 years |
| Google Tag Manager | Loads the tags in the categories you accepted | No cookie of its own |
| Mixpanel | Product analytics — feature use and funnels | Up to 1 year |
| eLang (elanguid, elangdate) | Distinguishes visits for our own usage counters | 1 year |
Marketing — optional
Measure whether our advertising works, and show eLang to people on other sites. This is the category that involves sharing identifiers with advertising companies.
| Set by | Purpose | Typical lifetime |
|---|---|---|
| Google Ads | Measures conversions from our ads; remarketing | Up to 2 years |
| Meta (Facebook) Pixel | Measures conversions and builds advertising audiences | Up to 3 months per event, up to 2 years for the browser identifier |
The Meta Pixel is not loaded into the page at all unless you accept this category.
5. Cookies set by others
Some pages embed content from third parties — YouTube videos, for example. Those providers may set their own cookies when the embedded content loads, under their own privacy policies. Where we can, we load embeds in a privacy-preserving mode or only after you accept the relevant category.
App stores and browser stores that distribute our apps and extension set their own cookies on their own sites. That is outside our control and outside this policy.
6. Cookies in the browser extension and mobile apps
The extension stores your settings and your sign-in token locally so it can work on the pages you use it on. It does not carry advertising identifiers.
Our mobile apps do not use browser cookies, but they use equivalent identifiers through the app-store and analytics SDKs described in our Privacy Policy. You can reset or limit advertising identifiers in your device settings — on iOS through tracking permissions, on Android through the ads settings.
7. More about your data
What we do with the data these cookies produce, who receives it, how long we keep it and what rights you have over it are all in the Privacy Policy.
8. Changes
We update this page when the cookies or providers change. When a change adds a purpose or a provider you have not agreed to, we ask for your consent again rather than relying on the old answer. The current version's date is in the box at the top.