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.
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.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.
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:
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).
- 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
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 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.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.
That one depends on the company. But in large corporates, that's the case unfortunately.@M66B it needs a lot of nerves and patience to escalate things and escape from the 1st level support stupidity.
...
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!
Did they invent * copy/paste*?After 5 similar answers from Google, I think replying again will only result in a new similar message.
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.
Text has changed in the meantime, and it is actually a 5 star review
Just remember Dr-bob doesn't speak for all of us in fact I doubt he speaks for even the 1%.I have been rather friendly and offered my help, so why this blind hate?
In any case your response clearly illustrates one of the reasons why I stopped supporting all my projects.
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.I am prepared, I only want answer to three simple questions:
I am not going to argue or pressure anyone and just see where this goes.
- Which contact info is being sent?
- When is it being sent?
- To where is it being sent?
- 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
The manual I linked to is maintained by disroot, an email provider.You could also let the community handle this and focus on your personal life a bit more.Isn't that current 'manual' already on a collaborative platform? This community is awesome with stuff like that!
Yes, but I would rather keep it out of a newbies' tutorial for a few reasons:Hi, selecting a theme is even more simpler by using the three dots menu. But anyway, your tutorial is great
Very professionally done! Appreciate your effort to a better FE communityThe manual I linked to is maintained by disroot, an email provider.
Here's a tutorial I just wrote as I found some spare time today, though. Any feedback is welcome (e.g. if something doesn't sound well phrased or something's missing)
FairEmail/first-config.md at tutorial · mkasimd/FairEmail
Fully featured, open source, privacy friendly...github.com
Great tutorial for initial setup!The manual I linked to is maintained by disroot, an email provider.
Here's a tutorial I just wrote as I found some spare time today, though. Any feedback is welcome (e.g. if something doesn't sound well phrased or something's missing)
FairEmail/first-config.md at tutorial · mkasimd/FairEmail
Fully featured, open source, privacy friendly...github.com
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:
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.
- 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)
Please make sure your privacy policy is available on an active URL (no PDFs) and is non-editable.