Absolutely, the Android community has been a lot more vocal about this. I actually had it on an old roadmap back when the iOS client was created, but I have not really caught up on it since the feature list was not 'finished' until last month. But hearing that this many people want that transparency, I would gladly bump it and will work on it as soon as the bugs are ironed out and Android is fully out. I admire people who are cautious, I work with security as my day job myself and would act the exact same way.
Thanks a lot! You are not the first person here asking about a version outside Google Play, so it is clearly something to look at once the Android launch is out the door. If it happens I will make some noise about it in this community.
Fair, that is the unfortunate truth with closed source. I completely understand where you are coming from, it is honestly the same skepticism that drove me to build Una in the first place. That is why the encryption keys are created and stored on your own device and the sync traffic only carries encrypted content. But I do get you! I will be sure to have you in mind if we open source the Android and iOS versions.
Quick update: thanks to your report we found an edge case that could leave the app frozen after the Google sign-in. A fix is now in review and should be available as an update soon, I really hope it solves it for you. Thank you very much for flagging it, I had around 8 testers before you and none of them ran into it, so this really helps me cover every case, especially in onboarding 😂
Today Una supports a one-time import from Google Calendar, the Android calendar and Outlook. There is no sync and we do not keep any tokens or ongoing access to your other calendars. A live subscription the other way, gcal or Proton cal reading the Una calendar, is not there yet. You are right that the e2ee makes that one tricky since the server never sees your events in plaintext.
Hm, interesting. I just ran through a fresh onboarding myself now and got past the oauth fine, so I want to figure out what is different on your end. Did you get any error message at all, or does it just freeze after the callback? And what device and Android version are you on? If you are up for it you can mail the details to feedback@unafamily.app and I will dig into the token exchange on my side.
Fair, and honestly that is the right instinct, you should not have to trust me. That is kind of the point of the design: the encryption key is created on your own device and stays in the device keyring. It never touches our server, so there is nothing to trust me with, I could not read your household data even if I wanted to. Details here: https://unafamily.app/privacy
No worries at all, thanks for giving it a look anyway. If I ever ship a build that works without Play services I will definitely post about it here. Best of luck with the Graphene setup!
Not right now, it is closed source. The privacy side is built on end to end encryption instead: household content is encrypted on your device before it syncs, so we technically see nothing even though the code is closed. If you want the details: https://unafamily.app/privacy. Totally understand if open source is a must have for you, and thanks for signing up either way!
Welcome aboard! The invite mail is on its way to you now. One thing to check: the opt in link needs you to be logged in to Google Play with the same email you signed up with, otherwise the test page shows nothing. If you need to use another mail, one that is signed in on your phone, just give me a shout here or add it on unafamily.app :) Let me know if it works!
Absolutely, the Android community has been a lot more vocal about this. I actually had it on an old roadmap back when the iOS client was created, but I have not really caught up on it since the feature list was not 'finished' until last month. But hearing that this many people want that transparency, I would gladly bump it and will work on it as soon as the bugs are ironed out and Android is fully out. I admire people who are cautious, I work with security as my day job myself and would act the exact same way.
Ah, sorry to hear that. Yes please, email me the details and I will dig into it right away. Thanks a lot for sticking with it!
Thanks a lot! You are not the first person here asking about a version outside Google Play, so it is clearly something to look at once the Android launch is out the door. If it happens I will make some noise about it in this community.
Perfect, thank you! And good timing: the update is live now. Would love to hear if it gets you through onboarding.
Fair, that is the unfortunate truth with closed source. I completely understand where you are coming from, it is honestly the same skepticism that drove me to build Una in the first place. That is why the encryption keys are created and stored on your own device and the sync traffic only carries encrypted content. But I do get you! I will be sure to have you in mind if we open source the Android and iOS versions.
Quick update: thanks to your report we found an edge case that could leave the app frozen after the Google sign-in. A fix is now in review and should be available as an update soon, I really hope it solves it for you. Thank you very much for flagging it, I had around 8 testers before you and none of them ran into it, so this really helps me cover every case, especially in onboarding 😂
Today Una supports a one-time import from Google Calendar, the Android calendar and Outlook. There is no sync and we do not keep any tokens or ongoing access to your other calendars. A live subscription the other way, gcal or Proton cal reading the Una calendar, is not there yet. You are right that the e2ee makes that one tricky since the server never sees your events in plaintext.
Hm, interesting. I just ran through a fresh onboarding myself now and got past the oauth fine, so I want to figure out what is different on your end. Did you get any error message at all, or does it just freeze after the callback? And what device and Android version are you on? If you are up for it you can mail the details to feedback@unafamily.app and I will dig into the token exchange on my side.
Fair, and honestly that is the right instinct, you should not have to trust me. That is kind of the point of the design: the encryption key is created on your own device and stays in the device keyring. It never touches our server, so there is nothing to trust me with, I could not read your household data even if I wanted to. Details here: https://unafamily.app/privacy
No worries at all, thanks for giving it a look anyway. If I ever ship a build that works without Play services I will definitely post about it here. Best of luck with the Graphene setup!
Not right now, it is closed source. The privacy side is built on end to end encryption instead: household content is encrypted on your device before it syncs, so we technically see nothing even though the code is closed. If you want the details: https://unafamily.app/privacy. Totally understand if open source is a must have for you, and thanks for signing up either way!
Welcome aboard! The invite mail is on its way to you now. One thing to check: the opt in link needs you to be logged in to Google Play with the same email you signed up with, otherwise the test page shows nothing. If you need to use another mail, one that is signed in on your phone, just give me a shout here or add it on unafamily.app :) Let me know if it works!