Operator: CKTIS GROUP SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ. Operator status: registered company.
Controller and contact
Service provider and platform operator: CKTIS GROUP SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ, address: ul. Towarowa 20B, 10-417 Olsztyn, Polska, KRS: 0001277399, REGON number: 54613824700000, registry court: Sąd Rejonowy w Olsztynie, VIII Wydział Gospodarczy Krajowego Rejestru Sądowego, NIP: 7394042224, share capital: 5000.00 PLN. Contact: office@cktis.com. For personal data matters, you can write to office@cktis.com or use the privacy form in CKTIS. This document covers users, invitees, guardians, organization representatives, newsletter subscribers and people contacting the operator. We will provide information about the appointment of a data protection officer if one is appointed; the current draft does not confirm such an appointment.
Data and sources
We receive data from you in forms and during your work in the application, from an inviting user or organization to the extent of the invitation, from a guardian to the extent of their confirmation, and from a login provider if you choose one. These include account identifiers, email, profile name, date of birth and country, login and device data, progress, answers, code and exercise results, learning documents, CV and cover letter content, reports, correspondence, consents, group data and shared reports. Data for billing, tax settlements and verification of adulthood are collected in the relevant prize claim or future purchase process, not during every lesson. Do not provide unnecessary special category data or other people's data in code and attachments.
Processing purposes and legal bases
- Account, chosen learning, progress recording, document issuance, CV and performance of a requested operation: art. 6(1)(b) GDPR — performance of a contract or steps before entering into it, solely to the extent necessary.
- Account protection, fraud prevention, assessment integrity, technical logs, handling ordinary enquiries and defending claims: art. 6(1)(f) GDPR — legitimate interest following an assessment of necessity, proportionality and the person's rights, with particular protection for minors.
- Accounting and tax obligations, exercise of individuals' rights and mandatory notifications: art. 6(1)(c) GDPR in conjunction with a specific legal obligation.
- Newsletter, voluntary additional sharing and optional technologies requiring consent: art. 6(1)(a) GDPR and the relevant requirements of the Electronic Communications Law. Consents are separate and can be withdrawn.
- Service operation survey: participation is voluntary; quality analysis is based on legitimate interest with limited data. Answers are not used to assess knowledge or award points.
Providing data marked as necessary enables the relevant service; without them, we cannot perform the corresponding operation. Optional data can be omitted. Legitimate interest does not replace required consent or the conditions for decisions under art. 22 GDPR.
Assessment integrity and automatic responses
CKTIS records results, attempts, limited code snapshots from the editor, runs, use of assistance and aggregate interaction statistics such as the rate of changes, pauses, paste events, focus, full-screen status and technical environment signals. It does not record the values of all pressed keys or the contents of the system clipboard in telemetry. However, code submitted for execution and decision evidence may contain text entered in the editor. Passwords and private information must not be entered there.
In a lesson, an automation assessment may reduce the award by 49 out of a maximum of 50 points. Additional assistance may reduce the remaining point to zero. The overall lesson result does not become negative; further learning and completion remain available. This applies only to that lesson, not to the violation counter for tasks or examinations. Users can see the recorded grounds and challenge the reduction. None of the following is sufficient on its own to establish automation: fluent work, not using a mouse, using a keyboard or using assistive technology. In a daily task, weekly task or examination, an assessment requiring enforcement of the rules or an accepted security violation report creates a case in the authorized support queue. Depending on the violation, the system stops the current attempt or temporarily suspends its effects; a warning alone is not a final penalty. You do not need to submit an appeal first. Final cancellation, refusal of a result or exclusion requires an independent review of the evidence and a reasoned human decision. You may present your position beforehand. An algorithm's indication alone is not evidence of AI use. If no human decision is made within 7 days, the temporary restriction expires. The system restores a reliably retained result or provides an actual repeat attempt if the result cannot be reconstructed; it does not record a fictitious pass. For a periodic task that has already ended, the remedial attempt window lasts 7 days from restoration of access. A correction retains the correct season and does not award points again for the same activity. Complaint deadlines and statutory rights apply independently of this mechanism. Following a favorable review, we attribute points to the original activity and the correct season. An open remedial attempt or unsettled correction suspends final prize settlement. Correcting a closed edition requires a separate settlement by an authorized person; the original entry remains in the history. Evidence and review status are available to the account owner and authorized support personnel. Monitoring is a risk assessment, not identification of a specific AI tool. An actual human review must precede a final significant sanction; a later appeal alone is not a justification for the admissibility of a solely automated decision under art. 22 GDPR.
Recipients and organizations
Access is available to authorized service personnel and infrastructure and communications providers to the extent necessary. The technical design provides for Microsoft 365 for email, Cloudflare Turnstile for protection of selected forms, Google and Meta for voluntary login, Stripe for future payments and inFakt for issuing invoices and corrections. Their actual roles, contractual entities and data scopes must correspond to the approved provider register before a given provider is used to process real data, including in the local beta. Google Cloud is currently used to host the CKTIS application, its main database and its files; these resources are configured in the Warsaw region (europe-central2). We do not declare that all data remain in Poland or the EEA without confirmation of the configuration and agreements.
A school or company organization may receive a learning report only within the permissions, allocation and visibility rules of the relevant program. A friend invitation does not provide access to private results. Leaving a group or withdrawing voluntary reporting limits further sharing; a report lawfully prepared earlier may have its own retention period. JOBMICS is disabled; we do not send data to it through an inactive option.
Publication in the ranking is voluntary and disabled by default. A separate choice covers the current and subsequent editions under the same rules: a seasonal alias, position, permanent points, seasonal points and the total. The total number of completed lessons and aggregate points by category are also public: lessons, quizzes, completed courses, daily and weekly tasks and seasonal activities, learning paths, confirmed reports and deducted points. These are summaries, without lists of individual activities, answers, code or reasons for point deductions. An edition entry is public for no more than 90 days after the edition ends, including to people who are not logged in. Email, surname, evidence and penalty details remain private. An alias is a pseudonym, not a guarantee of anonymity. In settings, you can withdraw consent for all editions just as easily, without losing learning, points or entitlement to settlement. Withdrawal applies to subsequent reads and does not change the lawfulness of earlier publication. The choice is independent of messages, the newsletter and cookies. We record the immutable consent text, version and date; after restoring a backup, we ask about publication again instead of restoring consent from the old state. Voluntary public disclosure is based on consent (art. 6(1)(a) GDPR). Withdrawal does not change the lawfulness of disclosure before withdrawal. You can also contact office@cktis.com.
Transfers outside the EEA
If an active provider service causes a transfer outside the EEA, the operator identifies the appropriate mechanism: an adequacy decision and, where its conditions are met, the scope of entities it covers, or standard contractual clauses and necessary supplementary measures. Information about the safeguard used and how to obtain a copy is available through the privacy contact. The provider register, including country, role and specific mechanism, must be completed before an actual transfer, including from the local application; a provider's name alone does not prove that a transfer is lawful.
How long we retain data
We retain account data and progress while the account operates. Closure initiates deletion appropriate to each data category and restriction of retained records. It does not automatically mean complete anonymization of history: some learning, points, settlement, consent or security records may still contain an account identifier and remain personal data. Continued retention requires a specific purpose, basis, limited scope and period, for example to document a right, dispute or statutory obligation. Learning documents and a minimal authenticity record may remain to the extent necessary for verification and protection of claims. Accounting and tax data have a period arising from the applicable provisions, counted from the relevant event rather than the last login. For claims, we take account of the relevant limitation period and actual proceedings; we do not retain the entire account indefinitely under a general security label. After 24 months of inactivity, in the absence of an active relationship justifying continued retention, the system provides for notice of planned account closure 30 days in advance and a reminder 7 days before the deadline. Renewed activity interrupts this process. Deadlines for exercising individuals' rights run from receipt of the request, independently of the technical data cleanup schedule.
Current authentication retention periods are 30 days for the history of ended sessions, 1 day for terminal single-use artifacts, 30 days for used recovery codes, 365 days for revoked methods and security events, and 180 days for resolved account-sharing signals. Raw IP addresses are minimized after 30 days. General security auditing has a separate 730-day period without extending shorter rules. Learning integrity events expire after 90 days. Raw code and results of ordinary tasks or quizzes are minimized 730 days after completion, and copies of automated assessment and appeal evidence 730 days after the later completed review. Canonical examinations have separate periods of 30 days for network data and 24 months for assessment and security material; an open case or specific hold protects evidence. Only necessary minimal decision data remain, for example to maintain a restored result. Managed backups expire after 35 days, and deletions and newsletter opt-outs are reapplied before a restored database is made available. Public ranking visibility is disabled after restoration and requires a renewed conscious choice.
We retain minimal data on earned points, progress, completion statements, certificates and corrections for the duration of the service or entitlement validity and the necessary protection of the decision. We do not delete earned achievements solely because of their age. The public ranking is voluntary and visible for no more than 90 days after a season; publication requires a new choice after database restoration. Minimal evidence of that choice expires 1826 days after the later action or end of the relationship, when publication is inactive. CV import originals expire within 30 days, CV exports after 90 days, and personal CVs and cover letters are deleted when an account deletion request is carried out. Closed support cases, complaints and content reports and their attachments expire 730 days after closure, except where a specific obligation or hold applies. Financial data have separate periods arising from documentation and the relevant obligation. The detailed map distinguishes private copies and raw evidence from the minimal entitlement record; pseudonymization does not mean anonymization.
Your rights
You may request access and a copy, rectification, erasure, restriction and data portability in cases provided by law, and object to processing based on legitimate interest. An objection to direct marketing is effective without justification. Consent can be withdrawn as easily as it was given; this does not change the lawfulness of earlier actions. As a rule, we respond within one month; where justified complexity or the number of requests requires an extension, we inform you during the first month of the reason and a maximum of two additional months. You have the right to complain to the President of the Polish Personal Data Protection Office (UODO) (uodo.gov.pl) and to judicial protection. We do not routinely require an identity document scan for rights requests; additional verification must arise from reasonable doubts and be proportionate.
A separate account security mechanism analyzes session and device signals. At high risk, it may end a session and suspend activity and earning points until access is confirmed again or the grounds for the restriction cease earlier. The state is reassessed according to the validity of signals, and the temporary restriction expires no later than after 7 days without a human decision. A single IP address or shared network is not an independent basis for such a block. The description of responses and how to challenge them through Support → Security are provided in the CKTIS Account Security information; these effects also require a separate assessment under art. 22.