Know what comes with the feedback.
The message and its context help your team understand the feedback. This page explains how that works. The legal documents set out the full terms.
The sender chooses what to send
Visitors choose whether to record or type. The microphone starts only after that choice. They can check the transcript before sending.
People reviewing feedback cannot play back or download the original voice recording. Audio is processed to produce the transcript and kept in private storage for no longer than 30 days after upload to support investigation of abuse and security incidents. It is then deleted from Voicedot’s storage.
The place matters too
- Page and pin
- To show the page and place being discussed. Pin metadata is minimized; it is not a copy of every field.
- Conversation
- To keep the submitted text, replies and decisions together.
- Captured page state
- To show a dynamic view that reopening the URL may not reproduce. Captured state is separate from pin metadata.
- Optional contact details
- To identify a submission or contact its sender where an email address was provided.
The saved page view is normalized: values typed into form fields are removed and replaced with masking characters before the capture leaves the browser, and the server masks them again. Even so, keep passwords, card details and sensitive personal information out of feedback. Choose suitable review pages and access settings.
A snapshot preserves the page view associated with a feedback message. These saved page views are stored privately in Cloudflare R2 for 90 days from capture by default, and then removed. The account owner can choose 30 days, a year or two years instead. Written feedback and discussions are separate: deleting audio or a snapshot does not by itself delete the conversation.
Who can see it?
The customer normally decides why feedback is collected and how it is used. Voicedot processes visitor messages to provide the service. Voicedot also has its own responsibilities for account, billing, support and operating data.
Administrative access is limited to operating, supporting, securing or legally administering the service. We keep the app and the server up to date and secured: dependencies are checked weekly for known vulnerabilities, the server accepts key-based logins only, and an encrypted backup is made every hour to separate, private storage. Data sent to providers depends on the feature: hosting, proxying, private storage and backups, email, billing and selected integrations. The providers list also describes optional services and restricted operator alerts.
What can my agent access?
The agent gets comments only from the projects you choose when connecting, and how much it sees depends on the address mode. On a private address, such as localhost, it gets the whole discussion: comments, team replies, internal notes and review-round comments, with the author’s role and time. On a team address, such as staging. or beta., it sees only threads handed over from the inbox, as they were handed over; a message added later reaches it only when the thread is handed over again. On a public site it gets only the team’s decision attached at handover and the spot on the page, never the visitor’s words. On team and public addresses, a thread nobody handed over is invisible to the agent: it isn’t in lists, search or counts. The agent sees a comment’s author with a partly masked email address and never gets recordings, the HTML of saved views or sign-in data.
Check connection permissions and your agent’s terms. The agent is separate from your subscription. Partial masking does not make information anonymous.
- Claude Code
- Codex
- Cursor
Providers, retention and deletion
Providers support infrastructure, processing, backups, email, billing and operations. User-selected services and alert channels have separate data scopes. See the providers and subprocessors list for their purposes, data and activation conditions.
Messages, audio, logs, billing records and backups do not all have the same retention rules. Read the retention section before relying on a specific storage period.
To request help deleting a message, contact support. Include the website, page, approximate time and a receipt or identifying email if you have one. An anonymous message may be impossible to locate without a reliable identifier.
Common questions
Do you sell personal data?
No. The Privacy Policy states that we do not sell personal data.
Are messages used to train generalized AI models?
The existing policy states that Voicedot does not use submitted messages, audio or transcripts for that purpose where provider configuration supports the commitment. The current provider configuration and legal terms determine the scope; this summary does not turn it into a broader guarantee.
Does a DPA replace our own privacy notice?
No. It documents processing responsibilities between the customer and Voicedot. The customer remains responsible for its own notice, lawful basis and use of the widget. See how to request a DPA.
Does Voicedot have a certification for every regulated use case?
No. Do not assume SOC 2, HIPAA or another certification from the fact that the product has privacy controls.
The full documents
Make peace with revisions. Then make progress.
Start with one page and one person whose feedback you need.
Try it yourself
Explore the full product at your own pace. Add the widget to your site and invite the first person to review it.
Annual plans only: 60-day money-back guarantee.
Let’s do it together
Meet Piotr to explore Voicedot, install the widget or discuss your project.
Free installation