API Compliance & Quota

This page outlines our access model, use of the YouTube Data API v3, data handling, and the quota rationale supporting our expected capacity. We do not scrape, bypass protections, or resell YouTube data.

Requested quota: 1,000,000 quota units/day (read-only).

Fallback we can accept: 550,000 quota units/day for a phased approval if preferred.

Contact: info@andinesutubeintelligence.com

Access Model (Owner-Operated)

Single operator: Only the owner (Andre Haynes) uses the API client and internal tooling.
No end-user API access: Clients never receive keys or direct access.
Deliverables: Clients receive finished PDF/XLSX reports derived from public metadata.
Server-side credentials: All API keys stored securely server-side; never exposed client-side.

Intended Use

We analyze public channel/video metadata to produce actionable insights for creators: content gaps, trending topics, and suggested 30/60/90-day calendars. Official API endpoints only; respectful rate limiting.

Technical Safeguards

QPS Control: Strictly enforced <5 requests/second
Batching: videos.list & channels.list with 50 IDs/call
Caching: 7-day temporary cache to avoid duplicates
Exponential Backoff: Implemented for 429/5xx errors
Circuit Breakers: Automatic shutdown on repeated API failures

Prohibited Behaviors

No scraping or circumvention of access controls
No mass downloading or automated account creation
No selling or transferring YouTube data to third parties
No unauthorized access to private user data

OAuth & Scopes

End-user OAuth: Not required; owner-only execution.
Scopes: Read-only; no uploads/edits.
Authentication: Server-side API keys only

Terms of Service & Privacy Policy Compliance

This API Client strictly adheres to YouTube API Services Terms of Service and Developer Policies:

Provides users with a link to the YouTube Terms of Service
Notifies users that it uses YouTube API Services and provides a link to the Google Privacy Policy
Explicit Compliance: This implementation fully complies with the YouTube API Services Terms of Service, including all usage limitations and data protection requirements
Implements strict data handling in accordance with YouTube's data protection standards

Our full Terms of Service and Privacy Policy are linked in the page footer.

User Data Revocation & Deletion

In compliance with YouTube API Services requirements, users can manage and revoke this application's access to their data:

Revoke Access via Google Security Settings

All data deletion requests are processed within 7 business days. We maintain clear audit trails for all data access and deletion activities.

System Architecture & Data Flow

Our architecture implements a secure, quota-efficient API integration model designed for full compliance with YouTube API Services Terms.

flowchart TD
    subgraph External[External Systems]
        A[Client Google Form]
        B[YouTube Data API v3]
        C[Client Email]
    end

    subgraph SecureZone[Secure Processing Environment]
        D[Google Sheet Intake]
        E[Owner-Triggered Job]
        F[Private Backend Service]
        G[Temp Cache 7-30 days]
        H[Analysis Engine]
        
        E --> F
        F --> G
        F --> H
    end

    subgraph Delivery[Delivery System]
        I[Report Generation
PDF/XLSX]
        J[Email Delivery]
    end

    A --> D
    D --> E
    F --> B
    B --> F
    H --> I
    I --> J
    J --> C

    style SecureZone fill:#e1f5fe
    style External  fill:#f3e5f5
    style Delivery  fill:#e8f5e8

Figure 1: Secure API integration architecture for YouTube Intelligence service

Data Handling & Privacy

Only public metadata accessed via official API
Raw API data stored temporarily (7-30 days)
Only aggregated insights persist in final reports
No redistribution of raw YouTube data
Comprehensive data deletion process available

Processing Controls & Optimization

Single operator with audit logs
QPS limited to <5 requests/second
Exponential backoff for errors
Batching to minimize API calls
Smart caching to reduce duplicate requests

Daily Capacity & Quota Rationale

Requested: 1,000,000 quota units/day (YouTube Data API v3, read-only).
Fallback we can accept: 550,000 units/day for a phased approval if preferred.

Key Technical Assumptions & Growth Timeline

Calculations based on conservative technical implementation and YouTube API quota costs:

