Skip to main content
Back to homepage
Legal

Privacy Policy

AIErudit — AI Education for Business Professionals processes personal data to authenticate users, deliver courses, handle payments, operate business workspaces, power optional AI-assisted study features, and meet legal obligations. This notice explains what we collect, why we use it, and how rights requests work.

Last updated: November 13, 2026

1. Controller and scope

The controller for the consumer platform is the operator identified at the foot of this page — Vitali Bibikov, a Polish sole proprietor (JDG) registered in CEIDG (NIP 5213977371, REGON 522636099), operating AIErudit from Warsaw, Poland. Privacy requests can be sent to privacy@aierudit.com. See the Operator and contracting party block below for the full registered address and electronic delivery details.

This policy covers visitors, registered learners, buyers, workspace members, team administrators, support requesters, and creator applicants or creators to the extent we act as the controller for that interaction. If a signed enterprise agreement or data processing addendum says otherwise for a specific business deployment, that document will govern that deployment.

We have not publicly appointed a Data Protection Officer at this time. If that changes, the DPO contact will be published here.

2. Categories of personal data

CategoryRepresentative examples
Account and profile dataName, email address, company, job title, language, profile settings, verification state
Authentication and security dataPassword hash, OAuth identifiers, session metadata, MFA state, device or login-risk signals
Learning and certification dataEnrollments, progress, quiz answers, scores, achievements, certificates, learning history
Payments and transaction dataPurchase type, amount, currency, Stripe transaction identifiers, refund status, invoice metadata
Support and communicationsMessages, contact forms, creator or sales inquiries, support history, attachments you send us
Device, usage, and preference dataBrowser, IP-derived region, public page path, anonymous Umami session hash, Clarity interaction, page-rendering, and diagnostic signals, logs, cookie/storage identifiers, language and UI preferences
Country and compliance evidenceIP-derived country code, account country, checkout billing country, payment-card country, self-declared contracting or operating country, creator tax country, and provider-eligibility decision metadata
Creator uploadsCourse videos and other files you upload as a creator, including your image and voice and any metadata embedded in the file, plus processed lesson copies and captions
AI feature inputs and outputsPrompts, attached context, selected model lane, generated responses, moderation or safety metadata

3. Purposes and legal bases

PurposeTypical legal basis
Create accounts, provide courses, issue certificates, and operate paid accessContract performance
Process payments, refunds, taxes, bookkeeping, and compliance recordsLegal obligation and contract performance
Protect the platform, investigate abuse, secure accounts, and prevent fraudLegitimate interests and, where required, legal obligation
Check country, sanctions, export-control, tax, payment, and AI-provider availability before selling, provisioning, storing provider keys, or enabling hosted AI featuresLegal obligation, legitimate interests, and contract performance
Answer support requests, sales inquiries, and creator operations requestsContract performance and legitimate interests
Run optional analytics or consent-based measurement toolsConsent where required
Improve products, documentation, and learning quality using de-identified or limited internal dataLegitimate interests

Adaptive Practice

Adaptive Practice. If you choose an eligible practice activity, we save your draft, the version you submit, the task and rubric version that applies, formative checkpoint responses, feedback, and limited receipts needed to restore your work, prevent duplicate submissions, investigate a report, and honour your data rights. These records are linked to your account. We use the data to provide the practice activity and the feedback you requested; storing your practice work is necessary to provide the activity you chose. You can continue an ordinary course without choosing the optional AI-supported practice path. Your practice results are shown to you, not supplied as individual or aggregate assessment to a buyer, employer, manager, or team. They do not determine course completion, certificates or employment outcomes.

