Legal
Privacy Policy
How we process personal data on our website and in the portal – clearly structured and easy to follow.
This is a translation for your convenience. Only the German version is legally binding: Datenschutzerklärung.
This policy covers the website (mailsecurity24.com), the portal (app.mailsecurity24.com) and our Instagram presence (section 15); for report data of business customers, the data processing agreement applies in addition.
1. Controller
Highlight PC, owner Günter Geisler, Emil-Pahl-Weg 4a, 85659 Forstern, Germany, email: office@mailsecurity24.com, phone: +49 8124 5268188. A data protection officer has not been appointed.
2. Roles
- For accounts, contracts, billing and the website, we are the controller.
- For the report data of business customers’ domains, we process data on behalf of the customer (Art. 28 GDPR). The customer is the controller for this data.
- For the report data of private customers, we are the controller ourselves.
3. Website
- Server logs: When the website is accessed, the server stores IP address, time, requested page, browser type and referrer for at most 14 days for security and troubleshooting (Art. 6 (1) (f) GDPR).
- Contact form: We use name, email address, company, subject, domain and message to handle your enquiry (Art. 6 (1) (b) or (f) GDPR). Messages are also stored in our system and deleted after 6 months.
- Free domain check: When you enter a domain, your browser queries its public DNS records via our portal (app.mailsecurity24.com). We process the domain entered and your IP address (Art. 6 (1) (b) or (f) GDPR). We cache the result for at most 10 minutes so that repeated queries do not burden the DNS servers. To limit abuse we count queries per IP address only as an encrypted short value (hash) that expires after 10 minutes. To see how the domain check is used, we store the checked domain together with the time, language, check result and whether the query came from our website – without your IP address and without any link to you. We delete these entries automatically after 30 days (Art. 6 (1) (f) GDPR; our legitimate interest is developing our service further).
- Free BIMI logo preview: When you upload a logo on our website, we transfer the file to our portal (app.mailsecurity24.com), convert it to the BIMI format there and show you the result as a watermarked image. We process the uploaded file, the title you enter and your IP address (Art. 6(1)(b) or (f) GDPR). The file and the result are deleted immediately after the conversion; we do not hand out the converted SVG file. To limit misuse, we count previews per IP address only as an encrypted short value (hash) that expires after one hour. We also count previews per day – without the IP address and without any link to you. Please only upload logos for which you hold the necessary rights.
- Audience measurement: To understand which content is read, we count visits with the analytics tool Independent Analytics, which runs exclusively on our own server. It sets no cookies and does not transfer any data to third parties. We record the page viewed, the referring page, time and duration of the visit, device type, browser and operating system, and the country and city derived from the IP address. We do not store the IP address itself: a hashed value is formed from the IP address and browser identifier using a key that changes daily, so visits cannot be attributed to the same person beyond that day. Logged-in users are not tracked. We delete the analytics data automatically after two years. The legal basis is our legitimate interest in improving our services (Art. 6 (1) (f) GDPR); you can object at any time (section 14).
- Cookies and embedded content: The website sets no cookies and does not store anything else on your device. Fonts and all content are loaded from our own server; we do not embed services of other providers. Only the portal (app.mailsecurity24.com) uses technically necessary cookies for signing in (see section 4). Exception: if you use the AI assistant (next item), it keeps the conversation and a window size you choose in your browser’s session storage for the duration of your visit; both are deleted when you close the tab. If you hide or minimise the assistant, your browser remembers this choice: when hiding, in session storage until you close the tab; when minimising, permanently in your browser’s local storage. This information is not transferred to us; you can undo it at any time via “Show AI assistant Monti” in the footer.
- AI assistant “Monti”: On the home page and the pages Features, Pricing and Contact you can ask our AI assistant questions. For this we process your questions and the course of the conversation. The answers are generated by a language model that runs exclusively on our own server (see section 12); no data is transferred to external AI services. To protect against misuse we limit the number of questions; for this we derive a short value from your IP address that changes daily and cannot be reversed – we do not store the IP address itself for this. We store questions and answers for 90 days in order to improve our offer; after that they are deleted automatically. If you send a contact request via the assistant, we process your name, your email address and – if provided – company and request as well as the conversation in order to answer your request. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in answering questions about our offer), for contact requests Art. 6(1)(b) GDPR (pre-contractual measures at your request).
4. Portal and account
- Account data: Name, email address, encrypted password, language, optional two-factor settings; organisation and role in the team (Art. 6 (1) (b) GDPR).
- Cookies: Login cookies as well as one cookie each for the language and the intermediate step of two-factor sign-in. In addition, two cookies only store your display choice: whether the menu is collapsed (“ms24_nav”) and which view you selected on the “Senders” page (“ms24_absender_ansicht”). All of them are technically necessary or required for the function you chose (Section 25 (2) TDDDG); consent is not required.
- Trusted devices: If your organisation allows it and you use two-factor sign-in, you can mark a device as trusted after entering the code. We then set the cookie “ms24_trust” with a random value for the period you choose (30, 60 or 90 days); your password is still required, only the code is skipped. We store only a cryptographic check value (HMAC) of it, plus a rough device label derived from browser and operating system (e.g. “Firefox on Windows”) and the times it was set up and last used. At most five devices per account are possible; you can remove them in the portal at any time. Changing your password, any change to two-factor sign-in or the organisation switching the feature off revokes all devices. We set this cookie only at your request; it is necessary for the function you chose (§ 25 (2) no. 2 TDDDG, Art. 6 (1) (b) GDPR).
- Passkeys: Instead of a password and code, you can sign in with a passkey (fingerprint, face recognition or device PIN). The private key remains on your device; we do not receive any biometric data. We only store the public key, an identifier of the passkey, a counter to detect copied keys, the name you assign (e.g. “iPhone”) and the times of setup and last use (Art. 6 (1) (b) GDPR). You can remove passkeys in the portal at any time; they are deleted together with your account.
- Log: Security-relevant actions (sign-in, changes to team, domains, plan) are logged with time and user (Art. 6 (1) (f) GDPR) and deleted after 12 months.
- Emails: We send confirmations, sign-in codes, alerts, billing notices and messages about support requests via our own mail server. Email programs load the logo in our emails from our server; we do not analyse these requests and do not use tracking pixels. For troubleshooting, sending can be logged with recipient, subject and content for a limited period of at most 14 days (Art. 6 (1) (f) GDPR); the log is deleted afterwards.
- Protection report: From the Premium plan, we send owners and administrators of an organisation a protection report on the previous month by email at the beginning of each month, with a PDF attached. It contains summarised figures and results for the organisation’s domains; for this we use the recipients’ name and email address (Art. 6 (1) (b) GDPR). We generate the PDF only for sending and delete it afterwards; we only store for which month, when and to how many recipients the report was sent. You can unsubscribe via the link in every report email without signing in, or in the settings; the report remains available in the portal. If your organisation is managed by an agency, the report may carry the agency’s name and logo.
- AI assistant “Monti”: In the portal, an AI assistant can answer questions about your email protection. For this we process your question, the previous course of the conversation and the details of your organisation needed for the answer, such as the status of your domains and add-ins. The answers are generated by a language model that runs exclusively on our own server (see section 12). No data is transferred to external AI services, and your questions are not used to train a language model. We store questions and answers for 90 days in order to improve our help, for example to add missing answers; after that they are deleted automatically. If you choose to hand over to support, the conversation is stored as a support request (see section 11). The legal basis is Art. 6(1)(b) GDPR (provision of the agreed service) and Art. 6(1)(f) GDPR (legitimate interest in understandable and continuously improved help). You can hide the assistant at any time under Settings → Appearance.
5. DMARC and TLS reports
Content: Reports contain IP addresses of the servers that sent emails on behalf of your domains, counts and check results (SPF, DKIM, DMARC), the domains concerned, and the name and contact address of the reporting organisation. Aggregate reports do not contain content or recipients of individual emails; we do not process forensic reports (ruf).
TLS reports: From the Premium plan, we additionally receive SMTP TLS reports (RFC 8460) once you set them up for a domain. They show whether emails to your domains could be delivered encrypted and contain the number of successful and failed delivery attempts, the type of failure, the IP address of the sending server, the names of the receiving mail servers and the name and contact address of the reporting organisation. They do not contain content, senders or recipients of individual emails. The reports reach us by email or via an encrypted web interface.
Enrichment and checks: To classify senders, we pass individual data to the following parties via DNS lookup:
| Recipient | Data | Purpose |
|---|---|---|
| Team Cymru (USA) | IP address of the sending server | Determine network operator and the country where the network is registered |
| SpamCop, PSBL, UCEPROTECT | IP address of the sending server | Blocklist check |
The IP addresses mostly belong to mail servers of companies and providers; only in exceptional cases can they be attributed to a person.
Retention: DMARC and TLS reports and their analyses are deleted automatically after the retention period of your plan (trial 30, Basic 45, Premium 90, Business and Agency 365 days).
6. DNS tools and mail server checks
We look up entered domains publicly in the DNS. We do not store results permanently; to limit lookups, we count them per user for ten minutes. A private DKIM key generated in the portal is shown only once and is not stored.
Mail server checks: For your domains we regularly connect to the mail servers listed in the DNS to check encryption (STARTTLS) and certificate, and we retrieve a published MTA-STS policy from https://mta-sts.<your domain>. We do not transmit any messages. We only store the technical results (server name, IP address, TLS version, certificate details, content of the policy); they are replaced at the next check and deleted when the domain is removed.
BIMI logo studio in the portal: We store uploaded logos, source images and results in your organisation until you delete them or the organisation is deleted. Hosted logos can be retrieved at a public address because mailboxes load them from there (Art. 6(1)(b) GDPR).
7. Checking suspicious emails (reporting address and Outlook add-ins)
Employees of our customers can forward suspicious emails to their organisation’s reporting address or have them checked with the “Check with Mailsecurity24” button in Outlook. The email (headers, text, links, attachments) is transmitted to our portal in encrypted form, checked automatically, and the result is shown or sent to the reporting employee. The content of the email is processed only for the duration of the check and is not stored. We store key data of the report (time, sender, subject, result, reasons, reporting mailbox, reporting channel) and any feedback from the employee on the assessment with an optional reason, each for 90 days.
To improve detection, we store anonymous check features for each check (e.g. whether sender authentication passed or a link deviates) without text, subject or addresses and evaluate them together with the feedback on our own server; they are not passed on to external AI services. We delete these features after 180 days.
The Outlook button for Microsoft 365 signs in with the employee’s Microsoft account (Microsoft Entra ID) and retrieves only the email being checked via Microsoft Graph; if desired, it moves it to the junk folder. The Windows add-in for classic Outlook transmits a random device ID, the computer name and the add-in, Windows and Outlook versions when Outlook starts, so that the customer’s IT can see the installations in the portal and updates can be provided; user names and email addresses are not transmitted. The Thunderbird add-on likewise transmits a random device ID, the add-on and Thunderbird versions and the operating system when it starts. With every check, both add-ins also send this device ID so that the customer’s IT can block individual devices. We delete this information 180 days after the last start. If an organisation enables automatic pre-checking, the Windows add-in checks incoming emails from external senders without a click; the same rules as above apply, and no report email is sent.
We process this data on behalf of our customers (Art. 28 GDPR, see the data processing agreement).
8. Payment via Stripe
Payments are processed by Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, Ireland. We transmit name, email address, billing address and, where applicable, VAT ID; the customer enters payment details such as card numbers directly with Stripe, and we do not receive them (Art. 6 (1) (b) and (c) GDPR). Stripe is an independent controller for payment processing; a transfer to Stripe, Inc. in the USA is possible and is based on the EU-US Data Privacy Framework.
9. VAT ID check
If businesses from other EU states provide a VAT ID, we check it via the VAT Information Exchange System (VIES) of the European Commission. We store the result, name and request identifier as tax evidence (Art. 6 (1) (c) GDPR).
10. Accounting
We transfer invoices and credit notes with invoice number, amounts, tax details and customer name to our accounting software Lexware Office (Haufe-Lexware GmbH & Co. KG, Munzinger Straße 9, 79111 Freiburg, Germany). For businesses in other EU countries with reverse charge, a contact with address and VAT ID is also created there (Art. 6 (1) (c) GDPR).
11. Support requests
Requests you submit in the portal under “Support” or send by replying to our notifications by email are handled in our own ticket system in the portal. It runs on our servers at netcup GmbH in Germany (see section 12); no external service provider is involved, apart from the storage of our backup copies (also section 12).
- Data: Your name, your email address, name and identifier of your organisation, as well as subject, category, urgency, content and attachments of your messages and our replies, the processing status and – if you provide one – your rating.
- Replies by email: We send notifications via our own mail server with a reply address assigned to the respective request. If you reply to it, the portal retrieves your message from our mailbox and assigns it to the request. It is only accepted if the sender address belongs to a member of your organisation. We evaluate our mail server’s results on the authenticity of the message (SPF, DKIM, DMARC) and log anomalies (Art. 6 (1) (f) GDPR).
- Attachments are checked on our server with a virus scanner (ClamAV) before they are released; infected files are deleted.
- Legal basis: Art. 6 (1) (b) GDPR insofar as the request concerns your contract, otherwise Art. 6 (1) (f) GDPR (handling of enquiries).
- Retention: Requests are kept as long as your organisation exists and are deleted together with it. If you delete your personal account, we remove your name from your messages in the requests; your email address is deleted together with the account.
12. Hosting
Website and portal are operated by netcup GmbH, Emmy-Noether-Straße 10, 76131 Karlsruhe, Germany, on a server in its data centre in Nuremberg, Germany. A data processing agreement is in place with the hosting provider. We transfer backup copies in encrypted form to Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany, where they are stored in its data centre in Falkenstein, Germany, for up to four weeks. A data processing agreement is also in place with Hetzner.
13. Retention
We delete account data 30 days after the end of the contract or after the end of a trial without booking. We retain invoices and accounting records for eight years in accordance with tax regulations.
14. Your rights
You have the right of access, rectification, erasure, restriction of processing, data portability and objection to processing based on legitimate interests (Art. 15–21 GDPR). You can lodge a complaint with a supervisory authority, for example the Bavarian Data Protection Authority (BayLDA), Promenade 18, 91522 Ansbach, Germany. We do not make automated decisions within the meaning of Art. 22 GDPR.
15. Instagram presence
We operate a business profile on Instagram (instagram.com/mailsecurity24), a service of Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland (“Meta”). We do not embed Instagram content on our website; data only flows to Meta when you open Instagram yourself.
- Processing by Meta: When you visit our profile or interact with our posts, Meta processes your data under its own responsibility, see the Instagram Privacy Policy. We have no influence on this processing.
- Statistics (Insights): Meta provides us with aggregated statistics on the use of our profile, such as reach, interactions and approximate age groups and regions. We cannot identify individual persons from them. We are jointly responsible with Meta for this processing (Art. 26 GDPR); the agreement is available at facebook.com/legal/terms/page_controller_addendum. Under it, Meta assumes primary responsibility for processing Insights data and for fulfilling your rights. You may also contact us; we will then forward your request to Meta.
- Comments and messages: We only use what you write to us via Instagram to answer your request and to communicate with you.
- Legal basis: Art. 6 (1) (f) GDPR; our legitimate interest is presenting our offering and communicating with prospects and customers. If a message concerns a contract with us, Art. 6 (1) (b) GDPR applies.
- Transfer to the USA: Meta may transfer data to Meta Platforms, Inc. in the USA; this is based on the EU-US Data Privacy Framework.
- Your rights: The rights under section 14 apply. You manage your privacy settings in your Instagram account.
Last updated: 13 October 2026
