Privacy

Your coursework is yours. Nobody else with an account can see it, none of it is sold or shared for advertising, and there is no third-party analytics or tracking on this site. The only things that leave the app are the documents you choose to have read by AI, and a password reset email if you ask for one.

• Your accountName, email, school, major and timezone. Your password is stored as a scrypt hash, never as the password itself.
• Your courseworkCourses, class times, assignments, grades you enter, study sessions, flashcards and their review history, and the schedules you add — work, practice and the rest.
• Files you uploadSyllabi, screenshots and notes, plus the text read out of them and the study material generated from them.
• Sign-in stateA session cookie, and — if you use Google — the account identifier Google gives us, so we can recognise you next time.
• Anything you send usThe text of a suggestion or a problem report. A report also records the page you were on and your browser's user-agent string, because a report without those is usually impossible to act on.

• Your Google passwordGoogle handles that. The app never sees it.
• Raw IP addressesPublic forms are rate-limited by a keyed hash of the address, which can recognise a repeat submission but can't be turned back into an address.
• Analytics of any kindNo Google Analytics, no pixels, no session recording, no advertising identifiers. There is nothing on this site reporting your behaviour to anyone.
• Payment detailsThe app doesn't take payments.

Three services, each doing one job, each only when the feature that needs it is used:

• AnthropicWhen you ask for a syllabus to be read or study material to be generated, the document or notes in question are sent to Anthropic's API to do it. Anthropic does not train on API content. If you supply your own API key, the request runs on your key and your account instead.
• Your email provider, via ResendOnly to deliver a password reset link, and only when you ask for one.
• GoogleOnly if you choose to sign in with Google, and only to confirm who you are. It receives no coursework.

Nothing else goes anywhere. Uploaded files are stored on the deployment’s own storage and are served back only to the account that uploaded them, through a route that checks the session on every request.

One cookie that matters: the session cookie that keeps you signed in. It is HTTP-only, expires after 60 days, and holds nothing but a random token. Signing in with Google briefly sets two more, which are deleted the moment the sign-in finishes. There are no advertising or analytics cookies, so there is no consent banner to click past.

Only you. Every record carries the id of the account it belongs to, and every read in the app is filtered by it — one account genuinely cannot load another’s courses, files or notes, and that is verified in a browser as part of testing, not just asserted here.

One exception, stated plainly: whoever set this deployment up has administrative access to the database, the same as any self-hosted app. They can also see how much AI usage each account has run up, since it is their bill. They cannot see your coursework from inside the app.

The daily rhythm feature is powered by House of Figs™ and Figatry™. Your preferences and generated schedule are stored in this app like everything else and are not sent to them. The links to their sites carry a referral tag that identifies this app as the source — no information about you travels with it.

Nothing in the app is medical, nutritional or mental-health advice. It will tell you when to eat and roughly what a meal should be built around; it will not put a calorie target on the screen, which is a job for someone who can actually see you.

Your data stays until you delete it. Deleting a course takes its assignments with it; deleting your account takes everything with it, in the same operation, because the deletion cascades through the database rather than being a flag on a row. Spent form tickets are cleared after two days.

There is no self-service delete button yet — say so from the report page or in Settings and it will be done. That is an honest gap rather than a policy, and it is on the list.

This is built for university students. It is not directed at children under 13 and no account should be created for one.

If this page changes in a way that matters, the date at the top changes with it. The policy describes what the code does, so a change here follows a change there rather than the other way round.

Use the suggestion box or the report page. Both work without an account, and both reach the person who runs this.