AI-assisted feedback, if enabled for you. We may send a minimized copy of your submitted work, the task and the rubric to Anthropic Ireland, Limited (Claude API; processing by Anthropic PBC and subprocessors) to produce formative feedback. The legal basis for sending your work to the AI provider is your consent; storing your practice work is necessary to provide the activity you chose. We do not include your platform account ID, email address or payment details in the request; your written answer may nevertheless identify you or someone else. Processing locations: mainly the United States; inference may run in other countries where the provider operates. Transfers rely on the EU Standard Contractual Clauses in Anthropic's Data Processing Addendum. The provider's effective content-retention, training and support-access settings are: no training on customer content; deletion within 30 days, or up to 2 years for content flagged under the usage policy (provider terms as of 2026-10-07). We do not authorize model training on this practice content unless a separate, clearly explained purpose and valid basis are approved. AI feedback can be wrong; it is identified when shown and you can report it.

Invisible pilot testing, only if separately enabled. A limited pilot may send a minimized submitted answer to the approved provider to test feedback quality without showing you that test result. This is a different purpose from delivering feedback to you. The legal basis is your separate consent, which you can withdraw at any time, given before any send through the module's "Help test AI feedback" switch; you can also use the contact route in section 8. If you withdraw, new shadow sends stop and you may continue the ordinary course. We will not treat general Terms acceptance as an invisible-test grant.

Personal continuation experiment, only if separately enabled. An AI-assisted criterion result from your submitted work may select one of the course author's prewritten follow-up activities for you alone. This does not decide course completion, a certificate or access, and neither the criterion result nor an aggregate of such results is given to a buyer, employer, manager or team. The experiment's selection logic, ability to use the ordinary course instead and human-review route are: the AI may select one of the author's prewritten follow-ups; you can switch AI feedback off and continue the ordinary course; you can report feedback. This use has its own AI Act and data-protection assessment; the preceding feedback paragraph alone does not authorize it.

Generated extra practice, only if separately enabled. With your visible AI help consent, we may send your submitted answer, its criterion result and relevant course material to the approved provider to prepare a personalized explanation, a worked example and a new extra exercise. We send the generated material for an independent AI review before displaying it and, if you submit an extra answer, send that answer and exercise for formative feedback. This AI review can also be wrong. The generated activities help you revise your original work yourself; they do not complete or replace it. The same provider, processing locations, safeguards, storage and deletion periods apply. They are private to you and do not determine completion, certificates or access. This uses a fresh choice under the current visible AI help notice; general Terms acceptance or shadow consent does not authorize it. You can withdraw that choice in the module, stop new sends and continue the ordinary course.

Storage and deletion. Practice content is designed to expire 365 days from creation of the draft or submission, with limited body-free receipts kept for 730 days, for restoring work, preventing duplicates and handling disputes. Provider and backup copies may expire later: provider up to 30 days (2 years if flagged); our backups 14 days; any restore re-applies earlier deletions before use. A specific legal claim may justify a reviewed hold; payment or commercial analysis alone does not keep your answer body. You may request access, export, correction or deletion using the contact and rights process in this policy. A report of sensitive or confidential material receives private review and deletion of the stored copy within 30 days of the report.

4. Team, employer, and admin visibility

If you use a team, company, school, or other sponsored workspace, the workspace owner and delegated administrators may be able to see information needed to manage the workspace. That may include your business contact identity, seat status, enrollment state, learning progress, completion status, and certificate status inside that workspace.

We do not intentionally expose your password, raw payment card details, or private authentication secrets to workspace admins. Admin visibility is shaped by the product design, the applicable customer relationship, and mandatory law.

5. Providers, disclosures, and transfers

We share personal data with service providers only where reasonably needed to operate the platform, such as infrastructure hosts, email delivery vendors, authentication providers you choose, payment processors, optional analytics and advertising measurement providers, and AI model providers when you actively use AI features or choose an optional Adaptive Practice AI feature described in section 3.

Our core service providers are Amazon Web Services (application hosting, database, and storage in the eu-central-1 region) with Amazon CloudFront for content delivery, Stripe for payments, Brevo for transactional and lifecycle email, and Better Stack for error and request-metadata monitoring. The canonical, complete list of providers, including their purpose, region, and transfer mechanism, is the Trust Center subprocessor list.

