Terms of Use · Dan Adiletta

The short version

You can read every free unit without an account. Nothing about you goes into our database when you do — though Google Analytics and our host still see the visit, as on most of the web. See other companies involved.
If you sign in, we store your name, email, and your coursework — answers, code you submit, and time-on-task.
If you join a class, your teacher can see all of that for their class.
During a live session, your teacher can see your name and which page you're on. A marker on screen tells you when that's happening.
We don't sell anything about you, and there is no advertising on this site.
Ask us to delete your data and we will. Contact is at the bottom.

Who runs this

These courses are written and published by Dan Adiletta.

If you're using this site as part of a course at a school, your school has its own policies covering student records. This notice describes what this site stores and sits alongside those policies rather than replacing them; where the two disagree about school data, your school's policy governs. Ask your teacher if you're unsure which applies.

Reading without an account

Most of the site is readable signed out, and in that state nothing about you is written to our database — there is no row anywhere with your name on it, because there is no account. (The third parties in the section below still see the visit; that part is out of our hands.) Your progress is kept only in your own browser, in local storage, under these names:

beliefs.v1.completed, beliefs.v2.* — units you've marked read, checkpoint results, your reading-width setting, and a note that an older key was migrated
progress.v3.*, lms.v3.courses — the same progress, per course, in the current format
lms.v3.key — that you redeemed an enrollment key
lms.v3.effects — whether you've switched the on-page animations off
lms.v3.autofollow, lms.v3.session, lms.v3.present — live-session preferences and, for a teacher, which class this tab is presenting
lms.v3.desk.class — teachers only: the class last opened on the teaching desk

These are not cookies and are not sent to us. Clearing your browser's site data erases them, and erases that progress with them.

If you sign in

Signing in uses Google. We never see your Google password. From your Google account we store your email address, display name, and profile picture URL.

Once you have an account, these are stored on our server:

Progress — which units you've marked read and your checkpoint results, so they follow you between devices.
Answers — for each question: what you picked, whether it was right, how many attempts, when, and which College Board standards it was tagged with.
Code you submit — the full text, plus the automated analyzer's findings, plus any rubric score, written feedback, or Loom video link a teacher leaves.
Time on task — seconds a unit's tab was actually visible, and how many times it lost focus.
Access events — when your account was created, when you signed in or out, and when you redeemed an enrollment key.
Your Story Circle document, if you use the planner in Writing Beliefs — chapters, characters, timeline, and any character portraits you upload. Portraits go in a private bucket and are served over short-lived signed links, never a public address.
Feedback you send from the menu on your name — what you wrote, the page you were on, the size of your window, any text you had highlighted, and a screenshot if you chose to attach one. Nothing is captured until you ask for it: your browser asks which window to share, and the highlighted text is shown to you with a button to drop it before anything is sent. Screenshots go in a private bucket on the same terms as portraits.

The site administrator (Dan) can read profiles and access events across all courses, because someone has to be able to fix an account that's broken. Teachers cannot — a teacher only ever sees their own class.

Feedback goes to Dan and to nobody else — not to your teacher, even when your teacher is Dan's colleague and the note is about their class. You are talking to the person who built the page.

The one exception is your Story Circle document. Nobody can read it but you — not a teacher, not the administrator. It is a half-finished novel, not coursework, and the database is set up so there is no way to look at yours.

A long-answer code question also records what share of your final answer arrived by paste rather than typing. It cannot tell anyone what you pasted or where it came from — an IDE, your own notes, or somewhere else — only the share. It is a reason for a teacher to ask how you're doing on a question, not evidence of anything, and it is never shown on this page or anywhere else you can see your own scores — only in the teacher's own grading queue.

What time-on-task can and cannot show

It counts only while the tab is visible, so it's time spent reading rather than time since you opened it. It cannot tell anyone where you went when you left, it doesn't notice a second window open beside this one, and on a phone it counts notifications and screen timeout as leaving. It is a reason for a teacher to ask how you're doing. It is not evidence of anything, and it is described that way to teachers in the gradebook itself.

If you join a class

Joining with a class code adds you to that class's roster. From then on, the teacher who owns that class can see, for that course: your name and email, your answers and mastery by standard, your code submissions, and your time-on-task figures. Other students cannot see any of it. Teachers of other classes cannot see it either.

A teacher can remove you from a roster. Doing so stops their access; it does not delete your work, which stays yours.

What can be graded, and what can't

