Hello,
UUID: support@roearn.io
My add-on was just taken down right now all versions rejected, and it now says “Incomplete” I have done absolutely nothing wrong.
This is absolutely unnecessary. I received no notification or was not contacted. Please fix this immediately. This is terrifying how you guys can just take people down without even contacting them and they did absolutely nothing wrong. I have never broken any policy ever in my entire life.
Hi @RoEarn and thanks for reaching out! I am here to resolve this as quickly as possible!
Per your previous request for an expedited review, the team has reviewed your newest version on the 29th of April.
Haven’t you received an email from them about the outcome of the review? I see in my systems that their feedback was sent to you via email and via the review platform.
Can you please confirm whether you have seen their feedback and whether you can address their comments to make your add-on compliant?
In the meantime, I will be working with the rest of the team to see how we can speed up everything. Again, I am sorry, and we will be sorting everything as quickly as possible.
Hi @mozchris
I now understand it was related to the absence of a proper privacy policy.
I did attempt to include one originally, but I ran into a limitation: the submission process doesn’t make it straightforward to add a dedicated privacy policy link, as most real-world extensions typically provide. As a workaround, I’ve included the privacy policy link directly in the privacy policy markdown section, because it is way too big!
I’ve taken the opportunity to update the manifest to properly target Firefox 140+ on desktop and 142+ on Android, using the built-in data consent mechanism as recommended.
I’ve resubmitted the extension. Could you please forward this to the review team so they’re aware of the context?
Thanks again for your help, and happy to provide anything else needed.
UUID: support@roearn.io
Hey @mozchris
Yeah, that privacy policy section is there, but it’s really awkward to use because most people host their policies on their site. It would be a lot better if you had a dedicated link section so users could just open it easily.
Thank you for your feedback @RoEarn . Just to make sure I pass the feedback as accurately as possible, you are suggesting instead of this big text box that has where you can either put your privacy policy or/and a link to it in case you are hosting it somewhere else, to replace it with a smaller one, clearly labeled with “URL to your policy”, correct?
Someone can ask, though, what about people who don’t have a website to host their policy, or they don’t want to maintain it somewhere else?
And my question before I relay the feedback is: what is keeping people from adding a link to their policy in this text box?
Hello Chris,
The text box for the privacy policy doesn’t make it clear to developers they are allowed to put a link, I put my link in the text box with the thought in the back of my mind that it will probably be rejected.
also, my extension is still stuck in review and users are not able to withdraw their cashback earnings. Can you please ask the review team to review my extension ASAP.
Thanks for the feedback, I will pass it on and let the reviewers know!
Hey Chris,
This is serious and now is getting out of hand, my submission which I fixed was rejected for this reason here (same reason as last time)
Personal data: background.js#185, 217 and others | Financial and payment information: background.js#412 and others
Consent, specifically Nonexistent: For add-ons that collect or transmit user data, the user must be informed and provided with a clear and easy way to control this data collection. This must be achieved by either using the Firefox built-in data consent (for exclusively targeting Firefox versions 140 or later on desktop and 142 or later on Android) or implementing a compliant custom data collection and transmission consent screen for your add-on.
“browser_specific_settings”: {
“gecko”: {
“id”: “support@roearn.io”,
“strict_min_version”: “140.0”,
“data_collection_permissions”: {
“required”: [
“none”
],
“optional”:
}
},
“gecko_android”: {
“strict_min_version”: “142.0”
}
},
To be clear, I am specifically targeting 140 or later on desktop and 142 on Android.
Therefore, this review is already extremely invalid. It literally says right there that I can target those versions and not have that required.
But I still included my privacy policy, which by the way does mention financial in payment information here is my link here so we are both on the same page:
And this privacy policy is included in the privacy policy section which me and you spoke about in previous chats Chris.
I don’t even have motivation to re-upload it again due to this. Please talk with the review team.
Hi RoEarn, and apologies for the late response.
I am sorry about the confusion, but the message states that you need to have consent in place for personal, financial, and payment information.
If you are aiming for Firefox 140+, you can use Firefox’s built-in data consent; if you are targeting earlier versions, you should implement a compliant custom data collection and transmission consent screen.
So, in your case, you need to add personal, financial, and payment data to the manifest.
Let me know if there is anything else I can help you with.
Thank you Chris,
Thanks to you informing me that it was referring to the data thing in the manifest, I now know how to solve this problem.
Unfortunately this was not made clear at all in the rejection message, and I would have never known to do that or that it even existed until you told me.
The new version has been submitted and I’m hoping the review team can review it fast.
