EIRS Privacy Policy

Crickit, LLC
Effective date:
September 24, 2026


This Privacy Policy explains how Crickit, LLC ("Crickit," "we," or "us") handles information in EIRS, our multi-source analytics platform for financial research. EIRS researches online video, social media, and podcasts, including material associated with YouTube, TikTok, Facebook, and Instagram. Crickit also produces its own analytics. We identify information by source and distinguish Crickit analytics from source-provided data.

1. Scope and your agreement

This policy applies only to EIRS and its related accounts, research workspaces, private demonstrations, and support. It does not govern the crickit.ai marketing website or the Crickit consumer browser extension, which have separate policies. Before accessing EIRS features, each user must affirmatively agree to this Privacy Policy. It remains available from within EIRS. If our use of YouTube API Data materially changes beyond what a user previously accepted, we will obtain renewed acceptance before that new use.

2. Information EIRS handles

Account and workspace information

For authorized users, we may process name, business email address, organization, role, account credentials or authentication identifiers, support correspondence, and workspace content such as topics, searches, notes, saved views, and export requests. We receive this information from users, their organizations, and the systems used to administer EIRS.

Public and licensed research information

EIRS processes information about companies, products, events, and public statements from multiple sources. Current coverage includes material associated with YouTube, TikTok, Facebook, Instagram, and podcasts. Depending on the source and our permissions, this may include video, post, channel, show, or episode identifiers; titles, descriptions, links, and dates; available engagement figures; and podcast metadata, transcript excerpts, or mentions. Creator and speaker names and public statements may identify people. The fields available to EIRS vary by source.

YouTube API information

Within that broader research coverage, EIRS uses the YouTube Data API to search for public videos and obtain public video and channel metadata and available statistics, such as identifiers, titles, descriptions, dates, channel names, links, and view or like counts. EIRS currently does not ask users to connect a Google or YouTube account and does not access private account data through Google authorization. We do not request or store users' YouTube passwords.

Crickit research analytics

Crickit may generate classifications, topic groupings, trend indicators, and other analytical outputs from permitted inputs across sources. We label source-provided information and Crickit-generated outputs separately. A Crickit assessment is not presented as a metric supplied or endorsed by a source platform.

Technical and device information

When a user accesses EIRS, we may collect IP address, browser and device type, access times, pages or features used, diagnostic events, and security logs. EIRS may use session and security cookies or similar browser storage to authenticate users, maintain sessions, and protect the service. If optional analytics technologies are introduced, we will describe them and obtain any consent required by law before use.

3. YouTube and Google

EIRS uses YouTube API Services. Google's practices are described in the Google Privacy Policy. When EIRS displays an embedded YouTube player, a user's browser connects to YouTube. YouTube may receive device and browser information, the page or video requested, and playback interactions, and may use cookies or similar technologies under its own policies. This transfer occurs when the player loads and may increase when a user plays a video. EIRS identifies YouTube as the source of YouTube videos and metadata and does not present Crickit analytics as YouTube data.

Because EIRS does not currently request Google or YouTube account authorization, there is no EIRS Google authorization to revoke. If we add an authorized connection later, we will update this policy and provide an in-product way to disconnect it. Users may also review and revoke connected app access through Google Account security settings. We will then delete data obtained under that authorization within the time required by YouTube policy.

 

linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram