Overview
Start from the main MailForge public overview page.
Quick Links
Use this page to jump to public overview sections, workspace entry points, support paths, and trust documents.
Sitemap
Sitemap
Understand how MailForge works when the client keeps its own sender infrastructure.
Learn what an SMTP-first campaign platform helps teams manage.
Review the limits, checks, and responsibilities for sending through client SMTP.
Clarify that the client remains responsible for consent, content, provider compliance, and campaign outcomes.
Compare the customer-owned SMTP model with traditional email marketing platforms.
Sitemap
Open an existing workspace with Client ID and user credentials.
Plan a workspace, request support, or discuss custom limits.
Signed-in teams can create and manage campaign sends.
Signed-in teams can configure timestamp and recurring sends.
Sitemap
How MailForge is designed to handle account, subscriber, campaign, and security data.
Expected use, customer responsibilities, acceptable use, and commercial terms.
Browser storage, session cookies, CSRF protection, and preference storage.
Processing roles, scope, safeguards, subprocessors, and data request support.
Permission-based sending standards and abuse enforcement.
Next step