Privacy Policy

• Account data: your email address, a salted password hash or magic-link credential, and the sign-in session managed by Supabase (auth cookies).
• Profile data: your display name, your declared gender, and the topic, language and location filters you choose.
• Verification results: the booleans is_verified and age_over_18, the verification tier you completed (declared, documented, identity verified or admin approved), the timestamp, and the provider name. Nothing else from your document.
• Safety records: reports you file or that are filed against you, with participant ids, room id, reason and, for automated flags, one evidence frame (see section 4).
• Trust data: post-call ratings you give or receive and any suspension flag on your account.
• Saved connections: the short list of people you choose to reconnect with is stored in your own browser's local storage and is not synced to our servers.

• Your identity document image and its number, your date of birth, and the face scan used for liveness. Verification providers process these; our database keeps only the derived adult-and-verified result.
• The video and audio of your conversations. Media travels peer-to-peer over WebRTC directly between the two of you and is not recorded, buffered or archived by us.
• Chat text sent during a call, which is delivered as ephemeral signalling between participants rather than stored as message history.

When you upload an ID for the document check, that image is transmitted to Google (Gemini vision) for parsing. The preview screen shows the fields it read so you can confirm them; when you commit the check, the server re-reads the image and keeps only the derived result - recorded sex, adult flag and document type. The legal name, birth date and document number are never written to our database. If you only declare your age, a birth date is sent once to compute the adult flag and is discarded immediately.

• Supabase (PostgreSQL, authentication and storage) — account, profile and safety records.
• Stripe Identity — document and biometric verification, as its own controller for that processing.
• Google Gemini vision API — optional document parsing for the in-app review step.
• Metered.live / Coturn TURN relays — encrypted media relayed only when direct peer-to-peer connection fails. Relay sessions use short-lived credentials; we do not store relayed media.
• Google AdSense — advertising scripts load only after you accept in the cookie notice; declining means no ad scripts load at all. Your stored choice is per browser and can be cleared at any time.
• Our hosting provider — ordinary web request logs (IP address, user agent, timestamp, URL).

Sample avatars and demonstration imagery are loaded from Unsplash, which receives your IP address when those images render.

A lightweight analyser runs on your device while you are in a call. It inspects incoming video frames locally; no continuous recording is made and nothing is uploaded unless a threshold is crossed.

When a violation is detected, one JPEG frame is captured from the current remote stream and attached to a moderation report so a human reviewer can judge it. That frame is biometric-adjacent content: it is kept only while the case is open, is visible only to authorised administrators, and is deleted once the review closes unless a legal hold applies. Manually reporting another participant attaches the same single frame.

• Contract: account, profile, matchmaking and relay data, kept while your account is open.
• Consent: camera and microphone capture, identity verification, advertising personalisation, saved connections.
• Legitimate interest and legal obligation: safety reports, evidence frames, suspension records and web-server logs, kept as long as needed to keep the network safe and to meet lawful requests.
• Deleting your account removes profile and verification data; safety reports tied to serious incidents may be retained in reduced form where we have a legal obligation or an active case.

• Authentication cookies set by Supabase, strictly necessary to keep you signed in.
• Google AdSense cookies, served only if you consent to personalised advertising where required.
• Browser local storage entries holding your saved connections and interface preferences; clearing site data removes them.

You can request access, rectification, export, restriction or deletion of your personal data, withdraw consent, and object to profiling, by emailing bitdegenbiz@gmail.com. We can usually delete an account and its derived verification flags within 30 days. If you are in the EU/UK you may also complain to your supervisory authority; in California you have additional rights under the CCPA/CPRA, and we do not sell personal information.

FaceMeet is not for anyone under 18. Age verification is enforced before matchmaking, and we do not knowingly collect data from children. If you believe a child has an account, contact us and we will remove it.

Media is encrypted in transit (DTLS-SRTP), credentials are hashed, service secrets stay server-side, and direct database access is blocked behind row-level security with matchmaking handled by a locked RPC. No system is perfectly secure, so never share sensitive information with a stranger.

Our providers process data in the United States and Europe; transfers rely on standard contractual clauses or an equivalent lawful mechanism where your data leaves your region.

Material changes to this policy are announced on the site and in the app before they take effect. Data protection questions, subject access requests and complaints: bitdegenbiz@gmail.com. The rules of use are in the Terms of Service.