Privacy Notice

1. Information used in the current test

• Guests: a temporary randomly generated identifier and an optional chat nickname. A signed guest token expires after six hours. Guest sessions do not require an email or password.
• Accounts: if you choose to register, we process your username, nickname, email address, password hash, and selected gender to operate your account. Gender matching filters are currently disabled.
• Technical data: your browser holds the session token in session storage. The server may process IP addresses and request data for access logs, connection handling, abuse prevention and rate limits.
• Live chat: text is relayed to your chat partner. The current text-chat code does not deliberately store chat history in the database. The other person can copy or capture what you write.
• Future features: reporting, blocking, subscriptions and Stripe payments are not operational in this test version.

2. What “anonymous” means on VibeRoom

VibeRoom is anonymous between members, not anonymous from the service itself. A chat partner sees your nickname and the information you choose to type in chat. We do not show your email address, password, internal account identifier, IP-related security information, or payment details to the person you are matched with.

To operate the service, VibeRoom processes the temporary guest identifier or account session while your chat is active, plus technical connection data. Dedicated reporting tools are not yet available. Do not type your real name, address, phone number, social-media details, or other identifying information if you want to stay anonymous to another member.

3. Purpose and sharing

Session and chat information is processed to provide a live chat service and limit abuse. Hosting and networking providers may process the technical information needed to operate VibeRoom. Google Fonts may receive connection information when its external fonts load. Payments and payment-data processing are not enabled. This draft requires a legal and operational review before public launch.

4. Retention

Temporary guest tokens expire after six hours and browser session data can be cleared when the tab/session ends. Active chat connections and waiting queues are in server memory and end when the connection is closed or the server restarts. Registered account data remains in PostgreSQL until processed under an account-deletion policy. Webserver logs and backup retention periods still need to be documented before public launch.

5. Your rights

Depending on the law that applies to you, you may request access, correction, deletion, restriction, or portability of your information, or object to certain processing. Contact the privacy address that must be published here before public launch. You may also have the right to complain to your local data protection authority. Some information may need to be retained to meet a legal obligation or handle a legal claim.

6. Security and updates

Passwords are not stored in readable form. Account and chat systems have access controls. This test deployment does not yet have HTTPS enabled; do not use real personal information until HTTPS is configured and reviewed. No online service can guarantee absolute security. We will update this notice when our data practices materially change and notify you where the law requires it.