Privacy

inlark is an app on your computer, not a service. There is no inlark account, no server of ours that sees your mail, and no telemetry. This page lists what the app and this website send to anyone other than your own mail provider, and what you can turn off.

The app

Your mail

Your messages go between your computer and your mail provider over an encrypted connection, and nowhere else. The index that makes search fast, your drafts and your settings are files in your own user folder.

Passwords and sign-ins

A login you ask inlark to remember is stored on your computer, encrypted using your operating system’s credential protection. Where that isn’t available, inlark asks first, and then keeps it in an unencrypted file only your user account can read.

Usage data

None. inlark sends no telemetry, analytics or crash reports. Copy diagnostics in Settings puts a redacted summary on your clipboard and sends nothing.

Setting up an account

inlark looks up your address’s domain in DNS and asks the domain, or wherever the domain redirects, for its published mail settings. Only if that finds nothing, and the domain isn’t recognized as Google’s or Microsoft’s, it asks Thunderbird’s public settings directory, which receives the domain and never the full address. Set up manually skips all of it.

Updates

Installed from the Windows, macOS or Linux installer, inlark asks GitHub shortly after it starts, and then every six hours, whether a newer release exists, and downloads it from there. GitHub receives your IP address and a random ID the updater creates once and keeps in inlark’s data folder. There is no setting to turn this off. The Flatpak and Nix builds don’t check; they are updated through Flatpak and Nix.

Images in email

On by default, with one switch: Settings, Privacy, Load remote images. When you open a message, inlark requests its images from the addresses the message names, following redirects. Those servers, which can be the sender’s or a tracking or image service the sender uses, receive your IP address and can learn that you opened the message. inlark sends no cookies and no referrer, and skips images marked as hidden or as one pixel in size, which does not stop all tracking. Nothing else a message points to is loaded. In encrypted mail, images stay blocked until you ask for them.

Sender pictures

Under the same switch. For the picture beside a sender, inlark asks Gravatar, with a hash of the sender’s address, and then the website of the sender’s domain and of its parent domains, or wherever those sites keep their icons. If none has one, Twenty Icons receives the domain, and DuckDuckGo only if Twenty has none.

Links and unsubscribing

Links open in your browser, and inlark fetches nothing from them. That includes the links in inlark’s own setup guides to Google’s and Microsoft’s pages; the ones to Google carry the address you are setting up, so that Google opens the right account. Unsubscribe acts only when you select it: it sends the sender’s one-click request, opens the sender’s unsubscribe page, or prepares an email for you to send.

Encryption keys

When encryption is switched on for an identity, inlark looks for recipients’ public keys at their own domains. Creating a key checks your own address the same way, and you can look up an address by hand. Each lookup shows that domain the address being checked. inlark uses no public keyserver and runs no key directory. Mail sent from such an identity carries your public key in a header, and encrypted mail can carry the public keys of its visible recipients too. Switching encryption off for an identity stops its automatic lookups.

Signing in with Microsoft

Happens on Microsoft’s page in your browser. inlark passes along its app ID and the address you typed, and keeps what Microsoft hands back the way it keeps a password. What inlark asks Microsoft for

Spell checking

On Windows and Linux, the spell checker downloads its dictionary from Google’s servers, so Google receives that request and your IP address. What you type is checked on your computer and never sent. There is no setting in inlark to turn the download off. macOS uses its own spell checker and downloads nothing.

Uninstalling on Windows

Removing inlark by hand opens a short, optional survey in your browser, by way of this website. The link carries inlark’s version number and nothing else. What you choose to answer, including an email address if you leave one, is stored by Tally, which runs the form for us.

This website

Hosting

inlark.com is served by Cloudflare, which processes your IP address and the pages you request, to deliver them and to protect the site. It also keeps traffic statistics, and uses some network and security data for its own purposes. If a page fails to load, your browser may report the failure to Cloudflare. The site’s own code sets no cookies, contains no analytics or tracking scripts, and loads no fonts, scripts or images from other servers.

Downloads

Installers are hosted by GitHub. When the download page recognizes a system it has an installer for, it can start the download by itself, and from then on your browser is talking to GitHub.

Links that lead elsewhere

Donate leads to Buy Me a Coffee, and the reminder on the mobile download page can open Google Calendar or Outlook. They only hear from you if you follow the link.

Who is responsible

inlark and this website are run by Paul Köck in Feldkirch, Austria, who is the controller under the GDPR. The full address is in the imprint, and questions about privacy go to legal@inlark.com.

The app sends us no telemetry, analytics or crash reports, and no inlark service receives your mail. Visits to this website, including the ones the app’s links and the Windows uninstall survey lead to, and anything you choose to send us are handled as described here.

Serving this website and keeping it safe is why your request is processed, on the basis of our legitimate interest in doing so (Art. 6(1)(f) GDPR). Cloudflare processes the traffic and its logs on our behalf under its data processing agreement, which covers processing outside the EU through the EU–US Data Privacy Framework and the EU’s standard contractual clauses. For logs processed on our behalf, that agreement limits retention to when they are no longer needed to perform it or the agreement ends, whichever comes first, unless the law requires further retention. We keep no copies. Cloudflare also processes some network and security data for its own purposes; its privacy policy describes how it uses that data and the criteria for keeping it.

An answer to the uninstall survey rests on your consent (Art. 6(1)(a)), and we use it to improve inlark. You can withdraw your consent at any time by asking us to delete your answer; this does not affect the lawfulness of processing before withdrawal. An email is used to answer you, and an issue or comment on GitHub, which is public, to maintain inlark; both rest on our legitimate interest in supporting and improving it (Art. 6(1)(f)). Survey answers and emails are kept for as long as they are needed for that and deleted when you ask. Issues and comments stay on GitHub until they are deleted there, and we keep no copies of them. A donation is handled by Buy Me a Coffee, which shows us what you entered there; we keep the record because, and for as long as, tax law requires (Art. 6(1)(c)).

Under the GDPR you can ask what is held about you, have it corrected, deleted or restricted, receive it in a portable form, and object to its use. You can also complain to a supervisory authority; in Austria that is the Datenschutzbehörde.

Cloudflare and Tally process what is described above on our behalf where they act as our processors. Everyone else named on this page receives it directly from you and decides for itself what to do with it. Several of them are in the United States. Their policies say how they handle it: Cloudflare, GitHub, Tally, Buy Me a Coffee, Gravatar, Twenty, DuckDuckGo, Thunderbird, Microsoft, Google.

Last updated 19 November 2026.