IndiTubeDb Chrome Extension Privacy Policy

IndiTubeDb is a YouTube creator discovery platform. The IndiTubeDb – YouTube Creator Discovery Chrome extension helps you find creators by geography, language, category, niche and related topics, view public creator profiles and community ratings, compare creators, and save a video moment through the IndiTubeDb website.

This policy covers the extension and the website services supporting those features. Visiting or signing in to the website also involves the main website privacy policy. The extension handles information, including search text and channel identifiers; it is not a product that processes no user data.

On supported YouTube channel pages, the extension reads the public channel identifier, handle, channel-owner URLs and page navigation state to identify the current channel. A packaged script in YouTube’s page context reads public channel/player metadata; the extension is not authorized to access your YouTube account, subscriptions, private messages or cookies. The popup uses the active YouTube tab address locally to resolve the channel. It does not submit the full page URL as a channel-lookup field.

For a channel lookup, the identifier or exact handle is sent to IndiTubeDb. IndiTubeDb returns approved public creator information, such as name, image URL, category, niche, geography, languages, a short description when available, ratings, review counts and related creators.

In the popup’s Discover YouTubers search, typed search text and selected filters can be transmitted for previews and matching. More complex requests can be interpreted after submission. Do not enter private or sensitive information. This search is separate from the optional automatic YouTube-search feature.

Automatic matching on YouTube search-results pages is off by default and requires acceptance of the in-extension disclosure. When enabled, a local relevance check selects creator-related queries to send to IndiTubeDb. That check is not a guarantee of perfect classification. Unrelated browsing history is not intentionally collected by this feature. Turning it off removes inline results and cancels pending work, but cannot recall requests already transmitted.

Compare Creator stores your selected public creator’s ID and name locally. Capture Timestamp reads the current public video ID, channel ID and playback position only when you click Capture Timestamp in the player or popup. The website receives that capture after you choose the feature, associates a successful save with your signed-in account, and stores a private saved timestamp and video title.

IndiTubeDb and its infrastructure providers receive ordinary request information, including IP address, request time and browser/network metadata. Short-lived hashed IP buckets support rate limiting. Application, hosting and proxy logs may contain request or response details, including query text or identifiers; those logs are distinct from the extension’s local caches.

We use the information to match channels and creator-related searches to approved IndiTubeDb records, apply geography/language/category/niche filters, display profiles, ratings and related creators, open a comparison between selected creators, and save the video timestamp you request. We also use request metadata for availability, troubleshooting and abuse prevention.

The extension sends a small set of fixed event names for profile, related-creator and submission clicks; the extension information page records an aggregate visit event. These event payloads do not include query text, channel IDs or user identifiers. The API keeps aggregate counters in memory rather than a durable individual event history. Requests still expose ordinary network metadata to the server.

Links to IndiTubeDb include referral parameters. When you open the website, its website analytics practices apply; the extension does not embed Google Analytics in its content scripts or popup. Website analytics may process page addresses, titles, referrers, device and network information. The dedicated discovery and timestamp-capture flows sanitize their analytics context, but not every ordinary website search or navigation has that same protection.

The extension uses chrome.storage.local for your inline-search choice and disclosure version, one selected comparison creator, and a bounded cache of public channel-lookup results. It does not request the browser history or cookies permissions. Its production host access is limited to www.youtube.com and www.inditubedb.com; its storage permission supports these local preferences and results.

Lookup results can be reused for 15 minutes, and missing-creator results for two minutes. The cache holds at most 100 identifier-keyed entries. Entries older than 24 hours are discarded when the cache is next accessed; they are not guaranteed to disappear at an exact time while the extension is inactive. Cached entries are not a chronological browsing-history list, but their identifiers and cache times can reveal recent lookups to someone with access to your device.

Popup search results and automatic-search previews are held in bounded memory for up to 30 seconds, with at most 40 entries per cache. The automatic-search cache is cleared when its consent setting changes. Public taxonomy options refresh after 60 seconds. Worker/browser lifecycle can clear memory caches sooner.

Manual timestamp capture opens the website with video/channel identifiers and the playback time in a URL fragment, rather than the HTTP request URL. The site removes that fragment and uses per-tab session storage for a pending save and success receipt during sign-in, retries and reloads. This is website storage, separate from chrome.storage.local.

IndiTubeDb’s website/API and hosting infrastructure process the searches, identifiers and network metadata needed to operate the extension. The project uses Replit hosting and a PostgreSQL database through the Neon database driver. The deployed infrastructure and database operator determine their own operational log and backup retention.

