Information processed
2PVP does not create server-side user accounts, accept public comments, or store sensitivity and crosshair inputs on the server. My 2PVP uses browser storage for saved items, reminders, picks, recent pages and the local player card. The hosting provider may process standard request logs such as IP address, requested URL, timestamp, user agent, response status, and security events. These logs support delivery, abuse prevention, and diagnostics.
Search queries are sent to the 2PVP server as part of the URL and are used to return local results. Do not enter personal or sensitive information into search.
Analytics, advertising, and cookies
2PVP offers a privacy choice before optional Google Analytics, Google AdSense, or Google Programmable Search scripts load. Choosing Essential only keeps those optional scripts disabled while core pages, filters, native search, and browser-based tools remain available. You can reopen Privacy choices from the footer.
If you accept optional services, Google and its partners may process device information, page activity, search queries, advertising identifiers, and cookies according to their policies. Google results can include clearly labeled sponsored listings. The site requests IP anonymization for analytics and does not require an account to browse. Browser controls can also remove or block stored choices.
Personal dashboard, reminders, and location
My 2PVP stores the local player card, favorites, recent pages, match reminders, picks, and saved tool fields in browser storage on the current device. The dashboard includes export, import, and clear controls. Match notifications are requested only after the visitor chooses a reminder and can be managed in browser settings.
The Gaming Places page requests browser location only after the visitor taps Use my location. City or ZIP searches and coordinates are sent to the 2PVP server to locate publicly mapped U.S. gaming places, then cached for reliability.
External services and images
The 2PVP server requests esports, place, and status records from configured services. Visitors do not receive private credentials. External images supplied with a current record may be loaded from that HTTPS host, which can receive normal request metadata such as IP address and user agent.
Links to broadcasts, organizers, publishers, maps, and documentation open external sites governed by their own privacy terms.
Retention and security
API cache files are retained only as needed for performance and resilience, then replaced. Server-log retention depends on the hosting configuration and should be limited to the period needed for operations, security, and legal requirements.
Security headers, server-side token storage, input limits, output escaping, path validation, and denied access to cache and application directories reduce risk. No internet service can guarantee absolute security.
Choices and contact
You can use the footer’s Privacy choices control or browser settings to block nonessential storage, disable JavaScript, or prevent remote images; core editorial pages remain readable. Privacy or deletion requests should be sent to dastanayhan@gmail.com. Because My 2PVP data stays on the visitor’s device, 2PVP normally cannot retrieve or delete that local profile from the server; the dashboard includes export and clear controls.
This policy is written for a US-first product and should be reviewed by qualified counsel before materially expanding accounts, payments, newsletters, personalized advertising, or user-generated content.