Cookie Policy: safer browsing, stronger account protection
This page explains how Poki Com Games uses cookies and similar technologies, and how our cookie protection approach supports user privacy, account security, and safe play for India-based visitors. This policy is written in Indian English for local clarity; where terminology differs across regions, the meaning remains consistent with our standard privacy and security commitments.
At Poki Com Games (https://pokicom.games/), we build a simple promise into every product decision: your sessions should feel smooth, and your data should remain controlled and protected. Our team cares deeply about safe gaming experiences, especially in the day-to-day reality of shared family devices, mobile networks, and quick sign-in habits that are common across India. We take pride in running a platform that respects your choices and makes security understandable rather than intimidating.
Quick summary in 7 points (details follow below):
- Cookies are small files that help websites remember settings and protect sessions.
- We use cookies for essential functions, security, performance insights, and user preferences.
- We avoid using cookies in a way that sells your personal data.
- We reduce risks like cookie hijacking through secure session handling and encryption.
- You can control cookies via your browser settings and device tools at any time.
- We apply extra care for minors and encourage healthy play habits.
- If you have concerns, you can reach our security team by email (see “Contact and reporting”).
1) What is cookie protection?
Cookie protection means using technical and policy controls to reduce the chance that a cookie can be misused, copied, or abused. A cookie can store a preference (like language) or support a session (so you do not get logged out during normal browsing). In a gaming context, cookie protection matters because a stolen or manipulated session cookie can expose your account, your activity history, and in some cases your in-site wallet or purchase flows.
Cookie protection is not a single setting. It is a bundle of good practices:
- Data minimisation: we store only what is needed for a stated purpose.
- Secure transport: we encourage encrypted connections so cookies are not easily intercepted.
- Safer cookie attributes: when relevant, cookies are configured to reduce cross-site misuse.
- Expiry discipline: cookies should not live longer than needed for the function.
- User control: you can clear or block cookies, and choose stricter browser modes.
Plain-language idea: Cookies should help you, not expose you. If a cookie is not necessary, it should not exist. If it is necessary, it should be protected and short-lived.
2) Why cookie protection matters for gaming platforms
Real-world risks we plan for
- Session hijacking: attackers try to reuse a valid session cookie to “become you” online.
- Shared device exposure: a café PC or a family phone may keep cookies unless cleared.
- Phishing and fake sites: look-alike pages can trick users into unsafe clicks and logins.
- Network interception: insecure connections can expose data in transit.
- Tracking misunderstandings: users deserve clarity on what is collected and why.
What matters to users (India focus)
- Privacy: clear control over what is stored on the device.
- Data security: safer handling of login states and browsing identifiers.
- Payment caution: protection around online purchase signals and checkout integrity.
- Identity safety: reduced exposure of personal details and behavioural patterns.
- Digital footprint: ability to reduce stored traces when using shared devices.
Gaming is fast-paced. Users click quickly, move between games, and may sign in from multiple devices. That convenience can create risk if session identifiers linger too long or if browsers store data silently on shared hardware. Cookie protection is therefore tied to day-to-day safety, not just legal compliance.
We do not claim any system is “risk-free”. Instead, we commit to practical safeguards, transparent explanations, and user controls so you can make informed decisions.
3) Our cookie protection framework
Poki Com Games follows a practical framework designed to be verifiable, understandable, and consistent with safe web practices. We combine technical controls with review discipline so changes do not happen quietly.
3.1 Controls we apply (technical and operational)
- Purpose mapping: each cookie category has a defined purpose and owner (team responsibility).
- Retention rules: cookies have a target lifespan, measured in days or until session end.
- Access restriction: where feasible, cookies are limited to reduce exposure in scripts and cross-site contexts.
- Encrypted transport: we encourage secure connections to reduce interception risks.
- Change control: new cookie usage is reviewed before release and revisited periodically.
3.2 What we do not do
- We do not use cookies to sell your personal data.
- We do not ask you to rely on “secret settings”. Controls and explanations are provided in plain language.
- We do not keep security cookies indefinitely; long lifetimes increase risk on shared devices.
If you are using a public or shared device, we strongly recommend using private browsing mode and clearing cookies after your session. This is particularly important when you have logged in, saved preferences, or completed any purchase-related action.
4) Policy-level safeguards and transparency
Policies matter because they set limits. A technical system can change, but a policy is a commitment users can hold us to. In practical terms, our policy safeguards focus on three outcomes: clarity, control, and account safety.
4.1 Clear cookie categories with plain purposes
We describe cookie categories so users can understand the trade-off: which cookies are essential for the site to function, and which improve experience or help us measure performance. Each category below includes examples and typical lifetimes. Actual cookie names may vary as we improve systems, but the purpose remains the same.
4.2 Measurable retention approach
We use reasonable time windows to reduce unnecessary persistence. As a practical reference:
- Session cookies: typically expire when you close the browser tab or app (0 days persistence).
- Short preference cookies: often 7–30 days (language, layout, “do not show again”).
- Security cookies: often 1–14 days, with shorter values used for higher-risk contexts.
- Analytics/performance cookies: often 30–180 days to observe trends without excessive detail.
These ranges are not guarantees. They are operational targets used to make the platform predictable and safer for users. Where a shorter lifespan works, we prefer it.
5) Independent oversight and accountability
Trust improves when checks exist. Our oversight approach includes internal review and structured escalation. Depending on the nature of the change, we may require review by engineering leads, privacy reviewers, or security reviewers.
5.1 Review roles
- Policy owner
- Ensures the written policy matches real cookie usage and user expectations.
- Security reviewer
- Focuses on session safety, abuse prevention, and risk reduction for account access.
- Engineering owner
- Confirms that technical settings match the intended purpose and retention window.
5.2 What users can verify
- You can inspect cookies using browser developer tools (most browsers provide a “Cookies” view under storage).
- You can clear cookies at any time and confirm that preference values reset.
- You can use stricter browser settings to block third-party cookies and observe site behaviour.
We encourage responsible reporting if you see suspicious behaviour such as forced logins, unexpected redirects, or repeated sign-in prompts that may indicate a session problem.
6) Types of cookies we use
The table below explains common cookie categories used on platforms like Poki Com Games. It is meant to be readable and practical, so you can decide what settings fit your comfort level.
| Cookie category | Purpose | Typical lifespan | What happens if you block it? |
|---|---|---|---|
| Essential (strictly necessary) | Core site functions, session stability, basic security checks, load balancing. | Session to 14 days (depending on function). | Site may not work reliably; logins and core navigation may break. |
| Security | Helps detect suspicious activity, reduces automated abuse, supports safer authentication. | 1–14 days (often shorter for high-risk actions). | Higher friction: repeated checks, more sign-in prompts, reduced protection signals. |
| Preferences | Remembers language, layout, consent choices, and comfort settings. | 7–30 days (sometimes longer if low-risk). | Settings reset; you may need to reselect language or preferences. |
| Performance and measurement | Helps us understand page reliability, errors, and what features users engage with (in aggregate). | 30–180 days. | We learn less about reliability issues; some improvements may take longer. |
Note: Some browsers treat certain identifiers similarly to cookies (for example, local storage). When we use similar storage, we apply the same principles: purpose clarity, data minimisation, retention discipline, and user control.
7) How users can control cookies
You remain in control. Most modern browsers allow you to block cookies, delete cookies, and restrict third-party cookies. If you want stronger privacy on shared devices, consider these practical steps.
7.1 Recommended controls (step-by-step)
- Use private browsing when playing on shared devices (cyber cafés, office desktops, family tablets).
- Clear cookies after gaming, especially if you signed in or used any payment feature.
- Block third-party cookies in your browser privacy settings if you prefer stricter tracking limits.
- Review site permissions (pop-ups, notifications, and location) to reduce unwanted prompts.
- Update the browser to benefit from the latest security patches and cookie controls.
Reminder for families: If a minor uses your device, set up a separate browser profile or a restricted mode, and clear cookies regularly. Shared devices are one of the most common ways sessions get exposed unintentionally.
Practical action
If you want to reduce stored data right now, open your browser settings and search for “Privacy” or “Cookies”, then select “Clear browsing data”. Choose an appropriate time range (for example, last 7 days) and confirm deletion.
This button does not change settings automatically; it is a quick reminder so you can take action using your browser’s built-in controls.
8) Risk warning: preventing cookie hijacking during game login
Cookie hijacking happens when an attacker gains access to a valid session identifier and uses it to impersonate a user. While modern browsers and secure connections reduce risk, users can further protect themselves with a few disciplined habits.
8.1 How attackers commonly try to steal sessions
- Phishing pages: fake “sign in” screens that imitate a known website.
- Unsafe Wi-Fi: insecure hotspots where traffic can be monitored.
- Malicious extensions: browser add-ons that request excessive permissions.
- Shared device leftovers: cookies stored after someone forgets to sign out.
8.2 Practical prevention checklist (10 items)
- Type the website address carefully and avoid look-alike links.
- Prefer a trusted network; avoid logging in on unknown public Wi-Fi.
- Keep your browser updated (monthly is a sensible baseline).
- Use private mode on shared devices.
- Clear cookies after your session if you used a shared device.
- Avoid installing unknown extensions; review permissions before enabling any add-on.
- Do not reuse passwords across multiple sites; use a password manager if possible.
- If you see unexpected prompts or redirects, stop and close the tab.
- Check for unusual account behaviour (sudden logouts, unfamiliar activity).
- Report suspected issues to the security contact listed below.
We design our session handling to reduce misuse, but user vigilance remains a powerful layer of protection—especially in environments where devices are shared.
9) Payment behaviour, encryption, and “data not sold” commitment
Online payments are sensitive because they can expose spending behaviour, device identifiers, and transaction timing. If Poki Com Games provides any payment-related flows, we treat that context as higher risk and apply stricter controls.
9.1 Encryption and transport safety
- Encrypted connections: we encourage HTTPS for page delivery and secure transmission.
- Session integrity: we aim to prevent session tokens from being exposed in unsafe contexts.
- Short-lived signals: payment-related signals should not persist longer than needed.
9.2 Handling of data
We aim to avoid using cookies in a way that sells your personal data. Where measurement is necessary for reliability and fraud prevention, we prefer aggregated insights and limited retention windows. If you prefer stricter privacy, you can block non-essential cookie categories in your browser and still access core content, though some features may behave differently.
Practical note: If you are on a shared device and have completed any purchase step, clear cookies and browsing data immediately after you finish.
10) Protection of minors and healthy gaming habits
Poki Com Games recognises that minors may access gaming content through family devices. Cookie and session data can inadvertently preserve settings or history that a family might prefer to keep private. We therefore encourage parents and guardians to adopt safer browsing habits and device-level controls.
10.1 Recommended family controls (India-friendly)
- Separate profiles: use separate browser profiles for adults and minors.
- Regular clearing: clear cookies weekly if the device is shared across multiple users.
- Screen-time routines: set fixed play windows (for example, 30–60 minutes) and take breaks.
- Open conversations: teach children to avoid unknown links, pop-ups, and “free reward” prompts.
Preventing internet addiction is not only about time limits; it is about setting healthy patterns early. We encourage users to take breaks, avoid late-night extended sessions, and seek support if gaming starts affecting sleep, studies, work, or relationships.
Safety-first reminder
If you suspect a child has used a shared device to sign in, clear cookies and saved passwords immediately, then review browser history and installed extensions. These steps reduce the chance of accidental data sharing and protect family privacy.
11) Contact and reporting
If you believe your session has been compromised, or you notice suspicious behaviour such as unfamiliar sign-ins, unexpected prompts, or repeated redirects, contact our security team as soon as possible. Please include clear details so we can investigate efficiently.
11.1 What to include in your message
- Date and time of the incident (include your time zone).
- Device type (Android/iOS/Windows/macOS) and browser name/version.
- What you were doing when the issue occurred (login, gameplay, settings, payment step).
- Any screenshots you are comfortable sharing (ensure sensitive information is hidden).
- Whether the device is shared or private.
Security contact email: [email protected]
We aim to respond in a reasonable timeframe based on severity. For immediate personal safety, consider also changing your passwords and clearing cookies right away.
12) Changes to this policy and version clarity
We may update this Cookie Policy to reflect improvements in security controls, changes in browser technology, or updates in how features work. When we make meaningful changes, we will update the publication date at the top of this page.
12.1 How you can stay informed
- Revisit this page periodically, especially after major browser updates.
- Review your browser’s privacy controls every 3 months as a practical routine.
- Clear stored cookies when you change devices or hand a device to another family member.
If a change reduces user control or introduces new categories of cookies, we treat that as a high-sensitivity change and apply stricter review.
13) Short glossary (to keep terms clear)
- Cookie
- A small data file saved by a website on your browser or device to remember settings or support sessions.
- Session
- Your active browsing period, typically from opening the site until you close the browser or sign out.
- Session hijacking
- When someone steals or reuses a session identifier to impersonate a user.
- Third-party cookie
- A cookie set by a domain other than the one you are visiting; browsers increasingly restrict these for privacy reasons.
- Digital footprint
- Traces of your activity and settings stored across devices, browsers, and online services.
14) Brief introduction before conclusion
In summary, our Cookie Policy is built around practical security, transparency, and user control. If you would like to learn more about Poki Com Games and how we approach safe, user-respecting play, see more at Poki Com Games.
For additional updates, guidance, and general information related to this Cookie Policy, you can also visit Cookie Policy.
Thank you for choosing a platform that values clarity. We encourage you to use the controls described above—especially on shared devices— and to contact our security team if anything feels unusual.
-
Q: Does Poki Com Games require cookies to work?
A: Some essential cookies are required for basic site functions and session stability. You can block non-essential cookies using your browser settings, but certain features may behave differently.
-
Q: How often should I clear cookies on a shared device?
A: If the device is shared, clearing cookies after each login session is the safest practice. As a baseline routine, many families also clear cookies weekly.
-
Q: What is the easiest way to reduce session hijacking risk?
A: Use private browsing on shared devices, avoid unknown Wi-Fi for logins, keep your browser updated, and clear cookies after you finish playing\u2014especially after any sign-in.
-
Q: Will blocking cookies stop games from loading?
A: Blocking all cookies can cause issues with sign-in, preferences, and some site functions. Blocking non-essential cookies is typically a balanced approach for many users.
-
Q: Does Poki Com Games sell my personal data through cookies?
A: We aim to avoid using cookies in a way that sells your personal data. Cookies are used for essential functions, security, preferences, and performance insights as described in the policy.
-
Q: How can parents protect minors using the same phone or laptop?
A: Use separate browser profiles, clear cookies regularly, avoid saving passwords, and set healthy play routines (for example, 30\u201360 minutes with breaks). Shared-device hygiene is key.
-
Q: Who do I contact if I suspect a security issue?
A: Email the security team with details such as time, device type, browser, and what happened. The policy recommends reporting promptly so risks can be assessed and reduced.