Coursework Compass

Privacy Policy

Last updated: 17 November 2026

Coursework Compass helps students plan and evidence their coursework. This policy explains what personal data it uses, why, who else is involved, how long it's kept and what your rights are. It's written to be read, so it uses plain English.

Who we are and how to contact us

Coursework Compass ("we", "us") is an independent, non-commercial student project. We decide how and why your personal data is used, so we are the data controller under UK data protection law (the UK GDPR and the Data Protection Act 2018).

For any privacy question, request or complaint, email privacy@courseworkcompass.com. That includes asking for a copy of your data, asking us to correct or delete it, objecting to how we use it, or telling us about a security problem. We'll reply within one month.

What we collect and why

DataWhere it comes fromWhy we use itLegal basis
Account: name, email address, profile picture (if you sign in with Google), when you confirmed you're 16 or over, which version of the Terms you agreed to and when, when you accepted the AI notice, and whether your account is suspended and whyYou, or your Google account if you sign in with GoogleTo create and run your account, keep a record of what you agreed to, and contact you about it, including notices about material changes to the Terms or serviceContract
Sign-in details: password (stored only as a scrambled hash), linked Google account, passkeys (a public key and device type), two-step verification (an encrypted secret and hashed backup codes)YouTo let you sign in securelyContract
Your coursework: modules, assignment briefs, criteria, sources and the text taken from them, notes, to-dos, plans, activity logs (including any location you type), tutor feedback, timer sessions, Compass AI chats and the draft files you uploadYouTo provide the app's featuresContract
Google Calendar, if you connect it (see How we use Google user data)Your Google accountTo show your timetable, tag events to modules and add study sessions you approveContract
Sessions: the browser or device you're signed in on and its IP addressYour browserTo keep you signed in, show you where you're signed in, alert you to sign-ins from new browsers and protect against attacksLegitimate interests (security)
AI usage records: the type and time of each AI requestThe appTo apply fair daily AI limits so the free service stays affordable and can't be abusedLegitimate interests
Messages you send usYouTo answer youLegitimate interests

"Contract" means we need the data to provide the service you signed up for. Where we rely on legitimate interests, we've checked that our interest (keeping accounts secure and the service affordable) isn't outweighed by your privacy, and you can object by emailing privacy@courseworkcompass.com.

We don't ask for sensitive information (such as health, religion or ethnicity). Coursework can sometimes include it, so please only add what you need, and don't upload other people's sensitive information. We don't make any automated decisions about you that have legal or similarly significant effects, and we don't use your data for advertising, profiling or selling.

How AI features use your content

Some features use Claude, an AI model made by Anthropic. When one runs, the content it needs is sent to Anthropic in the USA to produce a response. Before any of them can run, the app shows you a notice explaining this and asks you to continue; until you do, nothing is sent.

Features that run when you ask

  • Compass AI chat: your messages and the conversation so far, plus context about the page you're on: your modules, briefs, criteria, to-dos, sources and summaries, and the draft you're viewing. If you've connected Google Calendar, each message also includes your calendar names and the next 7 days of events (day, time, title and module tags), and the AI can look up other events (title, time and location). It can suggest creating, changing or deleting events, but nothing changes until you confirm.
  • Reading a brief: the brief and any criteria document you add.
  • Extracting a source: the source's text and your module's criteria.
  • Refreshing nudges, planning, and proposing tasks from tutor feedback: the relevant module details, to-dos, recent activity and the text you enter.

Features that run automatically

  • Draft feedback when you upload a draft: the draft's text (or image), the sources you link and the brief.
  • An AI note when you save an activity: the activity and your module details.
  • Suggested links when you add a to-do or checklist item: the names of your to-dos, checklist items and criteria.
  • Guessing the module while you type tutor feedback: the feedback text and your module names.

None of the automatic features use your calendar. We never send your name or email address to Anthropic, although anything you type or upload is sent as it is.

Anthropic acts as our processor. Under its commercial terms it doesn't use this content to train its models, and it deletes it within 30 days, except that content flagged for breaking its usage policy can be kept for up to 2 years. AI output can be wrong; see our Terms.

How we use Google user data

You can sign in with Google, and separately connect Google Calendar. Both are optional and you can remove them at any time.

What we access

  • Sign in with Google (scopes openid, email, profile): your name, email address and profile picture.
  • Google Calendar: we request exactly these scopes:
    • https://www.googleapis.com/auth/calendar.calendarlist.readonly: to see the list of your calendars (name, description, time zone, colour and your access level).
    • https://www.googleapis.com/auth/calendar.events: to read events on those calendars (title, description, location, start and end time, all-day, status and repeat series) and to create, change or delete events, but only after you confirm each change in the app.
    • openid and email: to identify which Google account you connected.
    We don't read or store attendees. Connections made before 17 November 2026 asked for calendar.readonly instead of calendar.calendarlist.readonly; disconnecting and reconnecting Google Calendar in Account settings replaces it with the narrower permission.

How we use it

  • To show your calendar and today's classes in the app, let you tag events to modules, count study time and add study sessions you approve.
  • To answer your questions in Compass AI chat, as described in How AI features use your content. Calendar data is only sent to Anthropic when you use Compass AI chat, and never to train AI models.

How we store, share and protect it

  • Calendar data and the access tokens Google gives us are stored in our database on our server (see Where your data is processed), are only ever shown to you, and are never sold or used for advertising.
  • We share it only with Anthropic, for the chat feature above. People don't read it unless you ask us to, it's needed for security or to investigate abuse, or the law requires it.
  • Disconnecting Google Calendar in Account settings revokes our access at Google and deletes your calendars and events from our database straight away. Deleting your account does the same and also revokes Google sign-in. You can also remove access at myaccount.google.com/permissions.

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

