Privacy policy

Information collected

The site may receive standard request data such as an IP address, browser type, device type, referring page and requested URL. Hosting and security providers use this information to deliver pages, diagnose failures and protect the site from abusive traffic. We do not ask visitors to create an account, and the guide does not sell in-game items or collect Roblox credentials.

Aggregated measurement may be used to understand which guides are useful and which pages need improvement. Measurement data is not presented as a personal player profile.

• Do not enter a Roblox password on any page linked from this guide unless the domain is an official Roblox domain.
• External services apply their own privacy policies when you leave this site.
• Contact details are not requested for ordinary reading.

Cookies, Google AdSense and measurement

The site may use cookies or similar storage for measurement, preferences and advertising. Google AdSense and its advertising partners may use cookies to serve, limit and measure ads. Those systems may process device or browser information under Google's own policies.

Advertising and hosting systems may also evaluate requests to prevent invalid traffic, automated abuse and fraudulent ad interactions. This protection is necessary for reliable service and does not change the editorial answers on the site.

Third-party vendors, including Google, use cookies to serve ads based on a user's visits to this site and other sites. You can manage those settings at https://adssettings.google.com and https://www.aboutads.info.

Your controls

You can block or delete cookies in your browser settings. Google also provides advertising settings that let you manage personalized advertising. Blocking some storage may affect preference remembering, but the written guides remain available without an account.

Google describes how it uses advertising data in its How Google uses information from sites or apps that use our services page and privacy policy. You can manage personalized ads in Google Ads Settings and learn more at aboutads.info. The domain lists Google as an authorized seller in ads.txt. We do not pass a Roblox username, password, or other account secret into an ad request, Our only contact address is the one on the Contact page.

This policy may be updated when the site's providers or operating needs change. The current version is dated October 15, 2026.

Expanded retention & requests

Email threads for corrections/privacy are kept as needed to finish the request, then deletable where feasible. CDN logs follow provider windows. We do not ask for Roblox passwords. Children: general-audience guide; parents may request deletion of threads containing a child’s personal data.

Ads & cookies

When AdSense inventory is allowed, Google may process data under its policies. Browser controls remain available. Details on monetization boundaries: Advertising disclosure.

International delivery

CDN may handle requests in multiple regions as ordinary hosting. Contact hello@ttktesting.com with subject Privacy.

October 25, 2026 — vendor, consent, children, and rights

This section was added on October 25, 2026. It itemizes the scripts this host actually loads, the consent defaults those scripts set, and the requests a reader can send. The October 15, 2026 paragraphs above stay in place. Where a sentence below is more specific, it adds detail. It does not quietly replace the earlier date. The operator of this independent guide is reachable at hello@ttktesting.com. Use the subject line Privacy. The site is www.ttktesting.com. It is a fan publication about the Roblox experience TTK Testing. It is not Roblox Corporation, and it is not Sable Digital or the people who build that experience.

What this site is, and what it does not run

Reading a guide does not create an account. There is no username, no password field, no Roblox login, no comment box, no newsletter form, and no store. We do not ask for a Roblox username, a birthday, a phone number, a postal address, or a payment card. Do not send those. If a message arrives with a password, a .ROBLOSECURITY cookie, or a backup code, the useful act is to rotate that secret on Roblox. Then mail us so we can delete the mailbox copy we control. We do not want the secret, and we will not use it to enter a game account.

The personal information a visitor ordinarily gives us is the content of an email that the visitor chooses to send. Everything else in this section is technical data that arrives because a browser requested a page, because the host logged that request, or because Google's advertising and measurement scripts ran in the page. We do not combine those streams into a player profile, a skill ranking, or a list of Roblox accounts.

Google AdSense, item by item

Pages on this host load Google AdSense from pagead2.googlesyndication.com. The client id in the script tag is ca-pub-7189405305305848. The same publisher id is the one named in ads.txt, where google.com is listed as a DIRECT seller. That file is how a buyer can see that Google is an authorized seller of inventory on this host. We do not list other ad sellers in that file.

AdSense is there to serve ads, to cap how often a creative is shown, to measure whether an ad was requested, and to help Google detect invalid traffic. Those are Google's purposes for the tag. Editorial sentences on the guides are not written to match an advertiser, and an advertiser does not get to insert a weapon rank, a code string, or a map name. The boundary is restated on the advertising disclosure.

Personalized advertising. When ad personalization is allowed, Google may select an ad using this browser's visits to this site and to other sites that use Google advertising services. That is the ordinary meaning of a personalized ad. When ad personalization is not allowed, Google may still serve an ad that is not tailored that way, subject to Google's own rules. This site does not run a second ad server that builds its own interest profile.

DoubleClick. Google's ad serving uses cookies associated with DoubleClick, Google's advertising cookie domain, to help with ad selection, frequency, and measurement. We do not operate a separate DoubleClick account dashboard for readers, and we do not publish a private cookie name that we invented. The cookies are set by Google when the AdSense tag runs. Google describes that advertising technology in its own policies, including the advertising technologies page and the partner-sites page.

