Your list is valuable. We treat it that way.
Your data stays yours.
We don't sell your data or share it. We don't mine it for trends, train models on it, or show ads against it. Your contacts, your content, and the activity you track belong to you. We use analytics to see which pages and features get used, so we know what to improve.
Every account is isolated at the database level. Row-level security enforces the boundary in the database itself, and the app scopes every request and background job to your account after checking you belong to it. Automated tests check proposed code changes for any query that isn't scoped to an account.
Your domain, your cookies.
Tracking runs on your domain. Opens, clicks, and website activity all resolve to a subdomain you own — not ours. Cookies are first-party. Your visitors never see a third-party domain in their browser, and no ad network can piggyback on the data.
You control what gets sent.
Nothing goes out to your contacts unless you build it and turn it on. Broadcasts send when you schedule them. Sequences and automations run on rules you write — and they stop when you say stop. There's no scenario where we decide to email your list.
You bring your own sending provider — your SES account, your SendGrid account, your Mailgun, Mailjet, or Resend. You own the sending domain, the reputation, and the rate. If you leave, your provider account and deliverability history stay with you.
We watch your back on deliverability.
We monitor your DMARC posture and Google Postmaster reputation daily. Domain health checks run in the background, and you'll see warnings in the dashboard when something needs attention — a missing DMARC record, a reputation drop, a spam rate climbing.
This is monitoring, not management — you own your DNS and your sending authentication. We let you know when something's off that we can see.
Infrastructure.
Connections to RadarSend use TLS, and browsers are told to always use HTTPS. Your sending provider credentials, integration tokens, and outbound webhook secrets are encrypted with AES-256-GCM before they're saved, and the keys are kept apart from the database.
RadarSend runs on Railway in the US, with traffic coming through Cloudflare, which also protects against denial-of-service attacks. The database can be restored to any point in roughly the last four weeks, and a daily backup is encrypted and kept with a separate provider for 14 days.
What we don't do.
Transparency is part of the deal. Here's what's out of scope:
We don't manage your DNS.
DMARC, SPF, and DKIM records are yours to configure. We check them and tell you what's wrong, but we can't fix them for you.
We don't hold a SOC 2 certification ourselves.
Our hosting provider, Railway, is SOC 2 Type II certified. If your compliance team needs specifics, we'll share exactly what's covered and what isn't.
We don't offer HIPAA or BAA agreements at this time.
We don't guarantee deliverability.
Nobody honest can — it depends on your content, your list hygiene, and your sending reputation. We give you honest data to manage it.
Questions about security?
If your team needs details about our infrastructure, data handling, or compliance posture, we're happy to walk through it.