Your privacy in BrainByte
Understand what the platform collects, how learning and monitoring data are used, and where to ask for help.
Updated
Information we use
BrainByte project team operates BrainByte for academic programming practice and assessment.
- Account details: your name, email address, assigned role, and sign-in information. Google sign-in connects your verified Google identity to your account, or creates a student account when you are new to BrainByte.
- Learning records: enrollments, submitted code, quiz answers, scores, completion records, team membership, and competition results.
- Uploaded content: learning materials, documents selected for AI features, course images, and competition media.
- Service and security records: activity timestamps, IP address, browser information, and actions recorded to operate and protect the platform.
Camera and activity monitoring
Monitoring is configured by the instructor or competition organizer. The workspace explains the required camera, fullscreen, and browser checks before monitored work begins.
When enabled, camera analysis runs in your browser using MediaPipe. BrainByte receives monitoring events and, when evidence capture is enabled, selected image frames. The monitoring feature does not upload a continuous camera recording or request microphone audio.
Authorized instructors, organizers, and administrators can review evidence. Evidence is not shown in public standings. Missing heartbeats indicate a lost connection and do not count as violations.
Monitoring events and their evidence images are scheduled for removal after 90 days. Removal depends on the scheduled cleanup service running. A flag can be inaccurate; ask your instructor or organizer to review a disputed event.
Services involved in your activity
BrainByte uses hosting and storage services, including AWS, to run the application and keep uploaded files. Code and the test inputs needed to evaluate it are sent to Judge0 for execution.
When an instructor uses an AI feature, prompts, selected source content, conversation messages, and the current page or form context are sent to OpenAI. Page context can include learning records shown to that instructor. Only select materials appropriate for that purpose, and avoid including unnecessary personal or confidential information. Generated content must be reviewed before use.
Google processes Google sign-in and Gmail SMTP delivers account and platform emails. Each provider also has its own privacy practices; BrainByte does not promise that provider records are removed when an account is deleted here.
Your records and requests
You can update your profile in Settings. Account deletion is available there after password confirmation. Deleting an account does not promise immediate removal of every uploaded file, academic record, provider record, or restricted recovery copy. Linked competition records can prevent automatic account deletion; an instructor or administrator must review that request.
Course and assessment records are retained for course operation and review. Ask your instructor or administrator about the retention of a particular record, or request access, correction, or deletion through the instructor or administrator who invited you to BrainByte. Explain which account or activity your request concerns; never send your password.
Recovery backups can contain earlier copies of records. The administrator must apply the backup retention policy and account for pending deletion requests when restoring a backup.