Third-party vendors. Google states that Google and other vendors may use cookies to serve ads based on visits to this site and other sites. The vendor we load by name in the page source is Google. We do not add a Facebook pixel, a separate marketing-automation tag, or another named ad network in the templates. If Google's own auction calls additional vendors under Google's policies, those vendors are Google's partners, and their notices are Google's. We do not pretend to publish an exhaustive live list of every partner in an auction we do not operate.

IP address. A request for a page, a script, or an ad can include the IP address the browser used. The host and its delivery network use the IP to return the page, to diagnose failures, and to resist abusive traffic. Google's ad and measurement tags can also receive an IP as part of the request those tags make. We do not copy IP addresses into a visitor account, because there is no visitor account. We do not publish a reader-by-reader location. An IP can imply a coarse region. That is a property of the network request, not a profile we sell.

Device identifiers. The advertising script may store or read an identifier so that the same browser can be recognized from one page view to the next. That identifier is a device or browser signal in Google's advertising system. We do not collect a mobile advertising identifier into a database of our own. This publication is a website. It is not a mobile app, and it does not ask a phone operating system for an advertising id. Browser storage that Google sets can be cleared in the browser.

Web beacons. Ad and measurement tags can use a small request, sometimes called a web beacon or a pixel, to record that a page or an ad creative was fetched. A beacon is a technical request. It is not an article, and it is not a screenshot of the game. We do not use beacons to recommend loadouts, to score players, or to decide which sentence is true. Truth on this site is a sourced sentence with a date, which is an editorial rule, not an advertising signal.

The categories below are the ones this host is in a position to describe. Durations for Google's own cookies are Google's. This page does not add a second clock, and it does not invent a day count for a cookie we do not control.

Google Analytics 4

Pages also load Google's tag from googletagmanager.com with the measurement id G-027306W3KH. That is Google Analytics 4. We use it to see, in aggregate, which guides are opened and whether a template is failing in an obvious way. We do not use it to publish a leaderboard, a weapon tier, or a list of Roblox usernames. The tag can process browser and device signals, including the page address and a client identifier stored in a cookie, under Google's analytics terms.

We do not turn analytics into a customer list. There is nothing to buy on this host, and there is no logged-in player to attach the hit to. If you block the analytics tag, the written guide still loads. A missing measurement hit does not change the Active codes result, the control list, or any other sourced sentence.

IP handling inside GA4 is Google's product behavior. This policy does not republish a numeric retention setting for Google's property, because that number would be a claim about Google's console rather than a switch we document here. Readers who want Google's current description should read Google's own analytics and privacy pages.

Consent Mode v2, and the EEA, UK, and Switzerland default

The analytics tag on each page issues Google consent defaults before it sends a hit. Four storage signals are set: ad_storage, ad_user_data, ad_personalization, and analytics_storage. For the region list in the tag, which covers the European Economic Area, the United Kingdom, and Switzerland, the default command sets all four signals to denied. A second default command sets all four signals to granted for browsers that are outside that region list. That pair of defaults is Consent Mode v2 as this static template implements it.

The denied default is the starting state for those regions. It is not a banner we then flip. This host does not load a separate consent-management vendor, and it does not run a popup that later calls a consent update. A reader in the denied regions therefore keeps the denied default. A reader outside those regions receives the granted default. Browser settings still sit on top of either default. Blocking third-party cookies, or blocking the Google scripts, still works, and it does not require an account on this site.

We describe the default this way so a reader in the EEA, the UK, or Switzerland can see that the tag is not written to assume permission. We do not describe a choice screen that the HTML does not contain. If a later template adds a real update to those four signals, this section will gain a dated paragraph that says so. Until that paragraph exists, the source of truth is the denied default for those regions and the granted default elsewhere.

Google's explanation of consent mode is on Google's tag documentation. Our sentence is narrower: it describes only the defaults present in this site's template on October 25, 2026.

How to opt out of personalized advertising

You can turn off personalized ads in Google's own settings at adssettings.google.com. That page is Google's. It applies to the Google account you are signed in with, and Google explains the scope there. You can also use the industry opt-out page at aboutads.info, which explains how participating companies treat browser opt-out cookies. Those two addresses are the opt-out paths this policy points to. We do not operate a third opt-out form that would ask you for more personal data in order to stop an ad.

You can also block or delete cookies in the browser, block third-party cookies, or use the browser's tracking controls. After you do that, pages on this host should still be readable. A blocked cookie can mean we cannot remember a purely technical preference, if a future page ever stores one. It does not lock the guides. It does not change a fact we have already published.

Opting out of personalized ads is not the same thing as opting out of every ad request. Google may still serve an ad that is not personalized, or it may serve nothing, depending on Google's systems and on whether the consent default allowed storage. This site does not promise a particular ad layout, and it does not promise that an opt-out produces a blank column. The guides are the product. The ads are optional inventory around them.

Children, Roblox's audience, and COPPA

TTK Testing is a Roblox experience. People who play Roblox include children under 13. A child can find this guide the same way an adult can, by searching for the game. That fact shapes what we collect. It does not turn this text site into the game, and it does not let us see who is playing.

