Privacy Policy
This page describes current product behavior and the privacy work still required before broader public traffic. It is product copy, not final legal approval.
Guest setup
Frinly stores a temporary guest setup in your browser: self-declared age, gender, chat mode, optional interests, broad public location label, browser location status, rules acceptance, and network-safety assessment metadata.
Location privacy
Other guests should only see a broad public region, such as a city or area label. Exact GPS coordinates stay in local browser state during this prototype and should not be shown to other guests.
Reports and moderation
Reports can include a room reference, broad public location labels, chat mode, media state, report reason, details you type, and a limited recent-message snapshot. Hosted reports can enter the database-backed moderation queue. New in-chat reports use a one-time server token so the protected ban target stays hashed and server-side.
Ban appeals
A ban appeal includes the contact email, opaque ban reference, and explanation entered on the appeal form. Frinly does not ask for passwords, raw IP addresses, exact location, government ID, or device fingerprints in an appeal. Submitting an appeal does not automatically change a ban.
Admin safety review
Hidden admin screens are for launch readiness, reports, broad network-safety summaries, moderation decisions, bans, and appeals. Admin tools use broad location labels and protected hashes rather than exact GPS, raw IP addresses, credentials, or exposed browser-session identifiers.
Advertising
Frinly keeps advertising disabled until the provider account, consent flow, policy review, privacy review, and real public slot identifiers are ready. When enabled, display ads can appear on Guest Setup and while waiting for a stranger, never over an active video or text chat, report, appeal, safety action, or admin screen. Between-chat eligibility uses only local counts and timestamps, not guest IDs, messages, rooms, reports, location, or device fingerprints.
Production data still planned
Retention windows for ban records, safety reports, appeals, and admin audit events remain deliberately unset until owner and legal review. Cleanup writes are disabled. Frinly still needs final decisions for deletion requests, age-policy handling, support response expectations, and policy approval.