Privacy Policy

Purpose and operator

Korean Classroom Bot is a private personal automation tool operated by Gleb Monetchikov, not a public subscription service. It retrieves information from an authorized Google Classroom account and delivers relevant notifications to its authorized user through Telegram.

Google Classroom information

The bot reads course identifiers, names and states; coursework titles, descriptions, publication states, deadlines, maximum points, links and timestamps; and announcement text. It processes attached material titles, types and links. It does not download the contents of attached Drive files. Some publication metadata, such as topic identifiers, work type and scheduled time, may be read while synchronizing.

The requested permissions are:

• classroom.courses.readonly
• classroom.student-submissions.me.readonly
• classroom.announcements.readonly

The student-submissions permission is used for access to coursework available to the authorized student. The current implementation does not separately retrieve or store student submission records. The bot does not create, modify, submit, grade or delete Google Classroom resources.

Storage and synchronization

Supabase stores enabled course records, synchronized coursework and announcements, material metadata, source links and timestamps, content hashes, synchronization events, delivery status, retry counts and error details. Telegram message identifiers and delivery timestamps allow updates to existing notifications and help prevent duplicate delivery. Optional AI enrichment is cached with its content hash and timestamp. Credentials are stored privately by the operator, separately from this website, and used only for authorized service access. The bot does not request or store your Google password.

Telegram delivery

Selected Classroom content, source links and optional translations or summaries are formatted and sent to the configured authorized Telegram chat or channel. Edited publications may update existing messages. Content is accessible to members of that destination; the operator is responsible for restricting membership to authorized recipients. Telegram processes delivered messages under its own terms and privacy policy.

Optional DeepSeek processing

When the operator enables DeepSeek, coursework titles, descriptions, announcement text and material titles are sent to its API to generate Russian translations, summaries, key points and explicit action lists. Personal information present in that text may therefore also be transmitted. This integration is optional and disabled by default. OAuth credentials and service keys are not included in the enrichment prompt. Authoritative deadlines, Classroom links, identifiers and timestamps come from Classroom; AI output does not replace them. Supabase, Telegram and DeepSeek may process information outside the user’s country.

Use and sharing restrictions

Google user data is used only for the described synchronization and notification features. It is not sold or used for advertising or unrelated profiling. Transfers to the described providers are limited to providing these features with the authorized user’s consent. Information received from Google APIs will be used in accordance with the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace API user data policy. Google user data must not be used to train generalized AI models. Human access is limited to the authorized user or operator with permission, and the exceptions allowed by these policies, such as security investigation or legal requirements.

Retention, revocation and deletion

Stored information is retained only as needed for synchronization, notification delivery, deduplication and the authorized user’s notification history. The current software has no automatic expiry or self-service deletion; the operator reviews retention and manually removes data that is no longer needed. The Google account owner can revoke authorization through Google Account connections. Revocation stops further authorized API access but does not automatically erase existing Supabase records or Telegram messages. Ask the operator to remove stored records, cached enrichment, private OAuth tokens and delivered messages where permitted. Provider copies and backups are subject to their retention practices.

Contact and changes

For access, privacy or deletion requests, email Gleb Monetchikov at support@hangugo.app. Do not post Classroom content, credentials or other private information in public GitHub issues. Changes to processing will be reflected here; authorization must be obtained before data is used for a new purpose.