Privacy Policy

Last updated: October 26, 2026. This policy describes how MicProbe handles information when you test your microphone, sign in, save reports or purchase Premium.

Who is responsible for your information

MicProbe is operated from Türkiye by Burak ÖZER, the data controller for the information handled through MicProbe. For privacy questions or requests about your information, contact support@micprobe.com.

How and why information is processed

Information is collected electronically through your browser when you use a test, choose settings, sign in or save a report, through Google's sign-in response, and through purchase-verification responses from Freemius. If you contact us, we also receive the information you include in your message.

Account recognition, requested report storage, purchase verification and related support are processed to provide the service you request, on the basis of establishing or performing that service contract under Article 5(2)(c) of Türkiye's Personal Data Protection Law No. 6698 (KVKK). Necessary security and fault-diagnosis processing relies on the legitimate interest in keeping the service secure and working, subject to your fundamental rights and freedoms, under Article 5(2)(f). The 30-day sign-in cookie is used only while “Keep me signed in on this device” is selected when you sign in; that box starts selected and you can clear it. Signing out removes the cookie. If you are in the European Economic Area or the United Kingdom, the GDPR section also applies.

Microphone tests and reports

Microphone recordings are processed in your browser. Audio recordings, PCM samples and transcripts are not uploaded to MicProbe. Reports contain measurements, microphone and browser information, captured settings, scope information, the saved evaluation and any personal notes you add.

During a call test, your browser asks Cloudflare's public STUN service for your connection's public address, so the test's two ends on your device can reach each other on mobile networks. A call test also checks your connection: your browser sends a built-in sample voice, not your own, through a Cloudflare relay server near you and back, and measures how much of it was lost or delayed. Cloudflare relays that sample and receives your connection's address, as it does for any request to this site. Your own audio is not sent to Cloudflare or MicProbe; only the connection measurements, such as how much of the sample was lost and how late it arrived, are sent with the test's other measurements.

The Raw recorder saves a recording without testing it: no report or measurement is created and nothing is sent to MicProbe. While you record, the audio is written to your browser's private storage on this device so that long recordings do not fill its memory. That file is deleted when you start another recording or open MicProbe again, so download it if you want to keep it.

Without signing in, you can test your microphone and view the current result, but reports are not saved to your account.

With Premium, you can explicitly save the current guest result to your account. Only that selected report is saved after its connection to this visit is verified. New reports are assessed independently, without earlier reports or personal notes as inputs. Earlier personal review answers and versions remain read-only; they do not affect new reports. Deleting a saved report also deletes its earlier review and removes stored comparison measurements.

Free testing has a daily limit. A first-party micprobe_visitor cookie contains a random browser identifier for up to 30 days; the server stores its hash. Signed-in limits use your account identifier. To manage interrupted tests, this tab may temporarily keep a test identifier and a small measurement summary. Audio recordings are never sent with these requests.

Test-access records contain identifiers, dates and completion status. Quota records and network/browser hashes older than the preceding two UTC days are deleted at the next test request. A daily salted hash of your network address (an IPv6 address is first reduced to its /64 range) limits anonymous testing from the same connection. A random daily browser key, stored only after you start a test, gives separate browsers their own allowance within a connection-wide ceiling. It does not use hardware or browser characteristics. The server stores only a daily salted hash of the browser key paired with the network; it does not store the raw key or network address. Clearing only the visitor cookie does not reset this pairing; clearing all site data or private browsing can create a new browser key, while the connection-wide ceiling still applies. If browser storage is blocked, the connection shares the smaller allowance. Minimal account-owned proof that a result was accepted is kept separately for up to the latest 200 outstanding reports, until saved, removed or replaced by newer proofs; it contains account/run identifiers, a measurement digest and completion/check counts, without network addresses, browser keys, audio or report text. People sharing a network connection can sign in to use their separate account allowances. Enforcing the free daily allowance this way relies on our legitimate interest in keeping free testing available and preventing its abuse, under KVKK Article 5(2)(f).

To check how the score works in real rooms, the server also keeps daily counts of test results. The first time a test's result is given, it adds one to a count named only by fixed words: the score model, the test type and app, whether a score was given and why not, how the quiet check and the sound range came out, and the device's operating system and type (phone or computer). The counts contain no identifier, network address, recording, measured value or time of day, and are not linked to your visit or account.

Google sign-in and sessions

The home page and test screen check your existing MicProbe session to show the right account and purchase actions. The home page never loads Google's sign-in interface or your saved reports. On the test screen, a visitor who is not signed in may see Google's sign-in suggestion, described below.

