Operator: CKTIS GROUP SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ. Operator status: registered company.
Why we store data on your device
CKTIS uses cookies and similar browser storage mechanisms. Some are necessary to perform the service you choose: login, maintaining security, remembering a cookie decision or saving your own document. Other categories require a separate choice. The controller of the associated personal data is CKTIS GROUP SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ; contact: office@cktis.com. Processing details are provided in the Privacy Policy.
Session, login and security
- cktis_candidate_session / cktis_employer_session: session for the respective account type, by default up to 12 hours. Configuration may set another period, no longer than 7 days. Logout or revocation ends the session's usefulness earlier.
- cktis_candidate_auth_device / cktis_employer_auth_device: pseudonymous device recognition for account security, up to 365 days. This does not mean identifying the user on other services. The older cktis_auth_device name may be read during migration.
- cktis_oauth_state and cktis_identity_link: association of an initiated login or conscious identity linking with the provider's response, up to 10 minutes. cktis_candidate_mfa: continuation of a specific MFA confirmation, up to 5 minutes.
- cktis_guardian_consent_exchange: limited to the guardian invitation process, up to 24 hours. Single-use identity or invitation linking has its own short deadline; it is not permanent consent to tracking.
- In the staff panel, the separate cktis_staff_session has a default period of 4 hours renewed during panel activity. This is not absolute expiry 4 hours after the first login and does not grant an ordinary user administrator permissions.
Authentication cookies are intended for the server and protected against being read by page scripts. A public service requires HTTPS. The stated values distinguish the default duration from the maximum limit where configuration permits changes. The presence of a cookie alone does not extend permissions after session revocation.
Preferences and working documents
- cktis_cookie_preferences: choice of cookie categories, up to 180 days; a local copy may be stored in localStorage. Local decision history contains no more than 20 entries from this period.
- cktis_privacy_subject and cktis_privacy_receipt: necessary server cookies linking the browser with evidence of selection or withdrawal of categories, up to 180 days. They are HttpOnly and SameSite=Lax; a public HTTPS service requires Secure. Refusal does not itself activate analytics or marketing.
- cktisExplicitInterfaceLanguage: the language deliberately selected in the interface; i18nextLng: a technical cache of the current language, which alone does not establish a deliberate choice. Without a saved choice, the interface uses a supported browser language and ultimately English. activeSessionMode selects the appropriate account interface, while cktisEmployerSessionChanged coordinates session changes between tabs. localStorage entries have no automatic expiry of their own; they remain until overwritten, appropriately removed by the application or deleted with site data by the user.
- cktis.education-language.v1 (localStorage): stores the language preference for learning documents (documentLocale) in this browser and may retain an earlier value of the materialLocale field. In the standard learning-material view, the language follows the main interface language selection, not this earlier field; the document language can still be selected separately. The entry contains only these two fields and is created or overwritten when the document language preference changes, including when automatic mode is selected. It has no automatic expiry; it remains until overwritten, removed by the application or deleted when the user clears site data.
- sessionStorage: cktis:auth:return-intent stores the return to an initiated action, cktis:lastSupportArticle — the support article needed for report context, and cktis:premium-checkout:v1:* — the retry identifier of an initiated order if the feature is available. Data are tied to the tab session and may be deleted after use. cktis:ai:oauth and cktis:gi:friend/business carry an invitation token through login: the entry has a 10-minute deadline checked when read; this is not the deadline for all invitations on the server.
- IndexedDB cktis-private-drafts: private working versions of a CV or cover letter, separated by account and document, with a deadline of 30 days from saving. An expired entry is deleted on the next read; a closed browser does not guarantee immediate physical deletion on the thirtieth day.
- cktis-announcement:<account or guest>:<announcement>:<version>: record of announcement acknowledgment and limitation of repeated display. For 'session' frequency it is stored in sessionStorage, and for 'once' and 'daily' in localStorage. 'Daily' schedules display again the next day; it does not automatically delete the local entry after one day; localStorage remains until site data are deleted or the application changes it.
Do not save a working CV on a shared device without access control. Clearing site data in the browser deletes local copies but is not a request to delete account data from the server. CKTIS should not store passwords in localStorage.
Optional mechanisms
First-party analytics may count support article use after the analytics category is enabled. The checked configuration contained no Google Analytics, Google Tag Manager or Meta advertising pixel. A marketing category button alone does not mean such a tool is activated. Before adding a new provider, the operator updates the list of purposes, recipients, periods and required consents. Consent to an email newsletter is a separate decision from consent to device storage.
External services and control of choices
Choosing Google or Facebook takes you to the login provider, which uses its own session mechanisms. If Cloudflare Turnstile operates on a given form, it processes technical data needed to assess traffic; its actual scope must be disclosed in the production configuration. We do not equate all future services with tools already active on every page.
Through the 'Privacy settings' button in the footer, available even without login, you can accept, refuse or change optional categories. They are disabled by default. Refusal does not remove access to necessary account features; it may disable only features dependent on the relevant optional mechanism. The Global Privacy Control signal is taken into account by disabling analytics and marketing. Withdrawal is as accessible as giving consent and does not change the lawfulness of earlier operations. Blocking all cookies in browser settings may prevent login.
The consent exception under art. 399(3) of the Electronic Communications Law concerns only storage or reading necessary for transmission or a service actually requested by the user. The label 'security' or 'functional' alone is insufficient for any additional purpose. When the use of an existing key changes, the operator reassesses necessity and any consent required. The list reflects mechanisms of the current application; a new script, domain or device does not become covered by consent simply by being added to the code.