Privacy policy

Our service and this policy

This privacy policy covers the Murgi Game content and demo-access interface that we supply. The original Chicken Road client belongs to InOut Games and runs from the provider's infrastructure. Its resources, session handling and policies are separate from our static content.

Our page assets and fonts are local. We do not load a remote font service as part of that static presentation. This does not mean that every runtime resource stays on our domain: activating the playable demo loads external provider resources inside the game area.

Information we do not collect through forms

We do not provide account registration, login, contact forms or payment forms. We do not request names, email addresses, phone numbers, passwords, card details or identity documents through our service. We also do not collect support messages through a hidden ticket or chat system.

We do not run our own analytics or maintain a saved game balance. We do not receive a deposit record or withdrawal request because our service offers neither function. A balance visible inside the original game is part of the provider's demo state, not an account that we maintain.

What happens when the demo is activated

When activated, our demo access loads the original InOut client in an embedded game frame. The provider receives the network requests needed to deliver that game. Browser and connection information may accompany those requests, and the external client may handle storage or session state under its own policies.

The alternative native-demo link opens the provider destination in a separate window or tab. That route also connects directly to external infrastructure. The provider's applicable terms and privacy practices govern its game resources and state in either format; an embedded frame does not make that processing first-party to us.

• Our static presentation and the playable game have different resource origins.
• Demo activation starts the connection to the external game.
• The provider controls its own session behaviour.
• We do not promise that closing or refreshing the game erases provider-held information.

Hosting and ordinary request metadata

Delivering static files requires network requests. A hosting or delivery service may process ordinary request metadata, including an IP address, request time, requested path, browser information and technical error data. If delivered through Cloudflare, relevant infrastructure processing follows the applicable hosting arrangements.

We do not state a fixed retention period, storage region or logging configuration without a verified basis. We also do not claim that a static service produces no technical records. Hosting metadata is different from a profile built through our own analytics, which we do not run.

External policies and privacy boundaries

We do not control the provider's storage, logs or deletion procedures. External privacy questions depend on the destination and the information it processes. The developer-published channels and policies at that destination define the relevant contact route.

Our contact section describes our own communication limits. We do not collect privacy requests through a form that does not exist or promise deletion of records held by another provider. Any future addition of forms, analytics or account features would require a corresponding change to our published privacy description.