Data practices
Privacy at megawatt.fun
megawatt.fun is a public, read-only energy site with no accounts, payments, advertising, analytics scripts, newsletter form, or first-party tracking cookies.
Data you provide
No personal-data forms on this site
megawatt.fun does not ask visitors to create an account, enter an email address, submit payment details, or complete a contact form. The interactive controls on the live-price and Kardashev pages change values in the visitor’s browser and do not ask for personal information.
Hosting
Request data processed by Vercel
Vercel hosts megawatt.fun and processes requests needed to deliver its pages and serverless function. As with ordinary web hosting, request metadata such as an IP address, user agent, requested URL, referrer, status, and timing may be processed in infrastructure and security logs under Vercel’s own terms and privacy practices.
The site’s initial public response sets no cookies, and the project does not include third-party analytics, advertising pixels, session replay, or chat trackers. If those practices change, this page and the public source should be updated to describe the change.
Live prices
How the ERCOT feed is retrieved
The live-price page requests the same-origin /api/prices function, which retrieves ERCOT’s public system-wide price feed and caches the result briefly at the edge. The function does not accept visitor-entered data, and its upstream request identifies megawatt.fun rather than forwarding a visitor identity to ERCOT.
External services
Links leave megawatt.fun
Pages link to GitHub, ERCOT, skill.supply, and cited research sources. Following an external link sends a request to that service, which can receive standard request information and applies its own privacy policy. Contact is offered through GitHub, so information posted there is handled by GitHub and may be public.
Questions and changes
A public revision trail
Privacy questions or corrections can be raised through the project’s published GitHub contact path. This policy is stored with the site in the public repository, so material revisions remain visible in the repository history.