Complex search interpretation and descriptive evidence checks can send your query, applicable taxonomy information and selected public creator text to OpenAI-model services through the existing Replit-managed OpenAI integration. Where the existing semantic search uses embeddings, the query can also be sent to the configured OpenAI embedding service. Structured filter searches do not require those AI calls. Provider processing and retention depend on the operator’s configured service and agreement; this policy does not promise zero provider retention or that every search remains on IndiTubeDb’s servers.

The website uses the YouTube Data API to verify a requested capture’s video/channel association and obtain public video metadata. Google/YouTube receives the video identifier and normal API request metadata from the website service. Visiting YouTube and using Google sign-in on the website, if you choose it, are also subject to Google’s policies.

Creator images may load from Google/YouTube image hosts or other HTTPS hosts recorded in the public directory. Those hosts receive normal image-request metadata, including your IP address. Extension images use a no-referrer policy. Website analytics, when configured, uses Google Analytics; its handling is separate from the extension’s fixed aggregate event payloads.

The audited extension does not sell user data or implement advertising-data transfers. We do not use or transfer extension-derived browsing data for personalized, retargeted or interest-based advertising. Information may need to be disclosed where required by law or necessary to protect users and the service.

The local and memory cache periods are described above. Selected comparison details remain until cleared or replaced; inline-search preferences remain until changed or the extension’s local data is removed. Removing the extension clears its local extension storage, but does not erase website account data, previously transmitted requests or server/provider logs.

Server-side derived search plans can be held in bounded memory for five minutes, descriptive evidence IDs for 60 seconds, and public taxonomy data for 60 seconds. Rate-limit buckets last approximately one minute; complex-interpretation rate-limit buckets last five minutes. Expired in-memory entries are pruned on subsequent activity, not by a promise of an exact background deletion schedule. Aggregate counters reset when their server process restarts.

Private saved timestamps are website account records, not temporary extension cache entries. They remain until you delete them through My Saved Timestamps or request applicable account-data deletion. The existing limit is three saved timestamps per channel. Closing the relevant tab normally ends its session storage, subject to browser session-restoration behavior.

Server, hosting, analytics, AI-provider and backup retention is governed by the operator’s deployed configuration and provider agreements, not the extension’s cache timers. A single verified retention period for all those systems is not established by this extension. Contact us for retention details or a deletion request, identifying the account or record involved without sending passwords. We may need to verify ownership and retain information where required for legal or security purposes.

Extension API transfers use HTTPS and omit website credentials and referrers on public lookup/search requests. Scripts are packaged with the extension, its content security policy restricts remote code, inputs and destination links are validated, and displayed directory text is rendered as text rather than executable HTML.

Saving a timestamp uses the website’s existing authenticated session and server-side video verification. The extension itself does not receive website passwords or session cookies. Local browser storage is not an encrypted vault supplied by IndiTubeDb: protect access to your device. No transmission or storage system can be guaranteed completely secure, and this policy does not assert independently verified encryption-at-rest or provider access controls.

IndiTubeDb’s handling of user data obtained through the extension is limited to providing or improving its disclosed creator-discovery, comparison and user-requested timestamp features, in accordance with the Chrome Web Store User Data Policy, including its Limited Use requirements. Transfers must be limited to service delivery or improvement, security, legal obligations, or other circumstances expressly permitted by that policy, not unrelated monetization.

Extension-derived user data is not to be sold or used for personalized advertising. Human access must be limited to the policy’s permitted exceptions, such as your explicit consent for specific support, necessary security investigation, legal requirements, or permitted aggregated and anonymized internal operations. These are operating commitments, not a statement that a privacy page by itself proves all deployed provider settings comply.

The Chrome Web Store listing and Data Usage declarations must remain consistent with this policy and the extension’s in-product disclosures. Store approval and independent certification are not guaranteed by publication of this page.

The extension is a general creator-research and discovery tool, not a service designed specifically for children. It does not provide a child-specific account system or verify the viewer’s age. Because search text may be transmitted, children should not enter personal information. If you believe a child has provided personal information through the extension or related website features, contact us so the matter can be reviewed and appropriate deletion steps considered.

We will publish changes at this URL and update the Last updated date. Where changed data handling requires a new disclosure, consent or extension permission, that must be presented through the appropriate in-product or browser mechanism before that handling is enabled. Merely revising this page does not grant consent for undisclosed collection.

Use IndiTubeDb’s existing Contact Us page for privacy questions, access/deletion requests, or concerns about extension data handling. No separate support email is specified in this policy. The main website privacy policy continues to apply to general website features and accounts.