Author: Reddy Arnav  |  Reviewer: Nair Meera  |  Publication Date: 04-01-2026

Privacy Policy that puts player safety first

Welcome to Poki Com Game. This Privacy Policy explains, in practical terms, how we handle information when you use our website and related services in India. We run a gaming-focused experience where safety, account protection, and fair play matter. That means we collect limited, relevant information to keep accounts secure, improve device compatibility, and reduce misuse. We do not promise outcomes or benefits; our goal is to be transparent about what we do, why we do it, and what choices you have.

This document applies to the services accessible via https://pokicomgame.app and pages that link to this policy. If you do not agree with this Privacy Policy, please do not use the service. If you have questions, you can contact us at [email protected].

Quick clarity for Indian users: We follow a “need-to-know” approach. For example, we keep security logs to detect suspicious logins, and we store a small set of device details to troubleshoot compatibility issues. We avoid collecting sensitive personal details unless required by law or essential for a specific support request.

1) Who we are and what our mission means for privacy

Poki Com Game is a gaming-focused website that aims to provide a stable, safe, and dependable experience for users. Our mission is simple:

• Enhance gameplay experience by improving performance, reducing errors, and keeping features consistent.
• Improve device compatibility by understanding what browsers/devices work well and where issues occur.
• Strengthen security and risk control by detecting and responding to unusual activity, fraud attempts, or automated abuse.

In practice, this mission affects the kind of data we collect. We focus on data that supports account safety, system reliability, and responsible operation.

2) What information we collect

We collect information in four main categories. The exact fields may differ depending on how you use the site, whether you create an account, and whether you contact support. Below is a detailed breakdown in a tutorial-style format, with examples to help you understand what each category means.

2.1 Account Information

Account Information is what you provide when you register or maintain your profile. Typical examples include:

1. Identifier details: username, display name, or account ID.
2. Contact details: email address (for verification, account recovery, and support).
3. Preference settings: language choices, notification preferences, and similar controls.

We encourage users to keep profiles minimal. Do not share sensitive personal details in profile fields or in public areas. If you provide extra information voluntarily, it may be stored as part of your account record.

2.2 Login and Security Information

Login and Security Information helps us protect accounts and detect suspicious activity. This can include:

• Login timestamps: date and time of sign-in attempts (successful and unsuccessful).
• Security signals: password reset requests, account recovery actions, and verification events.
• Risk indicators: repeated failed logins, unusual location patterns, or abnormal session behaviour.

Important: We do not ask you to share passwords over email. If you receive a message claiming to be us and requesting your password or OTP, treat it as suspicious and contact [email protected].

2.3 Game Behaviour Data

Game Behaviour Data relates to how the service is used. This helps ensure fairness and improve features. It may include:

• Session activity: game sessions started, duration, and basic interaction events (e.g., button clicks).
• Performance events: crash reports, error codes, and loading time measurements.
• Fair-play signals: patterns that may indicate bot-like behaviour or abuse (without accusing users unfairly).

We use these signals carefully and proportionately. Automated patterns can happen for legitimate reasons (shared networks, device constraints, or accessibility tools). Our approach is to investigate anomalies using multiple signals rather than relying on one indicator.

2.4 Technical Device Data

Technical Device Data helps the site work smoothly across devices used in India, including budget phones and varied network conditions. This can include:

• Device and browser details: browser type, version, operating system, language, screen size.
• Connection and diagnostics: approximate latency signals, error logs, and page response timings.
• IP address: used for security checks, rate limiting, and basic geo-level analysis (not precise tracking).

We do not try to identify you through invasive fingerprinting methods. Our goal is device compatibility and safety, not hidden surveillance.

3) Why we collect this data

We collect data for a limited set of core objectives. Each objective maps to a practical operational need. If you prefer a simple checklist, here it is:

3.1 Enhance gaming experience

We measure page performance and error rates so we can fix issues that reduce playability. For example:

• If a game page crashes repeatedly, crash logs help us identify the cause.
• If loading times exceed a reasonable threshold (for instance, 3–8 seconds on average connections), we can investigate optimisation at the engineering level.
• If users report that a feature is confusing, interaction events help us see where users get stuck.

