Your mail stays in your inbox — not in OhRelay

The first trust question to ask

Any time email passes through a third party, one question matters: where does my mail actually live? Does this service become the archive for all my conversations?

With OhRelay, the answer is no. OhRelay is a routing layer, not a mailbox. Your email lives in your own inbox account.

Inbound mail routes through — it doesn’t stay

When a customer writes to one of your addresses, OhRelay reads the recipient information to decide where the mail should go, then delivers it to your inbox.

OhRelay doesn’t need to build its own archive to do this. The service that stores, indexes, and searches the message is still your Gmail, Outlook, or Apple Mail account.

• Routing uses headers, not message-body analysis
• Mail is delivered to your own inbox account
• Your inbox provider remains your system of record

Outbound replies pass through briefly — just to fix the sender

When you reply, OhRelay’s job is to send it from the correct customer-facing address. So the outgoing message passes through OhRelay briefly. But the sent copy lands in your own sent folder — not locked inside a separate dashboard.

• OhRelay corrects the sender address on replies
• The sent copy goes to your sent folder, not OhRelay’s servers
• Reply history stays searchable in your existing inbox

Why this architecture matters

This isn’t a limitation — it’s how OhRelay is designed. Your communication history stays portable, familiar, and under your control.

The privacy boundary is structural: OhRelay doesn’t need to store your email content to route it correctly.

What OhRelay does store

OhRelay stores the configuration it needs to route mail: connected domains, managed addresses, destination inbox mappings, and account settings.

That’s operational configuration — not your email archive. If you stop using OhRelay, your message history stays in the inbox where it has always been.