Private Email Threads for Marketplaces
without Exposing Real Email Addresses

Secure peer-to-peer communication without exposing user emails. RelayCore generates per-thread aliases so users communicate through their existing email clients.

No new inbox. No leaked identities. Full control at the platform level.

Join Private Beta

Illustration of RelayCore routing marketplace buyer and seller email through a private relay thread

How It Works

From API Call to Secure Conversation

  1. Instant Thread Provisioning

Create a secure relay thread via API with approved participants, and initial message. Relay generates a unique, thread-bound email alias. Participants receive an email from a unique alias instantly.

  1. Seamless Peer Communication

Participants reply using their existing email clients. Relay validates participants and routes messages securely between verified thread members only.

  1. Visibility via Webhook Events

Track replies, engagement, and deal milestones in real time through structured webhook events.

Benefits

Key Benefits

API-First Integration

Create threads, manage participants, control lifecycle programmatically.
Works with your existing backend in minutes.

Privacy by Default

Relay replaces real emails with secure, per-thread aliases. Buyers and sellers never see each other’s personal contact details.

Clean Reply Threading

Proper In-Reply-To and References headers handled correctly. Clean threads in mail inbox.

Access Control

Messages are accepted only from approved thread participants. No random inbound spam. No impersonation risk.

Native Email Experience

Users reply directly from Gmail, Outlook, etc. No new inbox. No friction.

Controlled Communication

Your marketplace controls who talks to whom and when. Instantly revoke access by disabling a thread.

Pricing

Flexible Pricing

Currently in Private Beta. We are onboarding 3–5 early integration partners.

Contact Us

Join Private Beta

Tell us about your platform. We’ll reach out within 24 hours.

FAQ

Your Questions, Answered

Answers to common questions about RelayCore and marketplace email relay

How does RelayCore protect user email addresses?

RelayCore generates a unique alias for each thread. All communication is routed through that alias, and real email addresses are never exposed.

Who can send messages to a thread alias?

Only registered thread participants can send messages. Incoming emails are validated against the participant list. Unknown senders are automatically rejected.

Can someone guess an alias and send spam?

Aliases are long, unique, and bound to a specific thread. Even if discovered, messages from unauthorized senders are blocked at the relay layer.

Can I add observers or moderators to a thread?

Yes. Threads can include additional participants such as moderators, admins, or observers who receive messages without exposing user emails.

How do I integrate RelayCore into my platform?

RelayCore is API-first. You create a thread via API, register participants, and RelayCore generates the alias. No UI integration is required.

Can threads be expired or disabled?

Yes. Threads can be expired, blocked, or moderated programmatically. You maintain full lifecycle control.

Is RelayCore suitable for high-volume marketplaces?

Yes. RelayCore is designed for transactional platforms and supports scalable thread creation and message routing.

Do users need to create accounts with RelayCore?

No. RelayCore operates as infrastructure for your platform. Your users never interact directly with RelayCore.