Privacy Policy

1. Scope and contact

This Policy explains how Anamaak handles information on www.anamaak.live and the corresponding chat service. Anamaak is the service name; this notice does not assert that it is an incorporated company. Privacy, access, correction, deletion, security and grievance requests may be sent to official@thebluebamboo.in with subject “Anamaak privacy”.

2. Information processed

We process the nickname and gender option you choose, your adult/terms confirmations during connection, a randomly generated session credential and derived chat identity, room membership and socket identifiers, public and direct message contents, message times and participant identifiers, conversation previews, read/unread markers and session-based block preferences. The web server and hosting/security infrastructure may process IP addresses, request timestamps, requested paths, browser/user-agent details, connection errors and security events. If you email us, we receive your email address, the information you include and correspondence needed to handle the request. A nickname may identify you when combined with your messages or other information.

3. What other users can see

People in a public room can see your nickname, presence and messages; people entering later can receive that room’s latest 50 retained messages. Your gender selection affects the online filter and avatar color and can therefore be inferred by other room users. A private conversation is available to its two session identities through the application; recipients can see messages, times and read-state effects. Your IP address and secret session credential are not intentionally displayed to other users. A fresh nickname entry is not verified anonymity and does not prevent identification from information you disclose.

4. Purposes and choices

We process these data to establish connections, route public and private messages, display presence and room history, maintain your current-session inbox and read state, enforce limits, protect against abuse, troubleshoot failures, respond to requests and meet applicable legal obligations. You can block or unblock another chat identity from its profile or private chat. Blocking prevents private messaging between those identities and hides that identity’s public messages from you. A new session identity is not covered by the old block; this feature does not verify or permanently ban a person. Block preferences are database metadata and are not covered by the 24-hour message-content deletion rule. Enter only information you choose to share; use a nickname and select “Prefer not to say” for gender if desired. Optional information you put in messages is not required by Anamaak. We do not use the chat application to sell personal data, run targeted advertising, or train an AI model on your messages. Providers may process technical data for their own security or legal purposes under their policies.

5. Session identity and device storage

A new random chat credential is created in browser memory each time you submit the details form. It is used for the current entry and room switches, not as a permanent username account. The current application does not intentionally persist the credential in localStorage, sessionStorage or an application cookie. Your chosen light/dark appearance is stored separately in localStorage as a non-identifying preference; it does not restore chat identities or messages. Refreshing, home exit and a fresh entry normally create a new identity; an identical nickname does not grant access to an earlier identity. Older development versions used browser storage, so leftover values may exist on devices that tested those versions; the current app does not use them. You may clear those values in browser settings. Clearing browser state or losing the credential can make earlier private history inaccessible to you even before its server retention expires.

6. Cookies and infrastructure providers

The chat application uses first-party aggregate usage measurement and does not currently include third-party analytics or advertising trackers. Essential infrastructure can still use cookies or equivalent technologies for security, traffic management and challenge handling. We use Hostinger VPS infrastructure for hosting and Cloudflare when its DNS, proxy and security services are active. These providers may process network and device information and may handle data in countries outside your own under their service arrangements. See Cloudflare’s Privacy Policy and Cookie Policy and Hostinger’s Privacy Policy, linked below. Third-party links in user messages are outside our control; visiting them may disclose information directly to their operators.

Daily usage totals

We count page visits, visits that successfully join a room, and visits that successfully send a first public or private message. Only aggregate daily totals, including visit counters by approximate city, state/region and country, are stored in a separate analytics database, using Asia/Kolkata (IST) dates. For a repeated location we increase its counter; a new location creates a new aggregate row. These location counters start on 26 October 2026; earlier visits have no recorded location. Conversions are attributed to the date the visit started, including when a visit crosses midnight. A refresh or a new tab creates another visit; these totals are not unique people.

