Support / Help
Help center and contact path
If you are blocked on account access, billing, mailbox behavior, privacy questions, or suspicious abuse, start here. This page collects the most useful help links into one place and gives you a contact form that actually writes into the system.
This surface gives you help links plus a contact form, and routes abuse, privacy, and delete/export issues toward the more appropriate current handling paths. But it is still not a full incident cockpit or a one-stop completion surface.
This page is good for finding the right entry point, submitting a support request, and following the current self-serve paths. But billing, privacy, abuse, and delete/export handling still mostly need backoffice workflow, runbooks, or human follow-through, so this page should not be read as a complete resolution cockpit.
Billing / plan help → billing manage plus deeper operator billing paths; Privacy / abuse → dedicated intake entry followed by support-case / operator handling paths; Delete / export / account data → support entry plus privacy/support handling paths and some account/admin capabilities, but not a full one-stop cockpit yet.
Contact us
Leave the issue type, subject, and details here. We will turn it into a tracked support record so the follow-up does not depend on scattered messages.
Quick links
Some issues do not need a reply first. These entry points are often faster.
If you need to report phishing, spam, malicious content, a complaint, or a takedown issue, use the dedicated abuse-report flow instead of the general contact form.
If you only need to get back to an earlier temporary mailbox, recovery links are usually the fastest path.
If you need plan differences, capacity details, or upgrade timing, start with the pricing page.
If you want the current data-processing, retention, and disclosure rules, start with the privacy policy.
If you need data access, export, or deletion handling, use the dedicated privacy-request path instead.
For account responsibility, acceptable use, and availability boundaries, read the terms first.
What this first version can cover
- • Account, verification, sign-in, password, and recovery issues
- • Basic guidance for billing, plans, mailbox operations, and automation paths
- • Abuse and privacy already have dedicated entry paths and downstream handling, but they are still not fully self-serve completion flows