3.2 Improve device compatibility

India has diverse device usage patterns—different Android versions, browsers, and lower memory devices are common. We use technical device data to:

1. Identify browser-specific issues (for example, a bug only occurring in a certain browser version).
2. Verify layout stability for different screen sizes, including small screens.
3. Reduce unexpected errors due to unsupported capabilities.

3.3 Strengthen security and risk control

Security requires signals. Without logs and authentication records, we cannot:

• Detect repeated password-guessing attempts or credential stuffing.
• Identify account takeover patterns (for example, sudden logins from a new device plus rapid changes to account recovery info).
• Limit automated abuse that can degrade service reliability for genuine players.

We apply controls proportionately and aim to avoid false positives. Where an action might restrict access, we prefer steps like verification prompts, rate limits, and manual review over permanent blocks.

4) How we protect your data

Protecting data is not just a statement—it is a set of operational practices. While no online system can guarantee absolute security, we implement reasonable safeguards aligned with widely accepted security principles.

4.1 Encryption technology

We use encryption where it matters:

• In transit: data transmitted between your browser and our servers is protected using standard HTTPS/TLS practices.
• At rest: sensitive fields (such as authentication-related data) are stored using protective measures appropriate to the risk.

If you are using public Wi-Fi, we still recommend basic precautions: log out after use and avoid saving passwords on shared devices.

4.2 Access control

We restrict access to data. Typical controls include:

1. Role-based access: only authorised personnel can access specific systems.
2. Least privilege: staff access is limited to what is required for their role.
3. Audit trails: administrative actions can be logged for accountability.

4.3 Operational security standards

We align our practices with widely used security approaches (such as monitoring, incident response planning, and routine patching). In practice, this means:

• Monitoring for unusual activity and spikes that can indicate abuse.
• Applying updates to reduce exposure to known vulnerabilities.
• Reviewing system configurations to reduce misconfiguration risk.

4.4 What you can do (user-level security steps)

A secure experience is shared work. For best account safety, we recommend:

• Use a strong password (12+ characters is a good baseline; mix words and symbols sensibly).
• Do not reuse passwords across services.
• Be cautious about links from unknown sources.
• Keep your device updated and use reputable browsers.

5) Transparency of cookies and tracking technologies

Cookies are small text files stored on your device. We use cookies and similar technologies for site functionality, security, and performance insights. We do not use them to secretly collect sensitive personal details. Below is a clear, category-wise explanation.

5.1 Necessity of cookies

Necessary cookies help the site function and stay secure. Examples include:

• Session cookies: keep you signed in during a session and maintain basic state.
• Security cookies: support fraud detection, abuse prevention, and session integrity checks.

If you disable necessary cookies, the service may not work correctly, and some security checks may fail.

5.2 Performance cookies

Performance cookies help us understand how the website behaves across devices and networks. This can include:

1. Counts of page views and feature usage at an aggregated level.
2. Load time measurements (for example, average time to first interaction).
3. Error frequency reporting (for example, how often a particular error appears per 1,000 sessions).

5.3 Analysis cookies

Analysis cookies can help us identify trends like which pages are most frequently visited and where users face obstacles. We prefer aggregated, non-identifying reporting. If we use third-party analytics, we aim to configure it to reduce unnecessary collection.

5.4 Managing cookie choices

You can manage cookies through your browser settings. Typical options include blocking third-party cookies, clearing existing cookies, or setting site-specific preferences. Note that clearing cookies can sign you out and reset preferences.

6) Third-party services and disclosure

Sometimes we rely on third parties to operate the service effectively. This may include:

• Infrastructure and hosting providers to serve content and maintain uptime.
• Security service providers for threat detection, rate limiting, and abuse prevention.
• Analytics providers to measure site performance and user flows at a broad level.

6.1 When we share data

We may disclose information:

