I have conflicting feelings about this. Closed source codebase; but even if I trust you, what if you get acquired?
In fact, because the risks are unknown this seems even riskier than a regular browser (for privacy conscious people). What's being captured, how safely is it stored, can you read it, etc.
I think something like acquisition is a really fair concern.
Someone here has recommended tying our values down into some form of legal agreement which prevents the company from straying from them. That would also work for acquisition (though I'm not sure how to go about something like that)
Someone else has suggested not talking about privacy at all, since those who care about it will want open-source browsers.
We're still figuring out how to talk about this. All we want to say is we want to build an awesome product, we try to handle as little user data as possible but handle it appropriately, and we will be doing more to resolve privacy issues in browsers.
If I can assuage any concerns (not the major one of it being closed-source though. I can only say trust us for that :p), no session data is captured when you use the app. We don't know what tabs are open. Now if you choose to sync your data across devices, your session data will then be uploaded to our server, stored encrypted. The only user data we have otherwise is from the sign up form.
I have conflicting feelings about this. Closed source codebase; but even if I trust you, what if you get acquired?
In fact, because the risks are unknown this seems even riskier than a regular browser (for privacy conscious people). What's being captured, how safely is it stored, can you read it, etc.