1Who we are, and whose data it is
Yamoreh is operated by Projekt Studio. When a school uses Yamoreh, the school is the controller of its students’, families’ and staff’s information and Yamoreh processes it on the school’s instructions, as a school official under FERPA. The school decides what is collected, who at the school may see it, and how long it is kept. This policy describes how we handle it on the school’s behalf, and how we handle the little we collect directly from visitors to this site.
2What a school’s workspace holds
- Accounts: name, email address, phone number (for sign-in codes), role, and sign-in events.
- Student records: what the school enters or imports: enrollment, contacts, guardians, documents, academic history, schedules, grades, attendance and notes.
- Applications: what an applicant submits on the school’s registration form, including uploaded documents and guardian consent.
- Course content: syllabi, assignments, files, discussions, messages and mail exchanged inside the school.
- Audit events: who opened sensitive information and when, kept so the school can answer that question.
3Who can see it
Access is by role, enforced on our servers. Each kind of sensitive information (contact details, family relationships, documents, case notes) is its own permission. Families and students see only their own information. Yamoreh staff do not read a school’s records except to resolve a problem the school has asked us to resolve, and every such access is logged.
4How it is protected
Every account requires a password and a one-time code. Each school’s data is isolated from every other school’s by the database itself. The most sensitive fields are encrypted before they are stored. Backups are automatic and restores are drilled. The technical overview is available to any school on request, and the security page has the plain-language version.
5Who else touches it
Yamoreh runs on a small number of subprocessors, all in the United States, for hosting, the database and file storage, and email. If a school turns on AI reading, the images and text of the student work being read are sent to Anthropic to be read; Anthropic does not use them to train its models, and AI reading is off unless the school turns it on. Each school's data processing agreement names every subprocessor and what each one does; the current list is on the service providers page for the school's own people, and schools are told when it changes.
6What we do not do
We do not sell personal information, we do not advertise, and we do not use student information for any purpose other than providing the service to the school.
7Retention and export
Records are kept for as long as the school keeps its workspace. A school can export every record at any time and delete its workspace on request; deleted data is removed from backups on their normal rotation. Audit events are kept for the life of the workspace.
8Your rights
Students and families exercise their rights (to inspect, to correct, to consent) through their school, which is the controller of the record. We support the school in answering every request. Anyone can write to us directly through the contact page.
9This website
This site sets no advertising cookies and uses no third-party analytics. We count, for ourselves, which pages are opened and which links and buttons are pressed, and which site sent each visit. That count keeps no cookie and nothing in your browser, and never stores your address: each visitor is a code that changes every day and cannot be traced back to you. The request form collects what you type in it so that we can reply. The application itself uses a session cookie and a small number of preferences stored in your browser.
10Children
Schools with students under thirteen use Yamoreh under the school’s consent as permitted by COPPA for educational purposes. We provide those schools with our COPPA checklist.
11Changes
When this policy changes we update the date above and tell every school by email. Questions go to the contact page.