Private by design.

Last updated 15 August 2026

Lectio Sync has no analytics, advertising, telemetry, crash-reporting service or application backend.

Stored locally

Lectio school ID, student ID, optional school name and connection time.
Sync settings, status timestamps and reconciliation metadata.
The identifier and display name of the dedicated calendar.
In Firefox only, a revocable Google OAuth refresh token required for synchronization after restart.

The extension does not store Lectio page HTML, MitID data, Lectio cookies, Google passwords or long-lived Google access tokens. Chrome and Brave leave token storage to the browser. Firefox caches short-lived access tokens only in memory.

Sent to services

Lectio receives normal authenticated timetable requests from the student’s browser.
Chrome, Brave and Firefox send selected timetable fields to Google Calendar after the user explicitly connects it.
Safari sends selected timetable fields to Apple EventKit, which writes them to the Google calendar configured in Apple Calendar.

Calendar events can contain the activity title, note, time, room, teacher, Lectio activity link and cancellation state. Homework is disabled by default. Attached files and their contents are not copied.

Deletion and disconnect

Disconnecting clears the relevant extension connection state. Firefox also removes its locally stored refresh token and requests revocation from Google. Disconnecting does not delete the dedicated calendar or existing events; the user can delete the Lectio calendar through Google Calendar or Apple Calendar.

Clearing browser extension data or uninstalling removes local state according to the browser’s normal storage behavior. Calendar events already sent to a provider remain subject to that provider’s retention controls.