CURRENT WEBSITE PRACTICES · LAST REVIEWED NOVEMBER 2026
Direct downloads, no signup.
The Silver website does not collect names or email addresses for downloads and has no account, signup, or waitlist flow. The website links directly to the published GitHub release; GitHub handles the file request under its own policies. The site uses no analytics or third-party cookies. Its hosting provider may process ordinary website request logs under its own policy. No download authorization database is used by this website.
Reports are processed locally.
Silver reads report and log files from folders selected by the user and writes generated reports in the project/build folder. The inspected desktop source has no account system, hosted cloud-analysis service, telemetry, or automatic AI-provider call.
Optional redaction can remove the configured user name, host name, and folder paths from supported output. Redaction does not anonymize a design: project identifiers, hierarchy, signal names, constraints, timing/resource details, or other sensitive content may remain. Review generated files before sharing.
Sharing requires your action.
- An AI provider receives content only when you choose to paste or upload it to that provider. The provider’s own data settings and policies apply.
- Optional ntfy notifications may send stage and result text. Keep the configured notification topic private and verify the notification settings before enabling them.
- GitHub hosts the source repository and published Windows release. GitHub handles downloads under its own policies.
Retention and contact.
Generated files remain in folders chosen by the user and can be deleted with normal file tools. The website does not maintain download authorization records or collect visitor contact details. Website request logs may be processed and retained by the hosting provider under its own policy. For privacy or security questions, contact bvsrvaibhav@gmail.com.
This page describes current practices; it is not legal advice.