Mirel 42 Privacy Policy

Last updated:

Mirel 42 gives you a marketing-strategy second opinion on what you choose to read. It needs the text you want assessed. It does not need carte blanche to follow you around the internet.

This policy explains how the Mirel 42 Chrome extension handles information. It is separate from the privacy policies for the Mirel website and other Mirel products.

Who provides Mirel 42

Mirel UG (haftungsbeschränkt)
Osterstraße 24
20259 Hamburg, Germany

Privacy enquiries: hello@usemirel.com

What the extension accesses

Mirel 42 uses temporary access to a tab after you invoke the extension through Chrome’s toolbar or its selection context menu. It does not request permanent access to every website you visit.

For an assessment, it reads the selected passage or extracts page text, together with accompanying page information. You can preview the source before sending it.

Extracted text may include information present in the page even when it is obscured by an overlay. Review the preview before submitting confidential or personal information, including information about other people.

What is sent to OpenAI

When you choose Analyse, the extension sends the following directly from your browser to OpenAI:

Your OpenAI API key is sent to OpenAI to authenticate the request. OpenAI also receives connection information, such as your IP address, as part of the network request.

Selection analysis includes accompanying page information; it is not limited to the highlighted words. Long sources are shortened before transmission.

The extension does not send screenshots, images, a complete HTML document or a list of your browsing history. It does send the URL and title of the specific page you choose to analyse.

Choosing Test connection in Settings sends a small sample argument to OpenAI instead of webpage content.

What stays in your browser

Your API key and model settings are stored locally in Chrome’s extension storage. They are not stored using Chrome’s sync storage.

The extension does not encrypt your API key. Access is restricted to trusted extension contexts, but someone with access to your browser profile or computer may still be able to obtain it.

Source previews and assessment results are held temporarily in the side panel’s memory. The extension does not maintain a saved analysis history.

A passage selected through the context menu and its accompanying information are temporarily placed in Chrome’s session storage so the side panel can receive them. They are removed when consumed or when the associated window closes. An unconsumed selection can remain until the window closes or the browser restarts. Selections older than 15 minutes are not accepted for analysis; this is not a promise of automatic deletion after 15 minutes.

What Mirel receives

Mirel operates no backend for the extension’s assessments. Your API key, source content and results travel directly between your browser and OpenAI, without passing through Mirel’s servers.

The extension includes no analytics, usage tracking or remote crash reporting. Mirel does not sell extension data, use it for advertising, or use it to determine creditworthiness or make lending decisions.

If you contact us, we receive the information you choose to include in your message. Please do not send API keys.

OpenAI’s processing and retention

You use your own OpenAI API account. OpenAI’s applicable terms, account settings and data-handling policies govern its processing, including any processing outside your country or the European Economic Area.

The extension requests that OpenAI not store responses as application history. This does not guarantee zero retention: other retention may apply, including abuse monitoring and processing required to operate the service.

Deleting information locally does not delete information OpenAI has already received.

Further information:

Purpose and legal basis

The extension processes the information described above to provide the assessment you request and remember the settings needed to operate it.

Where we process personal information to provide a service you request under our agreement with you, the legal basis is Article 6(1)(b) GDPR. For other enquiries, we rely on our legitimate interest in responding to communications under Article 6(1)(f) GDPR. Where processing relies on consent, you may withdraw that consent for future processing.

Submitting someone else’s personal information requires an appropriate basis on your part. Choosing Analyse does not establish consent on their behalf.

Your choices and rights

You can choose not to send a page, select a narrower passage, review the source before analysis, or stop using the extension.

Use Delete API key in Settings to remove the stored key and associated configuration. Uninstalling the extension removes its extension storage. You can also revoke your key through your OpenAI account.

Where applicable, you have rights to access, correct or erase personal data, restrict or object to processing, and receive portable data. You may also complain to a data-protection supervisory authority.

Contact hello@usemirel.com about data handled by Mirel. We cannot retrieve or delete assessment content that we never receive; requests concerning OpenAI’s processing should also be directed to OpenAI.

Support correspondence is retained only as needed to address your enquiry, meet applicable legal obligations or resolve disputes.

Visiting the Mirel website

Opening a website link from the extension does not send your assessment or API key to Mirel. Visiting this policy page or another Mirel webpage is subject to the website’s separate privacy policy:

https://usemirel.com/privacy-policy

Chrome Web Store Limited Use

Mirel 42’s use of information received through Chrome APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Information is used and transferred only as needed for the disclosed functionality described in this policy.

Changes

We will update this policy when the extension’s data practices change and revise the date above. Material changes will also be disclosed within the extension where required.