Google OAuth Disclosure
SplatWorks Google Access Disclosure
Security, privacy and terms covers the shared policy. This page provides the specialized reference or tool.
This public page identifies the SplatWorksTM ecosystem, 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 SplatWorksTM tools to Google storage or protected admin workflows.
App and Brand Identity
Public access is available at splatworks.org and drawsplat.org. Existing OAuth app IDs and consent-screen labels may still say DrawSplat; verify the actual app, requested permissions, and approved origins. Branding changes do not grant additional permissions. DrawSplat Hub is the existing whiteboard administration workflow.
| App name | SplatWorksTM ecosystem, 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.
The five SplatWorks office apps—GridSplat, ShowSplat, WriteSplat, ListSplat and LayoutSplat—work without sign-in and can optionally save native project files to Google Drive after an explicit user action and Google authorization. GridSplat can also reopen its last Drive save. This does not convert projects into Google Docs, Sheets or Slides. AudioSplat is a browser-based multitrack recorder and editor that can optionally upload a user-selected exported audio mix to the user's Google Drive and, only when requested, ask Drive to create an Anyone-with-the-link permission for sharing and a Drive-hosted preview embed.
SplatWorksTM 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, optional native SplatWorks office project files, and AudioSplat audio mixes explicitly saved by the user. AudioSplat creates public link permission only when the user selects that option. | Only the DrawSplat-created, SplatWorks-created, AudioSplat-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, native SplatWorks office project files when explicitly saved, 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.
PlanSplat optionally loads and automatically saves its planner and per-browser recovery files through drive.file. Google sign-in requests drive.file and calendar.app.created together, reusing one authorization to connect Drive and Calendar. Users may decline Calendar permission while retaining Drive saving and connect it later from the header. A Calendar-only retry confirms it uses the same Drive account. It creates a separate PlanSplat calendar and sends task titles, notes, course names, completion status, deadlines and study-block details to marked events there. The calendar ID is stored in the main Drive file’s app properties. It does not request access to all calendars, share calendars or invite attendees. Updates flow from PlanSplat while the app is open and authorized; Calendar edits do not update the planner. Tokens remain in tab memory; reconnect after expiry or reload. Disconnecting Calendar stops updates for the session and leaves existing events; the next Google sign-in connects both services again. Users may remove the calendar in Google Calendar and revoke authorization in their Google account. Planner connection guide.
For direct SplatWorks office and AudioSplat Google Drive save, files are stored in the authorizing user's Google Drive and access is limited to the narrow drive.file scope for files created or opened by the app. Office-app and AudioSplat access tokens stay in tab memory, with no refresh token saved. Google sign-in loads only after the Drive workflow is chosen; a separate Save button starts authorization and upload. Office apps create a new file without enabling sharing. AudioSplat can enable public-link sharing only when selected. Connection opt-out prevents these transfers.
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 SplatWorks-created files from Drive.
Privacy Policy
The shared Security, privacy and terms page describes the ecosystem policy. That URL should match the privacy policy URL entered in the Google OAuth consent screen configuration.