Privacy

We may modify this Privacy Policy from time to time, in which case we will update the “Last revised” date at the top of this page and post the updated version on the Services. If you do not agree to an update, please stop using the Services.

Information you provide to us

• Account information. We use a third-party authentication provider to register and sign you in. Depending on how you sign up this includes your email address, your name, and basic profile information from a social login if you use one. That provider holds your credentials; the only account detail our own systems store is an account identifier.
• Billing information. If you add credits, payment is handled by Stripe on a page hosted by Stripe. Card details are entered there and never reach our servers. We receive and store your billing email address, the amount, a transaction reference, and opaque Stripe identifiers that let you top up again without re-entering a card.
• Your content. Text prompts, audio you speak or upload, transcripts, and text you submit for speech synthesis. Section 4 explains exactly what happens to each.
• Messages you send us. If you contact us or complete a form on our website, we receive what you send, which typically includes your name, email address and anything else you write.

Information collected automatically

• Technical and log data. As with any website, our hosting and infrastructure providers process the IP address, browser details and request information needed to serve a request and keep it secure.
• Usage records. For each API request we record metering data: the model used, token, character or audio-second counts, latency, status, cost, timestamp and which API key was used. We do not record the content of the request or the response.
• Abuse-prevention identifiers. We use your IP address and a randomly generated identifier stored in a cookie to rate-limit our free demos. See Section 5.

• First-party analytics. We run our own first-party analytics to understand how the Services are used. We record pageviews, clicks, visible time on the site, and whether a homepage demo was attempted, connected, completed or ended. For completed demo turns we record pipeline latency timings, but not what you said or the generated response. Events include the page path, the referring page, a timestamp, an approximate location (country, region and city) derived from your IP address by our hosting provider, and your browser’s user-agent string. If you are signed in, events are associated with your account.
• Vercel Web Analytics. We also use Vercel to understand visits to our public website and Sandbox. It provides anonymous, aggregated reports on pageviews, referrers, campaign sources, approximate location, devices and browsers. We record selected link clicks, scroll depth, viewed homepage sections and whether an embedded booking was created. We limit the page URLs and campaign parameters sent to Vercel and exclude account, internal, authentication and private evaluation pages. We do not send account identifiers, prompts, audio, form contents or booking attendee details to Vercel Web Analytics. See Vercel’s analytics privacy documentation.

We do not share analytics with advertising networks or use advertising pixels or session recording on the Services.

Information from other sources

We receive account information from our authentication provider and from the login provider you choose to sign in with, and payment status and billing contact details from our payment processor. Information received from these sources is handled in accordance with this Privacy Policy. We are not responsible for the accuracy of information provided to us by third parties.

• Provide and operate the Services, including routing your requests to models and returning the output.
• Meter usage, calculate cost, maintain your credit balance, and issue receipts and invoices.
• Authenticate you and keep your account secure.
• Prevent abuse, fraud and misuse, and enforce rate limits and our terms.
• Respond to you, provide support and send service notices.
• Understand how the Services are used, so we can fix problems and decide what to build next.
• Send transactional email such as payment receipts and low-balance notifications.
• Comply with legal obligations and protect the rights, property and safety of Hopper, our users and others.

Hopper is infrastructure, so what happens to the content you send us is the part that matters most. Stated plainly:

• Prompts and completions are not stored. Requests to our language model API are proxied to the inference server and streamed back to you. We record metering data only. The content is not written to our database and does not appear in our logs.
• Speech-to-text audio is not stored by us. Audio is passed through to the model and discarded. We record its duration for billing.
• Text-to-speech input is not stored by us. We record the character count and which voice was used, not the text.
• Console history stays on your device. The console keeps your recent transcriptions and generated audio in your own browser storage so you can review them. That history is not sent to us; clearing your browser storage removes it.
• Website demos. The voice demo on our homepage streams your microphone through our real-time audio provider and our pipeline. It is not recorded, and sessions are capped in length. The speech-to-text comparison demo streams audio from your browser directly to the speech providers being compared, and keeps the results in your browser. To score their accuracy, a copy of that audio is also sent through our server to a speech provider’s batch API to produce a reference transcript. We do not retain it.

