Privacy Policy – CConnect

Effective Date: July 15, 2025

This privacy policy outlines how CConnect collects, uses, and shares user data in accordance with the Chrome Web Store Developer Program Policies.

1. Introduction

CConnect is a Chrome extension that enables users to watch online videos together in real time, with synchronized playback, text chat, voice, and video communication — all within the Chrome side panel. This document explains how your data is handled when using CConnect.

2. Information We Collect

• Display name / nickname: stored locally for identification in chat and video sync rooms.
• Firebase Authentication token: used temporarily for login and session validation.
• Room/session identifiers: required for coordinating video synchronization and group communication.
• Camera and microphone access: requested only when the user initiates video or audio calls.

CConnect does not collect your email address, browsing history, passwords, local files, or any personally identifiable information (PII). No sensitive data is accessed or stored beyond what is needed for core functionality.

3. How We Use the Data

• To authenticate users via Firebase Authentication.
• To synchronize video playback across multiple users using Firebase Realtime Database.
• To enable peer-to-peer video and audio communication using WebRTC.
• To store session preferences and user nicknames locally using Chrome's storage API.

All data usage is strictly limited to functional purposes within the extension and initiated by user actions.

4. Data Sharing

User data is shared only with the following services and only

• Firebase (by Google LLC): Used for authentication and real-time database synchronization.
• WebRTC (browser-native): Used for establishing peer-to-peer audio and video connections between users.

No data is shared with advertisers or analytics services. We do not sell or rent any user information.

5. Data Storage & Retention

User preferences (nickname, session ID, mute/camera states) are stored locally via the Chrome storage API. Firebase may temporarily store anonymous session metadata for real-time communication, but no personal user data is persistently stored or associated with a profile.

All permissions (camera, microphone, tab access) are only activated through explicit user interaction, not in the background.

6. User Consent

All actions that require permissions — such as using the microphone, camera, or accessing the active tab — are only performed after a user-initiated action (e.g., clicking a "Join Room" or "Start Call" button). No hidden or background collection occurs.

7. Managing Your Data

• Users can clear their nickname and session data by removing the extension or resetting Chrome storage.
• Permissions (camera, microphone) can be revoked at any time through Chrome’s site settings.
• Firebase login sessions can be terminated by signing out from the extension interface.

8. Compliance & Policy Updates

This policy is designed to comply with Chrome Web Store privacy requirements. If the extension’s behavior changes in a way that affects data use, this policy will be updated accordingly. Changes will also be reflected in-product where relevant.

9. Contact

If you have any questions, suggestions, or concerns about how your data is handled, please contact us at:

Email: yigit.trv@gmail.com