Privacy & trust

Microphone, tab and file transcription run on your device. Optional earnings automation records and transcribes on the owner's server, with email and encrypted backups when configured.

What is captured

For transcription on your device, the mode picker selects one of the three sources below. Server recording and earnings scheduling are separate features, described further down.

This computer's audio: when you click Record, your browser shows its own picker and you choose one tab (or window, or screen). Live Transcribe receives that source's audio — and a tiny throwaway video signal the browser insists on sending along, which is shrunk to a single pixel and never shown, saved, or used.

Microphone: the microphone is captured only after you pick that mode and your browser asks you and you allow it — never in the other mode, never on page load. By default your device's own automatic gain and noise reduction are left on, so quiet and distant voices are picked up — all of this microphone processing runs on your device. A visible “raw signal” toggle turns both off for close-up recording in a quiet room. Echo cancellation is always off (it is phone-call processing that smears room recordings). One honest limit: on a phone, a phone call takes the microphone over, so no app — this one included — can transcribe a phone's own calls. Microphone mode is for rooms you are in, or a second device beside a speakerphone.

Audio file: a recording already on your device, read only when you pick it in the file dialog. It is decoded and transcribed on your machine, and the app does not upload the source file.

What the app works out about a recording

After a recording, the app shows “Key excerpts” and “By the numbers”. Both are computed on your machine and both are mechanical: the excerpts are sentences quoted word for word from your own transcript, chosen by counting which sentences share the most vocabulary with the rest — and the numbers (words per minute, questions asked, sentences with numbers) are counted, with each line pointing at the exact moment it came from. Nothing here is written by an AI, nothing is a judgment, and none of it is a summary. The optional “tidy the transcript” switch only ever removes filler words and stuttered repeats — it never adds or rewords anything, and switching it off shows the exact words again.

Where the transcription comes from

For device transcription, the speech-recognition engine runs inside your browser, on your computer's own processor. The first time you record, it is downloaded once from this site — the dialog that asks first always shows the exact size, which depends on the quality level you pick — and kept in your browser's storage, so later visits skip the download. Every file is checked against a known fingerprint before it is used. Device audio is not uploaded for transcription. When the owner enables server recording or earnings automation, recordings made by the server can instead be transcribed by an engine running on that server. Neither workflow sends audio to an external transcription service. Playback, downloads, the Transcript bridge, and configured backups are described below.

What is stored on your computer

The items above live in this site's browser storage on your disk. Device transcripts stay there unless you save a file or enable the Transcript bridge. Server recorder and earnings automation keep their own server data when enabled. Access tokens entered for server features also stay in this browser and are sent to this site's server to authorize requests.

What is sent over the network

During device transcription with the Transcript bridge off, no recorded audio or transcript is uploaded. The browser requests the app, engine files, and feature status from this site; the app sends no analytics or telemetry. Its browser security policy limits connections to this site. Server features make additional requests, described below. You can inspect your browser's requests in its developer tools; those tools do not show requests made by the server.

One nuance, stated fully: the “My calls” page can show upcoming earnings dates from a public calendar feed. That feed is fetched by this site's server from a data provider (Alpha Vantage), at most once a day, and the request is identical no matter who visits or what calls anyone follows — so the provider learns nothing about you, and your browser still talks only to this site. “My calls” is stored in your browser and is not automatically synchronized. Scheduling a server recording or confirming a call’s import into earnings scheduling sends the selected call details to the server.

A second, narrower nuance: a call's Prep button (and the official-transcript viewer behind it) asks this site's server for that one company's earnings history or a past call's published transcript. Those lookups are symbol-specific — the data provider sees which ticker the server asked about (though not who asked, or anything else). They happen only when you click, are cached on the server for a day, and nothing about your recordings or transcripts rides along. After a recording, the fact check's “Check against the … call” button is the same kind of lookup: it asks the server for that one company's earnings history (if the Prep card was not opened) and one prior call's published transcript, only when you click it, and nothing from your recording rides along. If that trade is not worth it to you, don't click Prep or that button — nothing else uses these lookups.

Server recorder

