Cookie Policy

Last updated: 2026-10-28

1. What Cookies Are

Cookies are small files or similar browser storage values placed on your device. They let a site keep you signed in, remember choices, protect forms, understand journeys, and measure performance. Some are first-party cookies set by Wisprs. Some are set by a provider when that provider is enabled.

2. Cookies and Storage We Use

Strictly necessary authentication and security cookies keep Clerk sessions, upload flows, support access, and abuse controls working. Preference storage remembers choices such as theme, dashboard mode, and your cookie choices (wisprs_consent, kept for up to 12 months, and wisprs_region, a 24-hour note of the country your request appeared to come from). First-party measurement values include wisprs_cid for a long-lived client identifier, wisprs_sid for a rolling 30-minute activity session, wisprs_attr for first-touch marketing attribution retained for up to 30 days, and wisprs_attr_paid for the most recent ad click that brought you to the site, also retained for up to 30 days. With your consent where it is required, the browser may also receive analytics cookies from Google Analytics, PostHog, or Mixpanel, and advertising measurement cookies from Google Ads (the Google tag and conversion linker) and Meta (the Meta Pixel, which sets _fbp and, after a click on a Meta ad, _fbc). Names and lifetimes can change when a provider or browser changes its implementation.

3. How We Use Them

We use necessary technologies for authentication, security, uploads, rate limits, and core product functions. We use preference storage to avoid resetting your choices. We use attribution, analytics, session replay, and performance technologies to understand navigation, feature use, errors, conversion paths, and product quality. We use advertising measurement technologies to tell Google and Meta when a visit that started from one of our ads led to a sign-up, a first transcription, or a purchase, so we can see which ads work and pay for fewer that do not. For that purpose we may also send Google and Meta the same events from our servers, with your email address and account identifier in hashed form only, matched against their own records of the ad click. We do not intentionally put transcript text, audio bytes, access tokens, or passwords in analytics or advertising event properties. Session replay is a separate recorder and may capture rendered UI state when enabled for a surface, so sensitive content must be masked or that surface excluded before replay is enabled there.

4. Legal Basis and Consent

Necessary technologies are used because they are required to provide a service you request. If you visit from the European Economic Area, the United Kingdom, or Switzerland, analytics and advertising technologies are off until you accept them in the cookie banner, and the choice you make is sent to Google as a consent signal and recorded by us as evidence of that choice. You can change it at any time from the Cookie settings link in the footer. Elsewhere, these technologies run by default and you can block them in your browser or ask us to stop by emailing tosh@getwisprs.com. Where a US state privacy law applies, we ask Meta to process events under its Limited Data Use option. We do not sell personal information. A tag enabled through Google Tag Manager may have its own data practices, so review that provider’s policy when a tag is enabled.

5. Managing Cookies

You can block, delete, or restrict cookies in your browser. You can also use provider controls or contact tosh@getwisprs.com for an applicable privacy request. Blocking necessary cookies can prevent sign-in, uploads, or dashboard features from working. Clearing storage may remove your theme, attribution, or session state.

6. More Information

For the data categories, providers, retention, international transfers, and rights connected to these technologies, read our Privacy Policy. For questions about cookies, email tosh@getwisprs.com.

Long Recordings to Clean Documents | Wisprs