Privacy Policy

Preamble

With the following privacy policy, we would like to inform you about the types of your personal data (hereinafter also referred to as "data") that we process, for what purposes, and to what extent, in connection with the provision of our application.

Our terms of use also apply to your use of Lectio.

The terms used are not gender-specific.

Last updated: October 23, 2026

Table of Contents

Controller

Mateo Arenas Salas
Spreestraße 5, Flat 5130
64295 Darmstadt, Germany

Email: mateoas@icloud.com

Overview of Processing Activities

The following overview summarizes the types of data processed and the purposes of their processing, and refers to the data subjects concerned.

Types of data processed

Categories of data subjects

Purposes of processing

Relevant Legal Bases

Relevant legal bases under the GDPR: Below you will find an overview of the legal bases of the GDPR on which we base our processing of personal data. Please note that, in addition to the provisions of the GDPR, national data protection regulations may apply in your or our country of residence or registered office. Should more specific legal bases apply in individual cases, we will inform you of these in this privacy policy.

National data protection regulations in Germany: In addition to the data protection regulations of the GDPR, national data protection regulations apply in Germany. These include, in particular, the Federal Data Protection Act (Bundesdatenschutzgesetz – BDSG). The BDSG contains, in particular, special provisions on the right to information, the right to erasure, the right to object, the processing of special categories of personal data, processing for other purposes, and the transmission and automated decision-making in individual cases, including profiling. Furthermore, state data protection laws of the individual federal states may apply.

Applicability of data protection provisions in the country of registered office: In the country in which the controller has its registered office, national data protection regulations apply in addition to the General Data Protection Regulation (GDPR).

Security Measures

In accordance with the legal requirements, taking into account the state of the art, the cost of implementation, and the nature, scope, context, and purposes of processing, as well as the varying likelihood and severity of the risk to the rights and freedoms of natural persons, we implement appropriate technical and organizational measures to ensure a level of protection appropriate to the risk.

These measures include, in particular, safeguarding the confidentiality, integrity, and availability of data by controlling physical and electronic access to the data as well as access, input, disclosure, availability, and its segregation. Furthermore, we have established procedures to ensure the exercise of data subject rights, the deletion of data, and responses to any compromise of data. We also take the protection of personal data into account as early as the development or selection of hardware, software, and procedures, in accordance with the principle of data protection through technology design and through data protection-friendly default settings.

Securing online connections through TLS/SSL encryption technology (HTTPS): To protect the data of users transmitted via our online services from unauthorized access, we use TLS/SSL encryption technology. Secure Sockets Layer (SSL) and Transport Layer Security (TLS) are the cornerstones of secure data transmission on the internet. These technologies encrypt the information transmitted between the website or app and the user's browser (or between two servers), thereby protecting the data from unauthorized access. TLS, as the more advanced and secure version of SSL, ensures that all data transmissions meet the highest security standards. When a website is secured with an SSL/TLS certificate, this is indicated by the display of HTTPS in the URL. This serves as an indicator to users that their data is being transmitted securely and encrypted.

Disclosure of Personal Data

In the course of our processing of personal data, it may occur that such data is transmitted to or disclosed to other bodies, companies, legally independent organizational units, or persons. Recipients of this data may include, for example, service providers commissioned with IT tasks, or providers of services and content that are integrated into a website. In such cases, we comply with the legal requirements and, in particular, conclude appropriate contracts or agreements that serve to protect your data with the recipients of your data.

International Data Transfers

Data processing in third countries: If we transfer data to a third country (i.e., outside the European Union (EU) or the European Economic Area (EEA)), or if this occurs in connection with the use of third-party services or the disclosure or transmission of data to other persons, bodies, or companies (which becomes apparent from the postal address of the respective provider, or where the privacy policy explicitly refers to data transfers to third countries), this always takes place in accordance with the legal requirements.

For data transfers to the USA, we rely on the Data Privacy Framework (DPF) where the recipient is certified under it; the EU Commission recognized the DPF as a safe legal framework by an adequacy decision dated July 10, 2023. Where a recipient is not certified under the DPF, the transfer is based on the EU Commission's Standard Contractual Clauses, which establish contractual obligations to protect your data.

For each individual service provider, we inform you whether they are certified under the DPF and whether Standard Contractual Clauses are in place. Further information on the DPF and a list of certified companies can be found on the website of the U.S. Department of Commerce at https://www.dataprivacyframework.gov/. Specific information on the providers we use can be found in the section "Third-Party Providers Used (Supabase, Vercel, GitHub)".

