[APP][5.0+] FairEmail - Fully featured, open source, privacy oriented email app

Search This thread

Oswald Boelcke

Senior Moderator / Moderator & RC-RT Committees
Staff member
Wouldn't it be better to remove @Dr-Bob as a whole. Dr-Bob was clearly created yesterday with the sole purpose to escalate this situation and to get on Marcels nervs. It reminds me off this Mr kouch, Chef koch character(i don't remember the exact name) in the XprivacyLua thread a couple off years ago. I wouldn't be surprised if it's the same person.
He will open a new account and it would continue. I mean really, only ignoring helps.
Thanks very much for your concerns. As much as @M66B Marcel is and has always been friendly and polite, we don't want to appear like a "XDA police". We don't censor XDA but we evaluate every post we become aware of against the forum rules and only against these rules; if a post violates the rules it gets partially or completely removed. And our policies task us to more mediate than to moderate i.e. we start with a friendly conversation, friendly and polite like Marcel, to give everybody a chance to be a valuable member on XDA. Most of the times we succeed with this approach but sometimes we don't achieve this objective. And it's different from case to case, how quickly we do realise that this objective will never been achieve.
 

gvamp

Senior Member
Dec 25, 2015
99
52
Stuttgart
I use this Mail Client since a year or so as free version and it's a giant. I rated a 5* today and hope this helps a little bit. Regarding the 3 or less star receptions, I have to say that these are very rare and most times from simple people, you can't avoid this. The rating is at 4.8 and HELL, this is fantastic. I don't know, if any other app with many ratings and such a good sum exist anyway. Please, @M66B , don't make so much pressure for yourself. All the best to your girlfriend and you. Have a nice day. YOUR APP IS AWESOME !!!
 

sqwrl

New member
May 21, 2022
2
0
@M66B Thank you for your excellent software. Bought Pro on FairEmail only a week ago after having used it for years, just to say thanks. Glad now I did. I would be very happy to support you via non Google means going forwards if that is what you choose.
 

Donislawdev

Member
Feb 25, 2017
12
5
The few euros I receive in return for what's being offered and the fun of developing things are no compensation for the thousands of questions I answer every month, for unfair Play store reviews and for stress about unclear Google requirements.
Hello, I would like to thank you a lot for your great work, I got the PRO version of NetGuard + FairEmail, and they are both great apps, thank you a lot for developing them, and support.

I think you should just stop caring about Play store reviews, there will always be someone unhappy, that's normal. But I know it's hard. Remember that the apps are 100% open source/free (no ads/IAP, there is only paid PRO version), so you don't need to keep up with the user's support, you got your own life, and developing apps just takes a lot of time, when support consume probably a lot more time :-}


If you need a break you should take it, I know it can be hard, but you are a great developer, which had given Android users are a lot of awesome apps, I hope you will stay with us :-}
 

M66B

Recognized Developer
Aug 1, 2010
26,304
56,751
This is the message I just received from Google:

As previously advised, your app, FairEmail, privacy aware email (eu.faircode.email) on open testing track for APK version 1898 is uploading users' Contact List information:

  • without posting a privacy policy in both the designated field in the Play Console and from within the Play distributed app itself
  • without an adequate prominent disclosure
