10 KiB
Privacy policy
Overview
FairEmail does not send account information and message data to third party servers.
FairEmail does not allow other apps access to message data without your approval.
FairEmail does not require unnecessary permissions. For more information on permissions, see this FAQ.
FairEmail does follow the recommendations of this EFF article.
FairEmail is 100 % open source, see the license.
Error reporting via Bugsnag is opt-in, see here for more information.
FairEmail adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google API Services are used only to authenticate Gmail accounts through OAuth.
FairEmail can use these services if they are explicitly enabled (off by default) or are explicitly used by you:
- ipinfo.io – Privacy policy
- Spamhaus – Privacy policy
- Spamcop – Privacy policy
- Barracuda – Privacy policy
- Thunderbird autoconfiguration – Privacy policy
- LanguageTool – Privacy policy
- Gravatar – Privacy policy
- Libravatar – Privacy policy
FairEmail can access the websites at the domain names of email addresses (username@domain.name) if Brand Indicators for Message Identification (BIMI) or favicons were explicitly enabled (off by default).
FairEmail obviously will access the configured email servers.
FairEmail is GDPR compliant.
Summary of shared data
This table provides a complete overview of all shared data and the conditions under which data will be shared:
| Service | Data sent | When the data will be sent |
|---|---|---|
| Bugsnag | Information about warnings and errors | If error reporting is enabled, upon detecting an abnormal situation |
| ipinfo.io | IP (network) address of domain names of links or email addresses | Upon pressing a button in the link confirmation dialog |
| Spamhaus | IP (network) address of domain names of email addresses | If spam blocklists are enabled, upon receiving a message |
| Spamcop | IP (network) address of domain names of email addresses | If spam blocklists are enabled, upon receiving a message |
| Barracuda | IP (network) address of domain names of email addresses | If spam blocklists are enabled, upon receiving a message |
| Mozilla autoconfig | Email address of email accounts | Upon configuring an email account |
| LanguageTool | Entered message texts | Upon long pressing the save draft button |
| Gravatar | MD5 hash of email addresses | If Gravatars are enabled, upon receiving a message |
| Libravatar | MD5 hash of email addresses | If Libravatars are enabled, upon receiving a message |
| BIMI | Domain name of email addresses | If BIMI is enabled, upon receiving a message |
| Favicons | Domain name of email addresses | If favicons are enabled, upon receiving a message |
| Email server | Login credentials, messages sent | Upon configuring and using an account and upon sending messages |
Definitions of terms
This section defines some terms and words. Knowing those terms will help you understand the following sections.
- Data subject – the user of the app
- Personal data – any data the data subject could be identified with
- Data controller – the person / entity providing the app
- Data processor – the person / entity providing the app
- Sub-processor – a third party processing data
- Data protection officer – the person responsible for any privacy related enquiries
Contact details
Please feel to contact me if you have any concerns:
Marcel Bokhorst
Van Doesburg-Erf 194
3315 RG Dordrecht
the Netherlands
marcel+fairemail@faircode.eu
As FairEmail is a personal project of a single developer, the developer is both the data controller as well as the data protection officer. For any legal issues, the place of jurisdiction is Dordrecht, the Netherlands.
A. General information on data processing
I. Scope of personal data processing
This privacy policy / data protection declaration applies to the Android app FairEmail.
The data processor only processes personal data insofar as absolutely required for providing a functioning email client as well as the explicitly requested services. Users' personal data is usually only processed if required for fulfilling contractual or legal obligations or with the user's consent.
II Purpose of data processing
The purpose of any data processed is to provide you with the service requested. The app by default exclusively processes data that is necessary for the proper functioning of the app and its intended purpose of being an email client.
III. Data storage and data deletion
By default, all data (both personal and non-personal) remains on the data subject's Android device for as long as not explicitly sent or shared by the data subject. The data stored on the data subject's device can be deleted by the data subject at any time.
IV. Sub-processors
The services of all sub-processors are disabled by default. The data subject's data is sent to and processed by sub-processors if and only if explicitly enabled or requested by the data subject.
The sub-processors are:
- ipinfo.io – Privacy policy
- Spamhaus – Privacy policy
- Spamcop – Privacy policy
- Barracuda – Privacy policy
- Thunderbird autoconfiguration – Privacy policy
- LanguageTool – Privacy policy
- The hoster of a domain the data subject has received an email from, if showing favicons is enabled
- The hoster of a domain the data subject has received an email from, if Brand Indicators for Message Identification (BIMI) is enabled
- The data subject's email service provider, if an email account or identity is added
V. Permissions
The app only requests permissions that are necessary for the expected behavior of an email app. For more information on permissions, see this FAQ.
VI. Logging
The app does not send any log entries to the data processor by default. The error reporting system utilizes Bugsnag and is disabled by default. See this FAQ for more information.
VII. Legal basis
FairEmail is fully GDPR compliant. The legal basis for any data processing is Art. 6 (1) a - c GDPR.
B. Support requests
I. Description and scope of data processing
The data subject may contact the data processor to request support through channels offered by the data processor. When the data subject contacts the data processor, any provided personal data is stored by the data controller.
II. Purpose of data processing
The personal data is exclusively processed for finding a specific solution to support queries whilst recording and/or processing them. It is essential in this respect for the data controller to be able to contact the person requesting support.
III. Sub-processors
The data processor utilizes the services of the following sub-processors in order to process support requests:
- Google LLC, if support request sent via email – Privacy policy
- XDA forums, if support requested via the FairEmail XDA forum thread – Privacy policy
IV. Legal basis
Any support requests are sent voluntarily by the data subject, including any personal data that might be attached. As such, the explicit consent as outlined in Art. 6 (1) a GDPR forms the legal basis for processing.
Copyright © 2018-2022 Marcel Bokhorst.