When you choose Google sign-in, Google provides your account identifier, name, verified email address and, when available, a profile picture URL. MicProbe stores these to recognize and display your account, associate saved reports with you and link verified purchases. Your picture loads from Google's image service without sending the MicProbe page address as a referrer. If it is unavailable, we display your initials. MicProbe does not request access to Gmail, Google Drive, contacts or your Google password.

The Google sign-in form selects “Keep me signed in on this device” by default. Leaving it selected saves the sign-in cookie for 30 days after your last visit, and the session itself also remains valid on the server for 30 days after your last visit. Unchecking it uses a browser-session cookie, and the server independently ends that session 24 hours after your last visit regardless of whether the browser keeps the cookie longer (for example through session restore). Browser session-restore features may retain a session cookie past when its server-side session has expired, so sign out on shared devices. Signing out ends that session immediately; it does not delete your saved reports or purchase association. Sign-in security cookies expire after 10 minutes or are removed when sign-in succeeds.

These first-party cookies are named micprobe_session (your signed-in session) and micprobe_login_nonce_* (proof that a sign-in request started in this browser). Google's sign-in service loads when you open the sign-in panel or reach a step that asks you to confirm your Google account. It also loads on the test screen when you are not signed in, to show Google's sign-in suggestion (One Tap): a small Google prompt that offers your Google account. Nothing happens unless you choose an account there; choosing one signs you in and keeps you signed in on this device, as the selected box does. You can close the suggestion, and Google may then stop showing it for a while. Once Google's service loads, Google may set its own cookies on this site, such as g_state and, for sign-in on iPhone and iPad, g_csrf_token; Google's privacy policy covers them. You can test your microphone without an account.

Saved information and your controls

New reports captured for a Premium account are saved to that account. Free-account results are not added to a new browser or account archive. You can delete individual saved reports from Saved reports. Pending saves remain with their original account; older pending items are not automatically uploaded when you sign in or upgrade. Signing out hides your saved reports on this browser.

Your account keeps your latest 200 reports within 10 MiB, including reserved space for notes and any earlier reviews. New reports automatically replace the oldest saved reports when room is needed; an added explanation preserves its own report and may remove the oldest other reports. A report that cannot fit on its own does not remove existing reports. A change in Premium status does not itself delete reports. If browser storage for pending saves is full, the current result remains on the open page and the app reports that it could not be retained. Browser storage also holds preferences and pending account operations. Clearing site data removes those local items and may discard changes that have not synchronized. It does not delete information already saved to your account.

• Microphone and scenario preferences: the microphone and scenario you choose are remembered on this browser until changed or site data is cleared. No automatic expiry is currently applied.
• Pending reports and notes: pending report copies stay with their owning account until the save is confirmed or the pending item is removed. A note on an already saved report stays in the open page if its update fails; retry saving before leaving. A small account-bound test identifier is retained after deletion to prevent a delayed save from recreating that report; it contains no measurements or audio.
• Checkout return: temporary tab storage keeps the current report and scenario while you visit checkout. Restoration is allowed for 30 minutes and consumes the saved copy. A pending purchase return is removed after successful verification. These items otherwise remain until the tab session ends or site data is cleared.
• Diagnostic logs: MicProbe keeps no diagnostic log on the public site; errors and warnings appear only in your browser's developer console. MicProbe also deletes the diagnostic log that earlier versions kept on this browser.
• Earlier purchase access: if account sign-in is unavailable, verified purchase-access information may be remembered on this browser until replaced or site data is cleared. The server checks access before providing premium details.

Cookies and browser storage

The items below are stored on your device only for a feature you use. MicProbe uses no advertising or cross-site tracking cookies, and the page statistics described under Service providers use no cookies or browser storage. Because nothing here serves any other purpose, MicProbe does not show a cookie consent banner.

Checkout and purchase management on Freemius's site use Freemius's own cookies. Clearing this site's data in your browser removes MicProbe's items and signs you out.

Service providers

When Premium-access email notifications are enabled, Resend processes your email address, display name and notification content to send Premium-access confirmations. It also processes support replies written by the MicProbe operator. Audio recordings and saved report measurements are not included in these emails. Replies to these messages go to support@micprobe.com.

MicProbe stores notification identifiers, recipients, a copy for safe retries and delivery status with the account. These records currently have no automatic expiry. Addresses that bounce permanently or report spam are kept on a suppression list to prevent further automated mail until reviewed. Resend also keeps delivery records under its own retention policy.

