Privacy policy
How Senderward handles personal data about customers and visitors.
Last updated: 18 November 2026.
Who is responsible
NFI ApS, CVR 45583112, Langfreddal 3, 8471 Sabro, Denmark, is the data controller for the data described here.
Contact about privacy: [email protected]. General support: [email protected].
When you monitor domains with Senderward, we also process some data on your behalf as a processor. That is covered by our data processing agreement.
If you visit senderward.com
- Cloudflare delivers the site as CDN and proxy. Your browser connects to Cloudflare, which sees your IP address and the request, and passes the request on to our server.
- Our server logs contain the time, internal IDs, technical errors and, where an email address must be referred to, a short keyed hash of it instead of the address. The app does not write IP addresses or email addresses to its logs, and the access log of our proxy is switched off.
- Rate limits: to stop abuse of the sign-up and sign-in forms, we count requests per IP address (IPv6 grouped per /64), per network, and per email address from the same IP address. We store only a keyed hash (HMAC) of these with a key that changes every day, never the IP address or email address itself. The counters are deleted when their time window has passed, at the latest after 24 hours.
- Bot protection: when sign-up is open, the sign-up and sign-in forms use Cloudflare Turnstile, which runs in your browser and is checked by Cloudflare.
- About Cloudflare Turnstile: Turnstile is Cloudflare's CAPTCHA alternative that tells people apart from automated bots, usually without a puzzle. To do this, Cloudflare processes your IP address and signals from your browser, such as the User-Agent header and how the page is loaded, and we confirm the result with Cloudflare when you submit the form. Read more in Cloudflare's Turnstile Privacy Addendum.
- Lookproof badge: public pages show a small image from lookproof.dev in the footer. Your browser loads it from lookproof.dev, our own DNS checking service, which then sees your IP address. It sets no cookies.
- Analytics: self-hosted and cookieless, no third parties. Our server counts views of public pages in Umami, which we run on our own servers. It receives the page, any campaign tag (
utm_source,utm_medium,utm_campaign), the other website's domain name if you came from one, your browser's language and user agent, and your network instead of your IP address (the last part removed: /24 for IPv4, /48 for IPv6). From these, Umami derives a country, your browser, operating system and device type, and a visit ID made from your network and user agent, so several page views can be counted as one visit. Your full IP address is not sent or stored, no cookie is set, nothing runs in your browser, and pages behind sign-in, sign-in links and bots are not counted. Analytics events are deleted after 12 months. - We use no tracking pixels, no ads and no third-party embeds. Fonts are hosted by us.
If you have an account
What we process
- Account: your email address and company name, when the account was created and when you last signed in. Sign-in is by a link we email you; there is no password.
- How you found us: if the link you followed to sign up carried a campaign tag (
reforutm_parameters), or you came from another website, we store that tag or the other website's domain name with your account, to see which channels bring customers. Nothing else about your visit is linked to your account: the page views counted by our analytics (above) are not linked to your account, and use no cookies and no third parties. It is deleted with your account. - Sign-in links and sessions: we store only a SHA-256 hash of each sign-in link and of each session token, never the token itself. A sign-in link works once and for 15 minutes. A session lasts 30 days or until you sign out.
- Domains and check results: the domain names you add, the verification token for each, whether it is verified, and the result of each check: public DNS data about the domain (DMARC, SPF, DKIM, MX, MTA-STS, TLS-RPT), changes found, and which alerts were sent.
- DMARC aggregate reports (only if you point your domain's DMARC
ruaaddress to us): the reports mailbox providers send about mail that uses your domain. From each report we keep the reporting organisation and the address it reports from, the period and the DMARC policy it saw, and for each sending source: the IP address of the sending server and its host name (reverse DNS), the sender domains (header From, envelope From, and the domains in the DKIM and SPF results), the number of messages, and the SPF, DKIM and DMARC results. We use them to show you who sends mail as your domain. They contain no message content. Mail to the report address that is not an aggregate report, for example a forensic (RUF) report or any other mail, is discarded without being stored: we keep only the time, the sender's domain, the size and the reason it was discarded. We process the reports on your behalf under the data processing agreement. - Mail we send you: sign-in links, alerts, the weekly status (you can turn it off) and notices about your domains and plan. Alerts and the weekly status are queued in our database with recipient, subject and content, and deleted 90 days after they were sent. If an address hard-bounces or a recipient marks our mail as spam, we put it on our suppression list (see below) and never mail it again.
- Billing: Stripe handles payment. We store your Stripe customer and subscription IDs, the subscription's status, number of domains, trial and period dates, your billing country and the tax ID you enter in Checkout, and whether you have used the free trial. Card details go directly to Stripe and never reach our servers. Stripe receives your email address, company name, billing address and tax ID. Invoices are generated and sent through Stripe on behalf of NFI ApS.
Please only give us business contact details. Senderward is for businesses only.
Why, and on what legal basis
- To provide the service you signed up for: account, checks, alerts, billing (GDPR art. 6(1)(b), contract).
- To keep the service secure and working: logs, rate limits, bot protection, suppression list (art. 6(1)(f), our legitimate interest in security and in not mailing addresses that bounce or complain).
- To see which pages and channels bring visitors: cookieless page counts without your full IP address (art. 6(1)(f), our legitimate interest in improving the site).
- To keep accounting records (art. 6(1)(c), legal obligation under the Danish Bookkeeping Act).
For DMARC report data, you (the customer) are the controller and Senderward is your processor, as set out in the data processing agreement.
We do not sell personal data, and we do not use it for marketing profiles.
How long we keep it
- Rate-limit counters: deleted when their window has passed, at the latest after 24 hours.
- Sessions: deleted when you sign out; otherwise they stop working after 30 days and are deleted 30 days after that.
- Sign-in links: stop working after 15 minutes or once used, and are deleted 24 hours after they were used or expired.
- A removed domain: its check history, changes, alert state and DMARC reports are deleted at once when you remove it.
- DMARC reports: the incoming mail is stored by Amazon S3 and deleted there after 7 days; mail that is not an aggregate report is deleted as soon as we have read it. The report file is kept for 30 days, and the results extracted from it for 12 months. The record of a discarded mail (time, sender domain, size, reason) is kept for 30 days. Removing the domain or deleting the account deletes all of it at once. Deleted DMARC data is gone from all backups after about 13 months.
- Account, domains and check history: kept while you have the account. You can ask us to delete the account at any time. An account with no plan that has not been signed in to for 12 months gets a warning email and is deleted with all its data 30 days later, unless you sign in before then.
- Mail we have sent you: deleted from our mail queue 90 days after it was sent, or 90 days after it finally failed. When an account is deleted, all mail to its address is deleted with it.
- Suppression lists: hold only keyed hashes (HMAC with a dedicated secret key) of email addresses, domains and company names, never the values themselves, together with the reason and the time. (Amazon SES keeps a separate list, see Who else processes the data.) Addresses that hard-bounced or complained are listed by address. Unsubscribes and objections, including requests to erase outreach data, are listed by address, domain and company. The lists are kept without a time limit, also after an account is deleted, so that we never mail an address again that bounced, complained, unsubscribed or objected.
- Server logs: rotated automatically, and the oldest lines are deleted. There is no fixed time limit, so how far back the logs reach depends on how much is logged.
- Audit log: Account deletion, data export and removal of a domain by us are logged in an audit log with the time, the account ID and a fixed note (no email address or domain name). The audit log is deleted after 3 years.
- Backups: the database is backed up daily. Backups are encrypted (AES-256) before they leave our servers and stored in the EU, with an off-site copy in Germany (31 daily and 12 monthly versions, plus 10 daily snapshots). The off-site provider does not have the keys. Data deleted from the database is gone from all backups after about 13 months (12 monthly versions, the oldest of which can hold data from up to a month before it was taken).
- Invoices and accounting records are kept by Stripe and by us for 5 years from the end of the financial year they relate to, as the Danish Bookkeeping Act requires, also after an account is deleted. They hold the billing name, address and tax ID.
Who else processes the data
- Amazon Web Services (Amazon SES and SNS, region eu-north-1, Stockholm, Sweden): sends our email and tells us about bounces and complaints, and receives DMARC aggregate reports for your domains (Amazon SES receiving, with the incoming mail stored in Amazon S3 in the same region). Our account and transactional mail (sign-in links, alerts, the weekly status and notices) is sent without open or click tracking. Amazon SES also keeps its own list of addresses that bounced or complained, to protect our sending reputation. That list holds the address itself and is kept by AWS until we remove the address from it.
- Stripe: payments, invoices and the billing portal. Stripe receives your email address, company name, billing address, tax ID and payment details, and is an independent controller for the payment data it processes. Stripe may process this data in the USA.
- Cloudflare: CDN, proxy and TLS for senderward.com, and Turnstile bot protection.
- DNS: to check that you own a domain, we look up its verification record directly at the public resolvers 1.1.1.1 (Cloudflare) and 8.8.8.8 (Google). These lookups contain the domain name only. DMARC aggregate reports also make us look up the name of each sending server's IP address (reverse DNS) at the same two resolvers. Those lookups contain that IP address and nothing else.
- Lookproof, our own DNS checking service operated by NFI ApS, runs the checks of your domains. It receives the domain names only.
- mailbox.org (Heinlein Hosting GmbH, Germany) hosts our own mailboxes. If you write to support@ or privacy@, your email is stored there.
- Hetzner (Hetzner Online GmbH, data centre in Falkenstein, Germany) stores our encrypted off-site backups. They are encrypted before they leave our servers, and Hetzner does not have the keys.
- Hosting: servers are operated by NFI ApS in Denmark (EU). No hosting provider is involved.
Cloudflare, Google and Stripe may process data in the USA, and AWS has a US parent company. Each states its own transfer basis: AWS, Cloudflare and Stripe the EU-U.S. Data Privacy Framework and standard contractual clauses, and Google the EU-U.S. Data Privacy Framework. Amazon SES and SNS run in the EU region eu-north-1. mailbox.org and Hetzner are in Germany.
Your rights
You can ask for access to the data we hold about you, and ask us to correct or delete it, to restrict its processing, or to receive it in a portable format. You can object to processing based on our legitimate interest. Write to [email protected]. We reply within one month. You can also complain to the Danish Data Protection Agency (Datatilsynet).
Cookies
Senderward only uses what is needed to run the service and keep it safe. Our analytics are self-hosted and cookieless, and there is no tracking and no ads, so there is no cookie banner.
| Name | What and where | Why | How long |
|---|---|---|---|
sw_session | Cookie on senderward.com, set when you sign in | Keeps you signed in. It holds only a random token. | 30 days, or until you sign out |
sw-theme | Local storage on senderward.com, only if you switch between light and dark | Remembers your choice | Until you clear your browser data |
cf.turnstile.u | Local storage of Cloudflare Turnstile, on the sign-up and sign-in forms | Protects the forms against bots | Until you clear your browser data |
__cf_bm, cf_clearance | Cookies from Cloudflare, only if bot protection asks your browser for a check | Protects the site against bots | 30 minutes |
We do not use cookies for CSRF protection, rate limits or the weekly status: those work on our server. The Lookproof badge at the bottom of public pages is an image and sets no cookies.
Changes
When this policy changes, we update the date at the top. If a change is material, we will tell account holders by email at least 30 days before it takes effect.
Company details are on the About page.