Jujutsu Zero Wiki is designed to work without accounts, profiles, comments, or direct purchases. The site does not intentionally collect names, email addresses, payment information, or Roblox account details.
This policy reflects the site as built on August 21, 2026, including consent-gated Google Analytics, route-scoped Google AdSense loading, and the advertising-cookie disclosures below. If forms, additional advertising vendors, or other data-collecting features are added later, this page will be updated to describe their actual behavior.
Data the server may process
Like most websites, the hosting and network providers may process limited request information needed to deliver pages securely. That can include an IP address, browser and device details, requested URL, time of request, and security signals used to detect abuse.
This technical processing is handled by the infrastructure providers under their own terms. The site does not use that information to build player profiles.
Analytics and cookies
The site offers optional Google Analytics 4 with measurement ID G-DGLTDPQT7F to understand aggregate traffic and improve its guides. The analytics tag loads only after you choose Accept analytics. If accepted, Google Analytics may process page URLs, referring pages, browser and device details, approximate location derived from network information, and consent-gated interaction events such as guide navigation, table-of-contents use, language changes, source checks, official-link exits, and Play on Roblox clicks. These events use controlled labels rather than names, account details, free text, full destination URLs, or search queries.
Declining analytics leaves the tag unloaded and the guide content fully available. You can change the choice later through the Privacy choices control; declining after a previous acceptance removes accessible Google Analytics cookies and refreshes the page to stop the loaded tag. Separately, the theme preference and analytics choice are stored locally so the browser can remember them.
Advertising and Google AdSense
The site publishes an ads.txt seller record and a google-adsense-account meta tag for Google AdSense publisher ca-pub-1605610071220494. The external AdSense loader is restricted to site-designated, indexable content routes and is excluded from legal pages, the About page, search-held research notes, 404 responses, and the dedicated error route. Client rendering failures redirect to that clean error route so an advertising runtime is not carried onto the error screen. This configuration does not claim that Google has approved the site or that every visit receives an advertisement.
Third-party vendors, including Google, use cookies to serve ads based on a visitor's prior visits to this website or other websites. Google's use of advertising cookies enables Google and its partners to serve ads based on visits to this site and other sites on the internet. Depending on region, consent, account settings, and the ad request, Google may serve personalized or non-personalized advertising.
The AdSense loader and advertising-cookie processing are separate from the optional Google Analytics choice on this site. That analytics choice does not grant advertising consent. Where regional law or Google policy requires consent, the publisher must enable a Google-certified consent management platform in AdSense so the required advertising choices are collected before personalized advertising is enabled. That account-level setting must be verified separately from this site's source code.
Depending on the publisher's AdSense account settings and the ad request, Google-certified third-party vendors and ad networks may also serve or measure ads. Visitors can use Google Ads Settings to opt out of personalized advertising from Google and can use participating third-party vendors' own controls or the YourAdChoices opt-out page. The codebase alone cannot prove which account-level vendors are active; Google's certified ad-network information and the publisher's AdSense settings determine the available vendors.
Google and approved advertising vendors may process an IP address, page URL and referrer, browser and device information, security signals, advertising identifiers, and cookies or similar technologies for delivery, frequency control, measurement, and fraud prevention. The guide content remains usable if a visitor or browser blocks the advertising script.
- Google Ads Settings ↗Manage or opt out of personalized advertising from Google.
- Google-certified ad networks ↗Review Google's information about third-party ad networks that may participate in AdSense.
- YourAdChoices opt-out ↗Review or opt out of interest-based advertising from participating companies.
External services
Links to Roblox, Discord, YouTube, and Reddit leave this site. Google Analytics and Google AdSense are also operated by Google. Those services may collect data under their own privacy policies, and this site does not control their cookies, login flows, or retention practices.
Opening an external link is optional. The guide content remains readable without signing in to those services.
Retention and security
The site does not maintain a user database. Infrastructure logs, if retained by the hosting provider, are governed by that provider's operational and security settings.
No internet service can promise perfect security. The site minimizes risk by avoiding unnecessary personal-data collection and by keeping credentials out of the public codebase.
Your choices
You can accept or decline analytics when the preference notice appears and revisit that choice through the Privacy choices control. That control applies to Google Analytics, not the separate AdSense ownership script. You can also block third-party scripts, clear saved preferences through your browser's site-data controls, or decline to open any external service linked from the site.
Because the current site has no accounts or submission forms, there is normally no user profile here to access, correct, or delete.
Policy changes
Material changes will be reflected on this page with a revised review date. A new data-collecting feature should not be treated as covered by vague future language; its actual behavior must be documented when it ships.