Rubrica.
Legal

Privacy policy

Last updated October 30, 2026

Who we are

Rubrica is an independent software project created and operated by Travis Fraser ("we", "us"). This policy explains what information we handle through tryrubrica.com and the Rubrica app, and how we use it.

This website

This website has no accounts, forms, or advertising. We do not use it to collect personal information, and we do not use tracking cookies.

  • Email. If you email us, we receive your address and what you write. We use it only to reply and keep a record of the conversation.
  • Server logs. Our hosting provider may record standard technical data, such as IP address, browser type, and pages requested, to operate and secure the site.

The Rubrica app

Rubrica runs on the instructor's own Mac. Student rosters, exams, grades, and the link between each random code and each student are stored on that computer. We do not operate a server that receives or stores student records. The app has no analytics or usage tracking. Data leaves the app in these cases:

  • Grading. The app sends a random code, answer pages without the cover page, and rubric text to Anthropic, using the API key set up in the app. Anthropic handles the request under its own terms. Stored names, IDs, and cover pages are left out of grading requests in the default setup. Answer pages may contain incidental identifiers, which instructors should check for before grading.
  • Rubric tools. When the instructor uses them, the app sends sample answer pages from up to three graded exams, the rubric, and text the instructor types to Anthropic. They also send blank-exam files, including the first page, and short feedback excerpts from saved audit results.
  • Class diagnostic. When the instructor generates it, the app sends class statistics and up to ten feedback comments per question to Anthropic, without names or codes.
  • In-app assistant. When the instructor uses it, the app sends the instructor's question and a fixed list of fields, identified by random code, to Anthropic.
  • Optional audit. Only if the instructor runs it, the app sends answer pages and the rubric, identified by random code, to Google, OpenAI, or a second Anthropic model.
  • Google sign-in. Sign-in and Gmail authorization codes and tokens go to Google at sign-in, when Gmail is connected, when reports are sent, and when Gmail is disconnected. They belong to the instructor's own Google account.
  • Sign-in and license check. At each Google sign-in, which is about once a week, the app sends the instructor's Google ID token (email address, name, and Google account ID) to a server we run, through Cloudflare, to confirm the account is approved. It carries no student data. Between sign-ins the license is checked on the Mac and nothing is sent.
  • Email reports. Student reports are sent from the instructor's own Gmail account. We do not receive or store them. They pass through Google and carry the student's name, score, and feedback. The instructor can disconnect Gmail and revoke access at any time.
  • Regrade notes. When the instructor resolves a regrade request and sends a note, it goes to the student through the instructor's Gmail, with the student's first name, random code, question, result, and any reason typed.
  • Test emails. A test email goes through Gmail to an address the instructor chooses.
  • Cloud backup. Optional, and off unless the instructor turns it on. When it is on, the saved workspace, including names, IDs, scans, and grades, is copied to the instructor's own iCloud Drive, OneDrive, or chosen folder.
  • Model download. Installing the name-reading model downloads it from the Ollama model registry. No student data is sent.
  • Updates. When the instructor clicks to check for updates, the app requests a version file. The request contains no student data.

Instructors and their institutions decide how student information is used in Rubrica and remain responsible for it under their own policies and applicable law, including FERPA.

Sharing

We do not sell personal information. We share information only with service providers that help us run this website and the license check, including Cloudflare, when required by law, or to protect the security of the service.

Retention

We keep emails and the license allowlist for as long as needed to provide support and access.

Student data in the app is stored on the instructor's Mac. Deleting an exam removes its record and its scan file, though in a workspace copied from another computer the scan file can remain. Saved versions, cloud backups, exported files, and sent reports are separate copies that the instructor removes separately. Anything sent to a model provider is handled under that provider's terms.

Your choices

You can ask us to tell you what information we hold about you, correct it, or delete it by emailing us. Instructors can ask to be removed from the allowlist at any time.

Changes

If we change this policy, we will update the date at the top of this page. Significant changes for app users will be announced in the app or by email.

Contact

Questions about this policy: hello@tryrubrica.com.