Rate Limiting: QPS strictly limited to <5 requests/second with exponential backoff
Optimization: Efficient ID batching (50 IDs/call for videos.list and channels.list)
Caching: 7-day cache to avoid duplicate API calls and reduce quota consumption
Business Scale: This quota supports our 6-month goal to onboard 500+ creators
Growth Projection: Expected growth: 20-30 clients daily within first 3 months
Quota Efficiency: Conservative estimates with 15-20% buffer for unexpected usage

Granular Quota Calculations & Arithmetic Breakdown

Detailed arithmetic showing exact quota consumption per report tier:

Tier 1 — Content Gap Snapshot

Total: 4,000 units

• 25 search.list @ 100 units = 2,500
• 20 videos.list (batched) @ 1 unit = 20
• 10 channels.list (batched) @ 1 unit = 10
• 15 playlistItems.list @ 1 unit = 15
• 5 commentThreads.list @ 1 unit = 5
• Buffer & processing = 450

Tier 2 — Intelligence Suite

Total: 6,500 units

• 50 search.list @ 100 units = 5,000
• 30 videos.list (batched) @ 1 unit = 30
• 15 channels.list (batched) @ 1 unit = 15
• 20 playlistItems.list @ 1 unit = 20
• 10 commentThreads.list @ 1 unit = 10
• Buffer & processing = 425

Tier 3 — Channel Accelerator

Total: 10,000 units

• 80 search.list @ 100 units = 8,000
• 50 videos.list (batched) @ 1 unit = 50
• 20 channels.list (batched) @ 1 unit = 20
• 30 playlistItems.list @ 1 unit = 30
• 15 commentThreads.list @ 1 unit = 15
• Buffer & processing = 1,885

Arithmetic Validation: Calculations verified against official YouTube Data API v3 quota costs. All estimates include 10-15% buffer for pagination and error retries.

Service Tier	Units / Report	Reports/Day @ 1M Quota	Reports/Day @ 550K Quota
Tier 1 (Snapshot)	4,000	≈250	≈137
Tier 2 (Suite)	6,500	≈153	≈85
Tier 3 (Accelerator)	10,000	≈100	≈55

Quota Utilization & Growth Plan

Typical blended day (60% / 30% / 10% across T1/T2/T3): weighted ≈ 5,350 units/report → ≈ 187 reports/day @ 1,000,000 and ≈ 103 reports/day @ 550,000.

This capacity supports sustainable business growth while maintaining optimal API performance and compliance with YouTube's rate limiting policies.

Technical Notes: Owner-initiated batch runs; peak QPS < 5 with exponential backoff; read-only public data access; no scraping; clients receive PDF/XLSX deliverables only.
Fallback Acceptance: If 1M units/day requires phased approval, we can operate effectively at 550,000 units/day and will re-apply after demonstrating sustained utilization (>85% daily) and >95% success rate for 2–3 weeks.

Sample Report & Short Demo

Representative PDF demonstrating structure and sections (placeholder data; no client data).

Download Sample Report (PDF)

Shows form → admin run → API calls → export → email. Keys redacted.

Technical Implementation Details

API Endpoints Used

search.list - Discovery across targeted keywords/topics
playlistItems.list - Recent uploads per channel
videos.list - Stats for candidate videos (batched IDs)
channels.list - Channel-level metrics (batched IDs)
commentThreads.list - Qualitative cues only (optional sampling)

Compliance Guardrails

Server-side credentials only; restricted by project
Least privilege & read-only scopes
No scraping, no circumvention of access controls
Clear deletion channel for client information
Regular compliance audits and monitoring

Contact & Helpful Links

For audit questions or clarifications: info@andinesutubeintelligence.com

Google Cloud Project Information

This service operates under Google Cloud Project: 757868948237

Please reference this project number in all quota and compliance communications.

Where we request quota: YouTube API Services – Audit & Quota Extension Form · Reference guide: Quota & Compliance Audits

Location: Phoenix, Arizona, USA