A random page-visit identifier and its progress are held temporarily in browser/server memory for up to 24 hours to avoid recounting room switches, reconnects or additional messages. No analytics cookies or persistent browser identifiers are used. The analytics database does not store visit IDs, nicknames, message text or IP addresses. We temporarily use the connecting IP address for a local, server-side geolocation database lookup; visitor IPs are not sent to an external geolocation API. Approximate city, state/region and country are retained only as aggregate visit counters, without links to chat identities or messages. We do not request device GPS location. IP-based locations can be wrong, especially on mobile networks and VPNs; unavailable locations are counted as Unknown. IP geolocation data is provided by DB-IP under CC BY 4.0. IP addresses may be used temporarily in memory for rate limiting; operational/security logs are separate as described elsewhere in this policy. Daily aggregate totals are retained for usage reporting. Blocking scripts, failed requests, bots, capacity limits or server restarts can affect these approximate counts; they are not an audited count of people.

7. Storage, retention and expiry

Public and direct message bodies are stored in a server-side database. Public rooms retain at most their latest 100 messages in the active database; saving a newer public message removes older entries beyond that room’s limit. The 24-hour period is measured from each message’s original sending time; reading, replying, reconnecting or switching rooms does not restart it. Public and private message history excludes messages older than 24 hours. Cleanup runs at startup and approximately every minute to remove expired message rows from the active database; a cleanup failure may delay physical removal, while history queries continue to exclude expired messages. The application loads at most the latest 50 messages for a public room or private conversation, not the entire database. Identity-to-nickname mappings, conversation read markers and block preferences are separate metadata and are not currently covered by the message-body expiry job. Operational access/security logs follow server rotation and may have different retention. Backups, database journals, incident records and lawfully preserved material may retain copies beyond active-message expiry. Deleting a database row is not a guarantee of immediate forensic erasure from storage. We do not promise that all data disappear after 24 hours; contact us about a specific deletion or retention question.

8. Security and access

The live service uses HTTPS and secure WebSocket transport. The backend limits inputs and request rates and checks private-history access against the requesting session identity. Message text is rendered as text rather than executed as HTML. These controls reduce risk but cannot eliminate it. Public and private message bodies are not end-to-end encrypted and are not separately encrypted by the application within its database. Access by authorized administrators or providers may be necessary for operations, incident response, grievances or legal compliance. Do not share passwords, financial credentials, private identity documents or other highly sensitive information through this service.

9. Disclosure and legal obligations

We disclose public messages to the relevant room and private messages to their participants. We may disclose information to hosting/security providers as necessary to operate the service, to authorized advisers or personnel on a need-to-know basis, and to competent authorities or affected parties when required by law or reasonably necessary to address a credible safety/security threat. Requests and preservation duties are assessed under applicable law. If ownership or operation changes, any transfer of personal data must remain subject to applicable law and appropriate notice; this Policy does not create an unrestricted right to sell chat data.

GIF search and media

The optional private-chat GIF picker uses GIPHY. When you open or search the picker, your browser connects directly to GIPHY and sends your search words, API request details and ordinary network information such as your IP address. Loading a selected GIF also connects to GIPHY media servers. We do not send your private conversation text or Anamaak session credential to GIPHY. The selected GIF identifier is stored with the private message and follows our message-retention rules; copies held by GIPHY or another participant are outside that deletion process. See GIPHY’s Privacy Policy. You can continue using text chat without opening the GIF picker.

10. Your requests and limits

Depending on applicable law, you may request information about processing, access, correction, deletion, withdrawal of consent where relevant, or grievance review. Email official@thebluebamboo.in. Provide room/conversation details and approximate timestamps; never send your secret session credential, passwords or unnecessary identity documents by email. We may need proportionate verification and may refuse or limit access that would expose another user’s private information. A nickname alone is not proof that you own a session. Leaving the service stops ordinary participation but does not automatically delete past records. Legal duties, security investigations and others’ rights may restrict deletion; we will explain applicable limitations. You may also approach a competent regulator or court where the law allows.

11. Underage users and policy updates

Anamaak is intended only for people aged 18 or older. We use a self-declared age checkbox and do not claim independent age verification. If you believe an underage person is using the service or their data have been shared, contact us promptly with enough detail to locate the issue. We may restrict access and remove relevant data, subject to safety and legal preservation duties. We will post updates with a revised effective date and provide additional notice or request consent where required. Continued use does not waive rights that applicable law preserves.