Privacy Policy — IronMemo Audio Recorder

Effective date: 8 October 2026 · Last updated: 9 November 2026 (§9: the right-click item and the shortcut; no change in what data is handled) · Applies to extension v0.6.0 and later · Back to home

IronMemo Audio Recorder ("the extension") is a Chrome extension that records microphone and browser tab audio on the user's own device. Starting with v0.6.0, the extension can also send one recording at a time to IronMemo servers for transcription — always after a separate consent dialog and never automatically. This policy explains exactly what data the extension handles, what is optional, and what happens on the server if you choose to use it.

Summary. Audio recording is local. Transcription is optional and only starts when you click Transcribe with IronMemo on a specific recording. Nothing else is uploaded. IronMemo does not train models on your recordings.

1. Data the extension handles

The extension does not handle any of the following: web browsing history, form input, passwords, location, health data, financial information, biometric identifiers, personal communications outside of the user-initiated recording, or the content of tabs beyond the audio you chose to capture.

2. Where recordings are stored

All recorded audio and transcript files are written to the browser's Origin Private File System (OPFS) on your device. They stay in OPFS until you delete them. Uninstalling the extension deletes them all. The extension makes no automatic network request to any external service for a recording; the only outbound traffic ever originates from a Transcribe click you made.

3. Optional upload to IronMemo

Each recording carries a Transcribe with IronMemo button. Clicking it shows a separate consent dialog and, if you accept, uploads that one recording to IronMemo servers for transcription. The extension keeps the local copy at the same time — the upload is a copy, not a move.

What is sent

What is not sent

Where it goes

The upload target is app.ironmemo.com. The extension holds this origin as an optional host permission: it is requested from Chrome only when you accept the cloud consent, and no host-permission warning is shown at install time.

IronMemo performs the transcription itself and delegates individual steps to third-party sub-processors. As of the effective date shown at the top of this page:

Speech-to-text

Summaries, action items, AI chat

The provider used for a given recording is recorded in the transcript metadata (engine.asr_model_id for speech-to-text). The full and current list of sub-processors is maintained at ironmemo.com/subprocessors; if the list changes, this page is updated together with the extension update that changes it.

Retention on the server

No model training

IronMemo does not use your recordings, transcripts, or summaries to train speech-to-text models, language models, or any other AI system. This is a policy commitment of IronMemo the service. The third-party sub-processors above operate under their own terms, linked in this section — check them if that is a decision you need to verify independently.

Cost

The extension is free to install and use for local recording. Transcription of the first 10 minutes is free — per account, granted once your e-mail is verified. Beyond that a recording is processed only if the account has IronMemo credits. There is no subscription and no monthly cap in addition to that one-time 10-minute grant.

4. Retention and deletion — full picture

5. Sharing

The extension does not sell, transfer, or share user data for advertising or profile-building. There is no analytics provider, no advertising network, and no crash-reporting service embedded in the extension itself.

When you choose to Transcribe a recording, the audio file and its metadata are shared with IronMemo and the sub-processors listed in section 3: speech-to-text providers receive the audio, and LLM providers receive the transcript text for summaries and AI features. No other third party receives your data.

6. Chrome Web Store Limited Use compliance

The use of information received from Google APIs and handled by this extension adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Data is used solely for the extension's single purpose (audio recording and optional transcription) and is not transferred for advertising, sold to data brokers, or used for creditworthiness assessment.

7. AI use

Local recording performs no AI processing. When you click Transcribe with IronMemo, the audio is converted into a text transcript by the speech-to-text sub-processors named in section 3, and IronMemo may produce a summary, action items, or AI-chat answers from that transcript using the LLM sub-processors also named in section 3. Only the transcript text is sent to LLM providers — not the audio. IronMemo does not train models on your recordings, transcripts, or summaries (see section 3).

8. Recording consent and user responsibility

The extension shows a consent screen in the popup on first use that summarizes what it does and what it does not do. When you first click Transcribe, a second, separate consent dialog explains what is uploaded and where, notes that speech-to-text sub-processors are involved, and links to this privacy policy for the detailed list of providers. You must accept it before any upload starts.

By starting a recording, you confirm that you have the right to record all participants under the law of your jurisdiction. Recording laws differ between countries and, within the United States, between states — the user is responsible for compliance with the law that applies to them.

9. Permissions used, and why

The extension declares no static host permissions. The full manifest.json is visible in the public repository at github.com/igorsaevets/ironmemo-recorder.

10. Your rights

You can at any time:

11. Contact

Author: Igor Saevets. Email: igorsaevets@gmail.com. Issue tracker: github.com/igorsaevets/ironmemo-recorder/issues.

12. Changes to this policy

If the extension's data-handling practices change, this page is updated and, where the change is material, the extension's cloud-consent dialog is shown again automatically so that users must re-accept the new terms. The cloud-consent version is incremented whenever the text on that dialog changes.


Written in plain English on purpose. If any part is unclear, please open an issue on the repository and it will be revised.