Privacy Policy

AI character conversations

Koharu is an AI character. After separate consent, your nickname, messages, uploaded images/videos/voice messages and recent conversation history are sent to the selected provider (Google Gemini API or OpenAI API) to generate replies. URIAL sets store:false; processing and retention by each provider remain subject to its terms. Google free-tier conversation content may be used to improve its products. Avoid personal or confidential information. URIAL retains AI conversations containing a user message, including user text, uploaded media, Koharu replies and delivery errors, for operational review. Records are normally eligible for deletion approximately 90 days after creation, under the existing retention and preservation rules. Only authorized administrators may review saved data when operationally necessary. Transient disconnections can resume the same conversation within 5 minutes from the same screen. Leaving, page reloads, expiry or a server restart end the conversation, but does not erase retained administrative records. Greeting-only sessions are not saved. For abuse prevention and cost control, a hashed IP and daily usage count are kept in the budget ledger and daily records reset on the first use of the next UTC day. A random device identifier is used during the connection to exclude your other tabs when indicating other visitors.

1. Scope

This policy applies to the URIAL website, normal random chat, invite rooms, reports, support and related operational functions. Whether a particular data item qualifies as personal information, personal data or similar regulated information may depend on context and linkability.

2. Information collected

1. Profile: nickname, optional age/gender/short comment, and an avatar if you upload one.
2. Conversation/content: chat text, images, video, voice messages, files, send/receive timestamps, read status and report content.
3. Connection/session: IP address, timestamps, session identifiers, reconnect token, random device identifier, room information and connection/recovery logs.
4. Device/browser environment: User-Agent, OS/browser type, language/time zone, screen and viewport information, pixel ratio, touch support, network characteristics, browser capability/support states, storage availability, and camera/microphone/notification permission states. URIAL checks the location permission status locally in the browser and does not store it on the server.
5. Safety/operations: moderation detections, restrictions, reports, bans, rate-limit events, administrative actions, incident and audit logs.
6. Consent records: 18+ confirmation, acceptance of policies and the Important Notice, timestamps and document versions.

3. Purposes of use

Information may be used to provide matching, messaging, media, read status, reconnection and translation; enforce the 18+ rule and restrictions on dating/contact exchange; investigate reports and abuse; secure and troubleshoot the Service; comply with law and valid requests; improve reliability, safety and user experience; and provide important notices.

4. Location-related information

When you send media recorded or captured directly through URIAL, we obtain latitude, longitude, accuracy and the time of measurement if your browser permits access. The location follows the same retention and deletion rules as the media. Authorized operators may view it on a map for safety and investigations. Directly recorded or captured media can only be sent when location access has already been granted and the device location is available. URIAL does not open the browser’s permission prompt.

For safety, abuse prevention and troubleshooting, the connection IP address may be sent to an IP geolocation provider (currently ipwho.is, with ipapi.co as a fallback) to estimate country, region, city and approximate coordinates. IP-derived location is not GPS and may be inaccurate. During a random chat or invite-room session, if your browser has already granted location access, we automatically obtain your device latitude, longitude, accuracy and measurement time and share them with URIAL staff for safety and troubleshooting. Staff can request a new measurement. You can stop sharing by revoking location permission in your browser’s site settings. The result is held in the live session and removed when sharing stops, the connection drops or the session ends. Authorized operators may view the shared or media-associated device location using Google Maps or another mapping service. Location information is not shared with the chat partner.

5. Media and metadata

Images, video, audio and files may be stored and processed for delivery, safety, incident response and rule enforcement. If an uploaded original already contains EXIF, GPS, capture time, device information or other metadata, the original or extracted metadata may be retained for safety/investigation purposes. Image copies delivered to the other participant are designed to normalize orientation and remove EXIF-style metadata so original GPS metadata is not directly passed to the other user.

6. Translation and external services

Live translation is optional. If either participant enables translation, message text selected for translation from both participants may be sent to Google Cloud Translation API and the translated result returned to URIAL. Each participant sees a separate disclosure and confirmation before first enabling translation. Turning translation off prevents translation requests initiated by that participant, but your messages may still be translated when the other participant has enabled translation. When an authorized operator needs to review stored conversations for reports, safety, rule enforcement or similar operational purposes, the operator may also use the administrative translation function, which sends the relevant stored message text to the same API. Google's contractual and data-processing terms apply to Google's processing.

URIAL may also use hosting/network providers, GeoIP providers and Google Maps. Where applicable law requires specific disclosures, contracts, supervision, consent or measures concerning processors, third parties or overseas processing, URIAL will implement those measures as required.

7. Retention

