PRIVACY POLICY

1. Zero-Disk Ingestion & No Media Storage

TubeFetch provides on-the-fly streaming resolution. When you request a stream preview or download:

• No video or audio binaries are saved permanently or temporarily written to persistent server storage.
• All data packets are transferred directly in memory via streaming proxy pipes between origin content delivery networks and your client browser.
• Once your download completes or your preview finishes, all memory buffers are instantly released.

2. Telemetry, IP Logging & Abuse Prevention

To ensure uptime, prevent distributed denial-of-service (DDoS) attacks, and enforce fair rate-limiting across our serverless backend, we maintain minimal audit logs in our database:

• Logged Fields: Client IP address (resolved via standard proxy headers `CF-Connecting-IP` / `X-Forwarded-For`), timestamp (UTC), media ID, and requested format quality badge.
• Purpose: Strictly utilized for automated rate-limiting algorithms, bot prevention, and aggregated server performance telemetry.
• Retention: Logged IP entries are automatically pruned and are never correlated with personal identifiers, email addresses, or physical identities.

3. Cookies & Tracking Technologies

TubeFetch takes a zero-clutter approach to privacy:

• We do not set cross-site tracking cookies, behavioral tracking pixels, or third-party fingerprinting scripts.
• No user accounts, registrations, or login sessions are required to use any feature on this platform.
• Upstream authentication tokens used by our backend to bypass rate limits are isolated to server memory and are never exposed to clients.

4. Third-Party Service Providers

Our infrastructure leverages enterprise cloud providers committed to strict security and privacy standards:

• Vercel: Global edge delivery of our static Next.js frontend application.
• Railway: Containerized FastAPI proxy application hosting.
• Neon.tech: Serverless PostgreSQL database for caching video metadata and telemetry logs.

5. Inquiries & Data Requests

If you have questions about our privacy practices, technical data handling, or wish to submit an inquiry regarding telemetry records, please contact our engineering team via our public repository issue tracker or review our Terms of Service.