For data transfers to other third countries, corresponding safeguards apply, in particular Standard Contractual Clauses, explicit consent, or legally required transfers. Information on third-country transfers and applicable adequacy decisions can be found on the EU Commission's website: https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection_en.

General Information on Data Storage and Deletion

We delete personal data that we process in accordance with the legal provisions as soon as the underlying consent is revoked or there is no further legal basis for the processing. This applies to cases in which the original purpose of processing no longer applies or the data is no longer needed. Exceptions to this rule apply where statutory obligations or particular interests require longer retention or archiving of the data.

In particular, data whose storage is necessary for the assertion, exercise, or defense of legal claims or to protect the rights of other natural or legal persons may be retained for longer accordingly.

Our privacy notices contain additional information on the retention and deletion of data that applies specifically to certain processing activities.

Where multiple retention periods or deletion deadlines are specified for a given piece of data, the longest period shall always apply. Data that is no longer retained for its original purpose, but is retained due to statutory requirements or other reasons, is processed exclusively for the reasons justifying its retention.

Rights of Data Subjects

Rights of data subjects under the GDPR: As a data subject, you have various rights under the GDPR, arising in particular from Articles 15 to 21 GDPR:

Provision of the Online Offer and Hosting

We process users' data in order to be able to provide them with our online services. For this purpose, we process the user's IP address, which is necessary to deliver the content and functions of our online services to the user's browser or device.

Further information on processing activities, procedures, and services:

Registration, Login, and User Account

Users can create a user account. As part of registration, users are informed of the required mandatory information, which is processed for the purpose of providing the user account on the basis of the fulfillment of contractual obligations. The data processed includes, in particular, login information (email address and password, or the details from Apple or Google, see "Signing In with Apple or Google").

When using our registration and login functions and the user account, we store the IP address and the time of the respective user action. This storage is based on our legitimate interests as well as those of users in protection against misuse and other unauthorized use. This data is generally not disclosed to third parties unless it is necessary for the assertion of our claims or there is a legal obligation to do so.

A user account is optional and allowed only from the age of 16. Without a user account, Lectio stores your data only on your device (see "Semester Sync").

Users may be informed by email of matters relevant to their user account, such as technical changes.

Further information on processing activities, procedures, and services:

Signing In with Apple or Google

Instead of an email address and password, you can create your user account and sign in with Apple or Google. We never receive your Apple or Google password.

Semester Sync

Without a user account, Lectio stores all of your semester data only on your device. If you are signed in, we also store it on our servers (Supabase, see "Third-Party Providers Used") so that it is the same on all of your devices. The following is synced:

This data can only be retrieved with your user account. Your friends see only the parts of your class schedule that you share (see "Username and Friends"). A change that has not yet reached our servers, for example because you are offline, waits on your device until it is uploaded.

What does not leave your device: Without a user account, your semesters, your credit plan and your tags are not transferred to us. Lectio then connects only when you start it yourself: to send feedback (see "Third-Party Providers Used") or to retrieve data directly from your university (Moodle, TUCaN). It also asks the App Store for updates (see "Update Check"). Even with a user account, the following stays on your device: your Moodle token, the app's settings on this device, which friends you show on your schedule, and the data that widgets and reminders are made from.

Contact and Inquiry Management

When contacting us (e.g., by email, telephone, or through the feedback in the app), as well as in the context of existing user and business relationships, the information provided by the inquiring parties is processed to the extent necessary to respond to the inquiries and any requested measures.

Further information on processing activities, procedures, and services:

Moodle Integration

Connecting the app to your university's Moodle site is optional. You pick your university from a list built into the app, or enter the address of the Moodle site. Searching the list transfers nothing; the app checks an address you enter with a request to that site that contains nothing about you.

Usually you connect by signing in on your Moodle's own sign-in page, which the system opens in a browser window. Your password goes directly to your university; Lectio never sees it. Moodle then issues the app a personal access token, as it does for the official Moodle app. If your university does not allow this sign-in, you can paste a token instead that you create in your Moodle profile.

The token is stored only in the protected keychain of this device; it is never synced through iCloud Keychain or transferred to us or to another device. The connection itself, that is the site address and your name in Moodle, is also stored only on this device.

