Privacy Policy

Effective date: October 31, 2026

Who we are and whom this covers

Live Earnings is operated by Sierra Kaze LLC, 5683 Snowdon Place, San Jose, CA 95138, United States. We decide how the personal information described here is used, and where EU or UK law applies, we are its controller.

This policy covers:

• visitors to live-earnings.com;
• account holders;
• API, SDK and MCP users, and the AI apps they connect;
• people who contact us;
• people identified in earnings calls (company executives and financial analysts), most of whom are not our users.

1. Information about users

Account and sign-in.

• You can create an account with an email address and password, or sign in with Google.
• Supabase, our authentication provider, stores your email and, if you create a password, a hash of that password. Google sign-in does not give us your Google password.
• For Google sign-in, Google gives Supabase your account identity and basic profile.
• We use your account ID, name and email to recognize you, and we keep account-creation records.

Access keys.

• When you are signed in and open a call, we find your existing key for that call, or create one if access is available.
• We keep the key, which account and call it belongs to, your access role, and when it was created or revoked.
• Keys are stored in a form we can show back to you on the call page.

Your account choices. On your account page, and once after you first sign in, you can tell us:

• which emails you want (the week's calls, reminders before calls, recaps after calls you watched, product news). All are on when you sign up; you can turn any of them off;
• your time zone (suggested from your browser), what best describes you, and how you heard about us.
• We record your email settings when your account's choices are first saved, and each time you turn an email on or off: which email, on or off, how (the default at sign-up, your account page, or a reply to one of our emails), which version of our wording applied, when, and your browser details.
• If you arrived through a link tagged with a source (such as ?src=), we save that tag with your account.
• We also record which calls you opened, and when you first opened each.

Stream tokens. These are short-lived (2 hours). We store only a one-way hash of each.

AI app connections (MCP). When you connect an AI app such as Claude or ChatGPT, we keep:

• the app's registration: its name, identifier and return address;
• the resource it requested, and your authorization for the app to read the calls available to your account;
• pending and completed authorization requests, including ones you did not finish;
• security-check values;
• when authorization requests and credentials were created, used up and expire, and when a connection was revoked.

The authorization codes, access tokens and refresh tokens themselves are stored only as one-way hashes.

Requests and diagnostics.

• When you use our website, API, SDKs or MCP server, we process each request and its parameters, such as the call, section or page you asked for.
• We receive only the requests an AI app sends us. Connecting an app does not give us its conversation history.
• We and our hosting providers keep request and error logs to run, secure and troubleshoot the service. These logs can include your IP address, browser details, the requested address and error messages.
• When transcription diagnostics are switched on, they can also contain speaker names and transcript excerpts.

Terms acceptance. We do not currently collect a separate confirmation of acceptance of our Terms of Service or keep a dedicated terms-acceptance record.

Abuse protection. For our AI-app connection endpoints (registration, authorization, token and revocation), we store request counters keyed by endpoint and the requesting client's IPv4 address or IPv6 /64 network prefix. These are not hashed and may belong to a connected app's servers. Counter records become eligible for cleanup 1 day after their counting window starts. Account sign-in is protected separately by Supabase.

Browser storage.

• Supabase sign-in cookies (names beginning sb-) keep you signed in.
• If you arrive through a link tagged with a source, a cookie named le_src keeps the first tag for 90 days, so we can save it with your account if you sign up.
• Your browser's local storage keeps a few display preferences: your theme, and whether the API and insight panels are expanded and where. These preferences stay until you change or clear them. When you submit a sign-up or password-reset request from a sign-in link with a return destination, we also save that page's address on this site and the time it was saved, so you can return after following the emailed link in the same browser. We do not add your email or account ID to this entry. We read and remove it after a successful password sign-in or password reset, or when you start Google sign-in. Entries older than 30 minutes are ignored when read; they are not automatically deleted when that time passes.
• Apart from the le_src source cookie above, we use no analytics cookies, no advertising cookies and no third-party analytics. We do not track you across other websites, and we do not respond to browser Do Not Track signals, because we do no such tracking to switch off. The image hosts described in section 4 receive your request details and handle them under their own privacy practices.

2. People identified in earnings calls

We collect, use and disclose the following about the executives and analysts who take part in, or cover, the calls we transcribe:

• call audio and transcripts of what they said;
• names, professional titles, roles and firms;
• speaker-roster records. Some also contain image links and internal identifiers. We do not keep email addresses for the people on calls.

Profiles and predictions. We may build professional profiles of analysts from their past questions: recurring topics, question patterns and tone. We use them to identify speakers, for historical analysis and, where the feature is on, to predict likely questions. These profiles and predictions can be incomplete or wrong. They are our analysis, not statements made or approved by the person.

Where it comes from. Public earnings calls, published transcripts and other public professional materials, plus the profiles and inferences we derive from them. On request, we will tell you the source of a particular record.

Who sees it. Account holders see call transcripts, speaker names, titles, roles and firms through our website, API, SDKs and MCP tools. Our MCP tools do not return roster email fields or image links.

Speaker names are assigned automatically and can be wrong.

If our records identify you.

• Email legal@live-earnings.com; you do not need an account. Tell us the call, profile or statement concerned, and what you want corrected or why you object.
• Where we rely on legitimate interests and the law gives you a right to object, we will stop the processing unless we have compelling legitimate grounds that override your interests, or need it for legal claims.
• We will explain our decision and how you can challenge it.

Audio.

• We process and briefly buffer call audio to transcribe it and to play it live to subscribers.
• Some capture methods write temporary audio chunks before sending them to us.
• The live transcription pipeline does not archive incoming audio in its database. Separate recordings of public earnings calls may be kept and used for testing, replay and transcription-quality evaluation.

3. How we use information, and our legal bases

We do not sell personal information, share it for cross-context behavioral advertising, or use it for advertising.

4. Who receives it

We use the providers below to run the service. Providers acting on our instructions process information for us. Providers acting for their own purposes do so under their own privacy notices.

Images.

• Some pages load firm logos directly from Logo.dev. Logo.dev receives your IP address, the image address and standard browser request details, which can include the referring page.
• Executive photos are copies of headshots that companies publish on their own investor-relations pages, and company logos are copies of logos companies publish themselves. We store them and serve them from live-earnings.com, so no third party receives your request. We keep each image's source page. To have a photo or logo removed, email legal@live-earnings.com.

AI apps you connect.

• An AI app you authorize can keep reading the calls available to your account until you revoke it or its authorization expires.
• Its responses can include information about executives, analysts and others mentioned on calls.
• The app uses, stores and discloses those copies under its own privacy practices.
• Our MCP tools never return your email, password or credentials.

Legal disclosure. We may disclose information when the law requires it, or to protect the rights and safety of users or others.

Where information is processed.

• We operate in the United States. Our database is hosted in the United States (Ohio), our website in the United States (Virginia), and our transcription pipeline in the United States (Iowa). Our speech and AI providers process information in the United States or in other locations their own terms allow.
• If you are in the EU or UK, your information is transferred to and processed in the United States. To ask which transfer mechanism applies to a particular transfer, email legal@live-earnings.com.

5. How long we keep it

Expiry stops a credential working; it does not delete it at that moment. Cleanup runs from time to time, so expired records can remain for a while after the periods below.

6. Your choices and rights

Disconnect an AI app.

• Removing the connector in the app stops that app using it.
• Whether removal also revokes its credentials with us depends on the app. To make sure one or all connections are revoked, email support@live-earnings.com.
• Revoking stops future access. It does not delete what the app already received.

Emails. Change which emails you receive at any time on your account page, or reply "stop" to any of our emails.

Delete your account.

• Use "Delete my account" on your account page, or email support@live-earnings.com. A request from your account page turns off all emails at once, and we complete the deletion within 30 days.
• After verifying the request, we delete your sign-in account and application account, and revoke or delete your credentials. We keep information only where the law requires it, and will tell you about any such exception.
• Deleting your account does not remove earnings-call records. If a transcript, roster or profile contains information about you, you can make a separate request under section 2.

EU and UK rights.

• Where they apply, you can ask for access to, a copy of, correction or deletion of your data, restriction of processing, and portability.
• You can object to processing based on legitimate interests, and withdraw consent where we rely on it.
• Email legal@live-earnings.com; no account is needed.
• We may ask for information to verify your identity or an agent's authority.
• We reply without undue delay, and generally within one month.
• You can complain to your data-protection authority or the UK Information Commissioner.

California. We are not currently subject to the California Consumer Privacy Act. We do not sell personal information or share it for cross-context behavioral advertising; we disclose it only as described in section 4. California residents can still ask us for access to, correction of or deletion of their information at legal@live-earnings.com. We will handle these requests subject to identity verification, applicable law and legitimate retention needs, and will not discriminate against anyone for asking.

7. Security, children, and changes

Security.

• Our public endpoints use HTTPS.
• We store hashes, not the values, of stream tokens and of MCP authorization codes, access tokens and refresh tokens.
• Per-call access keys are stored so we can show them to their owner. Supabase manages browser sign-in sessions.
• No measure removes all risk.

Children.

• The Service is intended for people aged 16 and over. We do not verify ages at sign-up, and we do not knowingly collect personal information from children under 16.
• If you believe someone under 16 has given us personal information, email legal@live-earnings.com. If we learn that this has happened, we will stop collecting from that person and delete the information, except where the law requires us to keep it.

Changes.

• We will post updates here with a new effective date, and give notice of material changes before they take effect.
• If a new use needs your consent, we will ask first.

8. Contact

• Account, access, deletion: support@live-earnings.com
• Privacy rights, people named on calls, legal: legal@live-earnings.com
• Post: Sierra Kaze LLC, 5683 Snowdon Place, San Jose, CA 95138, United States