Privacy Policy
Creafix Media (“we”, “us”) produces documentary and cast-retrospective videos for its own YouTube channels. This policy covers Munshi, our internal production board at munshi.creafixmedia.com, and the internal Creafix Topic Research Scripts that support it. Both are used only by our own team; neither is offered to the public.
1. Use of YouTube API Services
The scripts call the search.list, videos.list, channels.list and playlistItems.list methods to read publicly available information about YouTube videos and channels: titles, publish dates, view counts, channel names and upload lists. We use this to decide which topics to produce videos about and to avoid duplicating subjects that are already well covered.
Our scripts do not use OAuth and do not ask any person to sign in with a Google Account. They do not access private channel data, subscriber lists, comments, watch history or any other non-public information, and they never post, upload, rate, comment or otherwise write to YouTube.
2. What we collect and store
- Public YouTube data retrieved through the API (video and channel metadata and public statistics), stored in internal spreadsheets and databases on our own servers.
- Team account data for Munshi: the work email, name and role of each team member, plus the production records they create (show titles, statuses, assignments, notes).
- Technical logs (IP address, browser, time of request) kept by our hosting for security and troubleshooting.
We do not collect any data from members of the public and we do not use cookies for advertising or tracking. Munshi sets only the cookies and local storage needed to keep a team member signed in.
3. How long we keep YouTube API data
In line with the YouTube API Services Developer Policies, data retrieved from the API that is not publicly available statistics is refreshed or deleted within 30 days. Public statistics (such as view counts) that we keep for trend comparison are retained no longer than needed for editorial decisions. Cached API responses are used only to avoid repeating identical requests.
4. How we use the data
- Choosing and scheduling topics for our own YouTube channels.
- Checking what has already been published on a subject and how it performed.
- Tracking our own production pipeline in Munshi.
We do not sell, licence, rent or otherwise share YouTube API data with third parties, we do not use it to build profiles of individuals, and we do not display it to anyone outside our team.
5. Sharing and processors
Data is processed on servers we control (Hetzner Online GmbH, Germany, with Cloudflare in front for transport security). We share personal data only with these infrastructure providers, and only as needed to run the service, or where the law requires it.
6. Your choices and contact
- Because our tools do not use Google sign-in, there are no Google Account permissions to revoke. If you ever granted our tools access to a Google Account, you can revoke it at any time from the Google security settings page.
- Team members can ask us to correct or delete their Munshi account data by emailing wardah@xwave.pk.
- Anyone with a question about this policy, or about data we may hold about them or their channel, can write to the same address. We reply within 14 days.
7. Security
Munshi is served only over HTTPS, accounts are password protected, and access to the underlying servers is limited to named administrators using SSH keys.
8. Changes
If this policy changes we will update the date at the top of this page. Material changes to how we use YouTube API Services will be notified to YouTube as their policies require.