Privacy Policy

Ruberis exists to help K–12 writing teachers grade student work. To do that, we store rubrics, assignments, and student-written essays. We try to collect as little personally identifiable information (PII) as possible. Students don’t need an email or password to use Ruberis. Their identity is whatever the teacher chooses to record — usually a name or a student ID.

We never sell your data. We do not use student work to train any general-purpose AI model. Student essays are sent to our grading model only to produce scores and feedback for your class and are not retained by the model provider beyond the length of a request.

• Teachers with a Ruberis account (signed in via email).
• Schools or districts that purchase Ruberis seats on behalf of their teachers.
• Students who submit writing to a class on Ruberis via a class code. Students do not have accounts.

When you create a Ruberis teacher account we store:

• Your email address and name.
• The classes, assignments, rubrics, and comments you create.
• Minimal technical information (IP address, user agent) tied to authentication requests, for security.
• Billing information, if you subscribe to a paid plan. Payment card data is handled entirely by our payment processor (Stripe) and never touches Ruberis servers.

Students use Ruberis without accounts. When a student joins a class with a class code, we store:

• A display identifier chosen by the teacher (typically a name or student ID).
• Each essay the student submits, along with their revisions and feedback history for that essay.
• A temporary anonymous session cookie so the student can return to the same submission in the same browser.

We do not collect email, date of birth, address, or any other PII from students unless the teacher explicitly enters it into a field. We do not set marketing cookies or advertising identifiers.

We use the data we collect to:

• Run the grading loop — rubric proposals, teacher overrides, student revisions.
• Keep your account secure and let you sign in.
• Process payments for paid plans through Stripe.
• Debug issues and improve the service. When we use production data for debugging, we access only what is necessary.

We never use student work for advertising, model training, or any purpose beyond the class it was submitted to.

We share data only with the third parties needed to run Ruberis:

• Supabase — hosts our database, authentication, and file storage.
• Anthropic — provides the grading model. Essay text is sent per request and is not retained by Anthropic for training.
• Stripe — processes billing for paid plans. Card data never enters our servers.
• Railway — hosts our background worker service.

Each sub-processor is bound by contract to use data only on our instructions. We will publish an updated sub-processor list here whenever it changes.

Teacher data and student submissions live in your account for as long as you keep the account. You can delete any class, assignment, or submission at any time, which removes it from our database. When a teacher closes their account, we delete or anonymize all associated student submissions within 30 days.

Audit records (e.g., billing events) are retained for up to seven years for tax and compliance purposes.

You can request a copy of, correction to, or deletion of data we hold about you by emailing send us a message. Parents and guardians can make the same request on behalf of a student; we route these through the teacher or school that controls the record.

Ruberis uses Postgres row-level security so that each teacher can only read and write their own classes, assignments, and submissions. All traffic between your browser and Ruberis is encrypted in transit. See our Security page for more detail.

Questions about this policy? Email send us a message. We aim to respond within two business days.