This website is a general-audience guide. It is not directed at children under 13 as a service that collects personal information. We do not ask anyone under 13, or anyone else, to make an account. We do not collect Roblox accounts. We do not collect a parent's email as a condition of reading. We do not run a club, a chat, or a contest that asks a child to submit a name. The pages are static HTML. A child can read them without telling us who they are.

We do not knowingly collect personal information from children under 13. The only way personal information reaches our mailbox is if someone sends it. If you are a parent or guardian and you believe a child sent personal information to hello@ttktesting.com, write to that same address with the subject Privacy and ask us to delete the thread. Say enough for us to find the message, such as the approximate date and the sender address. We will delete the copy we still control in the mailbox. We cannot delete a message that lives only in someone else's sent folder. We cannot delete anything inside Roblox, because we never receive Roblox account data.

We do not add an age gate that asks for a date of birth. A date of birth would be additional personal data. Refusing to collect it is the smaller footprint. Advertising on a site that children may visit is also covered by Google's program rules for AdSense. We do not design ad slots to look like a Roblox join button. That layout rule is restated on the advertising disclosure. It exists so a younger reader is less likely to confuse an ad with the game.

Data retention

Email is kept while we need it to finish the request you sent, and as a basic record that a privacy or abuse thread was handled. When the thread is no longer needed, it can be deleted. We do not publish a fixed number of days for that mailbox, because ordinary email is not a retention clock we invented for this policy. If you want a thread deleted, ask. Best effort is the standard, and it is the same standard the contact page uses. We will not answer a privacy request with a promise of a specific hour or a specific day count.

Host and CDN logs follow the provider's window. They exist so the site can be delivered and so abusive traffic can be investigated. We do not copy those logs into a private archive with a clock of our own. We also do not use them to identify a Roblox player.

AdSense and GA4 records are kept by Google under Google's settings. This policy does not invent a parallel number for Google's retention. If you want Google's current period, read Google's policy. If you ask us to delete data, we delete the email we have. We will say plainly when a log line sits with the host, or when an advertising record sits with Google, and is outside the mailbox.

We do not sell email contents. We do not trade them as leads. A legal demand is answered to the extent the law requires. A demand for a Roblox password is refused, because we do not have passwords and we will not ask a reader to provide one.

Your rights under the GDPR and the CCPA

If the GDPR or the UK GDPR applies to you, you can ask us for the mailbox information we hold that is tied to your email, ask us to correct it, ask us to erase it, ask us to restrict it, and object to our using a thread for anything beyond keeping a record of the request. Portability, for this site, means we can send you back the text of an email you sent. We do not hold a structured player database that could be exported as a file of game progress. You may also complain to a supervisory authority in your country. We do not name a single authority here, because readers write from many countries, and we are not appointing one office by guessing.

Those rights apply to the personal data we actually hold. For almost every reader, that is either nothing, or one email thread. Server logs and Google's tags are described above so you know they exist. A request to us reaches the mailbox. A request about Google's cookies is handled in Google's settings and in your browser, which is why the opt-out links are part of this policy.

If the CCPA, the CPRA, or a similar US state privacy law applies to you, you may ask what categories we collect, ask us to delete the email we hold, and ask us to correct that email. The categories are: identifiers you choose to put in an email, and internet activity in the form of standard request logs plus the advertising and analytics data Google processes when those tags run. We do not sell personal information for money. We do not run our own program that shares a customer list for cross-context behavioral advertising. Google's ad tag may process data for personalized ads when the consent default is granted. That processing is Google's, and the opt-out paths are adssettings.google.com and aboutads.info.

We will not hide the guides because you opted out of personalized ads or because you wrote to us. The pages are public. We do not offer a paid tier that changes the code list or the weapon pages. We do not ask for a government id, a precise GPS fix, or a card number in order to honor a request. An email from the address you used is enough for us to look for a thread. We do not publish a separate portal for authorized agents. A person can write for themselves.

We handle these requests on a best-effort basis. This policy does not promise that a reply will arrive within a stated number of days. If we cannot find a thread, we will say that. If the data you care about sits with Google or with the host rather than in our mailbox, we will say that too, and we will point back to the controls in this section.

Contact, related pages, and the date of this text

Privacy mail goes to hello@ttktesting.com with the subject Privacy. Say what you want done, and include any URL on www.ttktesting.com that the request is about. Do not include a Roblox password. Account recovery, bans, and refunds are not privacy requests we can perform. Those belong to Roblox or to the experience creators, and the official links page is the place we send readers for the real game identity.

Related reading on this host: the terms of use, the advertising disclosure, and the contact page. The terms explain what the guide is allowed to be used for. The advertising page explains the publisher id and the editorial firewall. The contact page explains which subjects the inbox will take.

This vendor, consent, children, and rights section is dated October 25, 2026. The current policy is the October 15, 2026 text together with this section. If a script, a publisher id, or a consent default changes, the change will be a new dated section, not a silent edit to this one.