1. Normal random chat: chat/operational logs and ordinary media are generally scheduled for deletion approximately 90 days after creation. Users do not receive a history/search feature for past random chats.
2. Invite rooms: a room and its conversation history may remain until the room is administratively deleted.
3. Legal Hold: normal deletion may be suspended when preservation is reasonably required for legal compliance, disputes, serious abuse/security investigations or valid official requests.
4. Backups: deleted information may remain in backups for a limited period until backups rotate, and is not retained there for ordinary active use.

8. Operator review

URIAL is not designed for continuous human monitoring of conversations. Authorized operators may review relevant stored conversations, media and logs only when reasonably necessary for reports, abuse/rule enforcement, security, troubleshooting, legal compliance or similar concrete operational needs. Access controls, authentication and audit logging are used as reasonable safeguards.

9. Cookies, browser storage and analytics

URIAL may use Local Storage, Session Storage or similar browser storage for theme/language settings, sound/vibration preferences, a random device identifier and session-recovery information.

Google Analytics 4 is used only if the visitor allows analytics. Google may receive the page viewed, time, broad browser/device information, referral information, and consented events such as starting a chat search, finding a match, successfully sending a message, or submitting a report. Google Analytics cookies may then be stored. Chat content, nicknames, invite-room codes and precise location are not included in analytics events. Individual invite-room paths are replaced with one anonymous path, and URL query strings are not sent.

Google Analytics is not loaded by default and no measurement occurs after a visitor declines. The choice is stored in Local Storage and can be changed at any time through “Analytics settings” in the footer. If consent is withdrawn, URIAL attempts to remove accessible Google Analytics cookies. Advertising storage, advertising user data, ad personalization and Google Signals remain disabled. Google's privacy terms apply to its processing.

10. Security

URIAL uses reasonable safeguards appropriate to the scale and risk of the Service, including administrator authentication/authorization, access controls, HTTPS, secret separation, logging/monitoring, rate limits and backups. Safeguards are reviewed as the Service changes.

11. Third-party disclosure and processors

Personal data is not disclosed to third parties without consent except where permitted or required by law, including circumstances necessary to protect life, body or property. Service providers may process information on URIAL's behalf where reasonably necessary to operate the Service. URIAL will take supervision and contractual measures required by applicable law.

12. Questions and statutory requests

Questions about this policy or data handling can be sent to urial@bxd.jp. Where applicable legal requirements are met, URIAL will respond to requests concerning disclosure, correction, suspension of use or deletion of retained personal data. Because URIAL is anonymous, some requests may not be technically or legally actionable when stored data cannot reasonably be linked to the requester.

13. Changes

This policy may be updated in response to changes in law, guidance, Service design or providers. Material changes will be announced through the Service and renewed consent may be requested where appropriate.

Operator: bx design (sole-proprietor trade name)

Automated media checks

When automated media checks are enabled, photos, avatar images and sampled video frames are sent to Google Cloud Vision, and video audio / voice messages to Google Cloud Speech-to-Text, before delivery. We check sexual or violent imagery and prohibited text or speech. Your required Important Notice consent before entry covers this processing, so selecting media does not show another confirmation. Blocked, uncheckable or timed-out media is not delivered. Temporary frames and decoded audio are discarded when processing ends. Blocked original media, matched terms, detection methods, timestamps, sender and room information are retained for administrator review for normally 90 days, except when preservation is required. Passing OCR and speech transcripts are not retained as review records. Video frames are sampled every 0.5 seconds, and speech recognition targets Japanese and English. Brief imagery, other languages, context or disguised language can be missed; false positives also occur. This does not determine a person’s age or the legality of content. Please report inappropriate material. Google processing is subject to its contractual and data-processing terms.

Call records

When calls are enabled, both participants must accept the call notice before audio and the displayed video-call view are automatically recorded and stored, and audio is transcribed using Google Cloud Speech-to-Text. Video calls retain separate local and remote views and a composed view reflecting the call layout, with audio. If you choose screen sharing, the selected screen is also shared and recorded; consider notifications and other people’s information visible on it. AI calls send transcribed speech and recent conversation to the configured AI provider and synthesize replies using Google Cloud Text-to-Speech. Video calls with AI also send sampled camera images (or images of the selected screen during screen sharing) to that provider; the displayed camera view, static AI portrait and portrait changes are retained in the call video. The AI uses ordinary character portraits and confirms before a video call that its display is static. External processing is subject to each provider’s data terms.

Video, audio, transcripts, timestamps, conversation details, consent records and indicative sensitive-content categories are normally kept for seven days for operational and safety review and download by authorized administrators. Administrators can delete unnecessary records or retain records until a hold is removed. Automated categories are provisional and do not determine safety or a violation. Recognition errors and omissions can occur. Interrupted recording may end a call. Retention practices also need to account for backups. Consider carefully before sharing sensitive information.