Addenda Carolina

SIS Login Fix — Privacy policy

Updated .

This policy covers the non-tracking SIS Login Fix extension and userscript, version 0.11.0, maintained by Addenda Carolina.

Local data

The extension reads the current SIS, WebApps, or CAS URL and relevant page elements. It checks login/logout controls and stores server-issued session IDs, the SIS tid value, timestamps, and recovery-attempt records in your browser. This lets it reuse a validated session when a SIS link is missing a session or contains one confirmed to have expired.

Session records use is.cuni.cz website storage (localStorage and per-tab sessionStorage), not browser sync. The extension does not keep a browsing-history or activity log.

On cas.cuni.cz, it adjusts the one-time-code field and its helper UI. It does not read, save, generate, or submit passwords or entered codes.

Network requests

No extension data is sent to the maintainer. There are no analytics, telemetry, ads, or remote scripts. Data is not sold or used for unrelated purposes.

Session IDs are reused only in HTTPS navigation to is.cuni.cz. Your browser still makes ordinary requests to the university's websites; those requests and the university's handling of them are not controlled by this extension.

Retention and removal

Active session records can be reused for up to 12 hours, rejected-session records for up to 24 hours (at most eight per service), and recovery-attempt records for up to 5 minutes. These are reuse limits, not scheduled deletion times: records can remain in website storage until overwritten or cleared.

To remove them, disable the extension and any other SIS session-bridge script, then clear site data for is.cuni.cz in your browser. This also removes other SIS site data and may sign you out. Uninstalling the extension alone does not clear website storage.

This website and contact

This page has no analytics, forms, or third-party embeds. It is hosted on GitHub Pages; GitHub may process ordinary web-request data under its privacy statement.

Questions can be sent through the project's GitHub issues. Issues are public; do not post session URLs, passwords, or one-time codes.