[Emc2fma]

I tried keeping a journal (to track what I did each day...otherwise it felt like the days were just blending together) but kept failing over and over because I just couldn't get into the habit.

For people who have the same issue, I came up with https://www.60secondseveryday.com

It's the fastest way of daily journaling - you make a 60 second phone call every night to answer the question "What do you want to remember about today?". From there, it gets transcribed, archived, and it's all searchable as well.

Disclaimer: I came up with the service after having a need for it myself

[jstanley]

The general idea sounds good to me (just spend 60 seconds on it, and no more).

But I wouldn't use it on principle because a journal is private, and having it handled by a third-party doesn't sound like a good idea at all. Especially when you explicitly state that it is transcribed, archived, and searchable.

[Emc2fma]

Why would it being transcribed and searchable mean it's not private? Everything is automated and encrypted along the way, so I won't be able to look at it even if I wanted to.

I realize that privacy is an important concern which is why I've taken it extremely seriously. So rest assured, this journal is private.

[throwanem]

That's nice to say and all, but there would seem of necessity to exist a point at which the incoming audio data is present on a server you control but has yet to be encrypted. In any case, since all the encryption and decryption necessarily takes place on hosts you control with keys you hold, your claim of privacy comes with a whole constellation of caveats which you choose not to mention. This fails to inspire confidence.

Perhaps I've misunderstood how your service works, and these concerns have no basis in fact. If so, it would be awesome to know that! Such information might make a very good fit for a privacy policy, which I'm having a very hard time finding any mention of on your site. (Yes, I saw the brief, breezy dismissal of such concerns in the FAQ section of your pricing page. That doesn't count. And, no, I haven't tried it. I shouldn't need to try it to get some idea of what you actually do to mitigate these risks.)

I hate to seem overly harsh on this point, but these are uncertain times, and your service is one which invites people to trust it with the sort of deeply personal information which, in the wrong hands, could be misused to ends from embarrassment to social and professional annihilation. Perhaps you have given this hazard the degree of concern it merits, and engineered your service to minimize it to the maximum possible extent. If so, you might do well to present the appearance of having done so, too.