Google OAuth Disclosure
How DrawSplatTM uses Google access.
This public page identifies the DrawSplatTM app family, including GridSplatTM, and explains why Google account, Drive, Sheets, Docs, and email-related permissions may be requested when a teacher, school, Hub administrator, or deployment owner connects DrawSplatTM tools to Google storage or protected admin workflows.
App and Brand Identity
| App name | DrawSplatTM app family, including GridSplatTM |
|---|---|
| Public website | https://drawsplat.org/ |
| Developer / support contact | Contact / Information Request form |
| Privacy policy | https://drawsplat.org/legal/combined-policy |
| Primary audience | K-16 educators, students, families using school-deployed classrooms, and small teams using browser-based whiteboard, spreadsheet, charting, and classroom tools. |
This page is hosted on drawsplat.org, the same public domain used for the DrawSplatTM homepage and privacy policy. It is visible without logging in.
What DrawSplat Does
DrawSplatTM is an interactive browser whiteboard for classroom and visual work. Users can draw, add text, shapes, sticky notes, images, audio notes, graphs, templates, panels, and classroom widgets. Teachers can create classroom links, configure collaboration rooms, review turn-ins, use moderation tools, and optionally save classroom work through a Google Apps Script backend that writes to the teacher's or school's Google Drive and Google Sheets.
GridSplatTM is a browser-based spreadsheet, charting, and pictograph tool in the DrawSplatTM app family. It can work without sign-in and can optionally save native .gridsplat.json files to Google Drive when a deployment enables Google Drive cloud save and a user authorizes it.
DrawSplatTM tools can also run without Google access in browser-only mode. Google access is used only when a teacher, Hub administrator, user, or deployment owner chooses a Google storage path or signs in for a protected admin workflow.
Why Google Access Is Requested
Google permissions are requested to provide teacher-controlled storage, user-authorized file save/open, classroom setup, and admin authorization. DrawSplatTM does not request Google access for advertising, profiling, selling user data, or unrelated analytics.
| Google capability | Purpose in DrawSplatTM | Data involved |
|---|---|---|
| Google sign-in / ID token verification | Verify that a Hub admin or instance admin is the approved Google account for that protected setup page. | Google account identifier, email address, email verification status, display name if returned by Google. |
| Google Drive | Create and manage DrawSplatTM folders/files for saved boards, PNG exports, templates, student turn-ins, image approval queues, privacy packets, Hub teacher onboarding folders, and optional GridSplatTM spreadsheet save files. | Only the DrawSplat-created, GridSplat-created, or configured Drive files and folders needed for the selected workflow. |
| Google Sheets | Record saved-board metadata, classroom room state, templates, turn-ins, audit records, parent/family access requests, time usage, compliance settings, and other deployment records. | Board metadata, classroom records, moderation/audit entries, parent request tickets, and configuration rows created by the deployment. |
| Google Docs | Create teacher setup documents for DrawSplat Hub onboarding when a Hub admin adds a teacher. | Teacher name, teacher email, setup slug, one-time setup password, and DrawSplat setup links. |
| Email through Apps Script | Notify the configured compliance/admin contact about parent/family access requests or related operational notices when the deployment enables that feature. | Recipient email, request subject, and request details submitted through the Family Access Tools workflow. |
How Google Data Is Used
- Google account data is used to authenticate an admin session and enforce access rules for Hub or classroom setup pages.
- Drive and Sheets data is used to store and retrieve DrawSplatTM classroom content, GridSplatTM save files when enabled, configuration, audit records, and teacher-managed workflow records.
- Docs access is used to generate setup instructions for teachers added through DrawSplat Hub.
- Email access is used only for deployment/admin notifications supported by the Apps Script backend.
- DrawSplatTM does not sell Google user data, use it for ads, or transfer it to advertising networks.
- Access is limited to the deployment workflows selected by the teacher, school, or Hub administrator.
Storage, Control, and Removal
For Google Apps Script deployments, the teacher, school, or Hub operator controls the Google account and Drive/Sheets files used by the deployment. DrawSplatTM stores classroom records in that operator-controlled Google environment, not in a separate DrawSplat-hosted database by default.
For direct GridSplatTM Google Drive save, files are stored in the authorizing user's Google Drive and access is limited to the selected Google Drive scope, such as files created or opened by the app when the deployment uses the narrow drive.file scope.
Administrators can remove teacher access from Hub Admin. The removal workflow deletes registry setup/admin/config entries for that teacher and attempts to remove the teacher's editor access from generated Drive folders and files. Deployment owners and users can also revoke app access in their Google Account security settings and delete DrawSplat-created or GridSplat-created files from Drive.
Privacy Policy
The full DrawSplatTM policy packet is available at https://drawsplat.org/legal/combined-policy. That URL should match the privacy policy URL entered in the Google OAuth consent screen configuration.