What this policy covers
This page explains the privacy baseline for Hackemist YouTube Intelligence public tools, including URL checks, YouTube API-backed lookups, AI creator workflows, exports, and future account features.
Trust and launch policy
Privacy Policy
Read how Hackemist handles privacy for public YouTube intelligence tools, account-ready workflows, cache-aware checks, exports, AI requests, and future saved reports.
Launch policy baselineVisitors, creators, registered users, and future workspace users.
Information users provide
Users may submit YouTube URLs, video IDs, channel URLs, keywords, creator prompts, optional checklist values, and calculator assumptions so the tools can produce results.
- Avoid entering private YouTube Studio data unless the tool clearly asks for owner-side checklist inputs.
- Do not paste secrets, API keys, passwords, private account tokens, or personal documents into public tools.
- Future saved-history features should store sanitized report data only after login and clear user action.
Cache, quota, and diagnostic data
The platform may use cache metadata, quota counters, rate-limit events, and sanitized diagnostics to keep public tools reliable and quota-safe.
AI creator workflows
AI creator tools are designed to use server-side provider settings. Public pages should not expose provider secrets, raw API keys, or admin-only configuration.
Frequently asked questions
Should I enter private account credentials?
No. Public tools should not receive passwords, API keys, private tokens, or unrelated personal documents.
Are unavailable public YouTube fields treated as zero?
No. Unavailable, private, or hidden public fields should be labeled as unavailable rather than stored or displayed as fake zero values.