Every tagged release publishes:
Delay-Setup-<version>.exe— the Windows installerSHA256SUMS.txt— SHA-256 of every published artifactlatest.yml— electron-updater manifest (also SHA-512 hashed)
Before running the installer, verify the hash matches:
# Compare this hash against the line for the same filename in SHA256SUMS.txt
Get-FileHash .\Delay-Setup-1.4.0.exe -Algorithm SHA256If the hashes do not match, do not run the installer — re-download from the official releases page.
Delay is not yet signed with a paid EV code-signing certificate, so Windows SmartScreen flags the installer on first launch (this is normal for every unsigned app — including most open-source tools).
You can confirm the installer is the one this repo built by:
- Matching the SHA-256 hash above.
- Reviewing the build that produced it — every release is built in a public GitHub Actions run you can audit at Actions.
Code-signing via SignPath Foundation (free for qualifying OSS projects) is being pursued. Until that lands, use More info → Run anyway on the SmartScreen dialog.
Delay is local-first and does not phone home.
- All notes, tasks, events, AI conversations, and memories live in your browser's IndexedDB inside the installed app.
- The only outbound network traffic:
- Update checks to
github.com/AzizX-coder/Delay/releases(electron-updater) - AI requests to whichever Ollama endpoint you configure (by default
http://localhost:11434) - Optional
searchWebtool calls toapi.duckduckgo.comwhen explicitly triggered by the agent
- Update checks to
No analytics SDK, no account system, no third-party trackers.
Please email security reports to the address in the repo's GitHub profile rather than opening a public issue. Include:
- A description of the vulnerability
- Steps to reproduce
- The affected version(s)
You'll get an acknowledgement within 7 days.