Privacy at Hangry UI
How this documentation site uses browser storage, analytics, session replay, and external services.
Browsing the documentation
Hangry UI is a public documentation and preview site. You can browse its components, blocks, and shaders without creating a Hangry UI account. Your browser makes requests to the site and its hosting infrastructure to load pages, fonts, images, and scripts. Those requests expose technical information such as the requested URL, IP address, and browser headers to the infrastructure serving them. This notice describes the site's implementation; third-party services have separate privacy policies.
Analytics and session replay
When analytics is configured, the site uses PostHog for page views, interface interactions, errors, performance measurements, and session replay. The current implementation initializes analytics unless a rejection is stored. Choosing Reject analytics opts out of subsequent client-side capture. Choosing Accept analytics enables it, and dismissing the analytics notice currently records acceptance. Replay masks input fields, blocks hidden and file inputs, and masks elements marked as sensitive. Request headers, request bodies, and console-log recording are disabled in replay configuration. Do not enter confidential information into public component demos.
Browser storage and preferences
The site stores the analytics choice in local storage under hangry-ui-analytics-consent and remembers the documentation sidebar preference in local storage. PostHog may also use browser persistence when enabled. You can remove these stored values through your browser's site-data settings; clearing them resets the saved choice and may display the analytics notice again. A rejection applies to client-side analytics and does not disable ordinary hosting requests or server-side operational logging.
External links and project contact
GitHub, X, sponsorship, and Ask AI links take you to external services. Ask AI links include a prepared question about the public Hangry UI website in the destination URL; using those links shares that question with the selected service. Review that service's privacy practices before using it. Messages you send through email or public GitHub issues are handled by those providers. For questions about this site or a privacy concern, contact ui@razzev.com. Avoid including sensitive personal data in public issues.