The app retrieves your name, your courses and their contents directly from your Moodle site: when you import or sync courses, and for linked courses also by itself when the app opens, to find new material. These requests do not go through us. What you import becomes part of your semester, and so that syncing with Moodle works on all of your devices, so do the site address, the ids and names of the linked Moodle courses, and the ids and links of the material imported and skipped. If you are signed in, this is synced with the semester (see "Semester Sync").

"Open in Moodle" opens a Moodle page in the Moodle app if it is installed, otherwise in the browser; the Moodle app receives the page's address.

You can disconnect Moodle at any time in the app under Profile, which deletes the token from this device. The Moodle site is operated by your university, whose own privacy policy applies to it.

TUCaN Import

Importing grades and credits from TUCaN, TU Darmstadt's campus management system, is optional. Lectio offers it mainly when you are connected to TU Darmstadt's Moodle, and imports only when you start the import yourself.

To import, you sign in on TU Darmstadt's own sign-in pages, which Lectio shows in a browser view of its own. Your password and your second factor go directly to TU Darmstadt; Lectio does not read or store them. The browser view keeps no data: cookies and other website data are discarded as soon as it closes.

After you sign in, Lectio receives only TUCaN's session cookie. With it, the app retrieves your transcript of records and your module results, and then signs you out of TUCaN. The cookie and the retrieved pages are held only in memory, are not transferred to us, and are discarded as soon as you close the import. The pages also contain details such as your name; Lectio takes only the data listed below and shows you what it would take before anything is saved.

What you take over becomes part of your semesters and your credit plan: module names and numbers, grades, credits, whether a module was passed, and the areas of your degree programme. If you are signed in, it is synced like all semester content (see "Semester Sync"). TU Darmstadt's privacy policy applies to the sign-in and to TUCaN's pages.

Username and Friends

If you have a user account, you can choose a username; this is optional. Without a username, nobody can find you, and you cannot add friends. With one, other signed-in users can find you by it: as soon as someone types at least three characters, the app shows up to five usernames that begin with them. Only the username is shown, never your email address or your name. A username that you give up, by changing it or by deleting your user account, stays reserved for seven days and can then be chosen by someone else. The app refuses offensive usernames; we may also remove a username later if it breaks our terms of use.

You can send other users a friend request, which they can accept or decline. You can withdraw a request and remove a friend at any time. Requests and friendships are stored on our servers together with the user IDs of both accounts and are visible only to the two accounts concerned.

By accepting a friend request, you and your friend agree to see each other's class schedule. Under "What Friends See" (in the app's Friends sheet) you choose what is shared: lectures, exercise groups, exams and other classes; the names of your semesters, courses and classes; rooms; and the notes you write on individual classes. The start date and number of weeks of your semesters are used to place the classes in the calendar. Your attendance, readings, tasks, grades, credits and study time are never shared. Your friend's app retrieves the shared schedule from our servers when it is displayed and does not store it permanently. Sharing ends as soon as either of you removes the friendship. Which friends you have chosen to show on your schedule is stored only on your device.

You can block another user. A block ends any friendship and deletes all requests between you; neither of you then finds the other in the search, and the blocked user cannot send you requests. The blocked user is not told. You can also report a user, for example for an offensive username or unwanted requests. A report contains your user ID, the reported user's ID and username, the reason you chose and any details you add. Only we can read reports, and we review them within 24 hours; the reported user is not told who reported them. We use reports to protect users of the app and to take action against misuse, for example by removing a username or deleting an account.

Update Check

If Lectio was installed from the App Store, the app asks Apple's public App Store lookup service at most once a day whether a newer version is available, and tells you if there is one. Apple receives the app's identifier (com.masprime77.lectio) and the region set in your device settings, and, as with any connection, your IP address; nothing about your user account or your semesters is transferred. Apple's privacy policy: https://www.apple.com/legal/privacy/.

Third-Party Providers Used (Supabase, Vercel, GitHub)

For the operation and provision of our application, we use the following third-party providers as processors:

Changes and Updates

We ask that you regularly inform yourself of the content of our privacy policy. We will adjust the privacy policy as soon as changes to the data processing we carry out make this necessary. We will inform you as soon as the changes require your participation (e.g., consent) or other individual notification.

Where we provide addresses and contact information for companies and organizations in this privacy policy, please note that such addresses may change over time, and we ask that you verify the information before making contact.

Glossary of Terms

This section provides an overview of the terms used in this privacy policy. Where terms are defined by law, their statutory definitions apply. The following explanations are intended primarily to aid understanding.

Created with the free privacy policy generator from Dr. Thomas Schwenke, Datenschutz-Generator.de