Privacy Policy

WorkMail ("we", "us") is the control center for your application's email, built on your own Resend account. This page explains what data WorkMail touches, and — just as importantly — what it doesn't.

The short version

Your Resend API key, sending domain, test email address, and sent-mail history are stored only in your browser's local storage. WorkMail does not operate a database, and does not have server-side accounts, logins, or user profiles.

What we collect

WorkMail itself collects nothing that persists on our servers. Two server-side routes exist to make sending possible:

• Sending an email — your API key, the from/to addresses, subject, and message body are sent to our server for the single moment it takes to relay the request to Resend's API. They are not logged or written to disk.
• Syncing domains — your API key is sent to our server for the single moment it takes to ask Resend which domains are verified on your account. Same handling: used once, not stored.

Standard web infrastructure (our hosting provider) may keep short-lived technical logs — such as request timestamps or IP addresses for abuse prevention — that are outside WorkMail's own application logic and are not used to build any profile of you.

What lives in your browser

Your Resend API key, default sending domain, verified-domain list, and sent-mail history are stored using your browser's localStorage. This data never leaves your device unless you take an action that requires it — sending a message or syncing domains — and even then, only the specific data needed for that request is sent. You can delete it at any time from WorkMail's Settings tab, or by clearing your browser's site data.

Templates, the API Playground, and testing tools

These don't introduce any new server-side storage — they use the same key and domain already described above.

• Templates are static content bundled with the app. Choosing one and filling in fields happens entirely in your browser; nothing is sent anywhere until you actually send the resulting email.
• The API Playground generates example code (cURL, JavaScript, Python, PHP, Node.js, React) in your browser, using the key already stored there. If you click Send this request, that request goes through the same relay described above — used once, not stored.
• "Send test to myself" uses an address you save in Settings, stored locally the same way as your API key and domain. Test sends go through the same relay as a normal send.
• Client preview (Gmail/Outlook/Apple Mail) renders your HTML entirely in your own browser. Nothing is sent to our server or any third party to generate it.

Third parties

Every email you send through WorkMail is delivered by Resend, using your own account and API key. Resend's handling of message content and recipient data is governed by Resend's own privacy policy, which we'd encourage you to read.

Cookies

WorkMail does not use tracking or advertising cookies. It relies on browser local storage, described above, rather than cookies for remembering your settings.

Data retention

Because WorkMail doesn't store your data server-side, retention is entirely in your hands: your data lives in your browser until you delete it, clear your browser data, or switch browsers or devices.

Children's privacy

WorkMail is not directed at children and is not intended for use by anyone under the age required to hold accounts with services like Resend in their jurisdiction.

Changes to this policy

If this policy changes, we'll update the date at the top of this page. Continued use of WorkMail after a change means you accept the updated policy.

Contact

Questions about this policy? Email info@workmail.space.