Privacy notice

Updated: 21 October 2026. This notice covers the public website at imdugud.uj.edu.pl, its language versions, and the identity service at id.imdugud.uj.edu.pl. The account section below explains registration and sign-in. Repository content and other Git activity require separate service-specific information.

Controller and contact

Jagiellonian University, ul. Gołębia 24, 31-007 Kraków, Poland. For this website, contact imdugud@uj.edu.pl. For personal-data questions or rights requests, contact the University’s Data Protection Officer at iod@uj.edu.pl. Current details: UJ Data Protection Officer.

What happens when you visit

Your browser sends technical information needed to deliver the page: your IP address, requested URL, time of request, and browser information. The HTTPS server records access and error logs for operation and security; a referring address can also be recorded if your browser sends it. There is no contact form, advertising, visitor analytics, behavioural profiling, or automated decision with legal or similarly significant effects on this public website.

The University’s data-protection information explains its statutory teaching and research tasks. The legal basis for providing this institutional information service and its necessary technical operation is Article 6(1)(e) GDPR, in connection with those public tasks. Data needed to respond to a rights request are processed to fulfil the applicable GDPR obligations, Article 6(1)(c). Browsing is not treated as consent.

Storage and recipients

Server access logs are configured for daily rotation with 14 retained rotations. Error records or material needed to investigate an incident or meet a legal obligation may need separate retention for that purpose. The static-page application keeps no user database or contact-form submissions. Authorised technical staff and service providers supporting the University may access operational records where necessary; disclosure to authorities requires a legal basis.

The page’s fonts, styles and images are served locally. Reading it causes no request to an analytics, font, advertising, CAPTCHA, or avatar provider. No international transfer is initiated by an embedded third-party service on this page. Ordinary internet routing and any links you choose to follow are separate from embedded services.

Your rights

Depending on the applicable legal basis, you may request access, correction, erasure, restriction, portability, or object to processing. These rights are subject to GDPR conditions and statutory retention obligations. Contact iod@uj.edu.pl. You may also complain to the President of the Polish Personal Data Protection Office.

Accounts, Git and correspondence

You can read this website without an account. Account management and Git process account, authentication, or repository data when you use them. Their session cookies are described separately in our cookie information. Gravatar and federated avatar lookup are disabled in Forgejo; avatars are stored or generated locally.

If you email us, your mail application and the University’s email service process your address and message to handle the enquiry. Do not send passwords or unnecessary sensitive information. Correspondence is retained as needed to resolve the matter and under applicable University records-retention rules.

Institutional information

See the UJ privacy policy and UJ data-protection information. Features described there, such as analytics or newsletters, are not automatically present on this website. Cookies and browser storage describes this page’s actual setup.

Identity and account data (Keycloak)

This section also covers id.imdugud.uj.edu.pl, including registration, sign-in and the account console. The controller, DPO and rights contacts above apply to this service too.

We process your username, email address, given and family names where supplied, verification status, saved language preference, account identifier, credentials in protected form, linked-provider identifiers, roles and permissions. Local passwords are stored as password verifiers, rather than readable passwords. Active sessions contain technical authentication information; requests also disclose IP address, time and browser information. Email verification and password recovery use the configured University email service.

If you choose UJ Login, your browser visits login.uj.edu.pl. Keycloak receives the identity claims released by that provider and links them to your account. Imdugud does not receive your UJ password. The UJ provider has its own privacy information. Data come from you, that provider when selected, and administrators assigning access.

The purpose is to provide and secure access to Imdugud services supporting the University's teaching and research tasks. Required account details are necessary to create and use an account; the public website remains available without registration. Connected services receive the identity claims and permissions needed for sign-in. Currently Git requests the openid, profile and email scopes; it can receive the account identifier, name, username and email address. Gravatar and federated avatar lookup are disabled.

Self-hosted Cap protects registration with a computational challenge. Your browser downloads its scripts and WebAssembly from the identity domain and sends the proof to that domain for validation. Challenge and token state are processed by the local Cap service and Valkey store. No external CAPTCHA provider is embedded. A failed check prevents registration; contact support if the check is inaccessible or appears incorrect. This anti-abuse check does not assess academic performance or make decisions about educational eligibility.

The current SSO idle timeout is 30 minutes, with a maximum session duration of 10 hours. Remember-me is disabled. These are session limits, not account-retention periods. Signing out does not delete the account. There is currently no automatic account-expiry policy: an administrator must remove account data. Contact support to request account closure or exercise your rights. Repository records and necessary institutional records may have separate retention obligations. HTTPS access logs use 14 daily rotations; Keycloak's persistent user-event and admin-event stores are currently disabled.

The account-retention schedule, the precise legal basis for each account use, and any processor/hosting arrangements must be confirmed by the responsible University unit and DPO. This technical notice does not establish those institutional decisions.

The header also checks an existing sign-in session through our first-party identity domain. That domain receives the technical request and, if present, its existing identity cookie; the public page receives only sign-in and administrator-status flags. It does not receive profile data or access tokens, and stores no result. See the session-navigation section in cookie information.

Optional USOS connection

Choosing USOS Login, or linking USOS in account management, sends you to the University's USOS authorization service at apps.usos.uj.edu.pl. Imdugud receives your USOS identifier, name and email address, and requests access to grades, course-test results, studies data for course/group student lists, and staff-perspective data for teacher-side academic reads. Mailclient permission is not requested. The retained studies, staff_perspective and crstests permissions also permit some academic writes at USOS, so the token is not strictly read-only. Imdugud restricts its use to reading academic data; enrolment changes, attendance writes and points/partial-grade writes are not implemented. The email permission supplies your own email address for your account; it does not grant mailbox access or message sending. Actual access remains limited by your USOS permissions. Your USOS password is not sent to Imdugud. USOS presents the authorization permissions before you approve them.

We request offline access and retain the access token and its secret encrypted on the server without a local expiry, including after sign-out, to support future background integrations. These credentials are not supplied to Git or browser clients. Keycloak reads your USOS staff status on USOS sign-in and at most once every 24 hours per user in the background, with delays between users to manage the Educators group. Status 2 (active academic teacher) grants membership; other statuses remove the automatic grant. Explicit administrator grants are preserved. During API failures the last verified status is retained for up to 24 hours. Group membership is supplied to Git: Educators can create organizations; Administrators can administer Git and the Imdugud Keycloak realm. Academic-data writes are not implemented.

Disconnecting USOS in account management deletes the active stored token and secret together with the account link; deleting the Imdugud account also removes them. This does not revoke authorization at USOS: you can revoke the application's access separately in USOS. Revocation at USOS invalidates its tokens, but automatic detection and removal of the Imdugud link are not implemented yet. Backup copies follow the applicable backup-retention policy; active deletion does not immediately erase existing backups.

When USOS is linked, its profile has priority over UJ. Otherwise a linked UJ profile is used. Email, first name and surname are read-only while either provider is linked; local editing becomes available when neither is linked. Provider data are refreshed when you sign in or link through that provider.

Automatic grants are shown separately in Educators/USOS and Students/USOS. Student status 2 grants Students/USOS membership; inactive or unavailable student status does not. Direct parent-group membership is reserved for manual grants. Both statuses are read in the same daily background request.

The daily USOS background check also refreshes your given name, family name and email address in Keycloak. Missing values do not erase existing data. Email addresses supplied by UJ or USOS are treated as verified, including during registration and daily USOS refresh; an address already used by another account is not assigned automatically. Git receives the updated profile on your next sign-in.