Where the analytics category is permitted by consent or the applicable regional opt-out posture, we use the following tools for measurement: self-hosted Umami for anonymous public traffic, acquisition, and funnel reporting; Google Analytics 4 for web traffic attribution; Mixpanel (operated from the EU region atapi-eu.mixpanel.com) for authenticated product, funnel, retention, and revenue dashboards; and MaxMind GeoLite2-Country, used server-side, to convert your IP address into a two-letter country code so geographic dashboards can be computed without sending the IP itself to Mixpanel. Umami is collected throughanalytics.pagefabrica.comon infrastructure controlled by AIErudit and does not use tracking cookies. Its server may use the request IP address transiently to derive country and an anonymous session hash, but does not store the IP address. We send Umami only the public path without query strings or fragments and an allowlisted set of coarse event properties. We do not use Umami's identify function or send it account ids, email addresses, names, payment identifiers, search text, prompts, support messages, or form contents. We do not send your email address, full name, or message content to Mixpanel; we send a numeric account identifier and the events you triggered while using the product. Mixpanel data is retained at the project default and can be reset by request.

Google Analytics 4 is loaded only after the Analytics category is permitted. It measures visits and navigation using normalized page route patterns rather than query strings or URL fragments. Google may process session statistics, approximate location, referrer, browser and device information, interaction events, and a first-party client identifier stored in the _ga and_ga_* cookies. We do not configure this integration to send names, email addresses, account identifiers, prompts, search text, support messages, payment identifiers, or other free-form content. Advertising storage, advertising user data, and advertising personalization remain denied unless you permit the Marketing category. Learn more about how Google uses information from sites and apps that use its services.

We also use Microsoft Clarity, only after the analytics category is permitted, to understand how visitors interact with the site through behavioral metrics, heatmaps, and session replay. Clarity may process page-rendering details and interaction signals such as clicks, scrolling, pointer movement, resizing, selections, and performance or script diagnostics. We use this qualitative evidence to find confusing layouts, broken interactions, and usability friction. We tell Clarity that analytics storage is granted while advertising storage remains denied; Clarity is not used by us for advertising or revenue attribution.

Clarity's masking controls protect page content, and input boxes and dropdown values are masked in every Clarity masking mode. We do not deliberately unmask authenticated, checkout, account, team, Terminal/AI, support, or other free-text surfaces. We do not call Clarity's Identify API or send it account identifiers, email addresses, names, prompts, support messages, form contents, payment identifiers, or other custom user identifiers. Microsoft may process Clarity data on our behalf; see the Microsoft Privacy Statement for more information.

When marketing consent and the corresponding product flags allow it, we may use Google Ads, Microsoft Advertising/UET, Meta Pixel and Conversions API, and X Ads for ad measurement, remarketing, conversion feedback, and browser/server event deduplication. These providers may receive page-view or standard-event signals, purchase or sign-up conversion metadata, the relevant ad-platform click identifier, and, only where a provider requires matching, an email address transformed into a SHA-256 hash at send time. We do not send raw email addresses, full names, message text, passwords, payment-card details, or private authentication secrets to these ad platforms.

For abuse prevention, protected forms may use Google reCAPTCHA to assess whether a request is likely to come from a person. The backend verifies short-lived tokens server-side and checks action and hostname binding. We use this for security and fraud prevention, not for advertising or product analytics.

For country eligibility and compliance checks, we may combine server-side request country resolution, account profile country, checkout billing or payment-card country, self-declared contracting or operating country, creator tax country, and AI-provider availability rules. Country-compliance audit events store decision metadata such as policy version, evidence-source names, country code, provider, and reason code, but are designed not to store raw IP addresses, email addresses, full names, prompt text, or payment card details.

We may also disclose data to professional advisers, auditors, counterparties in a business transfer, or competent authorities when required by law, to enforce rights, or to protect users and the platform.