A course here is allowed to put a number next to your name only if it is built out of three things: skills — what you are being asked to do — learning objectives underneath them, written as actions you can perform, and knowledge topics underneath those. AP Computer Science A is built that way. That is the only reason a score in it means anything: every point traces back through an objective to something you were told you would be able to do.

Anything not built that way is ungraded, and says so on the page. Writing Beliefs is ungraded and will stay that way — its units are convictions about craft, and a conviction is not a competency. Progress there is which beliefs you have marked read and which quick checks you have answered. It is never totalled, never turned into a percentage, and never sent to a gradebook.

This is enforced in the database and not only in the interface: a class meeting is the only thing on this site that turns an answer into points, and one cannot be opened for a course that has no skills, objectives and topics of its own.

Live sessions

A teacher can run a live session for a class they own. While a session is running:

You see a “live” marker on screen. It is showing for exactly as long as the session is, and it cannot be running invisibly.
Your name is visible to your teacher, so they can see who's connected — nothing about which page you're on, what you're doing, or how you're scrolling is sent.
Your teacher can ask the class a check-in question. If you answer it, that answer is sent too — see below for what happens to it.

What is not sent: your answers, your scores, which page you're on, how far down a page you've scrolled, anything at all once the session ends, and anything whatsoever from any other tab, app, or website. This site can only ever see this site.

Check-in questions

During a session a teacher can ask the class a question — a 1–10 slider (“how's your stress today?”) or a short open response (“what are you excited about?”).

The class never sees who said what. A slider question is shown to the room as a distribution only; an open question is shown as answers shuffled into an order with no names attached. This is enforced by the database, which has no rule that would let one student read another's answer — not merely by how the page is built.
Your teacher does see your name with your answer. That is deliberate: a check-in nobody can act on is a wasted question. The panel you answer in says so, above the question.
These responses are kept, so a teacher can notice a change over weeks. You can ask for yours to be deleted.

Answering is not required, and nothing about a check-in affects a grade.

Other companies involved

This is a static site, so most of what happens is between your browser and these services directly:

Supabase — the database and sign-in. Everything above is stored there.
Netlify — hosting. Keeps standard server logs, which include IP addresses.
Google Analytics (measurement ID G-JR8P7HT8V3) — loads on every page here and records page views, approximate location, device and browser. It sets its own cookies. It is not linked to your account by us.
Google Fonts — not used. The typefaces here are served from this site, so reading a page never reaches Google's font servers. The Story Circle planner used to be the one exception; it was rebuilt inside the course and no longer loads anything from a third party.
Google Sign-In — only if you choose to sign in.
YouTube and Vimeo — video players load only when you click play. Note that a YouTube video's thumbnail image is fetched from Google's image servers when the page loads, before you click anything.

Each of these has its own privacy policy, and we don't control what they do with what they receive.

How it's protected

Every table has row-level security: the database itself decides who can read each row, rather than the website asking nicely. The key this site ships to your browser is public by design and can only ever reach your own rows and the ones your teacher is entitled to. That said, no system is perfect, and you shouldn't put anything into a text box here that would harm you if it were seen.

How long it's kept, and getting it deleted

Coursework is kept while the course is running, so grades and progress survive a term. There is no automatic deletion schedule yet.

You can ask for your data to be deleted at any time, and you can ask for a copy of what's stored about you. Use the form at the bottom of this page. If the work is part of a grade at your school, there may be an academic record your school needs to keep — tell us and we'll explain what can go and what can't.

If you're under 13, please have a parent or guardian contact us before creating an account.

Using the courses

The writing and code here are © Dan Adiletta. You may use them for your own study and, if you're a teacher, in your own classroom. Republishing them, selling them, or feeding them into a product is not permitted without written permission.
Borrowed ideas are credited to their sources on the page that uses them. The College Board's course framework is quoted for alignment; AP is a College Board trademark, and this site is not endorsed by or affiliated with them.
Don't share your enrollment key or class code outside your class, and don't try to reach other people's work. The database will stop you, but trying is still a breach of these terms.
Answers you type are seen by your teacher. Keep them fit for a classroom.
The site is provided as-is, with no warranty. It's a teaching tool, not critical infrastructure — expect the occasional outage.

Changes

If what we store changes, this page changes with it and the date at the top moves. Material changes to what a teacher can see, or to what leaves your browser, will be announced in class rather than only here.

Contact

Questions, corrections, or a deletion request go here. If something on this page doesn't match what the site actually does, that's a bug — please say so.

This goes to Netlify, who host this site, and from there to Dan. Nothing is stored in the course database, and you don't need an account to send it — which matters, because "delete my account" is a thing you should be able to ask for without one.