Privacy, in plain language.

Website statistics

We count public page views, editor starts and installation checklists checked off. These are daily totals, grouped by page and screen size. They are not unique visitor counts. Analytics do not store your IP address, identity, referrer, search terms or anything you type into a form. We do not use tracking cookies or send these statistics to an advertising service.

Do Not Track and Global Privacy Control opt out of these counts. Administrators are also excluded. Aggregate counts are retained to compare trends over time.

Your account and contributions

GitHub sign-in is optional and only needed for contributions. We store your GitHub account ID, username and profile name to associate submissions with you. The website uses a session cookie for sign-in and a security cookie to protect forms. Approved contributions display your username and the text you submitted publicly; pending and rejected contributions are visible to you and administrators.

Do not include passwords, API keys, access tokens or private firmware files in feedback. A GitHub issue draft is only published if you submit it on GitHub.

Optional feedback from the add-on

If you choose to share how your screen works, we store your answer, model, selected problem categories and any versions, usage hours or comment you explicitly share. A random key per board lets the add-on update or delete the same answer; only a hash of this key is stored here. No account is required.

Individual feedback stays private to administrators. If you explicitly agree, your latest answer also contributes to public totals of positive experiences and experiences with problems for that model. Comments, versions, usage hours and individual records are not published. Existing private answers are not included without new permission. These totals are separate from reviewed public installation reports. You can withdraw permission or delete your answer through the add-on integration.

We do not request device names, hardware addresses, Home Assistant entities, configuration or logs. Do not include personal information or secrets in a comment. Feedback remains until removed; the add-on integration can delete it using the same board key. Keep that key to retain control of your answer. Losing it means we cannot identify your anonymous answer from your GitHub account.

Maintainer email alerts

New contributions, user replies and meaningful add-on feedback updates trigger a private maintainer notification through Resend. These emails contain the feedback category, screen model and a link requiring sign-in. Submitted text, account details and technical context are not included in these emails.

Hosting and your devices

Normal hosting and security logs may include IP addresses and request details; these are separate from the aggregate analytics dashboard. This website does not connect to your Home Assistant instance or automatically collect telemetry from your screens.

Questions or deletion requests

Sign in and submit a contribution asking the maintainer to remove your account or reports. Include no sensitive details. You can read the maintainer's response on your contributions page.