Compliance governs cloud processing.
GridGrade runs on Google Cloud using Cloud Run, Firestore, and Cloud Storage. Student submissions are stored and graded there under the institution's agreement, including the Student Data Addendum.
We built GridGrade so that the cautious choice is the default one. Here's exactly how student data is treated.
This is a plain-language stance page, not a legal contract. A formal Privacy Policy / DPA is available to institutional customers.
GridGrade runs on Google Cloud using Cloud Run, Firestore, and Cloud Storage. Student submissions are stored and graded there under the institution's agreement, including the Student Data Addendum.
Student submissions are uploaded to GridGrade's Google Cloud environment, stored in Cloud Storage and Firestore, and graded by services running on Cloud Run.
Anthropic's Claude helps instructors draft rubrics from a scrubbed structural representation of the instructor's solution workbook and any assignment instructions. It is on for classes by default. On request, we can switch AI assist off for your class. Student submissions and calibration workbooks are not sent to Anthropic.
We never log student names, IDs, or cell contents. Student work never enters our code repository or issue tracker; feedback we collect is scrubbed of personal information before any human sees it.
Student-linked records and stored files are deletable on request through an operator-run erase cascade, with separate steps for analytics and the authentication account.
GridGrade stores and grades student submissions in its Google Cloud environment. That processing is governed by the institution's agreement with GridGrade, including the Student Data Addendum.
The legal basis for institutional processing is the institution's agreement with GridGrade, including the Institutional Terms and Student Data Addendum. The addendum describes GridGrade's school-official role under FERPA. GridGrade does not collect student authorization for that institutional processing; the institution determines whether another notice or authorization is required.
When workbooks are de-identified, it's a real pipeline — author/company metadata, comment authors, headers/footers, and roster-name matches are all addressed — not just a renamed file. We don't treat "hashed the filename" as de-identification.
Your name, email, institution, role, course/enrollment context, your selected interest, and your message. We store this to respond to you and to plan the launch. We don't sell it or share it. We keep it only as long as needed to follow up.
We capture your approximate request metadata (a coarse rate-limit signal and timestamp) to stop abuse. We do not run third-party advertising trackers.
The marketing site has no login; the graded product (with its own privacy controls) is separate.
Student data is deleted on a validated request through the operator-run erase cascade. Daily Firestore backups are retained for 14 days, and diagnostic log buckets retain entries for 30 days, so deleted data may remain in those protected stores until their retention windows expire. Audit exports placed in the protected audit bucket are subject to a 400-day retention policy. For product data or this website's contact data, email hello@gridgrade.app to request deletion.
Security and privacy are built into how student data is stored, graded, and protected on Google Cloud.
Email hello@gridgrade.app.
Launching Fall 2026 — early access & pilot inquiries open now. One human reads every message.
One human reads every message. We aim to reply within two business days.
No commitment. We never share your information. Replies typically within two business days.