Privacy notice

Version 1 · applies to this deployment of the tracker.

Who is responsible

The data controller is .

What we hold and why

• Member records: name, email address () and GitHub username, plus which projects and teams each person is in and any roles (e.g. team lead, supervisor). Purpose: organising projects and teams. Lawful basis: legitimate interests in running the group's projects (UK GDPR / EU GDPR Art. 6(1)(f)).
• Accounts for people who sign in: GitHub numeric user id, GitHub username, administrator flag, access grants, sign-in times. Purpose: access control and security. Lawful basis: legitimate interests.
• Audit log: who changed what and when. People appear only as internal ids, never by name or contact details. Kept for days, then deleted automatically.

We do not keep your GitHub access token (it is revoked straight after sign-in), use analytics or tracking, load third-party fonts or scripts, or keep request logs with IP addresses.

Where it is stored and how it is protected

Data is stored in . Names, emails and GitHub usernames are additionally encrypted at rest with AES-256-GCM using a key held only as a deployment secret. All traffic uses HTTPS. Read-only exports are encrypted links protected by long, randomly generated passwords and expire automatically.

The storage provider keeps encrypted point-in-time backups for up to 30 days, so erased data disappears from backups within 30 days of erasure. Encrypted fields stay unreadable in backups without the deployment key.

Processors: Cloudflare (hosting, EU jurisdiction storage) and GitHub (sign-in). Only one strictly necessary cookie is used (your sign-in session), so no cookie banner is needed.

How long we keep it

Member records are kept while the person is involved in the group's projects and removed on request or when no longer needed. Anyone who is no longer in any project is erased automatically after days. Sign-in sessions expire after days. Export links always expire, at most a year after creation (30 days by default).

Your rights

You can ask for access to, correction or erasure of your data, object to its processing, or ask for a copy in a portable format. Signed-in users can download their own data and delete their account from the account menu. Administrators can export or permanently erase any member record. Erasure also revokes any snapshot export containing that person. You can also complain to the UK Information Commissioner's Office (ico.org.uk) or your local data protection authority.