Your information
Privacy policy
Last updated: 29 September 2026
ClassReplay is operated by ByteBot Tech Inc., based in Barbados. This policy explains how the ClassReplay extension and production service handle information. Contact support@bytebottech.com with privacy questions or requests.
Information we handle
- Account information: your Google account identifier and email address, sign-in sessions, and authorization tokens needed to deliver recordings.
- Recording content: your selected presentation, microphone narration, incoming meeting audio when enabled, and your local camera when enabled. Content can include participants' voices and information visible in a shared presentation.
- Recording details: meeting URL, recording title, settings, timestamps, upload and processing status, file identifiers, integrity checks, and error messages.
- Service and support information: connection information such as IP addresses used to operate and protect the service, operational error logs, and information you send when contacting support.
Why we use it
We use this information to identify approved teachers, record and recover lessons, verify uploads, assemble videos, deliver them to Google Drive, display status, provide support, and protect the service against misuse. The service does not use recordings or Google user data for advertising, sale to data brokers, or training general-purpose AI models.
Google account and Drive access
Google sign-in supplies your account identity and email. ClassReplay requests the drive.file permission for files created or opened with the app; it does not request full access to your Drive. The implemented workflow uploads recordings and checks the resulting file's identity, size, and availability. Authorization can remain active after you close Chrome so the server can finish delivery once all pieces have uploaded. ClassReplay does not receive your Google password.
ClassReplay's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Human access to Google user data is limited to your affirmative permission, necessary security investigation, or legal requirements.
Where information goes
Recording pieces are stored in your browser's local extension storage until remote storage is verified. They are temporarily transferred to administrator-managed Microsoft SharePoint storage and processed on the ClassReplay server. The finished recording is uploaded to the signed-in teacher's Google Drive. Google, Microsoft, and the infrastructure providers involved process information to deliver these services. Processing locations depend on the configured hosting and cloud accounts and may be outside Barbados.
Authorized administrators can manage staging storage and server operations. We do not automatically publish recordings or share them with students. Teachers and their organizations control subsequent sharing from Drive. Information may also be disclosed when necessary to comply with law or protect service security.
Retention and deletion
Local pieces are deleted after the server verifies remote storage. After delivery is verified, the service attempts to remove temporary SharePoint pieces and server working files. Deletion can be delayed by failures, SharePoint recycle bins, retention policies, or applicable backup arrangements.
Unfinished or failed recordings are retained for recovery and are not automatically purged after a fixed number of days. Account details, recording metadata, and authorization tokens remain until removed through account administration or a deletion request. Contact support to request deletion of service-held account data or unfinished recordings; we may need to verify your identity and coordinate with the responsible school or administrator. Any legally required retention will be explained where permitted.
Finished Drive videos remain under the teacher's or organization's control until deleted there. Deleting service data does not delete copies already downloaded or shared by others. Removing the extension does not delete server or SharePoint copies.
Your controls
You can stop or pause a recording and select whether to include meeting audio or your camera before starting a new recording. Microphone recording follows the detected Meet mute control. Camera capture depends on the enabled camera setting and detected Meet camera state. Recording behavior depends on browser and Meet compatibility.
You can revoke Google access through your Google account connections. Signing out of ClassReplay only ends that device's application session; it does not revoke Google authorization or cancel processing jobs. To request access, correction, deletion, or raise an objection concerning personal information, contact support. Participants can also contact the teacher or school responsible for the recording.
Classroom recordings and students
The extension is intended for approved teachers, not student sign-up. Schools and teachers are responsible for the appropriate basis, notices, and permissions for classroom recordings, including recordings involving minors. ClassReplay does not itself send Meet's built-in recording notification. This policy does not replace the school's recording agreements or responsibilities.
Security and website storage
The service uses HTTPS in production, account-based access controls, and encryption of stored Google authorization tokens. Local recording files and temporary media are not end-to-end encrypted by ClassReplay. No system can guarantee complete security. These public pages do not add advertising cookies or analytics trackers; the extension uses browser storage for settings, sessions, and recoverable recording pieces.
Changes and contact
We will update this page when practices change. Material changes to Google data use will be disclosed and additional consent sought where required before the new use begins. Questions and requests: ByteBot Tech Inc., Barbados, support@bytebottech.com.
