Privacy and Your Practice Data
This page explains how the site is designed to handle practice data. The site is a static website: its speaking tools operate in your browser. Hosting providers still receive ordinary website requests, which can include an IP address, requested path, browser information, and access logs. Their retention and processing depend on the hosting configuration chosen by the site operator.
Preferences and Saved Practice
The tools use localStorage for versioned preferences, recent topic IDs, and saved-topic IDs. These are stored under an impromptu:v1: prefix. If browser storage is unavailable, most features continue for the current page and explain when a preference cannot be saved. This is local browser storage, not an online account or a cross-device backup.
Reviews and recordings that you explicitly save use the impromptu-practice IndexedDB database, schema version 1. Reviews contain a date, topic ID, selected duration, and your three self-check answers. Saved recordings contain the audio blob and a date. The tools do not upload these records or audio files.
Use Clear Local Practice Data above to remove saved reviews, recordings, favorites, recent topics, and preferences for this site in this browser. The control also clears an unsaved recording in the current practice tab if that tab is open. Other open tabs can still hold their own in-memory state; close or reload them if necessary. Downloaded audio files and hosting logs are outside this control. Browser settings can also remove site data.
Microphone and Audio
The homepage and guided practice page offer optional microphone recording. The browser is asked for permission after you press Record. Stopping the recording releases its audio tracks and makes the clip available for local playback. The clip remains temporary until you separately save it on this device or download it. Closing or refreshing a tab can interrupt a recording and lose unsaved audio. You can revoke microphone permission in browser settings.
Audio is not sent to an AI service, transcribed, or included in analytics events by these tools. Device storage is not a guarantee against access by someone who uses the same browser profile. Choose whether a shared device is an appropriate place to save a recording.
Configurable Google Analytics and Microsoft Clarity
The deployment can be configured with GA4 and Microsoft Clarity measurement IDs. An empty or invalid ID prevents the corresponding script from loading. The configuration summary above reports this build’s settings. When enabled in regional mode, configured GA4 may send restricted measurement requests with all four Consent Mode v2 storage and advertising states denied before configuration or events. No visitor is silently treated as having granted consent.
Clarity is additionally blocked until the site operator marks its project-side consent setup as verified. When that requirement is met, its Consent V2 API is queued with both analytics and advertising storage denied before its script is added. In this mode Microsoft documents limited measurement without persistent consent cookies. The site masks its main content and private input areas for Clarity. Third-party requests can still expose connection information such as an IP address to their recipients.
The regional setting does not infer location from your language or time zone. This implementation uses conservative denied defaults worldwide and does not offer a consent-granting button. The stricter deployment mode blocks all measurement requests. Choosing between restricted measurement and blocking requires the operator to assess applicable rules and project settings; the software cannot determine a lawful basis for every visitor.
Your Analytics Choice
Disable Analytics on This Browser stores a rejection preference under impromptu:analytics-denied, sends denied updates to already initialized providers, and reloads the page to prevent their scripts loading again. This preference is kept when you clear practice data. If storage is blocked, it may only apply to the current page; use a browser blocker for a persistent independent control. Requests already sent cannot be recalled.
Permitted custom events describe actions such as starting a timer or generating topics. Their properties are limited to a fixed tool name, a count, and a duration. Topic text, search text, recordings, review answers, and user-written speech content are not included. Analytics page locations use clean paths without query parameters. The deployment operator must disable GA4 enhanced measurement for forms, site search, and other automatic content collection before enabling a measurement ID.
See Google’s consent documentation and Microsoft’s Consent V2 explanation for provider behavior. This page describes implementation behavior and needs operator review before launch, including hosting details, contact identity, provider settings, and applicable retention obligations. See contact and feedback for the available contact route.
Settings in This Build
Analytics switch: on. Privacy mode: regional. GA4 ID: configured. Clarity ID: configured. Clarity consent setup: marked verified by operator.