LOCAL-FIRST.
BOUNDARIES SHOWN.

What the tools save

The site uses browser local storage for saved gameplans, slider presets, and game-log entries. These records can include labels, game results, notes, platform, build, mode, and settings that you enter.

The current client code contains no application API or cloud database path that uploads those saved records. It may also create short-lived local write-lock records while coordinating saves between tabs. Other people who can use the same browser profile may be able to view local records.

Share links leave the tool

Gameplan and Slider share links encode selected values in the URL. Search terms also appear in URLs such as /search?q=…. A URL can be stored in browser history, copied to another person, included in a screenshot, or sent to the network that serves the page.

Do not place private information in a preset name, matchup label, build label, search query, or any value you plan to share. The site cannot retract a URL after someone else receives it.

Vercel serves the production build

Production pages are deployed on Vercel. Vercel necessarily receives the requested URL and network information needed to return a page, and may process request and diagnostic logs for delivery, reliability, abuse prevention, and support. This site does not maintain a separate application database of those requests. Vercel describes its processing and user choices in its Privacy Notice.

Cloudflare manages authoritative DNS for the domain. Depending on whether a web record is in proxied or DNS-only mode, Cloudflare may also handle a web request before it reaches Vercel. Cloudflare describes its service data practices in its Privacy Policy.

As checked August 8, 2026, Vercel documents one-hour Runtime Log retention for Hobby projects. Build logs and deployment records follow Vercel deployment retention; the Hobby plan documents deployment retention as unlimited by default. These plan terms can change. See Vercel’s Runtime Logs documentation and Hobby plan documentation.

Google Analytics measures site use

On the exact production host, Google Analytics 4 remains off until you choose “Allow analytics.” If allowed, the site loads measurement ID G-53GFTKJ5G5. Google Analytics can receive the page URL and title, referrer, approximate location, browser and device information, interactions, and diagnostic data. It may set or read Analytics cookies such as _ga.

An “Analytics choices” control remains available after either choice. You can use it to allow Analytics later or withdraw consent just as easily. Withdrawing sends an analytics_storage: denied update, disables the Google tag, and removes this site’s accessible _ga and _ga_* cookies. It does not erase information Google already processed. Your choice is stored only in this browser profile.

The GA4 property is configured to retain user-level and event-level data for 14 months, with user retention reset on new activity. Google notes that retention-setting changes can take up to 24 hours to apply and do not control most aggregated standard reports. See Google’s Data retention documentation.

Local game-log entries, slider presets, and saved gameplans are not intentionally sent to Analytics. Page URLs can still contain search terms or shared settings, so do not place private information in them. Google processes Analytics data under its Privacy Policy.

One isolated, consent-gated ad unit

The production HTML publishes the official google-adsense-account meta record, and the site serves a single ads.txt seller record. These are text-only ownership and publisher records. They do not execute code, contact an advertising endpoint by themselves, or display an ad.

The current application does not load adsbygoogle.js, include AdSense ad units, or enable an AdSense Auto ads loader. Its English homepage contains one clearly labeled Adsterra Native Banner slot. The Adsterra frame is not created until you choose “Allow sponsored ads” and the page completes a clean reload. Choosing “Keep ads off” leaves the slot disconnected. The separate choice is stored under madden27:advertising-consent:v3 in this browser profile. Older approvals are not carried forward; older denials remain denials.

If allowed, the advertising script runs in a credentialless sandboxed frame served from the separate madden27.vercel.app origin. Supported browsers give that frame a temporary, separate credentials and storage context; browsers without credentialless-frame support keep advertising off. Browser same-origin rules prevent the frame from reading madden27.wiki page content, cookies, Game Log, Slider, Gameplan, or other first-party storage. The sandbox may run scripts, and advertiser destinations may open in separate sandboxed windows subject to browser popup controls, but it grants no form, download, top-page navigation, or popup-escape permission. If the frame navigates itself, reports a delivery failure, or stops its site-managed heartbeat, the whole advertising frame is removed.

Opening “Advertising choices” immediately removes the isolated frame. Saving either choice after a frame has run reloads the page so the next document starts from that choice. Reloading cannot erase information already processed or delete cookies held by advertising partners; use browser site-data controls for those records.

If allowed, Adsterra and participating advertising partners may receive network and device information and process ad impressions, clicks, cookies, pixels, fraud-prevention signals, or interest-related advertising data. Adsterra describes advertising and marketing cookies in its Cookies Policy. The “Analytics choices” control remains limited to GA4 and does not grant advertising permission; Google advertising-storage signals remain denied.

YouTube loads only after play

The official video players use YouTube’s privacy-enhanced embed domain. An iframe is not created until you press a play control. Starting it connects your browser to YouTube, which can process the resulting request under Google’s policies.

If you prefer not to load the embedded player, do not press play; the rest of the guide remains usable.

Local media, deliberate exits

Site media is served from site-owned paths in the current build. Merely displaying that media does not contact an EA image host. Choosing an EA, YouTube, store, community, or other external link sends a request to that destination.

The destination controls its own content and data practices. Review its notice before providing information there.

How to remove your records

Use your browser’s site-data controls for madden27.wiki to remove local tool records. Private browsing modes may discard them automatically and can also block saves.

The Game Log can export JSON or CSV, and Slider Lab can export saved presets as JSON. Because the current build has no tool-data account or restore service, cleared records cannot be recovered by the application.

No public intake channel

The current application has no published mailbox, contact form, submission API, ticket system or automated receipt.

Do not send personal or sensitive information to an address found outside this site and assume it reaches the operator. The site cannot promise access, deletion, correction or a response time without a documented working channel and confirmed production responsibilities.

Current boundaries stay visible

Vercel hosting, the date-scoped Hobby log-retention facts, and the GA4 retention and consent configuration are identified above. The site offers no public operator intake workflow or response-time commitment.

The current code includes Google Analytics 4, production-only AdSense ownership records, and one English-homepage Adsterra Native Banner that remains off without a separate saved advertising choice. It includes no AdSense JavaScript, user account, application database, or upload path for local tool records. Read the Terms and operating notice for the matching use boundaries.