When its owner has switched on the legacy Server recorder, you can hand the server a direct media link (a replay's playlist, say) and it downloads that stream to its own disk — only the link you gave it, nothing from your device. When its owner has also switched on server transcription — a separate switch; the recording's card says whether a server transcript exists — the server transcribes that recording itself with a speech-recognition engine that runs inside the server on its own processor: the same kind of on-machine engine your browser uses, only on the server's machine instead of yours. No external transcription service processes that audio. You can retrieve the results, and configured encrypted backups can copy them off the server as described below. The server transcribes only recordings the server itself made — from a link you handed it, or from a capture its owner scheduled — and never anything captured on your device. Your tab audio, your microphone and your imported files are transcribed in your browser, as the section above says, and nothing about this feature changes that. With that switch off, a server recording is transcribed only when you click Transcribe here, in your browser. The recording and any transcript the server made of it rest on the server until you delete the recording, which removes both from its active store; backup copies follow the separate retention rules below. The transcript is also filed where the Transcript bridge (below) files transcripts, when this server has that store at all, whether or not you have switched the bridge on in your browser — because it was made on the server and was never on your device. You can download the transcript from the recording's card, or open it here for review — this browser then keeps its own copy of those words, in the same storage as your transcripts, marked as the server's, and never sends that copy anywhere (the Transcript bridge below is not told about it, because the server filed its own copy when it made the transcript); the review's Delete transcript removes this browser's copy and nothing on the server, and says so. Or still click Transcribe here to transcribe the recording in your own browser instead. The access token you paste is a capability key for that server, kept in this browser's storage — it is not a password to anything else. If the section isn't visible, the feature is off and this paragraph describes nothing.

When this site's owner has armed a scheduled capture, the server can start recording at a set time with no browser open at all — nobody present, nothing on your screen. Said exactly: at that time, or later within a limit the owner sets, so a server that was restarting at the appointed moment starts once it is back rather than not at all. These manual schedules use the supplied media link and never record anything from your device. Earnings automation can also discover call links from followed companies' sources, as described next. A manual scheduled recording is transcribed on the server when the owner has switched server transcription on — otherwise in a browser, when someone clicks Transcribe here.

Earnings automation on the server

When the owner enables this service, you can follow a company or save a webcast event. Company identifiers, follow choices, source and event links, exact times and time zones, schedule changes, and recording attempts are stored on the server. The service checks followed companies regularly and can start supported scheduled calls without your computer or this page being open. Importing an old “My calls” entry requires review and confirmation; the browser's existing list is not silently armed.

Discovery makes requests from the server to the SEC company directory, company investor relations sources, and webcast providers. These services receive the server's network address and the requested pages, tickers or event links. Your recordings and transcript text are not included in discovery requests. Finding a company does not guarantee access to its call: unverified times or links and unsupported access remain flagged for preparation. The service does not provide a general automatic login or registration tool, and does not bypass login requirements, challenges or provider restrictions.

The server records the supported webcast, generates provisional live text and a final transcript with its local speech-recognition engine, and stores audio, text, timestamps, source information and recording diagnostics. Recording-access credentials are required to retrieve the audio and transcripts. The scheduling credential controls company tracking and events. Source recordings and final transcripts remain until the owner explicitly removes them. The earnings console does not yet have an artifact-deletion control; retention and removal are managed by the server owner.

Email, when configured: status notifications go through the owner's chosen SMTP provider to the configured notification address. They contain the call label, status and a link to the authenticated dashboard. They do not include audio, transcript contents, access tokens or signed source links. The mail provider and recipient can retain those notifications independently of this app.

Encrypted backups, when the owner authorizes and configures them: the service copies server recordings, transcripts, schedules and catalog checkpoints to a dedicated private Dropbox folder. Existing Server recorder and Transcript bridge data on the server are included too. File contents, filenames and directory names are encrypted before upload; recovery keys are kept separately by the owner. Checkpoints run about hourly and after completed calls. Versions are retained for at least 30 days, and shared files remain while a retained version references them. Bounded cleanup or a backup problem can extend that period. Deleting an active server record does not immediately erase its retained backup copies. This backup feature is off until configured and enabled; it does not automatically upload device recordings.

Transcript bridge

The Transcript bridge is the feature that sends a device transcript — what was said — off this device. Switched on, each paragraph is copied to this site's server as it is committed, so a long call survives the tab closing and can be read while it is still running. Said plainly, because it is the one claim on this page that a feature can reverse: with the bridge on, your transcript text is stored on the server — not the audio, which never leaves your browser, but the words. It is off until you switch it on yourself, in the Transcript bridge section on the front page: that section takes an access token of the bridge's own, and turns the bridge off again in one click. The Server recorder's token does not turn it on, and neither does anything else. Turning it on during a session also sends what that session has already committed — the words so far, not just the words to come — and timestamped notes you type travel with the transcript while it is on, and are re-sent when the session ends if they failed to land, the same way the words are. While the bridge is on, that section says so and shows what is still waiting to be sent, so you are never guessing; an armed bridge always shows its section, even when the server cannot be reached. Switching it off stops anything further leaving; what was already sent stays on the server until the transcript is deleted — and deleting is in your hands: after a recording (or on reopening a recovered one), the review screen's Delete transcript button removes this browser's copy — the words and any notes you typed on them — and, for a transcript made in this browser with the bridge on, asks the server to delete its copy of that transcript too, telling you once the server has confirmed. (For a server transcript you opened here, the same button removes only this browser's copy and says so; the server's copies go with the recording, in its section.) If the bridge is off — or the server cannot confirm at that moment — the browser's copy is still removed at once, and the request to delete the server's copy is kept in this browser and sent the next time the bridge is on here; the note the button leaves says so, and so does this section whenever it is on the page. Three carve-outs, stated plainly: that kept request lives in this browser's storage, so clearing this site's data before it is sent abandons it; if your browser refuses to store it at all (private browsing, or storage limits), the note says that outright instead of promising a retry; and if your browser's own storage refuses to give up the transcript or the recording, the note names which part is still here rather than claiming a clean deletion. A request that was discarded or never stored cannot retry; any remaining server copy must then be removed separately. If the section is not on the page at all, no bridge token is stored here and this server offered nowhere to put transcripts. If the bridge is off, no device transcript is sent by the bridge. One exception, stated under Server recorder above: transcripts the server makes of its own recordings are filed in that same store when the store exists, because those words were never on your device — and they leave when that recording is deleted in its section, not through this button, which reaches only transcripts made in this browser.

Deleting browser and server data

Your browser's own controls remove this site's local browser data: click the padlock/tune icon next to the address, open Site settings, and choose Delete data (in Chrome: Settings → Privacy → Site settings → View permissions and data stored across sites → this site → Delete). That removes the cached engine, saved access tokens, “My calls” entries, transcript checkpoints (a copy of a server transcript you opened here included), and any unsaved audio. Files you saved with the Save buttons are ordinary files of yours — delete them like any other file. One carve-out, stated plainly: what already left for the server is not in your browser's storage, so this does not touch it — a Server recorder recording, and any transcript the server made of it, stay until you delete the recording in its section, and anything the Transcript bridge sent stays on the server until that transcript is deleted (for a transcript made in this browser, the review screen's Delete transcript button reaches the server's copy too, as the bridge section above describes) or until it is removed on the server itself. Clearing this site's data also discards a delete request the bridge was still waiting to send.

Clearing browser data, disconnecting, or closing this page does not cancel server schedules or remove the server's company list, earnings recordings, transcripts or backups. Use the earnings scheduling controls to cancel pending calls, and ask the server owner to manage stored earnings artifacts. The legacy recorder and bridge deletion controls described above still apply to their active server copies. Encrypted backup versions follow their separate retention period, and sent notifications remain in the recipient's mailbox.

What does not exist yet

There is no public sharing feature or personal-account system. Device transcripts are not automatically synchronized between browsers; the bridge, server storage and encrypted backups work as described above. The server does not transcribe audio uploaded from a device. Legacy Server recorder transcripts have no separate retry button. Earnings automation has bounded capture retries, but does not promise unattended access to every provider or company. Server transcription currently uses English models.

← Back to Live Transcribe · Health check