COPPA and FERPA aligned
Your data, handled plainly.
No legalese games. Here is exactly what SketchIO stores, what it never touches, and why. If a line is unclear, that is our fault, so tell us.
1
What we store, and what we do not
We store this
- The link between a SketchIO assignment and its Classroom courseId and courseWorkId.
- The Sketchpad account of the teacher who created it.
We never store this
- Drawings or any student work. Those live in the uploader's own Drive.
- Rosters, course content, or grades.
- Google access tokens after the short connection window.
2
Every Google permission, and why
See your Google Classroom courses classroom.courses.readonly
read onlylists your courses so you can pick which one to create an assignment in.
Teacher scopes classroom.rosters.readonly
read onlyshows student names next to submissions in the grading dialog.
Manage coursework you create classroom.coursework.students
writecreates the Sketchpad assignment as coursework, lists its submissions, and patches or returns them with grades.
Save files you upload drive.file
scopedwhen you opt to attach the open Sketchpad drawing as assignment instructions, uploads that JPEG to your own Drive so Classroom can reference it as a Drive-file material.
3
Where the drawings actually live
Every drawing, whether a student turn-in or a teacher prompt, is stored in the uploader's own Google Drive. SketchIO does not keep a copy. Delete it in Drive and it is gone, on your terms.
A drawing Made in Sketchpad
turned into
SketchIO keeps the link courseId + courseWorkId only. No art, ever.
posts to
art saved to
Google Classroom The assignment students open
The uploader's own Drive Where the drawing actually lives