Last updated: 16 September 2026
joingg.cc sets no cookies. There is no analytics, no tag manager, no tracking pixel, no advertising script, and nothing on these pages loaded from another company's server. You can read every article here without accepting anything and without telling me who you are.
One record does exist: the web server's access log. It is described in full below, because it is the only place where anything about your visit is written down.
joingg.cc is written and run by one person, Sergei, who writes as SweetMask. There is no company behind it and no staff. For data protection purposes, that one person is the controller of everything described here.
joingg.cc is a sibling of joingg.co, a game server directory run by the same person. The two are separate sites, with separate content, separate databases and separate policies. Nothing on this page describes joingg.co, and reading one of them tells the other nothing about you.
The way to reach me is the contact form on this site.
The site runs on a rented virtual server, behind nginx. nginx writes one line to an access log for every request it answers, the way most web servers on the internet do. Each line holds:
/reviews/an-articleThat is the whole of it. No script on the page reports anything back, so nothing is recorded about how long you stayed, what you scrolled past or where you went next.
Why it is kept. To keep the site running and to defend it. Logs are how I find out that a page is returning errors, that a link is broken, or that one crawler is hitting the server hard enough to slow it down for everybody else.
Legal basis (GDPR). Legitimate interests, Article 6(1)(f): operating and securing a website I am responsible for. The logs are not used to build a profile, are not matched against anything else, and are not sold, shared or handed to an advertiser.
Who can see them. Me. The company I rent the server from has the access to its own infrastructure that any host has.
How long they are kept. Fourteen days. The log is rotated once a day and fourteen files are kept, so the oldest entry on the server is always about two weeks old and everything before that has been deleted. Nothing is archived elsewhere first.
If you send a message through the contact form, it collects your name, an email address, a subject line and the message you wrote. Those four things are stored on the same server as the site, and I read them there.
Why. To read what you sent and to answer you. That is all the form is for.
Legal basis (GDPR). Consent, Article 6(1)(a). You give it by choosing to write to me, and you can withdraw it at any time by asking me to delete the message.
How long. Messages are kept while the exchange is still useful and deleted when it is not, or sooner if you ask. There is no newsletter and no mailing list here, so an address you send me is not added to anything and is not used to contact you about anything other than your own message.
There are no user accounts on joingg.cc. No login, no registration, no comments, no forum, no newsletter sign-up, no shop, no payment of any kind. Nothing on the site asks you to identify yourself in order to read it.
The site sets none. Not a session cookie, not a preference cookie, not an analytics cookie, not a third-party cookie. There is no cookie banner because there is nothing to ask you about.
You do not have to take my word for it. Open your browser's developer tools on any page here and look at the cookies for this domain; there are none.
If that ever changes, this page changes with it and the date at the top moves. See the advertising section below for the one situation where it is likely to.
No third-party script runs on these pages. Articles are served from a SQLite database on the same machine that answers the request. There is no CDN in front of the site, no hosted font service, no analytics provider, no social widget and no comment platform.
One honest caveat. If an article ever embeds something hosted elsewhere, such as a video player, your browser has to contact that provider to load it, and that provider can see the request and applies its own privacy policy to it. Where that happens it is visible in the article itself.
No advertising runs on joingg.cc. There is no ad script on the page, no ad network is contacted when you load an article, and no advertising cookie is set. Anything you read below about advertising is about what would change in future, not about what happens now.
I have applied to Google AdSense. If the site is accepted and ads begin to run, the date at the top of this page will change on the day it happens, and the following will then apply:
Serving an ad involves your IP address and your browser's user agent reaching the ad network, because that is how any request over the internet works. If you would rather that did not happen at all, the ad network's opt-out links above and an ad blocker are both effective, and neither one stops you reading the site.
Everything described here lives on one rented virtual server: the site, the article database, the logs and any contact form messages. None of it is passed to an analytics platform, an advertising network or a marketing service.
The server is in Frankfurt, Germany. That is inside the EEA, so nothing described on this page is transferred out of it. Backups are copies made on that same machine — they are not sent to another provider, another country or any cloud storage.
One exception worth naming rather than burying: a message sent through the contact form is forwarded to joingg.co's moderation queue, because the same person runs both sites and reads one inbox rather than two. That is a different application, and it runs on the same server in the same country.
The site is served over HTTPS, so what you read here is encrypted between your browser and the server.
If you are in the EU or the UK, the GDPR gives you the right to ask for a copy of the personal data held about you, to have it corrected, to have it erased, to have its use restricted, to object to its use, and to receive data you provided in a portable form. Those rights apply here, and the way to use any of them is the contact form.
Two limitations worth stating plainly, because you cannot check them from outside:
A log line is identified only by an IP address. I cannot tell from one who you are, and I have no way to find "your" entries unless you tell me the IP address and roughly when you visited. Log files also rotate, so entries from any given visit are usually gone before a request about them could arrive.
A contact form message is easy to find and easy to delete, so a request about one is straightforward. Ask, and it goes.
You can also complain to the data protection authority in the country you live in if you think your data has been handled badly here. That right exists whatever I say on this page.
The site is not aimed at children. There is nothing to sign up for, so no information is asked of anybody, of any age. Children who read an article appear in the server log the same way every other visitor does and in no other way.
When something changes in what the site actually does, this page is updated and the date at the top changes with it. The likeliest change is advertising, which has its own section above so that you can see in advance what it would mean.
If anything on this page turns out to be wrong about the site as it is running today, that is a fault worth reporting. Tell me through the contact form and it will be fixed.