That's where the story rises above the mundane.
That's where the story rises above the mundane.
If support at your company got an email saying "omg! sensitive information in our recording is being referenced in this random survey we got from you!" I guarantee 2/3 companies would flub the initial response because the support person doesn't understand the technical side of the issue which is that titles are used in one of the survey templates
Journalists who are casual or reckless with this kind of data shouldn't be in the business, and companies that don't make these kinds of risks apparent to their user base, or go to lengths to disguise a clear conflict of interest as bad support should not be in that business either.
The shocking revelation should be that journalists who normally are so careful they use end-to-end client-side encryption for their communications are using third party transcription services that have full access to their sensitive interviews. That's a faux pas and critical security blunder on the journalist's part, not otter's, though one learning here is maybe otter should consider offering some sort of secure enclave service for situations like this with additional guarantees and client-controlled encryption keys.
"Not respond to that survey and delete it" is also the ending of a sentence that begins "if you would feel more comfortable, you can".
Where are you getting your information from - is there a link to this correspondence, in the article or elsewhere?
'Is also' has very different implications than 'could have been'.