Keep every receipt local. Add mail only if you want it.
Submission Guard’s dashboard is the canonical Sent folder. It needs no email account, OAuth permission, server, or provider setup. Technical users can optionally connect an SMTP server through the included localhost bridge.
Local dashboard firstNo Google identity accessOptional SMTP test
The staged download matches this site’s release metadata, and the public source clean-build reproduces the exact upload bytes. Chrome Web Store review and the Store-signed smoke test are still pending.
Use the Store—or inspect the staged package yourself.
The Chrome Web Store is the normal installation path. Check the version shown there because it may lag while a newer build is under review. The ZIP below is staged version 1.3.1 for source review and advanced testing; it is not presented as the Store-signed build.
This is the verified upload candidate, not a claim that the Store-signed release has passed its post-review smoke test. Inspect its manifest.json and permissions before loading it.
01
Use the built-in Sent folder
Install, check a form, and submit.
Install Submission Guard, open Chrome’s Extensions menu, and pin its shield.
Open an important form and protect it before typing if you want draft recovery. Keep it temporary or remember that exact page path.
Submit; the new local receipt opens only after the website’s Submit action resumes.
Search, inspect, delete, or export receipts without connecting an inbox. Attempted, moderated, and website-confirmed results stay visibly distinct.
02
Optional mail-server bridge
Put SMTP credentials in the local service—not the extension.
Download the source and generate a private bridge configuration. Provider presets are available for Gmail SMTP, iCloud, Fastmail, and compatible Outlook tenants; use custom for another server.
cd email-bridge
npm install
npm run setup -- --provider custom --email you@example.com --smtp-host mail.example.com
# Edit .env with your SMTP password and any provider-specific settings
set -a; source .env; set +a
npm run check:config
The generated RECEIPT_TOKEN authorizes the extension to call the bridge. Your SMTP password remains in the owner-only local .env file.
03
Prove delivery before enabling it
Smoke-test SMTP, then start the bridge.
npm run smoke:mail
docker compose up -d --build
SMTP is required for optional copies.The smoke test sends a real harmless receipt through your configured server.
IMAP is optional.When configured, the bridge verifies the exact Message-ID in Sent and appends only if the provider did not create a copy.
04
Connect Chrome to localhost
Send one test, then enable automatic copies.
Open Mail server (optional) in the Submission Guard dashboard.
Enter http://127.0.0.1:8789/v1/receipts, the destination address, and the generated RECEIPT_TOKEN.
Click Send test & enable copies.
The extension requests access only to that localhost origin. A failed connection test does not enable delivery, and disconnecting clears the stored bridge token.