Privacy policy
Draft for the public service · Written October 26, 2026. Public registration is not currently available. The effective date will be announced after the server provider, storage country and deletion procedures are finalized and verified. This document does not apply retroactively to all existing classroom distributions.
Codebitda describes the personal information to be processed by the public Codebitda C++, Java and AI services and the choices available to users below. Contact: codepretender.dev@gmail.com .
1. Information processed and purposes
| Google account | Instructor and teaching assistant email addresses, email verification status and Google account identifiers are used for login and role verification. Google passwords are not received or stored. |
|---|---|
| Connection and class information | Instructor Drive connection tokens, instructor–assistant relationships, exam and folder identifiers, and submission permissions are stored to handle submissions for each class. |
| Student submissions | Student IDs and names, code and answers, per-question results and scores, submission times, and exam progress or disqualification information submitted by the app are sent to the instructor's designated Drive. Fields vary by question and app version. |
| Submission verification | Submission hashes, file identifiers and filenames are stored on the server to prevent duplicate saves. Filenames may contain student identifiers. |
| Contact | Email addresses and inquiry details are used to resolve issues and process rights requests. Do not unnecessarily attach original answers or passwords to support emails. |
2. Google Drive access and use restrictions
Login uses the openid and email scopes; Drive connections use drive.file. The app works with files it creates or files and folders the user authorizes it to access. It does not request unrestricted access to all Drive files. Supported folder selection is explained in the app.
With instructor approval, the app creates class folders and stores submissions. A student's self-reported information alone does not verify their Google account or identity. Information received from Google is not sold or used for personalized advertising or general-purpose AI model training.
Our operating standard is compliance, including the Limited Use requirements, with the Google API Services User Data Policy for the use of information received through Google APIs and its transfer to other apps.
3. Storage and access
Submission data passes through the submission server and is stored in the instructor's connected Google Drive. The server stores account, connection, class and submission verification information. Answers are processed by the server during transmission. The server under development is not designed to keep answer bodies in a separate database.
Instructors manage submissions and Drive sharing permissions and should give assistants only the access they need. The service operator processes information as necessary, including to resolve incidents. Details of the server provider, storage country, processors and international transfers will be finalized and announced before public launch, after server selection.
4. Retention and deletion
- Answers in the instructor's Drive: The instructor sets the class retention period and informs students. The instructor deletes data when that period ends. Students may ask that instructor for access, correction or deletion.
- Server account and connection information: The planned policy is to retain this information while the account is in use and delete it when the account is closed. Linked deletion of connection tokens, class connections and submission verification records will be verified before public launch.
- Disconnecting Google: Google account connections lets you revoke access. Revoking access alone does not automatically delete server records or existing Drive files.
- Local backups: Upgraded versions create encrypted, timestamped backups approximately every 20 seconds in app data and temporary folders for recovery. Automatic cleanup periods have not yet been implemented, so backups may remain after uninstalling the app. Follow the instructor's guidance to clean them up after the exam.
Account closure, access, correction, deletion and suspension-of-processing requests are accepted by email and processed after identity or authority is verified. Copies separately downloaded or shared by instructors must be managed by the relevant administrator. Any legally required retention will be explained separately with its basis and period.
5. Safeguards and cookies
Public server connections are designed to use HTTPS. Server-stored information such as connection tokens and recovery backups is encrypted. Role-based access and duplicate-submission prevention are applied. These measures do not eliminate every risk on users' devices or in separately shared files.
Temporary cookies verify requests during Google login. The current product pages do not add separate advertising or analytics tracking scripts. GitHub, the website hosting provider, may process technical information such as visitor IP addresses. GitHub privacy information and Google Privacy Policy provide further details.
6. Changes
Changes to data fields or storage methods and their effective dates will be announced on this page. Operator identification and required notices will be finalized before public launch.