Skip to content
SpecMiru

Privacy policy

Last updated: October 14, 2026

This policy covers two things that work differently: the SpecMiru Chrome extension and the specmiru.com website (including its forms, roadmap, optional accounts and API).

Publisher (data controller): Mehdi KEDDOUCHE, sole trader (entrepreneur individuel, micro-entreprise) · Rue B.R. Française 1789-1989, 91600 Savigny-sur-Orge, France · SIRET 105 952 337 00019 · RCS Évry 105 952 337 · Contact: support@specmiru.com

1. The Chrome extension

Inspection is processed on your device

SpecMiru inspects pages inside your browser. What you inspect (DOM, HTML, page text, selectors, computed styles, colors, fonts, page URLs, screenshots, assets, the AI instructions you type and the context you copy) is processed locally. The extension does not send it to SpecMiru, to an AI service or to anyone else. The only exception is the short report context of a bug report you choose to send (see “Help & feedback in the extension” below). What you copy or download goes only where you paste or save it.

Data leaves your device in two cases only, and only the data each one describes: the extension’s usage statistics, on by default and off in one click (below), and what you send yourself (Help & feedback in the extension, forms on this website in section 2). Previewing or saving an asset in Assets only requests that file from the site that already serves it to the page (see “Assets: previews and downloads”).

Privacy protections (Settings › Privacy)

Three protections are on by default (recommended). You can turn each one off in Settings › Privacy; your choice is saved on your device and kept until you change it again. Turning one off for the first time shows a short warning, and “Reset privacy protections to recommended defaults” turns all three back on.

Protection On (default) Off (your choice)
Mask emails and tokens Emails, API keys, tokens, credentials and probable secrets are replaced by [redacted] in captured text and exports Shown as they appear on the page
Exclude form values What is typed in fields, text areas, drop-downs and editable areas is never read; fields are masked in screenshots The current values are read and fields are not masked in screenshots
Mask passwords Passwords are never read and are masked in screenshots, even if form values are included Passwords are read and visible in screenshots, only if form values are included too

When you turn a protection off, the corresponding data can appear in the Inspector, in Code exports, in Prepare for AI / Copy for AI and Full context exports, and in screenshots you take. It still stays on your device unless you share it yourself. Masking of emails and tokens is best-effort detection: review what you copy before sharing it.

Always applied, whatever your settings: page URLs in captured data are reduced to origin and path (no query string, fragment or credentials); hidden and file inputs are never read; iframes and other embedded content are masked in screenshots; control and bidirectional-override characters are removed.

These settings never change what the usage statistics contain (see below).

Screenshots taken in the extension

Screenshots (Design › Capture, element capture) are only taken when you click, are masked according to the protections above, and stay in the panel until you copy, download or discard them. The extension does not store them and does not send them anywhere. Pixels that are not fields or frames (displayed text, images) are not analysed or masked: check the image before sharing it.

Assets: previews and downloads

In Assets, when a site does not let the page read one of its images (no CORS), the panel can display that image directly from the address the page itself uses, without a referrer. It is never read, stored or sent anywhere, and carries no badge.

When you save a file the page cannot read (or a video file), SpecMiru can ask Chrome to download it, with the optional downloads permission (“Manage your downloads”). It is never granted at install: the panel first explains why, and Chrome asks you when you click “Allow”, once: it is then reused for later downloads. Chrome’s download manager then requests the file from the site that already serves it to the page, with that site’s cookies and no referrer, and saves it to your Downloads folder. SpecMiru only reads the download’s status and file name; the address and the file are never sent to SpecMiru. YouTube videos and DRM-protected content are never downloaded.

