ACCOUNT & ASSESSMENT · VERSION 2026-10-19 · EFFECTIVE 19 October 2026
Privacy Policy
This policy explains how gradingspace.com handles account information, assessment materials and AI-assisted evaluations. It applies to the service operated by the gradingspace.com product team. For privacy questions or requests, email gradingspace@gmail.com, our current support contact, and identify the Google account associated with your workspace. Do not send student submissions in a support email unless a secure transfer has been agreed.
Information we process
Google sign-in supplies your account identifier, verified email address and display name. We record registration and teacher approval status, plus the versions of these terms and this policy you acknowledge and the time of acceptance. Your workspace may contain course information, student names or identifiers, rubrics, assessment briefs, submitted files, marks, feedback, teacher notes and grading-job status. Technical records needed to operate and troubleshoot requests may include timestamps, errors, request identifiers and usage or storage accounting.
Why we process it
We use this information to authenticate accounts, approve teacher access, maintain separate workspaces, store and retrieve your assessments, process requested AI reviews, display results, protect the service and respond to support requests. Where paid plans are enabled, we also process plan, customer, subscription and usage information to administer billing. Google sign-in alone does not approve teacher access.
Student information and institutional permission
The teacher or institution determines which student materials to upload and must have an appropriate lawful basis and any required institutional approval, notices or permissions. Your acceptance of our terms is not student consent and does not replace your institution's requirements. Minimize personal information, use student codes where practical, and do not upload sensitive personal information that is unnecessary for assessment. The service is intended for educators, not direct student or child registration.
Storage and retention
Course, roster, rubric, result and job metadata are stored in the dedicated gradingmatrix Firestore database. Original file bytes are stored separately in private cloud object storage, not in Firestore. ZIP archives are unpacked in your browser and are not retained by default; extracted originals can be retained within your storage allowance until you explicitly delete them. Deleting a course does not necessarily delete its original files or job history. Use Storage & files to manage retained originals. Temporary grading transfers may use opaque Vercel Blob URLs; anyone possessing a valid transfer URL may be able to access that object. Cleanup of these temporary objects is best-effort, not a guaranteed expiry. Account, assessment, job and acceptance records may remain until separately deleted or handled through an account-erasure request. No universal automatic deletion schedule is currently promised.
AI processing and service providers
When you request an AI review or rubric task, the relevant files or extracted content, rubric, course context and student identifiers may be sent through Hyperagent to the configured AI provider. AI processing can include visual inspection, text extraction and sampled video-frame analysis. Providers involved in operating the service include Google/Firebase for identity and storage, Vercel for hosting and temporary transfers, Hyperagent and its configured AI providers for requested processing, and Stripe where paid billing is enabled. These providers have their own privacy and retention terms. We do not promise that all processing remains in one country or that providers apply a particular training or retention policy without a separate applicable agreement.
Access, sharing and security
The application restricts workspace access by Google account and teacher approval, and uses teacher-scoped authorization and short-lived links for private original downloads. The approval administrator sees registration and approval information rather than a shared student gradebook. Authorized service operations and infrastructure providers process data as needed to run the service; application isolation is not a claim that infrastructure administrators can never access data. Do not forward file links or expose account credentials. No online system can guarantee absolute security. New runtime grades and student records are not intended to be stored in the source-code repository; historical pre-migration records may require separate cleanup.
Locations and international processing
The current dedicated Firestore database is in Google's us-central1 region and the private originals bucket is in US-EAST1. Hosting, temporary transfers, authentication and AI providers can process information in other locations. Do not upload materials subject to a location restriction unless your institution has confirmed that the complete processing arrangement is suitable.
Browser storage
Google/Firebase uses browser storage to keep you signed in. The application may also store interface preferences such as tour dismissal and sound settings. Legal acceptance is recorded against your account in the project database, not merely remembered by a browser checkbox. Blocking or clearing browser storage can require you to sign in again.
Your choices and requests
You can review and edit accessible workspace information, export available results and delete retained originals using the provided controls. For account erasure, access, correction, restriction or other applicable privacy rights, contact the team using the home-page contact link. We may need to verify account ownership and coordinate with your institution. Some records may need to be retained for security, dispute resolution or legal obligations; erasure is not currently a self-service account-wide operation. Students should ordinarily contact the teacher or institution responsible for their assessment first.
Policy changes
We identify this policy by its published version and effective date. Material changes will be published here, and the service may require acknowledgement of a new version before workspace use. Existing acceptance is not silently relabelled as acceptance of new wording.