Our primary infrastructure is intended to run in the EU, but some providers may process data in the United States or other countries. Where cross-border transfers require safeguards, we rely on adequacy decisions, Standard Contractual Clauses, or another approved transfer mechanism.

We do not sell personal data for money. Some privacy laws may treat ad-platform pixels, conversion APIs, or cross-context ad measurement as a "sale" or "sharing" of personal information. We therefore gate marketing pixels and conversion uploads through the marketing-consent category and the Do Not Sell or Share opt-out where that control is shown.

6. Retention and security

We keep personal data only for as long as needed for the purposes described above, including legal, accounting, anti-fraud, and dispute-handling needs. Different categories have different retention periods. For example, learning records may remain attached to an active account, payment records may be retained for tax and audit purposes, and security logs are typically kept for shorter operational windows.

Self-hosted Umami does not automatically expire analytics records. We retain them only while reasonably needed for aggregate trend, acquisition, and funnel analysis, then delete or aggregate them through our operator-controlled retention process. Backups may keep deleted data for a limited additional operational period before rotation.

Google Analytics user-level and event-level data follows the retention setting in the AIErudit GA4 property. Standard GA4 properties allow a two- or fourteen-month setting; standard aggregated reports are not governed by that setting. The exact provider-side setting is controlled by an authorized AIErudit operator and may change within those Google-supported limits.

Microsoft documents that Clarity playback data used for session recordings is retained for 30 days. Clarity click and aggregated page data, and sessions that are labeled or favorited, are retained for 9 months. Microsoft states that Clarity data and backups are deleted after the applicable retention period and cannot be recovered.

If you are a course creator, course videos you upload are kept while learners hold access, then for up to 90 days (archive) or 30 days (deletion) plus a 30-day notice, before the stored copies are deleted. We keep your original upload alongside the processed lesson copy for the same period, including after account deletion while learners still hold access to that course.

Authenticated IP observation rows are automatically purged after 90 days. User-action audit and admin audit rows are automatically purged after 365 days unless a legal hold or longer statutory need applies. Country and sanctions-compliance decision records are classified as security evidence.

Sanctions screening. Before we accept a payment, create a team, or pay a creator, we check the name on the account, team, or payment against the EU consolidated financial sanctions list and the US OFAC Specially Designated Nationals list. We do this to comply with EU restrictive-measures regulations, which apply to us (Article 6(1)(c) GDPR). We also do it in our legitimate interest in not causing our US payment providers to breach US sanctions (Article 6(1)(f) GDPR). A name match alone never leads to an automatic refusal: a person reviews every match, and you can contest the outcome by writing to us. If a match is cleared, our record of the check is kept for the standard 365-day audit period. If a match is confirmed, we keep the record for 5 years after the end of the year of the decision, because we may need to evidence it to the authorities. We do not copy your details into the sanctions lists. If you choose to send us your country or year of birth to help a review, we use it only for that review.

When an account is deleted, admin audit records keep stable event evidence such as the user id, anonymized subject label, actor, time, and reason, but they do not retain the deleted account's original email address or username in event metadata.

We use technical and organizational safeguards appropriate to the service, including access controls, password hashing, transport encryption, logging, and operational review. No system is perfectly secure, and we cannot guarantee absolute security.

7. Rights and choices

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or port certain personal data, and to withdraw consent where processing relies on consent. We may need to verify your identity before completing a request.

Some rights can be exercised through self-service product tools. For example, the account area supports export and deletion-related flows, and cookie preferences can be managed through the Cookie Policy controls and footer settings entry point.

If you are a course creator, you can download your processed lesson videos and captions in the product. The product does not offer a download of your original uploaded file. To receive a copy of an original upload we still hold, email privacy@aierudit.com; we provide it free of charge within one month. Originals that have been deleted under the retention rule above can no longer be provided.

