Privacy policy

Semestr is an independent academic planner for events, coursework, tasks, and reminders. This policy explains how information is handled when you visit the website, use your account, or connect another service. It should be read alongside our Terms of service.

1. Who is responsible

The data controller is Marius Morutan Vlad, Netherlands, the operator of Semestr. For privacy questions, support, or a request about your information, email mmorutan17@gmail.com. You do not need a Semestr account to contact us.

2. Information we process

• Account information: your Google account identifier, email address, and basic profile information supplied through Google sign-in, plus your chosen display name, timezone, preferences, and account access status. Google authenticates you; we do not receive your Google password.
• Planner content: titles, notes, locations, links, dates, times, recurrence information, completion status, and reminder details that you enter or import from a connected service.
• Connection information: the services and calendars you select, authorisation tokens or private feed links, permission settings, source identifiers, and synchronisation records needed to update items and prevent duplicates.
• Technical and support information: request and error diagnostics, security and access records, usage counters, and messages you send us. Hosting and authentication providers also process connection details such as IP addresses and browser information.

Information comes from you, Google when you sign in, the services you choose to connect, and operation of the website. A connected event may include information about other people. Only add information you are entitled to use, and avoid unnecessary sensitive personal information.

3. Why we use it

We use account and planner information to provide the service you request: signing you in, displaying your schedule across devices, saving changes, handling reminders, synchronising connected services, providing support, and carrying out account deletion. The legal basis is performance of our agreement with you, or steps you request before entering that agreement (GDPR Article 6(1)(b)). Without the necessary account information we cannot provide a signed-in planner.

We use proportionate technical records to prevent abuse, investigate failures, and keep the service secure and reliable, based on our legitimate interests (Article 6(1)(f)). Where processing is required by law, the basis is a legal obligation (Article 6(1)(c)). Where we ask for consent for an optional use, you may withdraw it without affecting the lawfulness of earlier processing (Article 6(1)(a)). Granting a Google permission is not blanket consent to unrelated uses of your data.

We do not sell your personal information or use it for advertising. We do not make automated decisions about you that produce legal or similarly significant effects. Accepting the Terms does not waive your privacy rights or authorise unrelated processing.

4. Google sign-in, Calendar, and Tasks

Google sign-in identifies your account. Connecting Calendar and Tasks is a separate choice that enables additional access. The Google consent screen shows the permissions requested. Our Google integration uses:

• Calendar read access: to discover calendars and import event details from the calendars used by your connection so they can appear in Semestr.
• Management of app-created calendars: to create and maintain a calendar in your Google account for items synchronised by Semestr, including updates and deletions arising from your actions.
• Google Tasks access: to find or create the task list used by Semestr and synchronise tasks in that list. Google grants a broader Tasks permission; Semestr uses it for this integration, not to browse unrelated task content.
• Optional editing of events on calendars you own: requested separately when you enable editing of those events or timetable cleanup. Cleanup removes selected duplicate timetable events only after checking their Semestr copies. Enabling event editing does not by itself request duplicate cleanup.

We store imported content and the connection state needed to provide these features, subject to the retention rules below. Access tokens allow synchronisation while you are away from the website. Google API data is used only for the disclosed planner features. It is not sold, used for advertising or credit decisions, or used to train general-purpose AI models. We do not automatically send your imported calendars or tasks to the Capture model.

Human access to Google API data is limited to specific data you have affirmatively agreed we may view for support, security investigations, legal requirements, or other uses expressly permitted by Google's Limited Use rules. Transfers are limited to providing the requested features through our service providers or other circumstances permitted by those rules, such as a legal obligation.

Semestr complies with the Google API Services User Data Policy, including its Limited Use requirements, when using information received through Google APIs. The applicable Google Workspace API user data and developer policy also applies to Workspace API data.

You can disconnect a service in Semestr and revoke Google permissions through your Google account connections. Disconnecting removes the stored credentials for that connection and stops further synchronisation. It does not by itself delete your Semestr account or all previously imported items; those follow the retention and deletion rules below. Revoking access in Google also prevents future authorised access, but is not an instruction to delete your Semestr account.

5. Other connections and Capture

If you connect an academic service such as Canvas or a TimeEdit calendar feed, we retrieve the coursework or timetable information needed for the import you request. A private subscription URL or access token is treated as a credential. These connections are optional.

When you submit a Capture note using Add, Semestr sends that note, the current date and time, and your timezone to Google Gemini through Vercel AI Gateway to interpret it as planner items. Typing and the initial basic preview do not make a model request. Your other planner content and connection credentials are not included. Anything you paste into the submitted note is included, so review it before submitting.

Semestr stores the resulting items you save and usage counters, rather than a separate chat history. Model processing is separate from database storage and may involve provider security retention. We do not promise that deleting a saved item instantly removes every provider copy. You can use the ordinary item forms without AI; a basic preview is also available when AI interpretation is unavailable. Check generated dates, times, and details, because interpretation can be wrong.

6. How long we keep information

The default retention period for finished planner content is 90 days. It does not run from the date an item was first saved. Future events and unfinished tasks or reminders remain available while your account is active.

