What stays TrekMail-branded

White Label Lite rebrands the customer-facing surfaces — dashboard, webmail, login, transactional emails. But it's "Lite" for a reason. A few things stay TrekMail-branded by design, and a couple of others might surface to a technical user even though they don't appear in normal use.

Here's what stays TrekMail-branded and why, so you know exactly what your customers might still see.

What's fully yours

These surfaces are 100% rebranded under your name, logo, and colors:

• The login screen at your custom domain (app.yourbrand.com).
• The dashboard — sidebar, page titles, primary and accent colors, navigation.
• Webmail — when your customers compose, read, or manage email, they see your brand.
• Transactional emails — password reset, mailbox invite, account notifications. Visible From name and email body are yours.
• SSL certificate — issued in your domain's name, not ours.
• The browser tab title — your brand, not TrekMail.

If your customer never opens the browser developer console and never asks you about your underlying email provider, they may never know TrekMail is involved.

What stays TrekMail-branded

The intentional ones:

Billing emails to you, the account owner. Invoices, dunning notices, payment-method warnings, renewal reminders — these come from noreply@trekmail.net and land in your inbox. They're for you, not for your customers. Your customers should never see one of these.

Your own dashboard password reset. If you (the account owner) hit "Forgot password" on app.yourbrand.com, the email that lands in your inbox is TrekMail-branded. That's correct: it's a TrekMail-account-owner credential, not a customer credential. Mailbox-user password resets (the ones your customers go through) are fully branded.

Help center and documentation. This site you're reading right now stays at trekmail.net/docs. Your customers shouldn't normally land here — you handle support directly. If they do find it, they'll see TrekMail branding. We don't currently offer a way to white-label the docs site.

Support tickets. When your customers open a ticket with you (via your own support channel), you handle it. If you need to escalate to TrekMail, you open a ticket from your dashboard at /app/support — your customers don't see that step. The support portal itself is TrekMail-branded for you.

The sender address (optional — you can change this). By default, transactional emails go out from noreply@trekmail.net with your visible brand name. If you want the address to match your brand too, set Transactional sender in the White Label settings page — pick any address on a domain you've already verified on TrekMail (e.g. noreply@yourbrand.com). We sign with your existing DKIM key, your SPF already includes us, deliverability stays clean. The setting just maps to the visible From-address on every branded transactional email going forward.

Inbound email infrastructure. Your mailboxes still receive mail through TrekMail's MX record (mail.trekmail.net). This is invisible to senders, but a technical investigator looking at your DNS would see the TrekMail MX host. We don't currently offer custom-MX-host branding under Lite.

What might surface to a technical user

These don't appear in normal use, but a developer with browser tools open might spot them:

Cookie and local-storage names. The dashboard sets cookies with names like trekmail_session and local-storage keys like trekmail-…. None of these are visible during normal browsing. A developer inspecting the page would see them. We don't currently rename these per-tenant.

Some embedded resource URLs. A few static assets are served from trekmail.net/assets/... even on your branded domain. Your customers' browsers download them transparently — never visible in the URL bar. Developer tools' Network tab would show them.

Internal API endpoints. A few asynchronous calls happen against trekmail.net/api/.... Same caveat as static assets — invisible in normal use, visible in the Network tab.

Email "Received" headers. When your customers send mail to one of your branded mailboxes, the technical "Received:" headers in the raw email show TrekMail's mail-server hostnames. Most email clients hide these headers by default; "View raw source" or "Show original" reveals them.

These are not customer-facing under normal use. Full obfuscation of the underlying infrastructure is out of scope for Lite. If you're working with a customer who needs every internal name scrubbed, contact sales and we'll look at your case.

What you can do to keep things polished

Even with the items above, most TrekMail evidence is invisible in your customers' normal day. A few habits help:

• Direct your customers to your branded URL only. Send app.yourbrand.com in your onboarding emails, not trekmail.net. After activation, set up bookmarks, internal docs, and any embedded links to go through your brand.
• Use Support email in your White Label settings. This puts a Reply-To on every transactional email pointing at you, so when a customer hits Reply they reach your team, not bounce off our no-reply.
• Write your own help docs. If you offer custom support to your customers, your own help site (separate from our docs) is the cleanest path. Reference our docs only as internal training material.
• Don't share your dashboard with your customers. The /app/billing and /app/settings/... pages are for you, the account owner. Your customers should never have direct access — they interact with you, who interacts with TrekMail.

Common questions

"Can I send transactional emails from noreply@yourbrand.com instead of noreply@trekmail.net?" Yes — set Transactional sender in the White Label settings page. It accepts any address on a domain you've already verified on TrekMail (the same domain you use for mailboxes). We sign with your DKIM key (which you already have because your mailboxes use it) and SPF was already aligned. No extra setup. Leave it blank to keep the default TrekMail address.

"My customer asked who runs your email service. What should I say?" Up to you. Some agencies are upfront about using TrekMail underneath; some say "our managed email infrastructure" and leave it at that. There's no contractual requirement to disclose or hide.

"What about the favicon?" The favicon at your branded domain is set from your logo (a 32×32 derivative). Your browser tab shows your brand, not TrekMail.

"What about error pages?" 404, 500, and other error pages on your branded domain show your brand chrome. Behind the scenes the response is generated by our infrastructure, but the visual presentation is yours.

"What about the source code? My customer's IT team might inspect it." The HTML and JavaScript served at your branded domain do include some internal class names and asset paths with trekmail-... references. We don't currently rewrite these per-tenant. If your customer's IT team is auditing source code, expect them to identify TrekMail underneath.

What's next

• What is White Label Lite? — overview of what's included.
• Set up White Label Lite — activation and brand setup.
• Brand assets best practices — logo sizing and color tips.