Who we share it with

Nobody else using Coursework Compass can see your data: each account only ever sees its own. We use these service providers:

ProviderWhat forWherePrivacy policy
Railway CorporationHosting: our server, database, files and backupsEU West (Amsterdam, Netherlands); Railway is a US companyrailway.com/legal/privacy
AnthropicAI featuresUSAanthropic.com/legal/privacy
Resend (Plus Five Five, Inc.)Sending account emails: confirmations, password resets, security alerts and service noticesEmails can be sent through Ireland; Resend stores email records in the USAresend.com/legal/privacy-policy
GoogleGoogle sign-in and Google Calendar, if you use them. Google is responsible for your Google account data under its own policyUSA and worldwidepolicies.google.com/privacy

Railway, Anthropic and Resend process data only on our instructions under data processing terms. We may also disclose data if the law requires it.

Where your data is processed

Our database and files are stored with Railway in the Netherlands, which UK law recognises as giving adequate protection. Some data goes to the USA, protected as follows:

  • Google, Railway and Resend are certified under the UK Extension to the EU–US Data Privacy Framework (the "UK–US data bridge").
  • Anthropic isn't certified, so it relies on the European Commission's standard contractual clauses with the UK Addendum issued by the Information Commissioner, in its data processing terms.

How long we keep it

DataHow long
Your account and everything in itUntil you delete your account. Deletion removes it straight away; any file that can't be removed at once is cleared by a daily check, so everything is gone within 30 days
Accounts nobody signs in toDeleted after 2 years without a sign-in. We email you 30 days before
Backups of the databaseExpire within 35 days, so deleted data disappears from backups within 35 days
Sessions (device and IP address)Until you sign out or the session ends, at most 30 days
Email confirmation and password reset linksUntil they expire (24 hours and 1 hour), then deleted daily
Server security and error logsUp to 30 days, held by Railway. We keep the content of your work out of these logs
AI usage records90 days
Google Calendar dataUntil you disconnect it or delete your account; synced events reflect your calendar
Messages you send us12 months after the conversation ends
At AnthropicUp to 30 days (up to 2 years if flagged for breaking its usage policy)
At Resend (email records)30 days

Your rights

Under UK data protection law you have the right to:

  • Access your data. Use Account settings, then Export my data, for a copy of everything (including your files) in a reusable format, or email us.
  • Correct it. You can edit almost everything in the app, or ask us.
  • Delete it. Delete your account in Account settings, or ask us.
  • Move it to another service. The export is in standard JSON with your original files.
  • Object to our use of it based on legitimate interests, or ask us to restrict it.
  • Complain to us at privacy@courseworkcompass.com, or to the Information Commissioner's Office at ico.org.uk/make-a-complaint. We'd appreciate the chance to put things right first.

Email privacy@courseworkcompass.com to make any request. It's free, and we'll reply within one month. We may need to confirm it's really you first.

Cookies and browser storage

We only use cookies and browser storage that are strictly necessary for the service you've asked for: keeping you signed in, keeping your account secure, and remembering choices you make in the app. There are no analytics, advertising or tracking cookies and nothing from third parties, so we don't need to ask for consent.

NamePurposeLasts
__Secure-better-auth.session_tokenKeeps you signed in30 days, renewed as you use the app; removed when you sign out
__Secure-better-auth.stateProtects Google sign-in from forgery5 minutes
__Secure-better-auth.two_factorRemembers you're halfway through two-step sign-in10 minutes
__Secure-better-auth.trust_deviceSkips the two-step code on this device, only if you tick "Don't ask again"30 days
__Secure-better-auth.better-auth-passkeySecurity check while you use a passkey5 minutes
cc_confirmedRemembers you re-confirmed your identity before an account change10 minutes
cc_deviceRecognises browsers you've signed in on, so we only send "new sign-in" alerts for new ones13 months
cc_ageCarries your "16 or over" confirmation and agreement to the Terms through Google sign-up10 minutes
google_oauth_stateProtects connecting Google Calendar from forgery10 minutes

The app also keeps a few settings in your browser's local storage, which never leave your device: your theme (theme), the study timer (coursework-tool:pomodoro-v2), which chat you last had open (compass:active:…) and panel sizes (coursework-tool:checklist-split). You can clear them in your browser settings at any time.

Children

Coursework Compass is for people aged 16 and over. Everyone is asked to confirm their age before they can use it. If someone says they're under 16, we delete the account and everything in it straight away. If you think a child under 16 is using it, email privacy@courseworkcompass.com and we'll delete the account.

Users aged 16 and 17 get the same protections as everyone else. Privacy-protective settings are the default: there's no profiling, advertising, tracking or sharing between users, and nothing is public.

How we protect your data

  • Everything is sent over encrypted connections (HTTPS).
  • Passwords are stored only as scrambled hashes. Two-step verification secrets are encrypted, and backup codes are hashed.
  • You can add two-step verification and passkeys, and we email you about sign-ins from new browsers and changes to your password, email address or two-step verification.
  • Every database request is limited to the signed-in user's own data, and we test that one account can't reach another's.
  • Sign-in attempts and AI requests are rate-limited, and sensitive changes ask you to confirm it's you.
  • Only the person who runs the project can access the server.

We take reasonable steps to protect your data, but no online service can be completely secure, so we can't guarantee it. Please use a strong password that you don't use anywhere else.

If something goes wrong

If a security breach affects your personal data, we'll report it to the Information Commissioner's Office within 72 hours of finding out where the law requires it. If it's likely to put you at high risk, we'll email you without undue delay to tell you what happened, what we're doing about it and what you can do to protect yourself.

Changes to this policy

If we change this policy in a way that matters, we'll tell you in the app or by email before the change takes effect. The date at the top shows when it last changed.