To deliver a request, content necessarily passes through the infrastructure and model providers listed in Section 6, including rented GPU capacity used to serve open-source models. Their handling of data in transit is governed by our agreements with them.

We use cookies to operate the Services. We do not use analytics or advertising cookies.

• Session cookies set by our authentication provider, which keep you signed in to your account.
• A demo rate-limit cookie, set when you start the voice demo on our homepage. It holds a random identifier with no connection to your identity, is used solely to stop the free demo being abused, and expires after 30 days.

Our first-party analytics use a random identifier in your browser’s local storage and a session identifier in session storage. Clearing your browser storage for this site removes both. Signed-in events may also be associated with your account, as described in Section 2. Vercel Web Analytics uses a short-lived hash derived from requests instead of cookies and does not track visitors across websites.

Blocking or deleting cookies may prevent sign-in and the demos from working. Like most websites, ours is not designed to respond to “Do Not Track” signals.

We are a small company and rely on third-party providers to run the Services. Your Personal Data may be shared with:

• Vendors and service providers. We share information with providers who help us run the Services, and only what each needs to do its job. These cover authentication and account management, payment processing, email delivery, cloud hosting and infrastructure — including rented GPU capacity used to serve open-source models — real-time audio transport and turn detection for our voice demo, speech-to-text and text-to-speech model providers, rate limiting and abuse prevention, documentation hosting, website analytics, and the delivery of fonts and site icons. Vercel provides our website hosting and public Web Analytics.
• Payment processor. Our payment processor, Stripe, collects and processes your card details and billing address directly. We do not see or store your card number. You can read Stripe’s privacy policy on their website.
• Professional advisers such as our lawyers, accountants, auditors and insurers.
• Corporate transactions. In connection with the consideration, negotiation or completion of a financing, merger, acquisition, bankruptcy or sale of all or part of our assets.
• Legal and safety. With law enforcement agencies, regulatory bodies and public authorities where we believe disclosure is required or appropriate to comply with applicable law or legal process, or to protect the rights, property and safety of Hopper, our users and others.

We will name the specific providers in each category on request. If you need a current list of our subprocessors, email us using the details in Section 12.

• Content we do not store — prompts, completions, streamed audio and synthesis input — is not retained at all.
• Account records, usage and metering records, and billing records are kept for as long as your account is open, and afterwards for as long as we need them for accounting, tax, dispute-resolution and other legal purposes. Our billing ledger is append-only by design, because it is the record of money owed and paid.
• Copies of data may persist in routine backups for a limited period after deletion from our live systems.

• Access, correction and deletion. Email us and we will action reasonable requests to access, correct or delete your information, subject to records we are required to keep for billing and legal reasons.
• Marketing email. Use the unsubscribe link in any marketing message. You will still receive transactional email about your account, such as receipts.
• API keys. You can create and revoke API keys at any time in the console. We store only a hash of each key plus a short display prefix, so a key is shown to you once and cannot be recovered afterwards.

We limit access to your information to those who need it to operate the Services, and we hold only a hashed form of your API keys. That said, information you send electronically may not be secure in transit, no security measures are impenetrable, and we cannot guarantee perfect security. Please do not send us sensitive or confidential information over unsecured channels.

The Services are intended for developers and are not directed to children. You must be at least 18 to use them, and we do not knowingly collect personal information from anyone under 18. If we learn that we have, we will make commercially reasonable efforts to delete it. If you are a parent or guardian and believe your child has provided us with information, please contact us using the details below.

The Services may link to websites and platforms we do not control. If you follow those links, you should review the privacy notices and terms that apply there. We are not responsible for the privacy or security practices of, or the content found on, those sites, and linking to them does not imply endorsement.

Hopper Inference, Inc. is a Delaware corporation based in San Francisco, California. If you have questions about our privacy practices or this Privacy Policy, or if you want to make a request about your information, email us at founders@withhopper.com.