Data handling

Privacy Policy

DIM is a local-first Windows desktop teaching workbench. This policy explains what the app stores locally, what Google data it requests, and how optional integrations are used.

Effective date: July 1, 2026

Information DIM Stores Locally

DIM stores class schedules, student lists, local recording metadata, material references, application settings, and integration connection records on the user's device. DIM does not require cloud storage for its core workspace.

Data leaves the local workspace only when the user explicitly chooses an external action, such as connecting a provider or uploading a selected recording.

Google User Data

DIM requests Google access only after the user starts a Google sign-in or connection flow. Depending on the enabled feature, DIM may use Google account identity information to sign in, YouTube read-only access to identify and display the authenticated user's YouTube channel, and YouTube upload access to upload a local recording selected by the user.

DIM does not read unrelated YouTube videos, comments, subscriptions, or private account activity. DIM does not edit or delete YouTube videos in this release. OAuth tokens and retrieved channel details remain in the user's local DIM workspace and are used only to provide the connected feature requested by the user.

DIM's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

YouTube Publishing

When a user uploads to YouTube, DIM uploads only the local video file the user selects and only after the user provides the video title, description, privacy setting, and starts the upload.

DIM stores the returned YouTube video ID, URL, upload time, and publishing status in the local workspace so the teacher can find the class recording link later.

Google Classroom and Zoom

DIM may offer optional Google Classroom and Zoom connection workflows. These integrations are used only when a user connects them from the application. Provider tokens are stored locally and can be removed by disconnecting or clearing the integration inside DIM.

Sharing and Sale of Data

DIM does not sell user data. DIM does not share Google user data with advertisers or data brokers. User content is sent to third-party providers only when the user explicitly uses an integration action, such as uploading a selected recording to the user's YouTube channel.

Security

DIM stores workspace data on the user's device. Users are responsible for securing their operating system account and device storage. OAuth access can also be revoked from the user's Google Account or provider account settings.

Data Deletion and Revocation

Users can remove local workspace data by deleting the DIM data folder or using the application's clear/disconnect controls where available. Users can revoke Google's access to DIM at any time from their Google Account security settings.

Contact

Questions about this policy can be sent to g.d.j.business.corporation@gmail.com.