Data Sources

Powered by YouTube API Services

CloutOrbit retrieves channel and video metadata from the YouTube Data API v3, which is part of YouTube API Services. We do not scrape YouTube, do not redistribute video files, and link back to the original YouTube page for every record we display.

Use of the Service is also governed by:

• YouTube Terms of Service
• Google Privacy Policy

What data we display

• Channel title, handle, country, category, language, avatar, banner
• Subscriber count, total views, video count, Shorts count, creation date
• Video title, thumbnail, view / like / comment count, publish date, duration, description
• Aggregated growth deltas (1d / 7d / 30d) computed on top of public data
• Derived ranking snapshots per country / continent / category

All values originate from publicly available YouTube data. No private user data, OAuth-protected data, or restricted content is collected.

Refresh cadence

• Channels and videos we actively track are refreshed regularly so the figures we display stay reasonably current.
• Historical daily snapshots are retained to power growth and trend analysis.
• If a channel is removed or set to private on YouTube, or its owner requests removal, we stop displaying it.

We handle stored data in line with applicable YouTube API Services policies.

Attribution & linking back

Every channel and video shown on this Service includes a "View on YouTube" link that opens the original page on YouTube. We do not embed downloadable YouTube content; thumbnails are displayed for identification purposes and remain the intellectual property of the original creator.

Independence

CloutOrbit is an independent analytics platform. We are not affiliated with, endorsed by, or sponsored by YouTube, Google LLC, or Alphabet Inc.

Removal & corrections

If you are the owner of a YouTube channel that appears on this Service and you want your channel removed, corrected, or your data deleted, submit a request via the Compliance Center, the DMCA page, or email [email protected]. We respond within 30 days.

For YouTube API Services reviewers

This section summarises the technical use of YouTube API Services and supports our quota extension request.

• API client: YouTube Data API v3, server-to-server via API Key. We do not request user OAuth scopes against YouTube.
• Endpoints used: channels.list, videos.list, search.list, videoCategories.list, i18nRegions.list, i18nLanguages.list.
• Call path: Client request → backend cache (Redis — 5 min for hot reads, up to 24 h for low-volatility lookups) → on cache miss, YouTube Data API. Identical requests within the cache TTL never hit YouTube.
• Default quota: 10,000 units per project per day.
• Why we need more: (a) Asia-first creator coverage requires periodic refresh of channel statistics across ~28 country markets; (b) end-user search and channel discovery generate cache misses for long-tail handles; (c) brand / agency decision panels compare 2–5 channels at once and require reasonably fresh stats. Without a higher daily cap we have to artificially throttle refresh frequency and degrade UX for paid users.
• Data retention & refresh: stored public metadata is refreshed on a regular cadence (top channels daily, the long tail at least every 30 days). On channel removal or privacy change we stop serving it. We do not store private user data.
• Compliance pages: Privacy Policy, Terms of Service, DMCA, Compliance Center.

Disclaimer

Statistics shown may be incomplete, delayed, or temporarily unavailable due to the inherent latency of the YouTube Data API. CloutOrbit provides analytics on a best-effort basis and makes no warranty regarding the accuracy of any derived metric.