• Events: the 90 days start when the event ends. Each occurrence of a recurring event is treated separately, so retaining future occurrences does not require keeping expired past occurrences.
• Tasks: the 90 days start when the task is completed or deleted. An overdue task that is still unfinished is kept.
• Reminders: the 90 days start when the reminder is completed, dismissed, cancelled, or deleted. A reminder attached to an item is also removed when that item is permanently deleted.
• Items deleted before they finish: the 90 days start on deletion. Deleting an already finished item does not extend its existing retention deadline.

Completing or dismissing an item does not immediately erase it. If you reopen it or restore it before expiry, it returns to the applicable active-item rule. Content that reaches the retention deadline is removed from the active database by the next daily cleanup. Routine viewing, signing in, or synchronising does not restart the 90-day period. Content already permanently removed cannot be recovered by signing in again.

We keep your profile and necessary account settings while your account is active. Routine database records for completed synchronisation runs, resolved conflicts, and inactive security or usage counters are removed after 90 days from completion, resolution, or their last relevant activity. Minimal source identifiers may remain while a connection is active to prevent a removed item being imported again; these must not retain its title, notes, location, or event times and are removed on final account deletion.

7. Immediate account deletion

When you confirm Delete my account in Settings, we immediately and permanently delete your account from our active database, including your profile, planner content, tasks, reminders, connections, and stored connection credentials. You must type your account email address to confirm this action. Once deletion succeeds, we sign you out.

There is no waiting period or account recovery window. Completed account deletion cannot be cancelled or undone. Signing in again with the same Google account does not restore your deleted account or its contents. Account deletion takes precedence over any remaining 90-day item retention period, including for future events and unfinished work. Backup expiry and limited retention exceptions are explained below.

If the app reports that deletion failed, your request has not been confirmed as complete. You can retry or contact us for help. Deletion does not depend on receiving an email.

You can also request erasure by emailing mmorutan17@gmail.com. We handle a valid erasure request without undue delay, subject to any applicable legal exception. You do not need access to the app to contact us, although we may need to verify your identity before acting.

These rules concern copies held by Semestr. Deleting your Semestr account does not delete your Google account or erase calendars, events, or tasks that remain in your own Google account. You can manage or delete those directly in Google. Data held by your university or another independent source is also subject to that source's own policy.

8. Backups and limited exceptions

Deletion from the active database is separate from expiry of recovery backups. An older backup may temporarily contain deleted information until it expires under the hosting provider's configured backup schedule. Backup copies are restricted to recovery purposes; if we restore a backup, deletion instructions must be reapplied before the affected data returns to normal use. They are not an account recovery option after final deletion.

We retain support correspondence only for the time needed to resolve the request and any related dispute. Where a specific legal obligation, security incident, or legal claim requires limited information to be kept longer, we restrict it to that purpose and remove it when the need ends. This is not a general exception for retaining your schedule.

9. Service providers and international processing

• Supabase: database storage and account authentication.
• Vercel: website hosting, application processing, and AI Gateway.
• Google: sign-in, optional Calendar and Tasks connections, and Gemini processing for submitted Capture notes.
• Your connected academic services: providing the imports you request.
• Email delivery services: delivering essential account notices using your email address and the information needed for the notice, without including your schedule.

Providers receive the information needed for their role. Providers acting on our instructions are subject to data-processing terms. Google and your university also operate their own services under their own privacy notices. A disclosure required by law is limited to what the applicable legal requirement permits or requires.

An EU hosting region does not mean every support, security, email, or AI operation occurs in the European Economic Area (EEA). Where our providers process personal data outside the EEA, we use a valid transfer mechanism, such as a relevant European Commission adequacy decision or Standard Contractual Clauses with additional safeguards where required. Contact us for information about the safeguards applicable to your data and how to obtain a copy.

10. Security and browser storage

We use HTTPS for website connections and Supabase's encryption at rest for the database. Account access controls, including row level security, restrict users to their own records. Credentials for connected services receive additional encryption before database storage.

This is not end-to-end encryption. Authorised application processes and database administrators can technically read planner content when needed to operate the service. Access is limited by role and purpose, including the Google data restrictions above. Encryption does not make data inaccessible to every administrator or guarantee that no incident can occur.

We use cookies and browser storage for the access gate, authentication, connection security, and preferences such as your theme. Blocking these may prevent sign-in or other requested features from working. We do not use advertising cookies or third-party behavioural analytics on the website. Necessary technical logs are separate from advertising tracking.

11. Your rights and policy changes

Depending on the circumstances, you may request access, correction, erasure, restriction, or portability of your personal data, object to processing based on legitimate interests, and withdraw consent where consent is the basis. Email the contact above; you do not have to delete your account to exercise another right. We may request proportionate information to verify your identity.

We respond without undue delay and normally within one month. If a lawful extension is necessary because of the complexity or number of requests, we explain the reason within that first month; the extension may be up to two further months. If we cannot grant a request, we explain why and how you may challenge the decision.

You may complain to the Dutch Autoriteit Persoonsgegevens or the competent supervisory authority where you live or work, or where you believe an infringement occurred. You do not need to contact us first.

We update this policy when our practices change and show the revision date above. We give notice of material changes before they apply where practicable and obtain consent when the law requires it. A policy update does not itself authorise a new use of your information.