Privacy Policy

Overview

RelayMail ("we", "our", or "us") operates a service that connects your email to Slack. This Privacy Policy explains what data we collect, how we use it, and your rights regarding your information.

How RelayMail Works

Understanding our architecture helps explain what data we handle:

1. You set up forwarding from your email provider (Gmail, Outlook, etc.) to a unique RelayMail address we provide (e.g., inbox-abc123@relay.relaymail.app)
2. Forwarded emails arrive at our servers via Resend (our email infrastructure provider)
3. We post the email to your connected Slack channel
4. You reply in Slack, and we send your response as an email via Resend

This forwarding-based model means we never access your email account directly - we only receive the specific emails you forward to us.

Information We Collect

Account Information

When you sign in with Slack, we receive and store:

• Your Slack user ID and workspace ID
• Your name and email address (from Slack profile)
• Your profile picture URL

Slack Workspace Access

When you connect your Slack workspace, we store:

• Slack bot token (allows us to post messages to your selected channel)
• Channel ID where emails should be posted
• Workspace ID for routing

We only request permissions needed to post messages, upload a forwarded email's attachments, read replies and read files attached to those replies. RelayMail joins only the public channel you pick (a private channel needs you to invite it) Slack sends it the messages in that channel; it acts only on replies in threads it posted and keeps none of the other messages. When someone replies, it looks up that person's Slack display name to put on the email. It cannot read your direct messages or other channels.

Email Data

When emails are forwarded to us:

• We process: Sender address, subject line, and message body to display in Slack
• We store: Email message IDs and subject lines for thread matching (so replies go to the correct conversation)
• We do NOT permanently store: Full email bodies - these are processed and forwarded to Slack, then discarded
• Attachments: Files on a forwarded email pass from Resend to that email's thread in your Slack workspace. Files a teammate attaches to a reply in that thread pass from Slack to Resend and on to the customer with the reply email. We keep no copy of either
• When Slack can't take an email: If an inbox is over its monthly limit, its subscription has ended, Slack is disconnected or Slack refuses a message, we send that email to the inbox owner's email address instead, so it isn't lost.

Thread Mappings

To maintain conversation threads between email and Slack, we store:

• Email message ID (unique identifier from the email)
• Original sender's email address
• Email subject line
• Corresponding Slack channel ID and thread timestamp

This mapping data allows us to route email replies to the correct Slack thread and vice versa.

Billing Information

Payments are processed by Stripe. We store:

• Stripe customer ID (links your account to your Stripe subscription)
• Subscription ID and plan type
• Thread usage counts (for billing limits)

After your account data is deleted, we keep only the Stripe customer ID and subscription ID, so we can handle refunds and payment disputes.

We do NOT store credit card numbers, bank details, or other payment credentials. All payment processing happens directly through Stripe's secure systems.

Usage Data

We track basic usage metrics including thread counts per month (for billing), forwarded email counts (for verification), and general service health metrics.

What We Do NOT Collect or Store

How We Use Your Information

• Provide the service: Process forwarded emails and post them to Slack, send your Slack replies as emails
• Maintain thread continuity: Match email replies to the correct Slack thread
• Manage your account: Authenticate you, manage your subscription, enforce usage limits
• Communicate with you: Service and billing notices, and during a trial a few emails about setup, the trial end date and the charge, and a note if you cancel. Reply "stop" to any of the trial emails and we stop sending them.
• Learn why people cancel: If you cancel in Stripe's billing page, we read the reason and comment you choose to give there.
• Improve the service: Analyze usage patterns to fix bugs and improve features

Third-Party Services

We use the following third-party services to operate RelayMail:

• Resend (resend.com) - Receives forwarded emails on our behalf and sends outgoing emails. Resend processes email content to deliver it to us. Resend Privacy Policy
• Slack (slack.com) - We use Slack's API to post messages to your workspace. Slack stores the messages and files we post. Slack Privacy Policy
• Stripe (stripe.com) - Processes all payments. Stripe stores your payment information securely. Stripe Privacy Policy
• Google Analytics (google.com) - Measures visits to relaymail.app using cookies: pages viewed, referrer and approximate location. It never sees your email content or Slack messages. Google Privacy Policy You can block or clear these cookies in your browser. relaymail.app also sets its own cookies for your language, where your first visit came from, and your sign-in.
• DigitalOcean (digitalocean.com) - Hosts our servers in the United States. DigitalOcean Privacy Policy

Data Retention

• Account data: Retained while your account is active, deleted within 30 days after termination (your inboxes are deleted or their subscriptions end). We keep only your Stripe customer and subscription IDs after that, to handle refunds and disputes
• Thread mappings: Retained while your inbox is active to keep conversation history. Deleted within 30 days after termination (you delete the inbox or your subscription ends), or sooner on request to hello@greatwork.company
• Email content and attachments: Processed in real-time and not permanently stored - only metadata (message IDs, subjects) is retained
• Usage metrics: Retained for 12 months for billing purposes
• Backups: Deleted data also leaves our backups, which we keep for 14 days

Data Security

We implement appropriate technical and organizational measures to protect your data:

• All data in transit is encrypted using TLS/HTTPS
• Database access is restricted and authenticated
• Slack bot tokens are stored securely
• Webhook signatures are verified to prevent spoofing (using Svix for Resend webhooks)
• Regular security reviews of our infrastructure

Your Rights

Depending on your location, you may have the following rights:

• Access: Request a copy of the data we hold about you
• Correction: Request correction of inaccurate data
• Deletion: Request deletion of your account and associated data
• Portability: Request your data in a portable format
• Objection: Object to certain types of data processing

To exercise any of these rights, contact us at hello@greatwork.company.

For European Users (GDPR)

If you are in the European Economic Area (EEA), we process your data under the following legal bases:

• Contract: Processing necessary to provide our service to you
• Legitimate interests: Improving our service, preventing fraud, ensuring security
• Consent: Where required, such as for marketing communications

Our servers are located in the United States. By using RelayMail, you consent to the transfer of your data to the US. We ensure appropriate safeguards are in place for international data transfers.

For California Users (CCPA)

California residents have additional rights under the CCPA:

• Right to know what personal information we collect
• Right to delete personal information
• Right to opt-out of the sale of personal information
• Right to non-discrimination for exercising your rights

We do not sell personal information. To exercise your CCPA rights, contact us at hello@greatwork.company.

Children's Privacy

RelayMail is not intended for use by children under 16. We do not knowingly collect personal information from children under 16. If you believe we have collected information from a child, please contact us so we can delete it.

Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the new policy on this page and updating the "Last updated" date. We encourage you to review this policy periodically.

Contact Us

If you have questions about this Privacy Policy or our data practices, contact us at: