tesseraWebsite 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.
The wishlist and community discussions
Wishlist submissions and community discussions publish your GitHub username and request immediately. Votes are linked to your account to allow one vote per wish. Vote totals are public; voter lists are not. You can remove your vote. Imported wishes credit the original GitHub author and link to the original discussion.
Comments on wishes and community discussions are public, including your GitHub username and any pictures you include. You can edit or remove your own comments. Administrators can remove comments. Removed comments are no longer shown publicly. Uploaded pictures have public URLs, including while they are in a draft; removing a comment does not delete its image files.
Your email and notifications
When you sign in, we request your verified primary GitHub email and store it privately with your account. It is never shown on public profiles, wishes or comments. Existing members can reconnect GitHub from their account to enable email updates. We do not store your GitHub access token.
We email you about new replies in conversations you started or joined, private replies to your reports, and important status or maintainer updates. Wishlist updates also go to people who voted for the wish. Review decisions on your reports and manual edits are included. Your own actions do not trigger an email to you, and importing past GitHub conversations does not send historical notifications.
You can turn reply emails and update emails off separately in your account, or use the unsubscribe link in an email. These preferences do not affect updates on the website. We send these emails through Resend, which receives your email address and the notification content: a conversation title, the type of update and a link. We do not include comment bodies or attachments, and we do not send marketing emails.
Changes to the manual
When you send a change to the manual, we store the page text, your one-line summary and any pictures you upload, and send them to the manual's repository on GitHub as a proposed change with your GitHub username as co-author. Nothing is published until a maintainer approves it. Approved text and pictures become part of the public manual.
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. Shared answers, including previously submitted answers, contribute to anonymous public totals of positive experiences and experiences with problems for that model, unless excluded by a moderator. Only your latest answer counts. Comments, versions, usage hours and individual records are not published. These totals are separate from reviewed public installation reports. You can delete your answer through the add-on integration to remove it from the totals.
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.
Troubleshooting reports from the add-on
When a screen does not work right, the Tessera app can send a troubleshooting report, only when you ask it to and after you have read what is in it. The report is a zip with the screen's redacted configuration, its log, the related lines of the Home Assistant log, the add-on's log and the last build log, with a summary of the board, the versions and the last crash. The add-on removes passwords, keys, network names, addresses and coordinates before anything leaves your home, and you can read every file first. A note and an email address are optional: leave an address only if you want us to reply. Each report gets a reference you can quote on GitHub or Discord.
Reports are private to administrators, stored on the website's own server and deleted automatically after thirty days, together with the address and the note. They are not published and are not used for anything but understanding the problem. To have a report removed earlier, write to us with its reference.
Plugin likes, ratings and counts from the add-on
When you like a plugin in the add-on's plugin store, we store which plugin you liked, when, and a hash of a random key that belongs to that one installation of the add-on. The key itself is not stored here. No account is required. You can like any plugin, also one you do not run.
When you rate a plugin you run, we store the stars, the plugin's version and the model of the screen it runs on, with the same hashed key. When you agree to be counted, the add-on says once a day, and when you add or remove a plugin, which plugins your screens run: each plugin's name and version and the screen models. Counting is off until you turn it on.
To keep one home from filling a plugin's numbers, a new like, rating or count also stores a keyed hash of the network it came from: it is made from the address with a secret that changes every month, so it cannot be turned back into the address, and it is deleted after 30 days. The address itself is not stored.
Only the numbers per plugin are published: likes, the average rating from three ratings, and the number of homes that run it of those who agreed to be counted, also per screen model. The maker of a plugin, signed in with GitHub, also sees which of its versions those homes run. Individual likes, ratings and counts are not published. Unlike or delete your rating in the add-on, or turn counting off, to remove them. Nothing about your Home Assistant, your entities or the names of your screens is sent.
Maintainer email alerts
New contributions, wishlist requests, community discussions, replies, comment edits and removals, moderation updates, changes to the manual and meaningful add-on feedback updates trigger a private maintainer notification through Resend. These maintainer alerts are separate from personal email preferences and also cover administrative actions. These emails contain the feedback category, the screen model or the manual page, 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.