Privacy policy

1. WebRTC Media, Signaling & Evidence

Audio and video use encrypted WebRTC connections between browsers. TURN infrastructure can relay encrypted media when a direct connection is unavailable. Other participants may capture media on their devices; Rulxo cannot prevent that.

Signaling and text messages pass through our WebSocket server. Google account identities, profiles, friendships, abuse reports, no-rematch pairs and moderation bans are persisted in PostgreSQL. Older device-local encounter images and chats remain until you intentionally delete them; new calls do not automatically save partner images or transcripts.

2. Sessions, Accounts & Moderation Records

To pair you with strangers, Rulxo's lightweight signaling engine facilitates session negotiation over WebSockets. We do not require you to provide a name, email address, phone number, physical address, or password to use our service.

IP addresses support admission, rate limits and moderation. Abuse reports and ban records can include IP addresses and spoofable browser device signals. Operational logs may include connection metadata; we do not promise a zero-log service.

3. Optional Local Safety Analysis & Reports

Optional Neural Shield analyzes received video on your device. Model loading can fail and detection can miss harmful content. Shield status shows whether scanning is available. Neither this feature nor proof of work verifies identity or age.

Reports and automated moderation flags can send evidence and detection metadata to the signaling server. Only report submission acknowledged by the server confirms receipt.

4. Bilateral Chemistry Sparks Consent Model

Social handles are supplied to the signaling server and may be shared through friendship and mutual Spark flows. Share only information you intend the other person to receive.

5. Local Storage & Cookie Transparency

Browser storage holds preferences, local direct-message history, older encounters and guest contacts. Clearing site storage removes local data; Google sign-in recovers supported profile and friendships only. Settings provides intentional cleanup of local histories. Session cookies authenticate guest and account requests.

6. Retention, Erasure Requests & Contact

Server-held account and safety records are not removed by clearing your browser. Retention schedules, account erasure requests and applicable legal obligations require operator review. Contact [email protected] with questions or an erasure request; this statement does not certify GDPR or CCPA compliance.