Open bbigam opened 3 years ago
This looks like a good start.
does not profit from Iceraven in any way.
I don't think that's true necessarily. Somebody on Reddit sent me some money when I first put out the fork, and we also collect... Github stars and coolness points. Maybe we get better job opportunities. And who knows if we're going to set up an OpenCollective or something in the future.
The only information the fork-maintainers have on any user is only what users voluntarily share through GitHub issues.
They could also share it not through Github Issues.
We could also specifically mention how the log bundles people send us for debugging can have sensitive system information in them, and if people post them publicly on Github, that's their choice.
As much as possible, Iceraven removes or disables all telemetry or other tracking features from upstream Firefox that would collect or share user information with any upstream or third parties, such as Mozilla, Adjust, LeanPlum, or Google.
Does the crash reporter count as telemetry? We haven't made an attempt to rip that out, and I think it still does exactly what it says in the dialog and reports our app's crash to Mozilla when you tell it to do so.
We also keep Firefox Account sync, which shares all sorts of synced information with Mozilla, when you log into it.
This looks like a good start.
does not profit from Iceraven in any way.
I don't think that's true necessarily. Somebody on Reddit sent me some money when I first put out the fork, and we also collect... Github stars and coolness points. Maybe we get better job opportunities. And who knows if we're going to set up an OpenCollective or something in the future.
Ah, fair enough. Maybe we should say "do not profit from any data collection or ads in Iceraven" or something like that.
The only information the fork-maintainers have on any user is only what users voluntarily share through GitHub issues.
They could also share it not through Github Issues.
True. "...voluntarily share, such as through GitHub issues..."
We could also specifically mention how the log bundles people send us for debugging can have sensitive system information in them, and if people post them publicly on Github, that's their choice.
Indeed.
As much as possible, Iceraven removes or disables all telemetry or other tracking features from upstream Firefox that would collect or share user information with any upstream or third parties, such as Mozilla, Adjust, LeanPlum, or Google.
Does the crash reporter count as telemetry? We haven't made an attempt to rip that out, and I think it still does exactly what it says in the dialog and reports our app's crash to Mozilla when you tell it to do so. We also keep Firefox Account sync, which shares all sorts of synced information with Mozilla, when you log into it.
Good points. Yes, we need to be as accurate as possible.
I've updated the initial draft, taking into account Interfect's comments. Please keep commenting. And if anyone knows legalese, please help!
I think we might have forgotten about the information the app sends for the phishing/malware detection feature (see #145). The backend there happens to be provided by Google, apparently, so people are going to care, and even if we have a switch to turn off whatever novel download hashes or whatever it sends in, we probably still will ship it on by default.
I don't mind continuing to work on the draft, but I'd really like to hear more from others.
@abhijitvalluri You do a lot of work on Iceraven, any thoughts?
I've updated the draft privacy policy again, and I separated it into "Browser" and "Development" sections to make it easier to read, and put the Tl;dr at the top. @interfect @abhijitvalluri how does it look to to you now? Are we on the right track?
Not related to this but maybe we should change the name from 'Iceraven Mobile' to 'Iceraven Browser'.
Agreed, I'll take care of the wordmark banners for that when the new icon is decided.
On Tue, Oct 6, 2020, 11:21 AM hbarsaiyan notifications@github.com wrote:
Not related to this but maybe we should change the name from 'Iceraven Mobile' to 'Iceraven Browser'.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/fork-maintainers/iceraven-browser/issues/130#issuecomment-704346580, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQQNFQ3DBKZA32SJUUDT6Q3SJMYZJANCNFSM4RRKSSAQ .
Hello, lone wanderar and non-contributor here, but wouldn't the name "Halcyon Browser" fit better than "Iceraven"? Searching the net brought me to the myth of the Alcyonides and them turning into birds, Halcyons, upon thrusting themselves into the seas, and I thought that it fits with the theme of mythical elemental birds as Mozilla likes to do it?
I also would like to propose my own take on the privacy policy for this project:
@bbigam
Iceraven Browser
As we prepare to go public more fully, hoping for inclusion in F-Droid and maybe even Google Play, we probably ought to have a Privacy Policy, rather than just linking to Mozilla's. We can probably just do a Privacy.md in the repo and link to it from the About page. I don't think our next release needs to wait for this, though.
I'd like to see a simple policy. I don't suggest the following language specifically, and don't know the legalese, but here are some points we should probably hit:
EDIT: Draft 3
Just my suggestions to open the discussion. Comment away!