Privacy Policy

We designed this tool so we couldn't spy on you even if we wanted to.

Your voice stays on your device. Always. Here's the full picture of what we collect, what we don't, and why our approach to privacy isn't just policy — it's how the tool is built.

Last updated: January 15, 2025

The Short Version (For People in a Hurry)

We know you probably came here with one question: is this tool listening to me? The answer is no — and not just because of a privacy policy. Audio processing happens entirely inside your browser. We don't have servers that receive your voice. There is nothing to "promise" because there is no mechanism that could collect it in the first place.
🎙️ Voice data: never transmitted
👤 No account required
🍪 No advertising cookies
📊 Only anonymous page analytics

That said — a full privacy policy exists because there are things we do collect (basic, anonymous web analytics) and things you deserve to understand clearly. So here is the complete picture, written for humans, not lawyers.


What We Collect — and What We Don't

Most privacy policies list a mountain of things they collect and bury the important stuff in paragraph seventeen. We'd rather be upfront, so here's the complete breakdown:

Data Type Collected? What Actually Happens
Voice / audio recordings ✓ Never Processed in-browser only. Never leaves your device.
Microphone input stream ✓ Never The Web Audio API reads it locally. We have no access.
Your name or email ✓ Never No sign-up. No forms. No personal info requested.
IP address ✓ Never stored May pass through standard web requests but is never logged by us.
Page views & referrer URLs Anonymous only Basic analytics to understand how many people use the tool. No user-level tracking.
Language preference Cookie only A single cookie stores your language choice. No cross-site tracking.
Device or browser fingerprint ✓ Never We don't build profiles based on your device.

Why Your Audio Is Genuinely Private

We want to be specific here — because "your data is safe with us" is something every company says, and it's a promise that depends entirely on trusting whoever made it. We don't think you should have to take our word for it.

When you click Start Test and allow microphone access, here's what actually happens:

  • 🔧 Your browser's built-in Web Audio API receives the microphone stream — the same API used by voice memo apps, online musical instruments, and countless other tools that process audio locally.
  • 📈 That audio stream is used to draw the waveform you see on screen. The JavaScript running in your browser tab does this rendering. Our servers don't participate.
  • ⏺️ If you use the record and playback feature, the MediaRecorder API captures audio into your browser's memory. It plays back in your tab. When you close the tab, the recording is gone — we never had it.
  • 🌐 At no point is an audio stream, audio file, or recording sent to any server. There is no upload. There is no storage. There is no processing happening anywhere except your own device.
Technical note for the skeptical: You can verify this yourself. Open your browser's Developer Tools (F12), go to the Network tab, and run a mic test. You'll see no audio data leaving your machine — because none does.

The Analytics We Do Use

We're honest: we do use basic web analytics. Without some way to measure traffic, we'd have no idea whether the site is being used by ten people or ten million — and that matters for deciding what to improve.

What we collect through analytics is genuinely minimal:

  • 📄 Page views — which pages are visited and roughly how often.
  • 🔗 Referrer URLs — what website or search engine brought you here. This helps us understand how people find MicWorker.
  • 🌍 General geography — country-level only, based on anonymized data. We can't tell which city you're in, and we don't try.
  • 📱 Device type — whether you're on a phone, tablet, or desktop. Useful for making sure the tool works well on all screens.

None of this is linked to you as an individual. We see aggregate numbers — not personal histories.

ℹ️ We do not use Google Analytics, Meta Pixel, or any other advertising-driven analytics platform. The data we collect is never used to build advertising profiles or shared with third-party ad networks.

Cookies — What We Use and Why

MicWorker uses exactly one type of cookie for functional purposes: a language preference cookie. If you've selected a language like Spanish or German, this cookie remembers that choice so you don't have to re-select it every visit.

That's it. There are no advertising cookies. No session-tracking cookies tied to your identity. No third-party cookies dropped by advertising networks. If you use a browser extension that blocks trackers, you won't break MicWorker — there's nothing to block beyond the basics.

