7 ms·
We’re designing this thing so that even we can never access your recordings. Building it with actual security in mind poses some UX challenges (don’t lose all y
by gtank 13y ago
We’re designing this thing so that even we can never access your recordings. Building it with actual security in mind poses some UX challenges (don’t lose all your credentials at the same time!) but we’d rather have that problem than any amount of privacy risk.
- anonymoushn 13y agoDoes this mean that I can store the only copies of the recordings on my machines, or that they are on your machines and there is some step you cannot perform that is required to read them?
- gtank 13y agoThey're on our machines, but under keys that we don't have. We're also considering a federated model that would give users control over their storage.
- mserdarsanli 13y agoSo, the conversations are on server but the required indexes for searching are on client? Seems a little weird to me.
- gcb0 13y agoi think he meant keys in the cryptography sense, not database search indexes.
- mserdarsanli 13y agoNo I got that, but somehow the audio must be processed, right? And it has to be done on client or there is no point for encryption. Also, assuming the search indexes are sent to the server, how would the server access them if they are encrypted?
- hapless 13y agoAs long as it's closed source, I have only your assurance that you don't have keys. I doubt you or your cofounders set out to deceive users or spy on them, but there are many, many government-related reasons to lie to your users about privacy. The government can be very persuasive that way.