AI processing
Confirm the AI provider, API features, content sent, account controls, provider retention and terms that apply to the proposed workflow.
Provider statements about default training use do not establish the settings or commitments of a particular account.
A no-training or retention promise requires verification of the relevant account, terms and processing scope.
Other service providers
Review hosting and network services, database and file storage, backups, payment processing, email, security services and any remote support access.
Identify the contracting entity, purpose, data categories, locations, access and retention for each relevant supplier.
A supplier certification or report describes its own scope and does not certify TurboGrading.
Storage and processing geography
Assess primary storage, replicas, backups, logs, AI inference and support access separately.
A Canadian storage region alone does not establish Canadian-only processing.
If your institution requires a location restriction, confirm that every relevant service and agreement can satisfy it before sending records.
Extension and LMS access
Review the installed Chrome extension version, its permission prompts, selected LMS sites and any separate attachment-delivery sites.
The extension, LMS provider and TurboGrading service have different responsibilities and data-handling boundaries.
Browser access or support for an LMS does not imply an institutional partnership or approval.
Confirm the current Chrome Web Store listing and installed release before relying on a permission or storage description.
Agree how changes are reviewed
Institutional review should establish the supplier list and how material supplier, location or processing changes will be assessed and communicated.
Request the current applicable information before approving an institutional use case.
Start a review
Please send a short description of your review needs without student records, passwords or confidential attachments.
Request review materials