Privacy Policy

Effective August 16, 2026

Who we are

DynaMail (dynamail.io) generates live images — countdown timers, progress bars, gauges, and charts — that our users embed in their email campaigns. This policy explains what data we collect from account holders and from recipients who open emails containing DynaMail widgets, and how we use it.

Information we collect

Account information. When you sign up, our authentication provider, Clerk, collects your name and email address on our behalf.

Widgets and templates. We store the widget and template configurations you create — settings, labels, colors, target dates — so we can render your images.

Render and click logs. When a recipient opens an email containing one of your widgets, their email client requests the image from our servers. We log request metadata: a truncated IP address, an approximate location derived from the full IP address, browser/client headers (such as user agent, accepted formats, and language), a timestamp, and any campaign identifier you configured in the URL. If a recipient clicks a tracked widget link, we log a truncated IP address, an approximate location, the user agent, the destination URL, and campaign attribution. These logs are shown to you, the widget owner, as analytics — aggregate charts and individual render entries. If your campaign passes a recipient identifier in the image URL (the ?r= parameter), it is salted and hashed before storage — we never store the raw identifier.

Site analytics. We use PostHog to understand how our website is used. We capture pageviews and a small set of explicit events (such as clicking a sign-up button) only — no session recording and no automatic capture of page content. Analytics are anonymous until you sign in.

Cookies

We use Clerk session cookies, which are essential for signing you in and keeping you signed in, and PostHog analytics cookies, which link your visits into one anonymous profile.

Third-party processors

We rely on a small number of service providers to run DynaMail: Clerk (authentication), Railway (hosting), and PostHog (site analytics). To derive the approximate location in render and click analytics, the recipient's IP address is sent to an IP geolocation provider (ip-api.com or IPStack). Weather widgets fetch forecasts from Open-Meteo and map widgets fetch imagery from Google Maps — usually for the location configured in the widget, or, when a widget is set to use the viewer's location, for an approximate location derived from the recipient's IP. Uploaded images may be stored with an S3-compatible storage provider, and if you use the send-a-test-email feature, that email is delivered through our email provider. Each processes data only as needed to provide its service.

Your rights

You can request access to, or deletion of, your personal data at any time by emailing support@dynamail.io. Deleting your account removes your widgets, images, and analytics history from our database and requests deletion of your authentication record from Clerk. Templates you shared with the community remain available to other users but are no longer linked to you. If you want confirmation that everything, including externally stored images, is gone, email us and we will verify it.

What we don't do

We do not sell your data. We do not sell recipient data.

Children

DynaMail is not directed at children under 16, and we do not knowingly collect their data.

Changes to this policy

If this policy changes materially, we will update the effective date above and note the change on this site.

Contact

Questions about this policy? Email support@dynamail.io.