Transactional email, bound to identity.
AccountMaker handles email as part of authentication and operations — not as a general-purpose email service.
What this service is
Transactional email only
Emails triggered by authentication and system events, such as verification, password resets, invites, and security notices.
Domain-bound
All email is sent from your verified domain, aligned with your authentication flows.
Identity-aware
Email sending is scoped to the same identity surface as login and access control.
What this service is not
Not email hosting
No personal inboxes, no employee accounts, no IMAP or POP access.
Not marketing email
No newsletters, promotions, or bulk campaigns.
Not a general SMTP relay
Email is limited to identity and operational use cases.
Inbound email handling for identity addresses
AccountMaker can receive email sent to common identity-related addresses on your domain and route them into a shared interface.
Addresses
- support@yourdomain
- legal@yourdomain
- info@yourdomain
- security@yourdomain
Handling rules
- Aggressive spam filtering
- Attachments are removed
- Tracking pixels are stripped
- Messages are stored as plain content only
Designed to reduce abuse
Limited scope
By restricting email to identity and operational use, abuse vectors are reduced.
No attachments or trackers
This minimizes malware risk and prevents covert tracking.
Shared visibility
Inbound messages can be reviewed by a team instead of living in a single inbox.
Why email belongs in the identity stack
Users trust domain consistency
When login and email share a domain, legitimacy is easier to assess.
Security communication is clearer
Password resets and alerts are less likely to be mistaken for phishing.
Operations stay simple
Identity-related communication lives in one place instead of across tools.
Email as identity infrastructure
AccountMaker treats email as part of how users understand and trust your product.