Legal

Privacy Policy

Last updated: 18 November 2026

The short version

Who we are

MSGView (msgview.app) is built and operated by SSV Studio. Questions about this policy or your data: support@ssvstudio.dev, or the contact form at ssvstudio.dev.

Your files

When you open or convert a file, your browser reads it into its own memory and does all the work there. No part of the file is sent to our server. When you close or reload the page, it is gone. Exports (PDF, EML, HTML, TXT, ZIP) are created in your browser and saved straight to your device.

What we measure

Our own visit counter (Umami, self-hosted). It uses no cookies and no advertising identifiers, and it runs on our own server. It records the page you visited, the referring site, your country, browser, operating system and device type, and a handful of anonymous product events such as "a file was opened" or "a file could not be opened, and why", with the file type and a rough size range. After a file opens, the page also checks in your browser whether it displayed correctly (for example, no garbled characters and not blank), and may ask you "Did it show correctly?"; only that one-word result and your answer are recorded. It never records file names or file content. Visitors are told apart by a value that changes every month. To see how many people come back and how many use MSGView often, the counter also keeps a random number in your browser's local storage (mv-vid) for up to 12 months, together with how many files were opened in it this month (only the count, never which files). Your browser makes the number up at random: it is not built from your IP address, your device or anything else about you. It is sent with the counter's events so that a returning visit can be counted as the same visitor. On our server, these events and the number sent with them are kept for up to 13 months. In the European Economic Area, the United Kingdom and Switzerland it is created only if you consent in Google's consent message (to storing information on your device and to audience statistics); elsewhere it is created on your first visit. It is deleted if you choose "No thanks" on our banner or withdraw that consent, and you can delete it at any time by clearing this site's data in your browser. If you choose "No thanks" on our banner, this counter stops too.

Google Analytics. It is loaded with consent "denied" by default. Until you click "Accept", it sets no cookies and stores no identifier. After you accept, Google sets its analytics cookies (named _ga and _ga_*). You can change your choice at any time by clearing this site's data in your browser.

Server logs. Like every website, our web server records each request: the time, the address requested, your IP address, your browser's user-agent string and the referring page. We use these logs to keep the site running and secure. Older entries are deleted automatically; we keep only a rotating window of roughly the last one to two months.

Cloudflare. Our pages are delivered through Cloudflare, a content delivery network, so that the site loads quickly and can be reached from more countries. Every request (the time, the address requested, your IP address, your browser's user-agent string and the referring page) passes through Cloudflare's servers on its way to ours, and Cloudflare processes it to deliver the page and to protect the site from attacks, under its own privacy policy. Your files never reach Cloudflare either: they are not sent anywhere.

The Android app. If you install the MSGView app for Android, it reads your files on the phone and never sends them anywhere. Once a day it asks msgview.app whether a newer version exists; that request carries no file and no identifier. The app also counts anonymous usage and errors in the same counter as above, so that we can fix what breaks in it; the file, its name and its contents are never sent, and this counting cannot be switched off in the app. The full list is on the app's page.

Advertising

MSGView shows ads served by Google AdSense on its pages, including the page where you open files. Like ads on any website, Google's ad code runs in your browser while the page is open. MSGView itself never sends your files or their content to Google or to anyone else, and does not hand them to the ad code.

Google and its partners use cookies to serve ads, for example based on your earlier visits to this and other websites. Visitors in the European Economic Area, the United Kingdom and Switzerland are asked for consent first, through a Google-certified consent message. You can turn off personalised advertising in Google's Ad Settings, and learn how Google uses data at policies.google.com/technologies/partner-sites. You can also opt out of some third-party vendors' cookies at aboutads.info.

Cookies and local storage

Sharing

We do not sell your data. Visit data is shared with only two companies, as described above: Google, for analytics (cookie-free measurement pings until you choose, full measurement with cookies only after “Accept”) and for advertising; and Cloudflare, which delivers our pages. Our own counter and our server logs stay on our server in Finland (Hetzner, Helsinki).

Your rights

Depending on where you live (for example under the GDPR), you can ask what data we hold about you, and ask us to correct or delete it. Use the contact form at ssvstudio.dev. We hold no account data: MSGView has no sign-up and stores none of your files.

Children

MSGView is not aimed at children under 16. We do not knowingly collect data from them.

Changes

If this policy changes, we will update this page and the date at the top.