PRIVACY POLICY

1. WHAT INFORMATION DO WE COLLECT?

Nodus is a synchronized peer-to-peer watch-party platform designed to play media synchrony across devices. To enable local video selection and real-time syncing features, Nodus requests access to specific device systems.

Device Permissions & Media Access

The application requests the following Android permissions to function correctly:

• Video Media Selection (READ_MEDIA_VIDEO / READ_EXTERNAL_STORAGE / WRITE_EXTERNAL_STORAGE): We use these permissions solely to allow you to select and load your own local video files stored on your device to play inside a watch room. Nodus reads video files locally to render playback; your personal files are never uploaded, sent, or stored on our servers.
• Network & Wi-Fi States (INTERNET / ACCESS_NETWORK_STATE / ACCESS_WIFI_STATE / CHANGE_WIFI_STATE): These permissions are required to connect to signaling pathways, check connection availability, and discover local network peers to host or join a watch room.
• Local Peer Discovery (CHANGE_WIFI_MULTICAST_STATE): Used to allow the application to receive multicast network packets, enabling instant peer-to-peer discovery of other active watch rooms on your local Wi-Fi connection.

2. HOW DO WE PROCESS YOUR INFORMATION?

Nodus operates primarily as a decentralized peer-to-peer application. We process information to:

• Synchronize video playback events (play, pause, seek, time offsets) between room members.
• Negotiate and establish direct WebRTC audio/video and data channels between devices.
• Maintain a transient list of peer names within your active room.

Third-Party Infrastructure

We utilize Google Firebase (including Firebase Realtime Database and Cloud Firestore) to handle real-time signaling data, coordinate watch room configuration frames, synchronize live chat message packets, and process transient room session records. Firebase functions strictly as a secure connection pipeline; this metadata is treated as transient and is not permanently logged or retained beyond the active watch party session.

Note: All personal video files are played strictly on-device and shared directly between peers. They are never transmitted to or processed by Firebase infrastructure.

3. WHEN AND WITH WHOM DO WE SHARE YOUR INFORMATION?

Because Nodus utilizes a Peer-to-Peer (P2P) network model:

• Direct Peer Connections: Your IP address, session signaling metadata, and connection states are shared directly with the peers you explicitly connect with to establish WebRTC links.
• No Third-Party Sharing: We do not sell, rent, or distribute any user information, media references, or session details to advertisers or third-party corporate entities.

Public IP Exposure Warning (BitTorrent/P2P Swarm)

IMPORTANT SECURITY WARNING: Because Nodus utilizes direct peer-to-peer networking configurations and distributed torrent-like protocols to stream data streams efficiently, joining large watch rooms or connection groups means your public IP address becomes visible to other connected peers in the same swarm to facilitate handshakes and packet transfers. If you do not wish for your IP address to be exposed to other peers in the swarm, you should not participate in P2P rooms.

4. FOREGROUND SERVICES AND NOTIFICATIONS

To ensure watch-party synchronization is not disconnected by system optimizations:

• Background Services (FOREGROUND_SERVICE / FOREGROUND_SERVICE_MEDIA_PLAYBACK): These permissions are utilized to run a foreground media service, maintaining active network sockets and coordinating media clock states even when you navigate to other apps.
• Active Status Badges (POST_NOTIFICATIONS): Used to display an active media player controller and status notification in your notification tray, allowing you to quickly monitor sync state, disconnect from a room, or control playback.

5. WAKE LOCK AND PROCESS CONTROL

To prevent device timeout interruptions:

• Screen Lock Control (WAKE_LOCK): This permission allows the app to request the device CPU and screen to remain active during active video playback, ensuring the video stream and synchronization clock are not paused by automatic system sleep timers.

6. HOW LONG DO WE KEEP YOUR INFORMATION?

We retain user data for the shortest duration possible:

• Transient Session Data: Room signaling logs and peer states exist only for the duration of the active connection room session and are immediately purged when the session ends.
• Local Settings: Room nicknames and history preferences are stored locally on your device storage and can be cleared at any time by clearing the application cache.

7. HOW DO WE KEEP YOUR INFORMATION SAFE?

We prioritize direct security measures:

• Direct peer-to-peer data lines are encrypted by WebRTC protocol structures.
• Signaling servers do not inspect or store video packets.
• We do not request or collect account logins, passwords, or personal identifying keys.

8. DO WE COLLECT INFORMATION FROM MINORS?

Nodus is not directed to, and we do not knowingly solicit information from, children under the age of 13. If we learn that a minor has shared personal metadata, we will immediately close the signaling connection and delete all local cache registries.

9. CHILD SAFETY & EXPLOITATION POLICY

We maintain a zero-tolerance policy regarding child sexual abuse and exploitation. For our full compliance framework, enforcement actions, and legal reporting guidelines, please review our dedicated Child Safety Standards Policy.

10. WHAT ARE YOUR PRIVACY RIGHTS?

Depending on your regional laws, you have full authority to request, review, or delete any local logs. Because we do not store personal profiles, your rights can be exercised completely by managing app storage permissions directly within Android Settings.

11. CONTROLS FOR DO-NOT-TRACK FEATURES

Most web browsers and mobile operating systems include a Do-Not-Track ("DNT") signal. Because Nodus does not perform background behavioral profiling, track browser history, or deploy cross-site cookies, we do not monitor or modify behavior based on browser DNT signals.

12. DO WE MAKE UPDATES TO THIS NOTICE?

We will update this privacy policy as necessary to remain compliant with developer policies, network guidelines, and new feature sets. The updated version will be indicated by an updated "Last Updated" date at the top of the policy page.