Please kindly note that a valid privacy policy must be posted in both sections; the designated field in the Play Console and from within the app as well. Your privacy policy must disclose the types of personal and sensitive data the app accesses, collects, uses, and shares; and any parties with which any personal or sensitive user data is shared (e.g: users' contact list information).

Prior to the collection and transmission, you must provide an in-app disclosure that prominently highlight how the user data will be used, describe the type of data being collected and have the user provide affirmative consent for such use. Please include the uploading of users' Contact List information in your prominent disclosure to fix this issue.

Please make sure to deactivate the non-compliant APK version 1898 (open testing track) and increment the version number of APK before resubmitting your app for further review. Kindly note that all active versions of your app must be compliant with our policies including all release types (e.g. Internal test, Closed, Open).

You may read this article that describes the best practices for providing prominent disclosure. You can learn more about prominent disclosure and privacy policy requirements in the Developer Policy Center or in this video. You can also read through the personal or sensitive user data page for more details.

As much as I'd like to help, I’m not able to provide any more detail or a better answer to your question. In our previous email, I made sure to include all the information available to me.

If you have a different question about the Developer Program Policies, please let me know. Thanks for your continued support of Google Play.

The bigger font was in the original message highlighted.
 

M66B

Recognized Developer
Aug 1, 2010
26,304
56,751
I thought a human had contacted u and set up a call for Tuesday. Does this message supercede the call?
The email "conversation" is the "official" developer communication channel and the human who will be calling me (Policy and Privacy department) is an out of band channel. The purpose of the call is to "answer any questions you may have". So, what that will bring remains a question mark for now.
 
  • Like
Reactions: Austinredstoner

mkasimd

Senior Member
Apr 7, 2021
216
438
Düsseldorf
@M66B it needs a lot of nerves and patience to escalate things and escape from the 1st level support stupidity.
That one depends on the company. But in large corporates, that's the case unfortunately.

I'm glad it's totally different at my workplace. The first level guys are required to say "sorry, I don't know the answer to this. I'll redirect your request and we will get back to you shortly". Because that one action makes the difference between trying to solve an issue (customer's problem) or trying to get rid of the issue (the customer himself).

It's tiring when a company thinks of the customer as an issue to get rid of instead of looking into the problem the customer faces as the issue to solve. And corporates tend to act so.

That's among the reasons I prefer SMBs (small/medium businesses) over corporates whenever alternatives exist. Even if the SMB alternative costs slightly more. If you get better service, it's worth every penny. Too bad, Google has a de-facto monopoly over the Android Apps store business.. I'll refrain from any too political statement, but there's a lot politics (especially on EU level) could do to ensure customer rights are upheld in such situations..

I hope your phone call on Tuesday works better, @M66B. Talking to a real person on the phone makes a huge difference compared to writing letters. But you should prepare a cheat sheet with several keywords and key arguments on it before the call. Because trust me, Google will be prepared to face you and you will need to argue well even if put under some form of pressure or if the person on the phone tries to control the flow of your conversation. I wish you good luck and thanks for doing this!
 

M66B

Recognized Developer
Aug 1, 2010
26,304
56,751
...

I hope your phone call on Tuesday works better, @M66B. Talking to a real person on the phone makes a huge difference compared to writing letters. But you should prepare a cheat sheet with several keywords and key arguments on it before the call. Because trust me, Google will be prepared to face you and you will need to argue well even if put under some form of pressure or if the person on the phone tries to control the flow of your conversation. I wish you good luck and thanks for doing this!

I am prepared, I only want answer to three simple questions:
  1. Which contact info is being sent?
  2. When is it being sent?
  3. To where is it being sent?
I am not going to argue or pressure anyone and just see where this goes.
 

yasd4711

New member
May 21, 2022
1
1
@M66B Hi Marcel, thank you very much for providing such a great email app. A while ago I was looking for an email app that supports S/MIME certificates. FairEmail was the only app that I've found. And I was impressed by the privacy features. The need to acknowledge the URL when clicking on a link. The automatic suppression of tracking images. I let me feel more safe using email at all.

It's extremely bitter that Google accuses this very app to be spyware.

I absolutely do understand your frustration. About this accusation, Googles non-handling of it, and about unqualified and rude user comments, too. And about the permanently changing intransparent policies, of course. Not to mention the high-frequent API updates from one beta stuff to the next alpha version, and so on. Plus vendors producing their own device-dependent botch (e.g. battery optimization).

Android's success is primarily grounded on the work of "small" developers that produced tons of apps for free. And, yes, pro-features for roundabout 5 € are even for free IMHO - it's not "paid" or "bought" (most people cannot even image how much work it is to write an app). Now, that their job is done, Google is going to get rid of them. All these policy changes, API updates, vendor quirks and legalese cannot be handled by a single person or a small team, especially not in their spare time.

IMHO nowadays your app and team must be big enough to get whitelisted within Android to work correctly. Very sad.

I'm sadly missing a real open-source operating system for smartphones, or even better an open-source smartphone. Maybe it's time to return to a dumb phone.

Once again, thanks for your effort and all the best to your girl-friend and you.

P.S.: I've dropped a very, very small but appreciated app for similar reasons, too. After withdrawing it from the store I wanted to delete my developer account and had to learn that it's not possible. Contacting Google was a similar loop of policy repetition. It seems to be unlawful to me that I cannot delete my account but it's not worth the effort to prove it. The reasoning by Google that the account cannot be deleted because users may sill reload the app technically doesn't make sense to me. I think it could be solved differently if they wanted.
 
  • Like
Reactions: SigmundDroid

M66B

Recognized Developer
Aug 1, 2010
26,304
56,751
App läuft einfach / sehr gut. Der Winamp unter den Mail Clients. 👍😉 ...was soll das, die app aus Trotz gegenüber Google, aus dem Playstore zu nehmen? Ich habe für den E-MAIL Client Geld bezahlt und würde ihn auch gerne weiterhin auf dem nächsten Smartphone nutzen. Sollte ich in Zukunft nur noch den anderen Softwareschrott benutzen dürfen, gehe ich weg aus dem Android - Ökosystem. Das ist doch echt KINDERGARTEN hier.

Link

This is after I have explained the situation :-(
 
  • Angry
Reactions: _mat_

Itcouldbeyou

Member
May 14, 2010
29
21
I am prepared, I only want answer to three simple questions:
  1. Which contact info is being sent?
  2. When is it being sent?
  3. To where is it being sent?
I am not going to argue or pressure anyone and just see where this goes.
Maybe it is a dumb question. But did Google properly understand that you don't think you violate their Code? Maybe you should sprinkle an "allegedly" into your 3 points. Sure it would make no sense to ask Google where, when and what is sent if "you coded the malicious feature". But the people responding are probably not the best paid people. And I think they have to answer to a lot of dumb and malicious people.
 

truephoenix

New member
May 21, 2022
2
9
Hello,

I am also a (so far) very satisfied user of FairEmail. After suddenly not finding FairEmail in the Google Playstore anymore, I came across the Golem news article and forum here.

Just an amateur assessment from me (I can of course also be completely wrong!):

It seems to me that Google and M66B are "talking past each other". As I understand it, Google only complains that there is no privacy policy or that it does not contain all the relevant information. This is probably necessary as soon as the app sends any data (which every email app does). Not to mention favicons, third party services or pro versions linked to an account / email.

- without posting a privacy policy in both the designated field in the Play Console and from within the Play distributed app itself

- without an adequate prominent disclosure

Source: https://forum.xda-developers.com/t/...vacy-oriented-email-app.3824168/post-86923901

And at least I think FairEmail's privacy policy is really a bit "short":

For comparison, the very detailed privacy policy from Aqua Mail

Perhaps you can compare the two privacy policies (including the areas of payment and third-party services) and see what else FairEmail needs to do to satisfy Google.
 
Last edited:

Top Liked Posts

  • 2
    Version 1.1955 is available on GitHub now and in the Play store test program after Google's approval.

    Changelog/download:
    https://github.com/M66B/FairEmail/releases

    Generated icons (letter, identicon) will be cached now because after some measurements it appeared that reading cached files is faster than generating icons on the fly.
    1
    What you can try is increasing the sqlite cache size, which you can do by enabling debug mode in the miscellaneous settings. Try 20-30% and don't forget to confirm with the check mark button.

    Which Gmail animation do you mean exactly? If you mean a blurred outline view, this is not something I want to add to FairEmail for a number of reasons.
    Could the Hide from recent apps... setting have an impact on the warm start delay? (Just guessing.)
  • 20
    QUESTION ABOUT FAIR EMAIL OPTIONS:
    Assuming the starting point of no on-device Google Account...

    Q: Which of these Fair Email Google mail server options is "most" private?

    1. 2SV/2FA (using any of a half dozen secondary methods), or,
    2. What Fair Email terms "GMail (Android)", or,
    3. What Fair Email terms "GMail (OAuth)".

    Note Marcel knows the answer, so he can instantly nip this tangent in the bud by answering that question in a single word... (where I suspect the answer is undoubtably #3 but others strongly think it's #1 apparently, so I could be wrong - but it's NEVER gonna be #2.

    The desired single word answer is "none". Google scans all your messages and you can only hope that the gathered information isn't used in an un-private way. Option 1 (assumed to be app passwords) and option 3 do not send extra information to Google. Option 2 requires an on-device Google account. You can control the sync options of a Google account via the Android settings. If these options work as expected and are turned off, no information should be sent to Google. This applies to all other Google services and apps, like Maps and Drive, too. You'll need to go into the settings and turn things off and trust that Google honors this.

    I expect to see no more messages about this subject anymore, with no exceptions for anyone. If you want to continue discussing about this, you should create a new XDA thread for this.
    16
    The next version will have optionally VirusTotal integration, so you can check attachments easily:

    Screenshot_20220723-102554.png
    14
    Version 1.1951 is available on GitHub now and in the Play store test program after Google's approval.

    Changelog/download:
    https://github.com/M66B/FairEmail/releases

    There is a new option in the advanced section of the connection settings page to disable using insecure connections for images, including favicons. Insecure means http instead of https, an invalid server certificate (for example an expired certificate) or a redirect via http (for example https > http > https).

    Unfortunately, there are too many images being referenced in an insecure way, explaining why this option is default off.
    13
    That guy really needs his email. I wonder who he thinks will maintain the app after he killed you 🤔
    Given the messages I just received I am pretty sure this guy is reading here.

    To this guy: I am doing my best to hold this project together and what you are doing isn't helping, on the contrary. Instead, if the app is dear to you, you can better help and complain to the right people, mainly Google.
    13
    Version 1.1941 is available on GitHub now.

    Changelog/download:
    https://github.com/M66B/FairEmail/releases

    Besides a series of small improvements and minor bug fixes, VirusTotal Integration was added. Please see this FAQ for more information about configuring and using this new feature:

    (181) How do I use VirusTotal?

    Note that the app hasn't been restored in the Play store yet. For the latest status updates, please see here:

  • 242
    ic_launcher.png

    FairEmail
    Open source, privacy friendly email app for Android

    banner7_long.png


    See here for a description:
    https://github.com/M66B/open-source-email/

    See here for screenshots:
    https://email.faircode.eu/#screenshots

    Downloads:
    https://github.com/M66B/open-source-email#user-content-downloads

    Frequently asked questions:
    https://github.com/M66B/open-source-email/blob/master/FAQ.md

    Please read this before requesting a new feature:
    https://github.com/M66B/FairEmail/blob/master/FAQ.md#user-content-get-support

    This XDA thread is about using the latest version of FairEmail.

    For support on authorizing an account you should consult the documentation of your provider, see also here.

    Off topic comments are allowed as long they are related to FairEmail and are in the general interest of the followers of this thread.

    Discussion of purchases is not allowed here, please contact me via here instead.
    69
    How was the call with Google today, Marcel?

    Google was pretty friendly and cooperative and told me the favicons are indeed the problem, and it can/should be fixed by updating in the privacy policy to "disclose how your app accesses, collects, uses, and shares user data":

    Privacy Policy​

    All apps must post a privacy policy in both the designated field in Play Console and within the app itself. The privacy policy must, together with any in-app disclosures, comprehensively disclose how your app accesses, collects, uses, and shares user data, not limited by the data disclosed in the Data Safety section. This must include:
    • developer information and a privacy point of contact or a mechanism to submit inquiries
    • disclosing the types of personal and sensitive user data your app accesses, collects, uses, and shares; and any parties with which any personal or sensitive user data is shared
    • secure data handling procedures for personal and sensitive user data
    • the developer’s data retention and deletion policy
    • clear labeling as a privacy policy (e.g., listed as “privacy policy” in title)
    The entity (e.g., developer, company) named in the app’s Google Play listing must appear in the privacy policy or the app must be named in the privacy policy. Apps that do not access any personal and sensitive user data must still submit a privacy policy.

    Please make sure your privacy policy is available on an active URL (no PDFs) and is non-editable.

    So, I have updated the privacy policy and added this new table:

    https://github.com/M66B/FairEmail/blob/master/PRIVACY.md#summary-of-shared-data

    I am not sure if it covers everything, so feedback is more than welcome. @mkasimd maybe you can take a look?

    Note that I have also enabled BIMI, Gravatars, Libravatars and favicons for the Play store version again.

    The short term goal is to release a Play store test version (and associated GitHub version) and to get the update approved. I will think about the next steps after this has been accomplished. Given the huge number of supportive messages I received (much appreciated!) the project will be continued in some form in any case.
    50
    Version 1.1900 is available on GitHub now and in the Play store test program after Google's approval (which is the main goal of this release).

    Changelog/download:
    https://github.com/M66B/FairEmail/releases

    My girlfriend is slowly recovering too :)
    47
    It is time for a new, modern, open source, privacy friendly email client for Android.

    I have just released a first alpha version for feedback on the design and features.

    Not for production use yet!

    Most of the stuff basically works, but be prepared for crashes and error notifications.


    Safe email is a working name, but it is for several reasons not a convenient name, so suggestions for a name are welcome.
    37
    I have just released alpha version 0.15

    Changelog/download:
    https://github.com/M66B/open-source-email/releases

    With a bit of luck the next version can be a beta version.

    I am putting a lot of effort into this project, so thanks are appreciated.