You can clear cookies at any time through your browser settings without affecting your ability to use the tool. The only thing that resets is your language preference.


Third-Party Services

MicWorker is a simple tool, and we've deliberately kept the number of third-party integrations low. Here's what's on the page and what it does:

Font Awesome (Icons)

We use Font Awesome via their CDN for interface icons — the microphone icon, the chevron arrows, and similar UI elements. Font Awesome's CDN may log standard web request data (IP address, browser type) to serve the icon files. This is standard CDN behavior and is governed by Font Awesome's own privacy policy.

No Advertising Networks

MicWorker doesn't run ads. There are no advertising scripts, no demand-side platforms, no programmatic ad networks loading on the page. This means none of the usual advertising-related data collection (interest profiles, retargeting pixels, cross-site tracking) happens here.

No Social Media Plugins

There are no embedded social media widgets on MicWorker. No Facebook Like buttons. No Twitter embeds. These things are common vectors for cross-site tracking — we don't have them.


Children's Privacy

MicWorker is a utility tool suitable for users of all ages. We don't knowingly collect any personal information from anyone — children or adults. Since the tool requires no account creation and no personal data entry of any kind, there is no personal data of children's to protect in the first place.

If you are a parent or guardian with a concern about how your child used MicWorker, please email us at contactmu97@gmail.com. We take these messages seriously and respond personally.


Your Rights

Depending on where you live, you may have specific legal rights around personal data — including the right to access, correct, or delete data held about you. Under GDPR (for European users) and similar frameworks like CCPA (for California residents), these rights apply to identifiable personal data.

In practice: since we don't collect personal data, there's very little to exercise rights against. We don't have a profile of you. We don't have your voice recordings. We don't know who you are.

If you'd like confirmation in writing that we don't hold personal data about you — or if you have any other rights-related question — email us at contactmu97@gmail.com. We'll respond clearly and directly.


When This Policy Changes

If we ever change how we handle data in a meaningful way, we'll update the "Last updated" date at the top of this page and note what changed. We won't quietly alter the policy and hope nobody notices.

Our commitment is this: if we ever added something that changed the privacy picture for users — new analytics, a new third-party service, anything like that — we'd tell you clearly, not bury it in a footnote.


Privacy Questions People Actually Ask

No — and this isn't just a policy we're asking you to trust. The way the tool is built, audio processing happens entirely inside your browser. There's no connection between your microphone and our servers. We genuinely cannot receive your voice even if we wanted to. You can verify this yourself with browser developer tools: watch the Network tab during a test and you'll see no audio data leaving your machine.

Browsers require explicit permission before any web page can access your microphone — this is a core browser security feature, not something specific to MicWorker. When you click Allow, you're granting your browser access to the mic so it can draw the waveform. You're not sending anything to us. Granting permission to the browser and sending audio to a server are two completely separate things.

Yes. GDPR applies to the processing of personal data about EU residents. Since MicWorker doesn't collect personal data — no names, no emails, no voice recordings, no individual tracking — the GDPR compliance picture is straightforward: there's no personal data being processed. We use only anonymous page analytics and a functional language preference cookie, neither of which constitutes personal data processing under GDPR.

Yes. MicWorker doesn't install anything, doesn't require an account, and doesn't transmit audio data. It's a browser-based tool that uses standard browser APIs. Many IT teams and support staff actually use MicWorker themselves to help diagnose mic issues remotely, precisely because nothing is installed and nothing is stored.

Email us directly at contactmu97@gmail.com. There's no ticket system, no automated response queue. We read every message and respond personally. Privacy questions are taken seriously — if something isn't clear in this policy, we want to know so we can explain it better.

Privacy questions? Just ask.

We don't have a legal department — just a small team that reads every email. If something here isn't clear, or you have a concern we haven't addressed, reach out. We'll respond directly.

contactmu97@gmail.com