MicProbe also keeps internal operational event logs — for example a payment-provider outage, a failed email delivery, or an AI-explanation limit being reached — to notice and fix problems with the service. These records use internal account or license identifiers and error/event codes where needed; they never contain your email address, IP address, a session cookie, a key or a token. When a verified test cannot produce a score, a separate anonymous operational event records fixed failure categories: the scoring version and test type, browser/operating-system/device categories, the failed scoring stage, missing measurement categories, a one-word category for what the speech check found in the guided reading (for example voice found, nothing recorded, no louder than the background, or the check could not run; never a level or a length), and audio-source, analysis and model-check status/reason codes, including the model's execution stage and exception category. Exception messages and stack traces are not sent. This failure event contains no account, test, report or visit identifier, audio, audio hash, individual measured values or free text, and is independent of visit tracking. Operational records are kept for 90 days. Certain event types can trigger an automated alert email to the MicProbe owner, sent through Resend, independently of whether Premium-access email to you is enabled; score-failure warnings do not trigger these emails.

When you are signed in with Premium and request the full result for a completed report, Anthropic (United States) processes that report's labelled measurements, accepted findings, test settings and scope, the browser and operating-system categories reported during the test, and the microphone input name reported by your browser to help explain the result in plain language. The input name can describe a microphone, audio interface or virtual input; it is limited to 200 characters and does not verify the physical microphone. MicProbe also supplies its own explanation instructions and permitted recommendations. No audio, transcript, account or run identifier, email address, device or group identifier, or personal notes are sent to Anthropic. Accepted and in-progress explanations are reused, and daily request limits apply per account and across all accounts. The explanation does not change the report's score or measured findings. It is part of Premium: opening a result card or purchasing Premium does not automatically request it.

When a completed test's result is shown, signed in or not and with or without Premium, MicProbe also asks Anthropic for a short plain-language reading of that result for the result card. The same report information listed above is processed, with the same exclusions: no audio, transcript, account or run identifier, email address, device or group identifier, or personal notes. One reading is written per test and reused for six hours, and a daily limit applies across all visitors. It does not change the report's score or measured findings.

To monitor explanation costs and errors, MicProbe also keeps records of AI attempts: timestamps, the model used, a provider request identifier, token and cache counts, estimated cost and response/error status. These records contain no account or report identifier, audio, prompt or answer text. Records older than 90 days are removed when a new attempt is admitted.

Detailed analysis sends report measurements to the MicProbe server. The hosted service uses Cloudflare to serve requests and store account data. Hosting providers process network information such as your IP address when serving requests. Google provides sign-in. MicProbe serves its web fonts itself, so loading a page sends no request to a font provider. Freemius processes purchases; MicProbe stores the license association and access status so you can return with the same account.

For activated visit tracking, the assessment request can carry the page's temporary event reference and attempt number. The server records the accepted technical score or fixed unavailability reason before returning it; a separate event records whether the page displayed it. Visit activity also records when the pricing section is visible, Premium controls are used, and checkout opens, closes or reports a purchase linked to the account. A successful Google sign-in adds an anonymous completion event, without the Google identity, email address, account identifier, credential, license or payment details. These visit events use the same limited metadata and retention described below.

MicProbe uses Cloudflare Web Analytics to count page visits and measure how quickly pages load. Its script sets no cookies and uses no browser storage, and Cloudflare states that it does not fingerprint visitors. It reports the page address and referrer, browser, operating system, device type, the country derived from the connection and page-load timings. We see only aggregated statistics. This relies on our legitimate interest in understanding how the service is used and keeping it fast, under KVKK Article 5(2)(f).

MicProbe's own server also counts page views in which a person actually uses the page. Public pages load a small first-party script that activates once you first click, tap, scroll or press a key on the page, or after the page has been visible for 15 seconds. It sends the page path, the first interaction, the referring site's domain name and, when present, the address's source tag (for example utm_source=chatgpt.com). After activation, it also sends a limited sequence of named controls clicked, page changes, the selected test or recorder, which type of setting changed, recording start/stop/completion or failure, recording duration, audio playback and report opening. When a new test's accepted result is displayed, it also sends the displayed technical score out of 10 and its scoring version, or a fixed reason code when no score could be given. A click on a download, share or purchase control records the request, not proof that it succeeded. A random identifier held only in page memory and a page-local attempt number put these steps in order. Neither is an account, test or saved-report identifier. No audio, typed text, microphone name, setting value other than on/off, report text, individual measurements, or URL queries and fragments are included in these activity events.

