Skip to main content
Back to homepage
Legal

Cookie Policy

This page explains the cookies, local storage, and session storage used by AIErudit, what those technologies do, and where current implementation behavior matters for consent and preference management.

Last updated: April 21, 2026

1. How browser storage is used

AIErudit uses a mix of cookies, local storage, and session storage to run authentication, protect accounts, remember interface choices, keep purchase or invite flows consistent, and optionally enable analytics where configured.

Some storage is strictly necessary to provide the service you asked for, such as sign-in, secure session refresh, or payment-related continuity. Some preference storage is created when you directly use a feature such as theme, layout, or language controls. That means certain functional browser-storage values may exist because of your direct interaction with the interface even if you have not reopened the cookie settings dialog afterward.

Read this page together with the Privacy Policy. If implementation changes, technical key names may change too.

2. Representative inventory

The table below is representative rather than immutable. It is meant to describe the current classes of cookies and storage used by the product, not promise that every key name will remain identical over time.

Each item lists the provider inline so cookie details stay readable without horizontal scrolling.

refresh_token, trusted_device, github_oauth_state

Category
Strictly necessary cookies
Purpose
Account security, session continuation, OAuth and trusted-device flows
Typical duration
Session to roughly 30 days, depending on the flow
Provider
First-party

aierudit_has_session

Category
Strictly necessary cookies
Purpose
A non-sensitive flag (value "1") indicating an active sign-in exists, so the app knows whether to silently restore your session on load without keeping you needlessly signed out. Contains no account or token data.
Typical duration
Matches your sign-in session (up to roughly 30 days)
Provider
First-party

aierudit_cookie_consent

Category
Consent record
Purpose
Stores the current cookie preference state and policy version
Typical duration
Up to 1 year
Provider
First-party

academy_dark, academy_sidebar_collapsed, aierudit_language

Category
Interface preference storage
Purpose
Remembers UI state you request directly, such as theme, layout, and language
Typical duration
Until changed or cleared by the browser
Provider
First-party browser storage

Temporary session-storage keys used in auth or invite flows

Category
Session state
Purpose
Supports short-lived product flows, redirects, and continuity while browsing
Typical duration
Browser session
Provider
First-party browser storage

Google reCAPTCHA browser signals

Category
Strictly necessary security processing
Purpose
Abuse prevention and human verification on protected forms such as sign-in, contact, checkout, and password recovery
Typical duration
Provider-defined; verification tokens are short-lived
Provider
Google reCAPTCHA, when a protected form requires verification

_ga, _ga_*

Category
Analytics cookies
Purpose
Consent-based traffic and product measurement when analytics is enabled
Typical duration
Provider-defined, often up to 2 years
Provider
Google Analytics, when configured

mp_*

Category
Analytics cookies
Purpose
Consent-based product analytics for Mixpanel (EU region). Stores an anonymous distinct ID and session metadata so funnel, retention, and revenue dashboards can be computed.
Typical duration
Provider-defined, typically up to 1 year
Provider
Mixpanel (api-eu.mixpanel.com), when analytics consent is granted

Marketing is reserved in the consent UI for future use. The current public product baseline does not claim an active third-party advertising tracker stack on this page.

3. Third-party services

  • Stripe may place cookies or similar technologies on checkout, billing, or hosted payment surfaces when those surfaces are used.
  • Google Analytics cookies are only relevant if analytics is enabled in the product and the corresponding consent flow allows them to load.
  • Mixpanel (operated from the EU region atapi-eu.mixpanel.com) is loaded only when analytics consent is granted. Mixpanel receives a numeric account identifier, the events you trigger while using the product (such as opening a course preview or completing a module), the country derived from your IP address by MaxMind, and acquisition referrer data. AIErudit does not send your email, name, or message text to Mixpanel.
  • MaxMind GeoLite2-Country is used server-side to resolve your IP address to a two-letter country code. The country code is attached to analytics events to enable geographic dashboards. The IP address itself is not sent to Mixpanel.
  • Google reCAPTCHA may load on protected forms for abuse prevention and human verification. This is treated as necessary security processing rather than analytics or marketing consent.
  • Google or GitHub sign-in flows may use their own cookies or browser state when you choose those authentication providers.

4. Managing choices

You can reopen the cookie settings interface at any time using the footer control or the button below. You can also use your browser to clear cookies and storage. Doing so may sign you out or reset saved interface preferences.

Operator and contracting party

AIErudit is operated as a Polish sole proprietorship (JDG). The operator is the contracting party for every paid course, bundle, team workspace, and creator account on the platform.

Legal trader name
VITALI BIBIKOV
Legal form
JDG (Polish sole proprietorship)
Tax ID (NIP)
5213977371
Statistical number (REGON)
522636099
Registered business address
ul. Białej Koniczyny 5/1602-757 WarszawaPolska
Electronic delivery address (e-Doręczenia)
AE:PL-58782-70360-GUJTH-29
Primary registered activity
62.10.B — Pozostała działalność w zakresie programowania
Public CEIDG record
CEIDG.gov.pl
Legal notices and contact
privacy@aierudit.com