JehoschuaQ: ⁉️ The transcripts of *OUR* emails are published and publicly accessible here?: https://app.vocal.email/listen/…
Hello
Am I wrong?
I believe Vocal is acting with gross negligence and intentionally violating the GDPR / DSGVO.
You wrote:
❯ In voice messages, the transcription is always displayed (https://app.vocal.email/listen/5f4f6c86-dcaf-4ce7-aee7-7abb6e483fa5),
❯ but not in the email so that it is clear for the user what is a transcription / email.
❯ It would look bad to have the transcription directly in the email body.
Do we understand correctly:
1) that the millions of emails that have text in the body "look bad" (“It would look bad to have the transcription directly in the email body.”)
2) And that is why you store the transcription of our *private* emails on your servers?
3) And you publish these transcriptions so that anyone who guesses or catches a link can read them?
If that's true, your customers in EU will have very big problems
Nathan_Vocal
Edited Nov 28, 2025A: Hey,
Just to clarify, voice messages (and their transcription) are stored on our servers indeed.
And anyone you share a link with to your voice message, will be able to listen to the voice message and read the transcription.
Where you maybe have a little misunderstanding is around the idea of "guessing" a link. Those urls contain a key that is impossible to guess. It would be like saying that your bitcoin wallet is insecure because anyone who guesses your private key can access it. Loom for example relies on the same logic to keep your voice messages private. Only you and whoever you share the voice message with can access them.
As to the "looking bad" thing. Emails containing text don't look bad! The issue is with embedding a transcription in an email, because it is often unclear to the recipient that this is a transcription. For example, imagine receiving an email like:
"Hey, yeah, I know but..... Well let's discuss it tomorrow" - Would be strange/unprofessional and so on. That's why we chose to do it that way with the transcription being hosted and available on the web page :)
Hope that clears up things! We are fully GDPR compliant ;)