IronMemo — Meeting Recorder · Privacy Policy
Last updated: August 8, 2026
Applies to: IronMemo — Meeting Recorder browser extension (the “Extension”), version 0.2.1 and later.
This Privacy Policy describes how the IronMemo — Meeting Recorder browser extension handles your data. It covers only the Extension. The IronMemo web service at app.ironmemo.com is governed by its own separate privacy policy.
In short: The Extension records call audio and saves it as a file on your computer first. Nothing is uploaded automatically. If — and only if — you press “Send to IronMemo”, that recording is transmitted over an encrypted connection (HTTPS) to the IronMemo service and processed under your IronMemo account for transcription and summarization. The Extension contains no analytics or trackers, communicates only with IronMemo, and we never sell your data.
1. What the Extension does
The Extension lets you record the audio of a browser-based call or meeting and, at your explicit request, send the recording to your IronMemo account for processing. To make a recording it captures:
- Audio of a tab, window, or screen that you explicitly select through your browser’s standard sharing dialog (this may include the voices of other participants in your call).
- Your microphone audio, if you grant microphone access (optional — recording can proceed without it).
These sources are mixed into a single audio file (WebM/Opus format) directly in your browser, in a visible recorder tab that stays open for the whole recording and serves as the recording indicator.
Recording and saving the file locally work without an IronMemo account. An account is required only if you choose to upload a recording.
2. Data the Extension handles
| Data | What happens to it |
|---|---|
| Recorded audio (tab/screen + microphone) | Saved first as a local file in your Downloads folder, subfolder “IronMemo Records”. A working copy of the same bytes is kept in the browser’s extension storage (IndexedDB) so that the exact same file can be uploaded if you later choose to send it — and can still be sent to another workspace afterwards, because the Extension cannot read back the file it saved to your disk. That copy stays as long as the recording is in the Extension’s list: it is deleted when you delete that recording in the Extension, when its file disappears from your Downloads folder, or when you uninstall the Extension. Transmitted to IronMemo only when you press “Send to IronMemo” (see section 3). |
| Recording metadata (file name with date/time, file size, duration, the saved file’s path in Downloads, recording and upload status, and — for each workspace a recording has been sent to — the workspace name and identifier, the identifier of the recording created on the server, the link to the result, and the time it was sent) | Stored locally as a list of your recordings so the Extension can show them, restore its interface, and know which workspaces a recording has already been sent to. The file name (used as the recording title), size, and audio format are transmitted to IronMemo together with the recording when you send it. |
| Recording (transcription) settings | Your chosen recognition language and mode, recognition quality (ASR tier), and whether to separate speakers (“diarization”), stored locally. These preferences are transmitted to IronMemo together with the recording when you send it, so the service can process it as you asked; how the service applies them is governed by the IronMemo service privacy policy. |
| Account and sign-in data | The Extension has no sign-up or password form and never sees your password. To authorize an upload it reads your existing app.ironmemo.com session (an authentication cookie) through the browser’s cookie API, and keeps a copy of that session token plus your account label (the email address or phone number shown on your account) in local extension storage — so the popup can show “Signed in as …” and uploads are attributed to your own account. It also keeps a local copy of the list of workspaces available in your IronMemo account (their names and identifiers, together with the token the list was fetched with), so the workspace picker on the send screen appears without delay; the list is re-fetched each time you open the popup and is erased when you sign out of app.ironmemo.com. The Extension reads IronMemo’s own cookies only; it cannot and does not read cookies of any other website. |
| Privacy-consent record | The version of this policy you accepted in the Extension and the timestamp of acceptance, stored locally. |
The Extension contains no analytics, advertising, or tracking of any kind and communicates only with IronMemo (the app.ironmemo.com API and IronMemo’s file storage). Besides the upload you explicitly request, its network requests are authenticated calls to app.ironmemo.com only: a sign-in status check and a fetch of the list of workspaces in your account each time you open the popup (see section 3), so the send screen can show which workspace a recording would go to, and — when you open the recording settings — fetching the list of recognition languages. None of these carry any audio or recording data.
3. When data leaves your device
Your recording (and its metadata) leaves your device only when both of the following are true:
- you are signed in to IronMemo (sign-in happens on app.ironmemo.com, not in the Extension), and
- you press the “Send to IronMemo” button for a specific finished recording.
At that moment the Extension transmits, over HTTPS:
- the audio file of that recording — to IronMemo’s file storage, via a short-lived signed upload URL issued by the IronMemo API;
- the recording title (the local file name, which contains the date and time), the file size, and the audio format;
- your recording (transcription) settings — the recognition language and mode, the recognition quality (ASR tier), and the speaker-separation preference;
- the identifier of the workspace you selected on the send screen, so the recording is filed there;
- your session token, so the upload is attributed to your IronMemo account and workspace.
You can send the same recording to more than one of your workspaces: each send is a separate action that you start with the button, and the Extension does not offer to send a recording to a workspace it has already been sent to.
Because a sent recording is processed and stored by the IronMemo web service, uploading is also subject to the IronMemo service privacy policy; by sending a recording you accept that policy in addition to this one.
There is no automatic upload and no setting to enable one. Stopping a recording never uploads anything: it saves the file locally and waits for your decision. If you never press “Send to IronMemo”, the recording never leaves your device.
Separately from recordings: when you open the Extension’s popup while signed in, it may contact app.ironmemo.com to check and refresh your sign-in status and to fetch the list of workspaces in your account (so the send screen can offer you a choice, and so a renamed or newly shared workspace shows up). These authenticated requests transmit your session token to the same service that issued it, and never include any audio or recording data.
4. Processing on the IronMemo service
After you send a recording, it is processed by the IronMemo web service (transcription, summarization, storage in your account). That processing — including where and with which provider the uploaded file is stored, server-side storage periods, how your recording settings (such as speaker separation) are applied, security measures, and deletion — is governed by the IronMemo service privacy policy, which you accept when you send a recording. You can view and delete uploaded recordings in your IronMemo account.
5. Permissions and why they are used
| Permission | Purpose |
|---|---|
| storage | Keep settings, recording state, your consent record, your account label, the cached list of your workspaces, and a copy of the session token locally. |
| unlimitedStorage | Hold the finished recording in browser storage for as long as it is in the Extension’s list — an hour-long call is tens of megabytes and does not fit the default quota. This copy is what lets you send a recording (including to a second workspace) after it has been saved. |
| downloads | Save the finished recording as a file in your Downloads folder (“IronMemo Records”). |
| cookies + host access to app.ironmemo.com | Read your existing IronMemo session so that “Send to IronMemo” uploads under your own account without a separate login form, and call the IronMemo API when you send a recording. No other site’s cookies are accessible. |
| Microphone (requested at runtime) | Include your voice in the recording. Optional — recording can proceed without it. |
| Screen/tab audio (requested at runtime, per recording) | Capture call audio from the tab, window, or screen you select in the browser’s sharing dialog. |
6. Data sharing and selling
We do not sell or rent your data. The Extension transmits your data to no one other than IronMemo: a recording you choose to send goes only to the IronMemo service, solely to provide the transcription and summary you requested. Any service providers that process or store uploaded data on IronMemo’s behalf are described in the service privacy policy. We do not use your data for advertising, do not transfer it to data brokers, and do not use it to determine creditworthiness or for lending purposes.
7. Data retention and deletion
- The local recording file in Downloads is entirely under your control; delete it like any other file. The Extension never deletes your local files.
- The Extension keeps a local list of your recordings (their metadata and, for sent ones, the links to the results). The audio bytes held in extension storage are not deleted after an upload — they remain available so you can also send that recording to another workspace. They are deleted when you delete the recording in the Extension, when the recording drops off the list because you deleted its file from Downloads, or when you uninstall the Extension. An hour-long call is tens of megabytes, so deleting recordings you no longer need is how you reclaim that space.
- Locally stored settings (including your recording/transcription settings), recording metadata (file name, size, duration, saved file path, recording and upload status, per-workspace send history with result links), the consent record, the account label, the cached workspace list, and the session-token copy are removed when you uninstall the Extension or clear its data. Signing out of app.ironmemo.com ends your session: the Extension erases its stored token copy, account label, and cached workspace list, and can no longer refresh the session.
- Uploaded recordings live in your IronMemo account, where you can delete them; server-side retention is described in the service privacy policy.
8. Your rights
Depending on where you live (for example, the GDPR in the EU/EEA or the CCPA in California), you may have the right to access, correct, delete, or receive a copy of your personal data. For data in your IronMemo account, use the account tools or contact us at dsar@ironmemo.com. For data stored locally by the Extension, you are in direct control as described in section 7.
9. Recording other people — your responsibilities
Recordings may capture other people’s voices and personal data. You — not IronMemo — decide whom and when to record and whether to upload the result. Before recording, and before sending a recording that contains other people, you are solely responsible for complying with all laws that apply to you and to the participants, including:
- call-recording and wiretapping laws — many jurisdictions, including a number of U.S. states and EU countries, require the consent of all participants;
- data-protection laws (for example the GDPR or the CCPA) with respect to participants’ personal data;
- biometric-privacy laws (for example the Illinois Biometric Information Privacy Act) where they apply to voice data.
Notify participants that the call is being recorded, obtain every consent your jurisdiction requires, and do not send a recording to IronMemo unless you have the right to share it for processing. The confirmation screens inside the Extension document your acknowledgement; they do not replace the participants’ consent.
10. Children
The Extension is not directed to children and does not knowingly collect data from children.
11. Changes to this policy
We may update this Privacy Policy from time to time. Every update is reflected by the “Last updated” date above. When a change materially affects how your data is handled (as with the introduction of uploads in version 0.2.0), the Extension asks for your consent again before it can be used; clarifying or minor updates only update the date and do not require re-consent. The version 0.2.1 revision is of the latter kind: it covers the local recording list, the recording settings sent with an upload, the workspace picker on the send screen (including the locally cached workspace list and the ability to send the same recording to more than one of your workspaces), and the fact that a recording’s local audio copy is now kept until you delete the recording instead of being removed after an upload. None of this changes what leaves your device or when: audio is still transmitted only when you press “Send to IronMemo”.
12. Contact
For privacy questions about the Extension, contact: privacy@ironmemo.com (Oxford Construction LLC, provider of the IronMemo product).