Hi! I am the developer of Una, a privacy first planner for families, households and couples. It is live on iPhone with a few hundred households using it daily, and now I am finishing the Android version.

Google requires 12 testers for 14 days before a new app can go to production, so here I am :)

Short version of why I built it: as family life gets busier it gets hard to keep track between different apps and text messages. My own household tried many different family organizers and I was flabbergasted by how many of them never say how your info is stored. You trust some of your most valuable information to these apps and expect them to handle it delicate.

So Una is privacy first. Household content is encrypted on your device before it syncs, and only you can decrypt it. We technically see nothing.

The app itself connects the context around each plan. Link a recipe note to dinner, a travel checklist to a trip, or school documents directly to the calendar event where you need them. No more digging through messages, mails and separate apps.

If you want in on the Android test you can apply on unafamily.app. All feedback welcome, also the brutal kind :)

  • acgkOP
    24·
    27 days ago

    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!

      • acgkOP
        12·
        27 days ago

        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

        • OilyArena@lemmy.ml
          7·
          27 days ago

          However, noone can inspect the source code and see if encryption is implemented properly, or at all.

          • acgkOP
            1·
            27 days ago

            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.

    • CameronDev@programming.dev
      1·
      26 days ago

      You may want to consider splitting out the back end or the sync/encryption parts into a library that you open source, which would give a bit more trust that you have actually done the right things.

      • acgkOP
        1·
        26 days ago

        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.