The core exercise needs no account. Microphone access is requested only after you choose to record. Local recording, playback, and downloads are free. Only the indicated segment is uploaded, after you sign in and choose Analyze. Ordinary practice stays available. You may sign in with Google to save Deep Research and Impromptu learning history across devices, plus ignored-topic preferences for Deep Research topics. Google sign-in provides your name, email, profile-image URL, and provider account identifiers. We store the Better Auth user, session, account, and verification records needed to keep you signed in, and we do not load Google profile photos on the page. If you submit feedback, we store its type, message, optional reply email, source page, and a broad device and browser label. We use the email only to reply to that feedback.
Privacy policy
Beta update: September 8, 2026. This policy explains how unprompted.top handles information when you use random topics, timers, optional Google sign-in, learning history, content pages, and the feedback form, and how advertising scripts and consent signals work on allowlisted pages.
Information we handle directly
Learning history and ignored topics
After you sign in, we store learning completion events in Neon: a completion ID, practice mode, stable topic identity, category or research field, product locale, topic-text snapshot, and completion time. Deep Research also stores its research completion time and an optional speaking completion time. An Impromptu event is stored only when the speaking timer ends or you explicitly choose “Finish speaking”; closing the timer does not create a completion record. Ignored-topic preferences apply only to built-in Deep Research topics and store the topic ID and the time you ignored it. We use this data to show your history, keep ignored topics out of random draws, and delete it when you remove a record or your account. History is kept until you delete that topic’s records or delete your account. Ignored-topic preferences are kept until you restore the topic or delete your account. Sign-out and account deletion are available from the account control next to the language switcher. Deleting a topic’s history and restoring ignored topics are done on that language’s learning history page. The session cookie uses Path /impromptu-speaking-practice to keep you signed in and is not sent with public feedback requests.
Signed-in users may save private libraries. Original TXT or CSV files are parsed only in the browser; the server stores the library name, practice mode, and cleaned topic text. Deleting a topic, a library, or the account permanently removes those topics and their learning records. Topic text is not sent to analytics or advertising services.
Local browser storage
We save timer settings, preparation choice, sound, language, and analytics settings in local storage. You can remove them by clearing this site’s browser data.
Website analytics
Localized production homepages and English guide pages load Google Analytics, Microsoft Clarity, and Plausible served from plausible.clapoint.com only after the session is confirmed anonymous, and only unless the browser has stored a decline. Signed-in users, and visits whose session is still unknown or whose session probe failed, do not load these scripts or display ads. We do not send user IDs, email addresses, topic IDs, topic text, history counts, field distributions, or ignored-topic preferences to analytics, session replay, or advertising. These services may process device, browser, page, interaction, approximate location, and IP data under their own policies. Plausible automatically records pageviews, page engagement, outbound-link clicks, file downloads, and form-submission events, but it does not read or send form-field contents. Anonymous visitors can turn analytics off or back on from Privacy settings in the footers. Turning analytics off does not affect the tool.
To improve this site, we count key interactions such as offer views, purchase clicks and report views. Requests omit cookies and referrers and contain no account, visitor, order, recording or report identifiers or text. Neon stores daily totals by event, entry point, language and offer for 90 days, plus random delivery receipts for up to 30 days to prevent duplicate counting. Receipts cannot identify a visitor. These are counts, not individual journeys or unique people, and delivery failures or rate limits can cause gaps. Choose Decline in the footer Privacy settings to stop these requests.
If you are signed in and explicitly allow first-party product analytics in Privacy settings, this site may also store account-linked funnel events (offer views and choices, analysis outcomes, checkout, payment, and refund facts). This permission is separate from anonymous third-party analytics; a previous Allow does not turn it on, and a previous Decline stays in this browser. You can withdraw it; queued events are dropped and are not replayed after you allow it again. Behavior events are kept for 30 days. Payment and account records follow existing billing retention. Withdrawing does not affect practice, analysis, or checkout.
Google AdSense and advertising data
Allowlisted public pages may load the official AdSense script so Google can verify the site. Advertising storage starts denied through Consent Mode. If ads are later shown, third-party vendors including Google may place or read cookies, use local storage, web beacons, IP addresses, or other identifiers to select and serve ads, limit repeated ads, measure performance, and prevent invalid traffic or fraud.
Google and its partners may use advertising cookies to serve ads based on visits to this site or other sites, including personalized ads where consent and account settings permit.
Ad partners and opting out
If third-party ad serving is enabled, other vendors and ad networks may also use cookies, web beacons, or IP addresses. The certified consent message identifies the selected partners and their purposes where required. You can review Google’s advertising technology partners.
You can opt out of Google personalized advertising in Google Ads Settings, manage some third-party choices through AboutAds, and restrict or delete cookies in your browser. Opting out of personalization does not necessarily remove all ads.
Regional consent and choices
Advertising and analytics storage start denied through Consent Mode. For visitors in the EEA, the United Kingdom, or Switzerland, a Google-certified consent message that uses the IAB Transparency and Consent Framework can appear. That message is published from AdSense Privacy & messaging and lets visitors accept, decline, or manage purposes and partners. Until a visitor chooses, those signals stay denied. Footer Privacy settings separately control Google Analytics, Microsoft Clarity, and Plausible, and an analytics decline remains stored in the current browser.
Where ads may appear
Monetization uses an explicit route allowlist and manual placements. Only supported-language homepages and English guide articles can qualify. The Nepali /ne/ route, About, Pricing, Privacy, Contact, 404 pages, research history pages, navigation, the interactive practice and timer controls, settings dialogs, timer dialogs, and privacy dialogs are excluded. Auto ads are disabled. The official loader script may appear on allowlisted pages for verification; we do not call adsbygoogle.push or insert ad units automatically. The AdSense account meta tag and ads.txt authorize the publisher relationship. Manual placements are not published yet.
Sharing, identifiers, and retention
The operator does not sell personal information. Anonymous third-party analytics and advertising data stay with those services and are not copied into the application database. When you allow first-party product analytics, Neon also stores account-linked funnel events in a dedicated analytics schema, without recordings, transcripts, emails, or payment secrets. Business facts such as account creation, analysis outcomes, checkout, payment, and refunds may be projected there for conversion reporting. Google provides sign-in. Neon stores accounts, sessions, research history, ignored-topic preferences, and feedback. Feedback is stored in Neon to resolve issues and improve the product, then removed when it is no longer needed or after a reasonable deletion request. Cloudflare temporarily processes IP addresses for abuse rate limiting, but the feedback record does not store them. The site does not intentionally pass names, email addresses, phone numbers, topic IDs, ignored-topic preferences, or similar personally identifiable information in page URLs, analytics events, or ad requests. Google, Microsoft, Plausible, and selected ad partners process data under their product or deployment settings, retention periods, consent state, and privacy policies.
Contact and requests
For privacy questions, access or deletion requests, or policy concerns, email support@unprompted.top. Include the page and request, and avoid sending sensitive information.
Recording feedback Beta and the waitlist
Unsubmitted audio stays in your browser. For an explicit analysis, Google receives the selected audio; OpenAI receives the transcript, timestamps, topic, and analysis range. Avoid sensitive content. Providers follow their own data policies; we do not promise provider zero retention. Trial audio in Cloudflare R2 becomes inaccessible 24 hours after upload and is removed by cleanup jobs. Written reports and usage seconds are stored in Neon until the record or account is deleted.
The paid-plan waitlist stores only the email you submit, language, consent version, and signup time. It is used only for the launch notice and deleted after notification or withdrawal. No paid subscription is created. Contact us to withdraw. IP addresses are used for temporary rate limiting and are not stored in the waitlist.
Paid analysis and Stripe
Payment disclosure updated September 14, 2026. Joining the waitlist does not charge you. See Pricing for plans and Terms for delivery, cancellation and refunds.
For paid services, Stripe processes payment and billing details. We do not store card numbers or security codes. We store account-linked Stripe customer and subscription identifiers, plan and billing-period information, allowance usage and payment-event identifiers to deliver services, update entitlements, prevent duplicate processing, support refunds and resolve billing issues. Account identifiers needed for payment are shared with Stripe. Stripe collects the billing details you enter at checkout, including email, and handles them under its Privacy policy.
Deleting an account or feedback record does not necessarily delete transaction information that payment providers must retain by law or to resolve disputes. Payment and cloud services may process data outside Hong Kong. Contact us to request access, correction or deletion, or ask about billing privacy. Do not send full card numbers.