ProjectsApps
Apps, Rust
SecretSticky
Private, fast sticky-note workspace with a sleek dark UI. Capture thoughts without the cloud watching.
v0.2.0 released
Encrypted sticky notes for Windows — the feel of Sticky Notes, with secrets safe at rest.
Use it for API keys, passwords, recovery codes, and anything you would not trust to plain Sticky Notes or a synced notepad.
Local-only · Master password · Multi-window stickies · System tray
Why
Windows Sticky Notes is great for quick capture and terrible for secrets (plain local data, sync surface, no real vault). SecretSticky keeps the sticky UX and encrypts note titles and bodies on disk.
Features
| Area | Details |
|---|---|
| Vault | Master password unlock; optional recovery key (shown once at setup) |
| Crypto | Argon2id (64 MiB, t=3) + XChaCha20-Poly1305 AEAD |
| Keys | Stable content key — change password without re-encrypting notes or killing recovery |
| Notes | Multiple colored stickies (incl. black & dark green), per-note 📌 pin keeps a note on top (off by default), high-contrast ink |
| Tray | New note · Show manager · Open all · Lock · Quit |
| UX | Single instance (second launch focuses manager); close manager → tray; open a sticky → manager tucks away; every sticky has New note / Manager / Lock; Inter font (self-hosted) |
| Windows | Manager default 440×560; sticky min 345×250 (new notes 345×280) |
| Clipboard | Copy secrets with auto-clear (default 30s) |
| Idle | Auto-lock after inactivity — 15 min default, Off–12 h presets in the manager |
| Updates | Signed auto-update from GitHub Releases (About → Check for updates) |
| Language | Follows Windows on first launch (English if unsupported). Switch anytime from the unlock screen, recovery screen, or manager → Language. Saved in settings.json (not inside the vault) and applied immediately, including the tray menu |
| About | “Hi I'm Ahmi, hope this helps!” + profile / repo links |
Install
Prebuilt (recommended)
Download the latest Windows installer from
Releases
(NSIS .exe setup; MSI when available).
The NSIS installer creates Start Menu and Desktop shortcuts that use the sticky+lock icon (same mark as the taskbar and tray).
Installed builds can update themselves: About → Check for updates downloads the next signed release from GitHub and restarts the app.
From source
git clone https://github.com/AhmiDarrow/SecretSticky.git cd SecretSticky npm install npm run tauri:dev # development npm run tauri:build # release installers under src-tauri/target/release/bundle/
Requirements: Windows 10/11, Node 22+, Rust stable, WebView2.
Quick start
- Launch SecretSticky → create a master password (12+ characters).
- Save the recovery key offline (shown once). Lost password + lost recovery = permanent data loss.
- Pick a color → sticky opens. Type secrets. Save indicator confirms disk write.
- Close the manager with X → app stays in the tray. Tray → Quit to exit fully.
- Tray → Lock when you step away.
Data layout
%APPDATA%\SecretSticky\
vault.json # encrypted note blobs + KDF params (no plaintext titles/bodies)
vault.json.bak # last-known-good copy (restored if live is missing/corrupt)
settings.json # UI language only (not secrets). Unknown keys are kept
--home <dir> (or --home=<dir>) uses that folder instead of %APPDATA%\SecretSticky. SECRETSTICKY_HOME does the same when the flag is absent. The flag wins. Auto-update relaunches with the same arguments, so a custom home stays in use.
- Encrypted: note title, note body
- Plaintext by design: window geometry, color id, timestamps (so chrome can restore without unlock content)
Durable save path: write + flush temp → snapshot .bak → atomic replace into vault.json (Windows uses MoveFileExW replace-in-place — never delete-then-rename). A crash mid-write must not leave you with zero copies of secrets.
Updates must NEVER corrupt saved stickies
Non-negotiable product rule: installing or auto-updating SecretSticky only replaces the application. Your vault stays under %APPDATA%\SecretSticky\ and must remain unlockable with the same master password / recovery key after every update. App releases must not wipe notes, rewrite ciphertext incompatibly, or ship ACL/UI changes that leave stickies permanently unreadable. Full invariant: SECURITY.md.
Security model
Protects
- Vault file at rest (disk theft, backups, casual snooping)
- Authenticated encryption of note contents
- IPC least-privilege: a sticky window cannot list vault admin actions or read another note’s body (it may only create a sibling note or lock the vault)
Does not protect
- Malware / keyloggers while unlocked
- Screen capture of open stickies
- A compromised OS or attached debugger
There is no cloud, no account, and no backdoor.
See SECURITY.md for reporting vulnerabilities.
Development
npm install npm run tauri:dev # Tests npm test # TypeScript check + Vitest (UI helpers) npm run test:rust # Rust crypto / vault / ACL npm run test:all # both npm run build # Vite production bundle only
| Path | Role |
|---|---|
src/ |
React UI (unlock, manager, sticky windows) |
src-tauri/src/crypto.rs |
KDF + AEAD |
src-tauri/src/vault.rs |
On-disk format + session |
src-tauri/src/commands.rs |
Tauri IPC, windows, tray |
.github/workflows/ |
CI + tag release builds |
CI & releases
- CI (
.github/workflows/ci.yml) — on push/PR tomain: frontend tests + Vite build, Rust fmt + tests (Windows). - Release (
.github/workflows/release.yml) — on tagv*(or manual dispatch): test gate, then signed Tauri NSIS/MSI + updaterlatest.json, draft GitHub Release.
# Bump every version surface from one command (no hardcoded versions anywhere else) npm run bump:version -- <X.Y.Z> # Update CHANGELOG.md, commit to main, then tag and let the Release workflow build: git tag v<X.Y.Z> git push origin v<X.Y.Z>
Requires repo secret TAURI_SIGNING_PRIVATE_KEY (see CONTRIBUTING).
Stack
- Tauri 2 + React 19 + TypeScript + Vite
- Rust:
argon2,chacha20poly1305,zeroize,serde - Updates:
tauri-plugin-updater+tauri-plugin-process(signed GitHub Releases)
Auto-update
Release builds ship with the Tauri updater plugin:
- CI signs NSIS/MSI updater artifacts with a minisign key (
TAURI_SIGNING_PRIVATE_KEYrepo secret). - Each release publishes
latest.jsonnext to the installers. - The app polls
…/releases/latest/download/latest.json, verifies the signature with the public key embedded in the binary, then installs (About → Check for updates).
Dev (tauri dev) has no installer channel — use a packaged build to exercise updates.
Security
See SECURITY.md for the threat model, crypto details, and reporting vulnerabilities.
About
Hi I'm Ahmi, hope this helps!
- GitHub: github.com/AhmiDarrow
- This project: AhmiDarrow/SecretSticky
- Releases: github.com/AhmiDarrow/SecretSticky/releases
- Support: patreon.com/cw/AhmiDarrow — thank you!
SecretSticky is a small, local-first Windows app for people who live in sticky notes but need real at-rest encryption for API keys and passwords. Built with Tauri so the UI stays light and the crypto stays in Rust.
License
MIT © Ahmi Darrow
This comes from the project's README. Read it on GitHub