NexusSend · Journal
How we build and secure Gmail workflows
This is our engineering and compliance notebook—published for teams who care about OAuth scope discipline, token hygiene, MIME safety, and what Google reviewers actually look for. We favor concrete explanations over buzzwords: architecture choices, shipped behavior, and trade-offs we accept on purpose.
Posts are dated; when implementation changes, we update the article or add a follow-up so this stays useful for audits and onboarding—not SEO filler.
Featured
Product updates — April 2026
Template version snapshots in the editor, variable preview checks, retry-from-history, MIME hardening, and stricter security headers.
Recent articles
MIME injection and why email headers are dangerous
Header injection attacks are subtle and easy to miss. Here's how NexusSend's MIME builder defends against them.
Preparing for Google OAuth verification
What the verification process actually requires, what reviewers look for, and how NexusSend is structured to pass.
How NexusSend handles Gmail OAuth securely
A technical deep-dive into minimal scopes, AES-256-GCM token encryption, and why we deliberately avoid full mailbox access.