If you are in the EEA, UK, or another jurisdiction with similar rights, you can also complain to your local supervisory authority. For Poland, that is the President of the Personal Data Protection Office (UODO).

8. California notice, complaints, and contact

California residents may have rights to know, access, delete, correct, and limit certain uses of personal information under California privacy law, subject to statutory exceptions. To make a request, email privacy@aierudit.com.

Our self-hosted Umami integration honors the browser Do Not Track signal when analytics would otherwise be enabled by a regional default. An express later choice of Accept all records your contrary preference. Cookie settings and the Do Not Sell or Share control remain the authoritative ways to turn analytics and marketing off for this browser.

For general support, contact support@aierudit.com. For privacy questions, complaints, or rights requests, contact privacy@aierudit.com.

Global Privacy Control. If your browser sends a Global Privacy Control (GPC) signal, we treat it as a request to opt out of the sale and sharing of your personal information and of targeted advertising and, under the GDPR, as an objection to optional measurement. It applies to that browser and, if you are signed in, to your account. We do not ask you to confirm it, and the Do Not Sell or Share page shows when it has been honored. You can turn analytics back on in Cookie settings; marketing stays off while the signal is present unless you expressly allow it. Residents of Colorado, Connecticut, Oregon, Texas, Virginia, and other states with similar laws can use the same controls.

AIErudit is not directed to children under 16. AI practice features and pilots are available only to users aged 18 or over. If you believe a child provided personal data in violation of this policy, contact us so we can review and act.

9. Cookies and tracking

We use essential cookies and similar storage to keep users signed in, protect sessions, remember consent choices, and maintain core platform reliability. Protected forms may also load Google reCAPTCHA for abuse prevention. Optional analytics or measurement tools, including marketing measurement tools, are only enabled where the required consent or opt-out posture allows them.

Accept all is one combined action for every optional category, including self-hosted Umami and Google Analytics 4; neither provider has a separate consent button. In the EU, EEA, United Kingdom, Switzerland, and when location is unknown, optional measurement stays off until a positive choice. In the United States, optional measurement may operate under an opt-out posture and can be stopped through cookie settings or Do Not Sell or Share.

Withdrawing Analytics consent prevents future GA4 measurement and tells Google that analytics storage is denied. It does not necessarily remove provider cookies already stored by your browser; you can delete those through browser controls. Granting Analytics consent again allows GA4 and the other configured analytics providers to resume without enabling Google advertising storage or personalization.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Cookie identifiers may store items such as session tokens, localization preferences, dismiss-state flags, and consent choices. For a fuller breakdown of current cookies, retention windows, and opt-out controls, see the Cookie Policy.

You can review or change optional cookie settings from the footer preferences entry point at any time. Browser-level controls can also block or delete cookies, although doing so may affect login, checkout, and lesson playback behavior.

10. Marketing attribution

When you arrive at AIErudit via a marketing or ad link, we capture the link's UTM parameters and the ad-platform click identifier (for example gclid, fbclid, msclkid) and store them against your account on our servers for up to 90 days, after which the raw identifier is deleted. We use this to measure which channels bring learners to AIErudit and whether our marketing is effective.

We send a derived acquisition channel and the type of click identifier (not the raw identifier itself) to our analytics provider, Mixpanel (EU data residency). We do not send your email, name, or the raw click identifier to Mixpanel.

If marketing consent and the relevant product flags allow it, we may also send conversion feedback to Google Ads, Microsoft Advertising, Meta, or X Ads. Those sends may include the stored click identifier and conversion details, and, only where a provider requires matching, an email address transformed into a SHA-256 hash at send time. Raw click identifiers are automatically purged after the attribution window.

You can opt out of analytics and marketing cookies at any time in Cookie Settings. Where available, the Do Not Sell or Share control disables marketing pixels and conversion uploads.

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
Telephone
+48 500 554 429
Legal notices and contact
privacy@aierudit.com