Privacy

Semestr is a personal academic planner run by its author for himself and a small number of people he knows. It is not a commercial service, and there is no analytics, advertising, profiling, or tracking of any kind.

What is stored

• Your email address, chosen name, and timezone.
• The schedule, assignments, tasks and reminders you create, and those imported from services you connect.
• Access tokens for services you connect, and the synchronisation state needed to avoid importing the same item twice.

Google user data

By default, connecting Google requests three permissions: read-only access to your calendars, the ability to manage only calendars it creates itself, and access to Google Tasks. The optional timetable cleanup asks separately for permission to edit events on calendars you own. It deletes only selected TimeEdit duplicates after verifying their Semestr copies.

Capture with Gemini

When you press Add, that Capture note is sent to Google Gemini through Vercel AI Gateway to interpret and save tasks and events. Typing and the basic preview do not send notes to a model. Your connected calendars, credentials and other notes are not sent with it. Semestr stores the items you accept and usage counters; it does not store a chat history or log your Capture text. When Gemini is unavailable or a usage limit is reached, you can review and save the basic preview without sending another model request.

That data is used for one purpose: showing your schedule inside Study Semestr and writing your Semestr items back into a calendar it owns. It is never sold, never shared with anyone, never used for advertising, and never used to train any model.

Semestr's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Where it lives

Data is held in a Supabase Postgres database hosted in the European Union, and the application runs on Vercel. Every table is protected by row level security, so one account cannot read another's rows even if the application had a bug.

Tokens for connected services are encrypted with AES-GCM before being written, in a schema the public API cannot reach. The encryption key is held outside the database, so a copy of the database alone does not yield usable tokens.

Deleting it

Disconnecting a service deletes its stored tokens. Ask the author to delete your account and everything belonging to it is removed, including anything imported from connected services. You can also revoke Study Semestr's access at any time from your Google account permissions, independently of Semestr.

Contact

Semestr is maintained by a single student. Questions about your data go to whoever gave you the access code.