To copy an image, or add it to a .zip, SpecMiru needs the original file. When a site does not let the page read its images, the panel can ask for access to that one site (optional https://*/* host permission, “Read and change your data on ”), only when you use one of these actions and only for the sites they need. It is never granted at install, covers that site’s images until you remove it (chrome://extensions › Site access), and lets the extension read those image files itself, without cookies or referrer. The bytes stay in the panel until they reach your clipboard or the archive you save; they are never stored or sent to SpecMiru.

What the extension stores on your device

  • chrome.storage.local: your display preferences (theme, language, inspect mode, display mode, overlay side and width), your three privacy protections and which first-time warnings you have already seen, whether the Chrome Web Store rating prompt was already shown, and, for usage statistics, your choice (home screen message seen, or statistics turned off) and its version, then, while they are on, a random installation identifier with its creation date and a small queue of unsent events (100 at most, 7 days at most).
  • chrome.storage.session (cleared when the browser closes or the extension restarts): the cleaned current selection for each tab, deleted on navigation, tab closure or when you clear it, plus short-lived technical state for the overlay panel.

Nothing is stored in chrome.storage.sync, and there is no history of your captures.

Usage statistics

On by default, off in one click. The first time you open the extension, a line at the bottom of its home screen says so; its Manage link opens the Usage statistics switch in Settings › Privacy, where you can turn them off or back on at any time. Turning them off never reduces any feature.

  • Purpose: measuring how the extension’s features are used in order to improve it (sections and tools opened, exports made, errors met), for our own use only. No advertising, no profiling, never combined with the website, your account or your feedback.
  • What is sent: predefined product events (for example “section opened”, “export copied” or “capture completed”) with fixed-choice properties (such as format, section or a size range), the extension’s interface language, the extension version and a random installation identifier. Every event is checked against a closed list before it is sent.
  • What is never sent: DOM, HTML, page text, inspected URLs, form values, passwords, emails, tokens, screenshots, assets, AI instructions or copied AI context, whatever your privacy settings.
  • Nature: pseudonymous usage data. The identifier is random and is not linked to a name, email or account, but it links events from the same installation, so the data is not anonymous in the strict legal sense. No person profiles are created in PostHog.
  • Identifier lifetime: created at the first send, it is replaced by a new random identifier at the latest 390 days after its creation (under 13 months). Using it never extends that period. It is deleted as soon as you turn the statistics off.
  • IP address and location: like any internet request, sending goes through your device’s IP address. Our PostHog project is set not to store it, and the extension asks PostHog not to derive any location from it (no country, no city).
  • Recipient: PostHog, Inc., through PostHog Cloud EU (eu.i.posthog.com, servers in Frankfurt), as our processor.
  • Retention: 1 year at most in PostHog. On your device, unsent events are deleted after 7 days.
  • Objecting: the Usage statistics switch in Settings › Privacy (the Manage link on the home screen goes straight to it). Sending stops immediately, the identifier and unsent events are deleted from your device, and your choice is kept, including across updates. Events already received can no longer be linked to your installation and are deleted at the end of their retention period. You can also write to us (section 6).

If we extend what the statistics may contain, the home screen message shows again to tell you before any of the new content is sent; if you turned them off, they stay off.

Help & feedback in the extension

When you click Send in the extension’s Help & feedback sheet, the extension sends what you wrote, with the context described below, to our server (api.specmiru.com) over HTTPS. Nothing is sent before you click Send, and none of it goes through the usage statistics. Once received, it is handled like a message sent from the forms on this website (section 2: storage, retention, your rights). If sending fails, your text stays in the panel and you can copy it. You can also use the roadmap or the feedback form on this website instead.

What extension Feedback and Ideas contain. Feedback includes your rating, your optional message and email, and the SpecMiru version, the major Chrome version, the SpecMiru section you were in, the display mode and the interface language. An idea includes your description, your optional email, and the SpecMiru version, section and language. Neither includes any content of the page you were on. Ideas stay private; we only publish a roadmap item that we write ourselves.

What an extension bug report contains. When you send a bug report from the extension, it includes your description, your email if you add one, and a report context shown to you before sending: the SpecMiru version, the major Chrome version, the display mode (Docked or Overlay), the interface language, the SpecMiru section you were in, a predefined error code if the panel was in an error state, and the address of the current page reduced to its origin and path (query string and fragment are never included). A screenshot is attached only if you click “Add screenshot”. It shows your visible screen as it is, including anything typed in form fields, so that it shows the bug: you see it before sending, and you can remove it or take it again. A bug report never automatically includes the DOM, HTML, page text, styles, selectors, form values, passwords, emails or tokens from the page, your clipboard, console messages or stack traces.

2. The website and its forms

What each form sends

Form What you send
Feedback (Feedback, Bug, Idea) Your message (optional for Feedback), a rating 1–5 (Feedback only, required), optional email, optional extension version. For a bug only: optional page URL and screenshot
Support Your message and your email (required, so we can reply)
Uninstall survey A reason from a list, an optional comment and, if present in the link, the extension version. No email, never linked to an account

Every submission also records the page language (en/fr) and the date. The website never reads or attaches page content, browsing data or anything you did not type or choose. A bug page URL is reduced to origin and path (query string and fragment removed). A bug screenshot is a file you choose; we re-encode it, which removes its metadata (such as location or device information).

Data we process and how long we keep it

Data Why Optional? Retention
Messages (feedback, bug, idea, support), rating, version To read and act on them You choose what to send 730 days after receipt, then deleted automatically (earlier at your request)
Email address Only to reply to you Optional (required for support; none for uninstall) Same as the message
Bug report context (extension: versions, display mode, language, section, error code, page origin and path) To reproduce a bug Included with every bug report you send from the extension, shown before sending Same as the message
Bug page URL (web form) and screenshot To reproduce a bug Optional, explicit Deleted with the report; screenshots are in private storage, never public
Uninstall reason and comment To understand why people leave The whole page is optional 365 days after receipt, then deleted automatically
Internal notes and status Handling your message Written by administrators Deleted with the message
Roadmap voter identifier One vote per browser (or account) per item Only if you vote Cookie: 180 days after it is set. Votes: until you remove them
Anti-abuse key Rate limiting Automatic on forms, votes and sign-in Deleted by a daily purge once its time window (at most 24 hours) has ended
Human-verification signals Blocking automated abuse Automatic on the three forms above Processed by Cloudflare (see below); we store nothing
Account: email, optional display name, language Sign-in links and your Account page Optional: nothing requires an account Until you delete the account
Account: link to your messages and votes Showing you your own history Only while signed in Removed when you delete the account
Administrator accounts and audit log Secure, accountable administration Administrators only Accounts: while they exist. Audit log (identifiers only): 730 days

These deletions run automatically every day. You can ask us at any time to delete what you sent sooner (section 6).

Your messages are private: they are never published automatically. An idea can inspire a public roadmap item, but its public text is written by us: your wording, email and attachments are never shown.

We do not store your IP address. For rate limiting, the server derives a keyed one-way code from the network address and a time window. It cannot be reversed without our secret key, changes with each window, and is deleted after the window ends. Our server does not keep access logs, and application logs never contain your messages, emails, URLs or screenshots.

Roadmap votes

You can vote without an account. Your first vote sets the __Host-sm_voter cookie: a random identifier signed by our server, not derived from your IP address or your browser. It lets each browser count once per item, and it expires 180 days after it is set. Clicking the vote button again removes your vote. Vote counts are public; who voted is not. If you sign in, your votes are linked to your account so they count once across browsers; votes this browser cast before signing in are kept.

Optional SpecMiru account

An account is optional: installing and using SpecMiru, every current feature, sending feedback and voting work without one. If you create one, we process your email (to send one-time sign-in links: there is no password), an optional display name and your language. While signed in, messages you send from this website’s feedback and support forms are linked to your account so you can follow them on your Account page; the uninstall survey is never linked.

Your account is not connected to the extension’s optional usage statistics: no account identifier, email or name is ever sent to PostHog.

On your Account page you can see your linked messages and votes, change your display name and language, and delete your account. Deleting it removes your sign-in identity, profile and any synced preferences, and the link to your votes; messages you sent are kept like messages sent without an account and are no longer linked to you.

Preference sync is not active. A later extension version may offer to copy six display settings (theme, language, inspect mode, display mode, overlay side and width) to your account. Today the extension does not do this, so no preferences are stored. Sync will never include your privacy protections, the pages you inspect, their URLs, page text, selections, captures, assets, AI instructions or copied context.

Cloudflare Turnstile

The feedback, support and uninstall forms use Cloudflare Turnstile to block automated abuse. Turnstile runs a check in your browser and processes technical signals on Cloudflare’s side, such as your IP address and browser characteristics. Our server checks the resulting token with Cloudflare without sending your IP address. Cloudflare acts as our processor to protect the forms, and as a controller when it uses these signals to improve its bot detection. See its Turnstile privacy addendum and privacy policy.

Audience measurement

To understand how the website is used and improve it, we measure its traffic with Umami, an open-source tool we host ourselves on our server in France. None of this data is shared with a third party.

  • No cookie, no identifier: no cookie is set and nothing is stored on your device to recognise you.
  • Data collected: the page visited (without the URL query or fragment), the referring site, browser, operating system, device type, screen size, language, the country and city derived from the IP address, and a few actions such as clicking « Add to Chrome ». Never the content of your messages or forms.
  • IP address: used only during the visit to derive the country and city, then discarded: it is not stored. Page views of the same visit are grouped with a technical fingerprint whose salt is renewed every month; it cannot follow you over time or across other websites.
  • No cross-referencing: these statistics are used only to measure this website’s audience. They are not linked to your account, your messages or the extension’s statistics.
  • Retention: 25 months at most.
  • Objection: your browser is not counted if it sends the Do Not Track signal, or if you turn measurement off at the bottom of the cookie policy.

This website uses no advertising pixels, no session replay and no third-party trackers.

3. Service providers and hosting

  • OVHcloud (OVH SAS, France): virtual server hosting the website and the API, in Strasbourg, France.
  • Supabase (Supabase, Inc.): database, private file storage for bug screenshots, administrator authentication and optional account sign-in, including sign-in emails.
  • Cloudflare (Cloudflare, Inc.): Turnstile human verification on the three web forms.
  • PostHog (PostHog, Inc.): extension usage statistics only (on by default, can be turned off), in PostHog Cloud EU (Frankfurt).

Supabase, Cloudflare and PostHog are companies based in the United States. Where their processing involves a transfer of personal data outside the European Economic Area, it relies on the safeguards set out in their data processing terms.

4. Chrome Web Store: limited use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

In plain terms, data the extension handles through Chrome APIs is used only to provide SpecMiru’s features you use. It is not sold, not used for advertising, not transferred to data brokers or other third parties (except the processors above, to run the features you chose), and not used to determine creditworthiness or for lending.

  • Feedback, bug reports, ideas and the uninstall survey: our legitimate interest in supporting and improving SpecMiru.
  • Support requests: your request, and our legitimate interest in answering it.
  • Report context of an extension bug report: our legitimate interest in reproducing the bug you report.
  • Optional email, bug URL on the web form and screenshot: your choice to provide them (consent).
  • Extension usage statistics: our legitimate interest in measuring how the extension is used in order to improve it, with a simple right to object at any time (Settings › Privacy, reached from the Manage link on the home screen).
  • Optional account: performing the service you asked for by creating it (contract).
  • Website audience measurement: our legitimate interest in understanding how the website is used to improve it.
  • Anti-abuse measures, Turnstile and the voter cookie: our legitimate interest in protecting the service and keeping votes fair.

Inspection in the extension happens on your device: we do not receive that data.

6. Your rights

You can ask for access, rectification, erasure, restriction or portability of your data, object to its processing, and withdraw your consent at any time, by writing to support@specmiru.com. Messages sent without an account are not tied to you, so include enough detail (date, email used) for us to find them. With an optional account, you can see your linked messages and votes, change your profile and delete your account yourself on your Account page. You may also lodge a complaint with your supervisory authority (in France, the CNIL).

7. Security

See the security page. Private data is only accessible to provisioned administrators protected by multi-factor authentication.

8. Changes

We will update this page when our processing changes, and change the “last updated” date above.