Skip to main content

What Limud changes, and who sees it first

Limud AI rewrites teaching material so one lesson reaches thirty different readers. It does not change what is graded, and it does not reach a student before a teacher has seen it.

The five controls

The teacher approves it first
A classroom starts with review switched on. A rewritten version waits in the teacher’s queue, and until she approves it the student opens the original material with one line telling them their teacher is looking at their version first. A class can switch to publishing without review; it is a decision somebody makes, not a default.
You see exactly what changed
Every version is shown beside the material you uploaded, word by word, with the additions and the removals marked. Hebrew and other right-to-left text is compared the same way as English.
And why it changed
Each version carries a bounded list of what was changed and the reason for it, plus the approach Limud AI chose and a short note addressed to you. Nothing is stored that a student typed into a chat.
You lock the words that are the assignment
Beside the upload box you can list the words and terms that must survive exactly as written. After the rewrite the text is checked for every one of them. A version missing a locked term is flagged in the queue and is never published without a person approving it, even in a class that switched review off.
Every read is logged
Runs, approvals, rejections, regenerations, reverts and pins are recorded, and so is every time a member of staff opens a student’s version or a tutor conversation. Administrators can read the log.

Support that does not single a student out

A student's version is visible to that student and to their teacher. No student can see another student's version, no version is labelled as easier or harder, and nothing in the classroom says who received support. Every student in the class works from the same assignment.

What is stored, and for how long

Where it runs
The application and its scheduled jobs run in Oregon, in the United States (US West).
Live session data
Data from an accountless live session is deleted after 7 days by a scheduled job.
A lapsed individual account
When an individual learner subscription ends, the learner’s data is kept for 90 days and then removed by the retention sweep.
Wellbeing check-in notes
A check-in note is redacted 45 days after the check-in, or 14 days after its flag is resolved, whichever comes first.
Graded work
Assignments are never personalised. Every student in a class is graded on identical questions, worth identical points, due at the same time. A test in the build fails if any code path produces a per-student version of graded work.
Grading
Limud AI can read a typed answer, a photographed one or a spoken one and suggest a score and feedback. It cannot write a grade. A grade exists only when a teacher writes it, and writing it is what marks the suggestion approved.

Who processes what

Teaching material and student answers
Processed by Limud AI to produce a version, a tutor reply or a suggested grade. The vendor behind it is named in the subprocessor list.
Hosting
Render, in Oregon.
Database
Neon, PostgreSQL.
Payments
Stripe. Limud does not store full card numbers.
Transactional email
Resend, for password resets, one-time codes and contact replies.

Hebrew quality, measured

Limud is used in Hebrew as well as English. Hebrew output is scored on a fixed set of passages that is checked into the codebase, by checks that are the same every run, and the result is published.

See the latest Hebrew benchmark

Compliance packet

These files are drafts prepared for legal review. They are not policies and they are not legal advice. The binding documents are linked at the foot of this page.

The binding documents