Semester

Privacy Policy

Last updated 25 August 2026

Semester builds you a set of Google Calendars from your class schedule, your Blackboard assignment feed, the Razorback game schedule, and the campus and chapter calendars you choose to follow. This page describes exactly what it stores and why. It is written to be read, not to be skimmed past.

What Semester stores

All of it lives in a Supabase Postgres database in the US, protected by row-level security so one account cannot read another's rows. Your Google refresh token sits in a table that no signed-in user can query at all — only the server-side sync job can read it.

What Semester does with your Google account

Semester creates and maintains up to five calendars of its own: your classes, your assignments, Razorback games, the campus calendars you follow, and your Greek chapter. It only writes to events it created itself, which are tagged so it can recognize them. Events you add by hand, on those calendars or anywhere else, are never modified or deleted.

Being precise about the permission. Semester requests exactly one Google permission: calendar.app.created — "make secondary Google calendars, and see, create, change, and delete events on them". It is the narrowest permission Google offers that can still create a calendar, and it applies only to calendars Semester itself made. Your other calendars are not merely left alone; Google never grants access to them, so Semester cannot read or change them even by mistake. You can revoke this at any time.

What Semester never does

Semester's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Who else is involved

Semester runs on three services, and none of them receive your data for their own purposes: Supabase (database and sign-in), Cloudflare (serves this site), and Google Calendar (where your events go). Semester also fetches the public Razorback schedule from ESPN, which involves none of your data.

Semester reads your Blackboard feed directly from learn.uark.edu using the link you provide. It has no other connection to Blackboard or to the University of Arkansas.

How long Semester keeps it, and how it is protected

Your rows stay for as long as your account exists. Revoke Semester in your Google account and the stored refresh token stops working immediately; it is discarded the next time a sync tries to use it. Assignment titles and campus events are replaced on every sync rather than accumulating, so the database holds the current term, not a history of it. Nothing is kept after you ask for deletion.

Everything is served over HTTPS. The database is Supabase's managed Postgres, which is encrypted at rest, and every table is behind row-level security keyed to your account. The Google refresh token sits in a table with no client-readable policy at all — a signed-in browser cannot query it under any circumstances, only the server-side sync job can.

Deleting your data

Revoke Semester at myaccount.google.com/permissions and it immediately loses all access to the calendars it created. To have the stored rows deleted as well, email the address below and say so — everything tied to your account will be removed. The calendars Semester created stay in your Google account, and are yours to keep or delete.

Contact

lafarve09@gmail.com

Terms of Service