1. To service providers who process data on our behalf under contractual obligations.
2. For legal compliance where required by applicable law, lawful requests, or to protect rights and safety.
3. For safety investigations when necessary to detect, prevent, or respond to security incidents or suspected abuse.

6.2 What we avoid

We do not sell personal information as a routine business practice. We also avoid sharing more than what is necessary for the stated purpose.

7) Data retention

We retain information only for as long as needed to achieve the purposes described in this policy, or to comply with legal obligations. Retention periods vary based on the data type and risk context. To keep this practical, here is an example-based explanation:

• Account records: retained while your account is active and for a reasonable period after deletion requests, to handle disputes, compliance, and security investigations.
• Security logs: retained for a limited period to detect suspicious patterns and investigate incidents.
• Technical logs: retained for troubleshooting and improving stability, often with shorter retention windows than account records.

Where feasible, we reduce or anonymise data after it is no longer needed. If you request deletion, some data may still be retained for legal compliance or legitimate security reasons.

8) Your rights as a user

User rights can vary depending on where you live and the applicable laws. We still try to offer fair, user-friendly controls. In general, you may have rights such as:

8.1 Access

You can request a summary of personal data we hold about you, where feasible and legally permitted.

8.2 Correction

If your information is inaccurate or outdated, you can request correction. Many basic changes can be made through account settings.

8.3 Deletion

You can request deletion of your account data, subject to legal, safety, and operational constraints. For example, we may retain limited logs to prevent repeat abuse or to comply with lawful requirements.

8.4 Objection and restriction

In some cases you may object to certain processing or request restriction, especially where processing is not essential to provide the service.

8.5 How to exercise your rights

Send an email to [email protected] with:

• Your account email (if you have one)
• The request type: access / correction / deletion / restriction
• Any details that help verify identity and locate records

For safety, we may ask for reasonable verification before acting on requests. This protects you from fraudulent requests.

9) Children’s privacy (important for game services)

Games can attract younger users. We take children’s privacy seriously. If you are a parent or guardian and believe a child has provided personal information without appropriate consent, contact us at [email protected].

We encourage families to follow basic safety steps:

1. Keep login details private and supervise account access for younger users.
2. Avoid sharing personal details (school, address, phone number) in usernames or public spaces.
3. Report suspicious messages or requests for money, codes, or personal data.

Where we learn that we have collected personal information from a child in a way that violates applicable requirements, we will take reasonable steps to delete it or restrict it.

10) International data transfers

Depending on our infrastructure and service providers, information may be processed in countries outside India. When this happens, we use reasonable measures to ensure appropriate protection, such as contractual safeguards and security controls. We do not transfer data “just because”; transfers occur only when needed for reliable operations, security monitoring, or support.

If you have concerns about cross-border processing, you can contact us and we will explain the practical context and what safeguards apply in the specific scenario.

11) Contact us

If you have questions about this Privacy Policy, account safety, or a data request, contact our support team:

Email: [email protected]

To help us respond faster, include:

• Subject line: “Privacy Policy Query” or “Data Request”
• Your account email (if applicable)
• Relevant screenshots or error codes (optional)
• Approximate dates/time of the issue (for example, “03-01-2026, 7:30 PM IST”)

12) Policy updates and change notices

We may update this policy when operational needs change, when legal requirements evolve, or when we introduce new protective measures. We aim to keep updates practical and readable. If changes are significant, we may provide a clear notice on the website before the updated policy takes effect.

We recommend reviewing the policy periodically—especially if you use the service often.

13) A brief introduction before closing

Poki Com Game is built with a focus on reliable play, sensible safety controls, and transparency that Indian users can actually use. Our approach is to collect what is needed for account protection, fair play checks, and compatibility work— and to avoid collecting what we do not need.

Article 1 and 2 reflect the passion and dedication behind https://pokicomgame.app: we want a service that is stable, safe, and respectful of user privacy while still being practical for a gaming platform. You can see more about Poki Com Game and this Privacy Policy at Poki Com Game.

Before you go, you can also explore updates and related pages at Privacy Policy.

If anything in this document feels unclear, please reach out to us. Clear communication is part of safety.