Privacy

Page analytics. I use cookieless analytics that record which pages are viewed, where a visit came from, the country, and the browser type. No cookies are set, nothing follows you to other sites, and no personal profile is built. I cannot tell who you are from it.

Contact form. The form is processed by Formspree. When you send a message, the name, email, topic and text you type are passed to Formspree, which emails them to me and keeps a copy in my account there. Only I can read them, and I use them to reply to you and nothing else. Ask me through the form and I will delete a message.

Labs tools without an account. Anything you type into the Resume Builder, or into Semester while you are not signed in, stays in your own browser’s storage. It is never uploaded, and I cannot see it.

Web fonts. Pages load fonts from Google Fonts, which means your browser makes a request to Google to fetch them.

Questions. If you want to know what I hold about you, or want a message deleted, use the contact form and ask.

The Semester tracker works fully without an account, storing everything in your browser. An account is optional and exists for one reason: so your data follows you to another device. Creating one changes what is stored and where, so this section sets that out precisely.

What is stored. Two things. Your email address, held by the authentication service so you can log in and reset your password. And one row of your semester data: your college and programme, your subjects and their categories and credits, every class you log with its date and status, any approved-exclusion flags you set, your expected class counts, and your attendance threshold. If you sign in with Google, Google also passes on the email address of the account you chose.

What is not stored. No password is ever visible to me — authentication handles it and I never receive it. There is no tracking of how you use the tool, no analytics tied to your account, and no third party receives your semester data.

Where it is stored. On Supabase, a hosted Postgres provider, in a project I control. Supabase acts as the processor; the data sits on their servers, not mine.

Who can read it. Only you. Every request is checked against your own user ID by row-level security in the database, so one account cannot read, change or delete another’s row — the key shipped in the browser cannot bypass that. I have administrative access to the project, which means I could technically look at the table; I do not, and there is nothing in it I would have any use for.

How to export it. Open your account page and choose Download my data. You get a JSON file containing your email, your cloud copy and the copy on that device. This works at any time and does not require deleting anything.

How to delete it. On the same page, type DELETE into the confirmation box. Your semester row is removed from the database immediately and permanently. There is no backup, no soft-delete and no recovery window — once it is gone I cannot restore it, so export first if you want a copy. Logging out is separate and deletes nothing; it also asks before touching the copy on your device, and defaults to leaving it alone.

Data requests. For anything the buttons do not cover — a copy in another format, a correction, or removal of a login record — use the contact form and say what you want. It reaches only me. If you no longer have access to the account, say which email address it used.