V2T was designed from the ground up to minimize data collection and eliminate unnecessary risk. This document is for IT teams, CISOs, and anyone evaluating V2T for their organization.
Last updated: August 2026 · Hynds AI LLC, Coeur d'Alene, Idaho
Data flow architecture
↓ microphone audio (local only)
Chrome / Edge built-in · never leaves browser
↓ text transcript (stays in browser localStorage)
user clicks AI action (optional)
Text in → cleaned text out · nothing stored
↓ cleaned text returned to browser
Copy, download, or discard — your choice
Key takeaway: Audio never reaches Hynds AI servers. Transcripts live only in your browser. AI processing is text-only, on-demand, and transient — nothing is stored or used for training.
V2T uses the Web Speech API built into Chrome and Edge. Your microphone audio is processed entirely by the browser engine on your device. Hynds AI servers never receive, transmit, or store any audio data.
This means there is no audio endpoint to attack, no audio in transit to intercept, and no audio at rest to breach. The same applies when working offline — transcription continues without any network connection.
Transcripts are stored exclusively in your browser's localStorage on your device. Hynds AI has no server-side database of user transcripts. We cannot access, read, or recover your transcripts — they exist only where you put them.
When you close your browser tab or clear localStorage, the transcript is gone. You can also download it as a .txt file to keep a copy under your own control.
AI cleanup (Clean, Summarize, Email, Notes, Action Items, Prompt, Translate) is triggered only when you click the button. Only the text transcript is sent — never audio. Processing is stateless: text goes in, cleaned text comes back, and nothing is stored on our side.
The free tier requires no account creation — no email, no password, no OAuth login. We do not build user profiles, track usage history, or correlate sessions across devices.
Pro tier uses a license key (not an account). The only data we store for Pro users is the key itself, the associated email from Stripe checkout, and subscription status. No usage data, transcripts, or behavior is attached to the key.
All payment processing is handled by Stripe, a PCI DSS Level 1 certified processor. Hynds AI never receives, processes, or stores credit card numbers, CVVs, or bank details. Card data goes directly from your browser to Stripe's infrastructure.
V2T is a standard web application accessed via URL. There is:
IT teams can allowlist or block v2t.hynds.ai at the URL or DNS level like any other web application. No special firewall rules, VPN configurations, or endpoint management policies are required.
All traffic is encrypted in transit via TLS 1.2+. The application is served over HTTPS with HSTS enabled. Server infrastructure is managed and patched continuously — there are no customer-accessible servers, SSH endpoints, or admin panels.
API rate limiting is enforced per IP address to prevent abuse. Client-side rate limiting provides additional protection for the AI processing endpoints.
If your security team needs additional information, a vendor questionnaire completed, or a live walkthrough of the V2T architecture, contact us at hynds.ai.