Privacy at DEAFCS Widget
What DEAFCS Widget receives, what website analytics are used, and what the widget does not collect.
What the widget uses
The widget uses public DEAFCS profile and CS2 statistics to render the layout selected in the builder. The service may receive a DEAFCS nickname or player ID and the selected widget configuration so it can display the requested public statistics in the browser source.
DEAFCS Widget does not ask for a DEAFCS password, OAuth token, private account permission, or payment details. It does not modify a DEAFCS profile. Do not put secrets or private information in a widget URL, GitHub issue, or feedback message.
Website analytics
The public website uses Vercel Web Analytics to measure aggregate traffic and understand which pages and referral links are useful. It counts page views without cookies and does not identify individual visitors. The /widget/ browser-source route is excluded so an OBS source does not look like a new website visit.
Technical data
Hosting and security providers may process limited technical request data needed to deliver and protect the site. This project does not use that information to build profiles of players or identify people. It does not contain a DEAFCS password or account access token.
Questions and requests
This is an independent open-source project and is not affiliated with DEAFCS. For questions about the site or a request to correct project content, use the GitHub repository. DEAFCS account and platform requests should go to DEAFCS support. See the contact page for issue templates and the information that helps reproduce a widget problem.