Privacy policy

Earshot (earshotlabs.com) is a tool for researching what people search for around a topic, operated by Learnlab LLC (“we”, “us”). This page explains what we collect, why, who else handles it, and what you can ask us to do with it.

What we collect

Your account. When you create an account we store your name and email address. If you sign up with an email and password, we store your password only in scrambled (hashed) form; we can never read it. We record whether you have confirmed your email address.

Google sign-in. If you sign in with Google, Google shares your name, email address, profile picture address and Google account ID with us. Google also gives us sign-in tokens, which we store so the sign-in keeps working. We ask only for this basic profile information. We do not get access to your Gmail, Google Drive, contacts, calendar or any other Google data, and we do not post anything on your behalf.

Google Search Console (My sites). If you choose to connect Search Console, you grant Earshot read-only access to your Search Console data, separately from signing in. Earshot reads the list of sites you have in Search Console and, for the sites you add, the search queries, page addresses, clicks, impressions, click-through rates and average positions Google reports for each day, going back up to 16 months, plus each new day after that. It can't change anything in Search Console. We store an encrypted access token so the daily update can run, and the name of the Google account you connected. This data is private to you: no other Earshot user can see your sites or their numbers, and it is never added to the shared search results.

Your sign-in sessions. While you are signed in we keep a session record with your IP address and your browser's description (its “user agent”), to keep your account secure. Sessions end after 30 days or when you log out.

Your searches. When you search a topic, we store the topic and everything we collect about it: the related phrases, their search volumes, intent labels and clusters. These results are shared: anyone who searches the same topic sees the same results.

Your research. We save each account's research so you can come back to it: your idea checks, audiences, content plans and briefs, word lists, comparisons, the items you follow, your recently opened items, your projects and their “About this project” text. We also count how many new research runs each account starts each day, for the daily limits. This is linked to your account and only you can see it, unless you share a report with a link.

Payments. Payments are handled by Stripe. You enter your card details on Stripe's own pages, and Earshot never sees or stores your card number. Stripe tells us whether you are subscribed, which plan you are on, and when your trial or billing period ends, and we store that with your account.

What we don't do

• We don't sell your information or share it with advertisers.
• We don't use analytics or advertising trackers. The only cookie is the one that keeps you signed in.
• We don't send your name, email or account details to any of the research sources listed below.

Who else handles data

Earshot runs on, and sends requests to, these services:

• Vercel hosts the website, and Neon hosts the database, both in the United States. Your account and session records are stored there.
• Stripe handles payments and subscriptions. It receives your name, email address and card details, under Stripe's privacy policy.
• Resend sends our emails (confirming your address, resetting your password, the weekly email about what you follow, and the reminder before your free trial ends), so it receives your email address and what each email says.
• Google handles Google sign-in and, if you connect it, provides your Search Console data. To research a topic we also send the topic and related phrases to Google's search suggestions and to the Google Ads API (Keyword Planner) for search volumes.
• Wikipedia receives topics for article readership.
• Anthropic (Claude) does Earshot's analysis and writing. It receives: the phrases for a topic, to label their intent and group them into themes; the idea you describe in an idea check, with its search and YouTube figures, to choose the searches and write the verdict; the audience you describe, with its searches and the questions found for it, to find their searches, group them, sort the questions (who is asking, and whether each makes sense on its own) and write the summary; a topic's themes and searches to write content plans and briefs; searches and questions to find their words; and the “About this project” text of the project you are working in. For My sites, it receives a summary of your Search Console numbers (queries, pages and their figures) to write your site's summary. It never receives your name, email address or payment details. Anthropic doesn't use this data to train its models.

Only search topics and phrases go to the research services, never information about you. Your Search Console data goes only to Anthropic, for your own summary.

Google user data

Earshot's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use the Google profile information above only to create and sign in to your Earshot account, and your Search Console data only to show you your own My sites reports. We don't sell it, use it for advertising, or let anyone else see it. Our use of the Google Ads API is limited to looking up search volumes for keywords with our own Google Ads account; it never touches your Google Ads account or data.

YouTube

Earshot uses YouTube API Services. To research a topic or an audience, it sends search phrases to YouTube and reads public information about videos and channels (titles, view, like, comment and subscriber counts, publishing dates) and public comments on popular videos. It never connects to your YouTube account and collects nothing about you from YouTube. YouTube's data is used under the YouTube Terms of Service and the Google Privacy Policy. Earshot keeps YouTube's data for no more than 30 days, then deletes or refreshes it. Earshot sets no cookies of its own for YouTube and doesn't place YouTube content on your device.

How long we keep it

We keep your account until you ask us to delete it. Sign-in sessions expire after 30 days. Search Console data is kept while you stay connected; removing a site deletes its data, and disconnecting deletes all of it. Search results are kept and refreshed over time because they are shared research data, not personal data.

Your choices

You can ask us to see, correct or delete your account information at any time by emailing hello@earshotlabs.com. Deleting your account removes your name, email, password, Google sign-in link, sessions and your saved research. If you signed in with Google, you can also remove Earshot's access from your Google account settings.

Disconnecting Search Console

Go to My sites and click Disconnect. Earshot then revokes its access at Google and deletes your sites and every Search Console figure it stored. You can also remove Earshot's access from your Google account settings; the daily update then stops, and you can delete the stored data with Disconnect.

Children

Earshot is not meant for children under 13, and we don't knowingly collect information from them.

Changes

If we change what we collect or who handles it, we will update this page and the date at the top. If a change is significant, we will tell account holders by email.

Contact

Questions about privacy: Learnlab LLC, hello@earshotlabs.com.