Who we are
Koguko (“Koguko”, “we”, “us”) is a free, no-account one-to-one random chat service built and operated by Hane Studio (hane.studio). This policy explains what information is involved when you use Koguko, why, and the choices you have. By using Koguko you agree to this policy.
The short version
- No sign-up, no accounts, no profiles.
- We never ask for your name, email, or phone number.
- Ordinary chats are relayed live and are not stored. Chats are transmitted securely.
- Only if a chat is reported, or our safety system detects serious abuse, do we securely save the recent messages and related moderation data for review.
- Message-free operational session records are kept for a limited period to diagnose matching, connection, and safety problems.
- First-party return-visitor analytics stay off unless you choose to allow them.
Information we do not collect
We do not ask for or store your name, email address, phone number, date of birth, photos, contacts, precise location, or any account credentials, because there are no accounts. With your analytics permission, we may receive a broad country code from our hosting infrastructure. We do not build advertising profiles and we do not sell data. For roadmap voting on the Pulse page, we use a random browser ID and a server-generated non-reversible vote key to limit duplicate votes (see Local storage on your device below).
Information we do process
Chat messages (not stored for ordinary chats)
Messages you send are relayed in real time through our server to the stranger you are matched with. While a chat is active, the most recent messages are held briefly in memory so that reporting and rule-based safety checks (such as spam, threats, and abuse detection) can work. We do not write ordinary chats to a database. When a normal chat ends or you disconnect, that in-memory buffer is deleted and the conversation is gone from our systems.
The one exception: if you report a chat, or our safety system flags serious abuse (for example threats or content involving minors), we securely save the recent messages from that chat for moderation review. Those saved messages are encrypted at rest and can only be read inside our protected moderation system. They are never shown publicly.
Important: the other person can still read, remember, copy, or screenshot what you send while you are talking. Treat anything you share as public.
Saving a chat to your device
After a chat ends, you can choose Keep this chat to create an image from all or part of the conversation. The image is generated locally in your browser and downloaded directly to your device. It is not uploaded to Koguko, does not cause us to store an ordinary chat, and is not available to us. The downloaded image remains under your control until you delete it. Keep it private unless the other person agrees to sharing it.
Connection data
Like every website, our servers and our infrastructure providers automatically receive technical connection data such as your IP address, broad region, browser type, and timestamps. For ordinary use we do not store your raw IP address; where we need to recognise a connection for rate-limiting, ban enforcement, or basic safety, we use a privacy-preserving one-way hash instead. We do not use this data for advertising or invasive tracking.
Message-free session records
When two people match, we create a temporary operational session record. It can contain a random session identifier, pseudonymous participant references, match and end times, queue wait, connection and disconnection events, source attribution, message counts by side, first-message and first-reply timing, report involvement, and an end reason. It does notcontain ordinary message text. We use these records to diagnose failed matches, disconnects, slow queues, malformed sessions, and moderation links. They are visible only in the protected admin system and are deleted after 90 days by default.
Abuse reports & safety flags
If you report a chat, or our safety system detects serious abuse, we store a report/flag record: the reason, a temporary session identifier, a timestamp, and the recent messages from that chat. To investigate abuse and enforce bans, we also store the raw IP addresses of the people involved. All of this sensitive moderation data, both saved messages and raw IPs, is encrypted at rest and can only be decrypted inside our protected moderation review system. It is never exposed to the public, never used for advertising, and is retained only as long as needed for safety and enforcement before being deleted.
A report may include an optional comment and identifiers for exact messages selected by the reporter. We use non-reversible browser and network identifiers to group duplicate incidents, identify repeat abuse or report manipulation, enforce restrictions, detect likely ban evasion, and avoid rematching a reporting or blocking pair. Automated signals help reviewers find relevant evidence; they do not make an unreviewable or infallible decision.
Product & traffic analytics
If you select Allow analytics, we use a first-party random browser identifier, transformed on the server into a non-reversible analytics key, to count unique and returning visitors and calculate acquisition funnels and retention cohorts. Consented analytics can include visit date, first and later visits, chats started, matches made, broad country, device class, landing page, referrer host, and campaign. We also keep message-free operational totals such as queue wait, chat duration, disconnects, and whether neither, one, or both sides sent a message. Analytics never contain ordinary chat text, raw IP addresses, advertising IDs, or cross-site history.
Analytics are off until you make a choice. Choosing Necessary only does not limit chat, reporting, appeals, or safety features. You can change or withdraw the choice below at any time. We also honour browser Do Not Track and Global Privacy Control signals by keeping analytics off.
Aggregate counts
We may display the number of people currently in active chats or waiting to match. These are simple, non-personal counts and are not tied to any individual.
Local storage on your device
We use browser local storage to remember your 18+ confirmation, your opt-in match-sound setting, a random anonymous browser ID, and your analytics choice. The browser ID is used for Pulse voting and protected safety linkage without creating a public profile or account; on the server it is transformed with a secret salt before moderation use. If you allow analytics, a separately salted form supports unique-visitor and retention measurement. We also store first-touch source attribution locally while analytics remain allowed. If a safety action is delivered while you are connected, we also store its notice and opaque appeal reference locally until you dismiss it. None of these values is an advertising cookie or used for cross-site tracking.
Service providers
We rely on infrastructure providers to host and protect Koguko, including Vercel for the frontend and AWS-based backend hosting infrastructure for the backend server. These providers process technical connection data on our behalf to deliver and secure the service, under their own privacy and security terms. Live chat traffic passes through our backend infrastructure. Reported or seriously flagged chat data may be stored on backend infrastructure as encrypted moderation records.
Cookies, analytics & advertising
Koguko does not use advertising cookies or cross-site trackers, and we do not currently run any third-party analytics product. Our optional first-party analytics use local storage and the message-free records described above. We ask before enabling return-visitor analytics and retain the choice so we do not ask on every visit. If we ever introduce a third-party analytics tool or any non-essential cookie, we will ask for your consent first where the law requires it.
Koguko does not show ads today. We may introduce advertising in the future to help keep the service free and running. If we do, it will not require an account and will not be based on profiling the contents of your chats, and we will update this policy before any ads go live.
How long we keep things
Ordinary chat contents: not retained. The in-memory buffer is deleted when the chat ends. Message-free operational session records: up to 90 days by default. Consented pseudonymous visitor and event analytics: up to 395 days by default so yearly and 30-day retention comparisons remain possible. Reported-chat transcripts: retained for up to 30 days by default. Serious safety-flag transcripts: retained for up to 90 days by default. Raw IP addresses attached to reports or flags: retained for up to 30 days by default. These periods may be configured differently. Report records, IP hashes, bans, moderation audit events, long-running aggregate metrics, and Pulse votes may be retained longer for safety, abuse prevention, operations, and recordkeeping. We do not maintain long-term advertising or behavioural records about you.
Security
Traffic to Koguko is encrypted in transit (HTTPS / secure WebSockets). We apply reasonable technical and organisational measures to protect the limited data we handle. No online service can be guaranteed perfectly secure, but because we store so little, there is very little to lose.
Children
Koguko is strictly for adults aged 18 and over. It is not directed to children and we do not knowingly process data from anyone under 18. If we learn that a minor has used Koguko, we will remove any associated data. If you believe a minor is using the service, contact us at prateek@hane.studio.
International users
Koguko can be used from many countries, and the infrastructure that runs it may process technical data in locations outside your own. Where required, our providers use recognised safeguards for such transfers. By using Koguko you understand that limited technical data may be processed internationally as described here.
Your rights
Depending on where you live (for example under the GDPR or similar laws), you may have rights to access, correct, or delete personal data and to object to certain processing. Because we operate without accounts, we may need a session, appeal, or participant reference to locate a record and may be unable to verify that an unlinked record belongs to you. You can withdraw optional analytics directly above. For any other privacy request, contact our Grievance Officer at prateek@hane.studio and we will respond within the timeframes required by applicable law.
Changes to this policy
We may update this policy as Koguko evolves. When we do, we will revise the “Last updated” date above. Material changes will be highlighted on this page. Continuing to use Koguko after an update means you accept the revised policy.
Contact & grievances
Questions, requests, or complaints about privacy? Reach our Grievance Officer, Prateek Panwar, at prateek@hane.studio. For general help, email hello@hane.studio. Koguko is operated by Hane Studio.