The server records these signals with the country and network provider derived from the connection, device, browser and operating-system categories, your browser's user-agent string, whether that string identifies an automated client, the name an automated agent gives when it signs its requests, and a salted one-way hash of your IP address; the raw IP address is never stored. This counting uses no cookies or persistent browser storage for visitors: the only cookie involved, mp_notrack, is placed on the site operator's own devices to leave them out. These records help the operator understand how people find and use the site, separate likely human visits from automation, and review the steps within a visit. Visitors are grouped by IP hash and browser user-agent string, never by name; shared networks may combine people, and different devices or networks may split one person. The records are not used for advertising or linked to account data or saved test/report records. They are stored with Cloudflare and currently have no automatic expiry. This relies on our legitimate interest in understanding how the service is used, under KVKK Article 5(2)(f).

Checkout and purchase management open on Freemius's site when you choose them. For direct access to purchase management, MicProbe checks your Google identity against the purchase owner and requests a short-lived sign-in link from Freemius. MicProbe does not store that link or a Freemius password. Freemius's payment providers and cookie controls apply there; see Freemius's cookie information. MicProbe does not embed advertising scripts in its pages. Service providers may process information outside your country.

See the privacy information from Google, Cloudflare and Freemius for their services.

International data transfers

MicProbe is operated from Türkiye, and some of the processing described above takes place outside Türkiye. Under KVKK Article 9, transferring personal data abroad requires an adequacy decision, an appropriate safeguard provided for in that article (such as the Personal Data Protection Board's standard contract, notified to the Board) or one of the exceptions it lists. The providers below receive the information described in the relevant section above, in the United States unless noted:

• Cloudflare, Inc. (United States, with infrastructure in multiple countries) — hosting, request handling, account data storage, page-visit and engagement statistics, and the relay server for a call test's connection check, on MicProbe's behalf.
• Resend (United States) — sending Premium-access email, support replies and operational alerts to the MicProbe owner, on MicProbe's behalf.
• Anthropic (United States) — AI-assisted report explanations for Premium accounts and the short reading on a result card, on MicProbe's behalf.
• Google LLC (United States) — Google sign-in, under Google's own terms and privacy policy.
• Freemius, Inc. (United States) — checkout, payment and license management as the reseller of MicProbe Premium, under Freemius's own terms and privacy policy. MicProbe sends Freemius your account email (to prefill checkout and to activate a license key for you) and receives the license and purchase details needed to link a purchase to your account.

If you are in the European Economic Area or the United Kingdom

When you use MicProbe from the European Economic Area (EEA) or the United Kingdom, the EU or UK General Data Protection Regulation (GDPR) also applies to the processing described in this policy. The data controller named at the top of this policy is based in Türkiye.

Account recognition, saved reports, purchase verification, support and the Premium features you use, such as report explanations, are processed to perform the service you asked for (GDPR Article 6(1)(b)). Security and fault diagnosis, enforcing the free daily test allowance and page and engagement statistics rely on legitimate interests (Article 6(1)(f)); you can object to that processing on grounds relating to your particular situation (Article 21). MicProbe does not use your information for advertising or profiling, and it makes no decision about you based solely on automated processing that has legal or similarly significant effects.

You can ask for access to your information, its correction or erasure, restriction of its processing or a portable copy by writing to support@micprobe.com, and you can complain to the data protection authority where you live, where you work or where you believe an infringement took place. Storage on your device is limited to the items listed under Cookies and browser storage. Some providers process information outside the EEA and the UK, including in the United States, as described under International data transfers; Cloudflare's data processing terms include the European Commission's standard contractual clauses.

Contact and account requests

For privacy questions, access or correction requests, or a request to delete account information, contact support@micprobe.com. Individual saved reports can be deleted directly from Saved reports.

Depending on the law that applies to you, your rights may include learning whether your information is processed, accessing it, knowing its purposes and recipients, correcting it, requesting deletion or restriction, receiving a portable copy, objecting to processing, and complaining to a data protection authority. Where processing relies on consent, you may withdraw it for future processing. We may need to verify that a request concerns your own account before acting on it.

Under KVKK Article 11, you may also ask whether information is used in accordance with its stated purpose, request that corrections or deletions be notified to recipients, object to a result against you based solely on automated analysis, and seek compensation for damage caused by unlawful processing. Requests are handled under the applicable legal conditions and response periods.