Authenticated identity
Checks whether the sending domain and message can prove who they came from.
A personal communication boundary for your domain
TrustSender receives email for your custom domain and evaluates each message using authenticated sender identity, relationship history, and policies you describe in ordinary language.
Working public prototype with live SMTP decisions and a customer Activity view.
The domain identity is valid, but this sender is new and the message matches your “review unexpected proposals” policy.
Email admission controlled by you—not just a spam score.
Permission, not probability
Traditional filters identify abuse. TrustSender adds the question only you can answer: does this communication belong in your space?
Policies in your language
Describe the boundary without learning mail-server rules. Policies can refer to people, organizations, relationships, subjects, meaning, or receiving addresses.
These examples show the intended TrustSender experience as the policy model continues to develop.
“Always allow mail from my children and put it first.”
“Reject sales outreach about website redesigns.”
“Allow my dentist’s office, even when a new staff member writes.”
“Defer uncertain messages instead of making a permanent decision.”
Decisions built from evidence
TrustSender translates transport evidence, history, and policy into reasons a person can understand and correct.
Checks whether the sending domain and message can prove who they came from.
Uses prior communication and your corrections to understand who is expected.
Applies the boundaries you describe to the address receiving the message.
Avoids repeatedly spending your attention on the same message.
Act during delivery
Because TrustSender can operate as the mail service for a custom domain, it can accept a message, ask the sending server to retry later, or reject the current delivery before normal mailbox handling.
Visible and correctable
TrustSender Activity explains what happened, why it happened, which policy applied, and which identity and relationship evidence mattered.
See the reason. Understand each accepted, deferred, or rejected delivery in plain language.
Correct the record. Allow or block a sender, revise a relationship, or change a policy.
Keep authority. Your explicit correction takes priority over later inference.
Trust and safety
Incoming email is untrusted evidence. A message cannot rewrite your policy, authorize a tool, expose another person’s mail, or grant itself a trusted relationship.
Built openly, claimed carefully
Pre-mailbox decisions, sender-authentication evidence, correspondent controls, retry caching, and Activity audit.
Multiple identities, deeper relationship knowledge, daily briefing, adaptive views, and governed actions.
Redundant SMTP, monitoring, privacy controls, abuse handling, recovery testing, and production readiness.
Early access for design partners
Define your first communication policies with us. Review every TrustSender decision and help shape a person-controlled mail service.
Questions
No. It uses mail-security evidence, but its purpose is broader: applying your relationship and communication policies to decide what may enter your communication space.
The initial service is for custom domains. Your domain’s mail-delivery records point to TrustSender while you keep your existing address.
The intended policy model can accept, hold for review, temporarily defer, or reject delivery. You choose how uncertainty is handled within safe service limits.
Not by default. Outbound actions require explicit authority, defined scope, frequency limits, an audit record, and loop prevention.