PUBGNickname sets no cookies, runs no analytics, and shows no ads. An anonymous visit to this site stores nothing on your device and contacts no other company from your browser. What we do collect happens on our server, only when you press a button, and this page says exactly what that is.
Last updated: 20 August 2026 · Published by the PUBGNickname editorial team.
What this policy covers
This policy covers pubgnickname.com — the nickname generator and community nickname library for PUBG Mobile and Battlegrounds Mobile India (BGMI) described on our about page. It was last reviewed against the site’s actual source code, not against a template.
There are no user accounts on this site. We do not run a newsletter, we do not take payments, and we never ask for your name, email address, phone number or date of birth.
What happens in your browser: nothing
Loading any page on this site sets zero cookies and writes nothing to local storage. We checked this on 20 August 2026 with a real browser session: after loading the site and running the generator, the cookie jar, localStorage and sessionStorage were all empty.
Your browser also never contacts anyone but us. Every request a page makes goes to pubgnickname.com. There is no Google Analytics, no Google Tag Manager, no advertising network, no social pixel, no embedded video, and no third-party font or script host. That means there is no cookie banner on this site because there is nothing to consent to.
You can verify this yourself: open your browser’s developer tools, reload the page, and look at the Network and Application tabs.
What the name generator sends to our server
The styling happens on our server, not in your browser, so the name you type is sent to us. We would rather say this plainly than let you assume otherwise.
When you press generate, your browser posts the text in the name box and your four style selections to our generator endpoint, and the styled variants come back from there. Alongside that, our engine keeps a count of which names are being asked for, so we can see what to build next. That record is deliberately narrow:
- It stores the name and a weekly tally of how many sessions and how many builds it saw — not a per-person history, and not a timeline of what you personally typed.
- Your IP address is never written into that table. It is used once, inside a hash that expires after a day, purely so that building the same name twice on the same day counts as one visitor instead of two.
- Text that looks like personal contact data is discarded before anything is stored. The engine drops any entry containing an
@, a web address, or a run of six or more digits — the shapes an email address, a link and a phone number take. - Entries shorter than two characters or longer than forty are ignored. A banned-terms filter also exists, but its word list is presently empty, so at the moment it excludes nothing by itself.
So if you type something personal into the name box by accident, the most likely outcome is that it is filtered out and never stored at all.
What we store when you contribute a nickname
Submitting a nickname to the community library is the one action on this site that sends your IP address onward. If that is not something you want, simply do not use the submit form — every other part of the site works without it.
When you submit, the following goes to the provider that operates our nickname catalogue: the nickname text, the name it belongs to, any copy text you included, and the IP address the request came from. The IP is used by that provider for abuse prevention — stopping one person from flooding the library.
Do not put personal information into a submitted nickname. Contributed nicknames are public by design: they are shown to every other visitor, counted, and ranked.
Likes, dislikes, copy counts and ratings
Pressing copy, like, dislike or a rating records a number, not a person. These actions increment a counter attached to the nickname, and the counters are what let the library rank by what people actually use.
The counts are stored on our own server and forwarded to our catalogue provider so the totals stay consistent for everyone. We do not attach your identity to a vote, because we do not have one.
Server logs and security
Our web server keeps standard access logs, and they are deleted after about ten days. They are rotated once a day and ten rotations are kept, which we verified on the server itself.
A log line contains what every web server records: the IP address, the time, the page requested, the referring page and the browser’s user-agent string. We use it to diagnose faults and to investigate abuse. We do not build visitor profiles from it and we do not sell it.
The site also runs a security plugin that records requests it blocks or considers suspicious, including the IP they came from, and participates in a shared threat-intelligence network for attacking IP addresses. Continuous logging of ordinary visitor traffic is switched off.
Who else receives data
Four external services are involved, and all four are contacted by our server — never by your browser. None of them receives anything about you unless the row below says so.
| Service | What it does | What it receives about you |
|---|---|---|
| Nickname catalogue backend | Stores the community nickname library and its counters | Only when you submit or vote: the nickname text, and for a submission, your IP address |
| Demand analytics hub | Tells us which names people are looking for, so we know what to build | A weekly list of names with session and build counts. No IP address, nothing tied to a person |
| Decoration set provider | Supplies the emoji, symbol and kaomoji sets the generator decorates with | Nothing. It is asked for a set of characters, not for anything about you |
| Transliteration service | Converts text between writing systems where a page needs it | Only the text being converted |
Our hosting provider and the network in front of the site necessarily process your IP address in order to deliver a page to you, as is true of any website.
How long we keep things
| What | How long |
|---|---|
| Server access logs | About 10 days, then deleted automatically |
| The one-day hash used to de-duplicate name builds | 24 hours |
| Weekly name-demand counts | Kept as aggregate statistics; they contain no identifier |
| A nickname you contributed, and its counters | Until you or we remove it |
| Security records of blocked requests | Managed by the security plugin’s own rotation |
Your choices, and how to get something removed
You can use the whole generator without contributing anything, and a contributed nickname can be taken down on request.
To have a nickname removed from the library, tell us which one through our contact page and we will delete it. We act on takedown requests for nicknames that impersonate a real person, that contain someone’s personal information, or that are abusive.
Because we do not have accounts, we cannot look up “your data” by identity — there is no identity on file. If you believe a specific record relates to you, describe it and we will find it.
Children
This site is a naming tool for a video game and is not directed at children under 13. We do not knowingly collect anything from them — and since we collect no identifying information from anyone, there is nothing about a child for us to hold. If you believe a contributed nickname exposes a child’s personal information, report it and we will remove it.
Changes to this policy
When the site’s data handling changes, this page changes with it and the updated date above changes too. We do not backdate it, and we do not refresh the date when nothing has changed. If we ever add analytics, advertising or any cookie, this page will be updated before that goes live, not after.
Contact
Questions about this policy, or a request to remove something, go to the editorial team through the contact page. For everything else about who we are and how we work, see PUBGNickname.