TasunkeWitko

Privacy

23 October 2026. App name: Tasunke Music. Contact: [email protected].

Who this is

This page covers the TasunkeWitko website and the private desk that publishes the artist’s own music. The desk is a single-user tool run by the artist on the artist’s own computer. It is not a service other people sign up for. The app name on the Google OAuth consent screen is Tasunke Music (Google Cloud project tasunke-music). The Meta app uses the same name.

This website

tasunke.uk is a static page. It does not have accounts, forms, cookies, or analytics, and it does not embed trackers. The only contact method on the site is email. Choosing Spotify, YouTube Music, YouTube, Facebook, Instagram, or TikTok takes you to that service, which has its own policy.

What the desk does

The desk stays on the artist’s machine. It does four things with the artist’s own files and the artist’s own accounts:

The desk does not pull view counts or other analytics from those platforms. Readings, when they are kept, are typed in by the artist. It does not post to a personal Facebook profile.

Google and YouTube

Connecting YouTube is optional and is started from the desk. The OAuth client requests only:

The desk does not request YouTube Analytics, comments, memberships, or any other Google product. The refresh token is written to data/secrets.json on the computer that runs the desk. The OAuth client id and secret stay in that computer’s .env file. Those files are not part of the public website.

Tasunke Music’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

In practice that means:

Meta (Facebook Page and Instagram)

A Page access token is stored in .env on the artist’s computer. The desk uses the Meta Graph API to publish videos to the artist’s Page and Reels to the artist’s Instagram account, to read the Page name and the Instagram username so it can show that the right accounts are connected, and to check whether the token is still valid and when it expires. It does not read messages, comments, or insights, and it does not collect data about listeners.

Buffer and TikTok

A Buffer API token is stored in .env. The desk uses it to create a post on the artist’s TikTok channel in Buffer, and to list that channel so Settings can show the connection. The post carries the caption and the public video URL. It does not carry Google or Meta tokens.

Public video files

Generated social videos (the mp4 files in the output folder) may be copied to a Cloudflare R2 bucket and served at media.tasunke.uk so Buffer and Instagram can fetch them. Directory listing is off. A direct link still downloads that one file for anyone who has the link, which is what those services need. The audio catalogue and the artwork folder are not uploaded. Audio-only masters are not uploaded. Cover images are uploaded only if a publisher needs a public cover, and only from the output folder.

Captions model

If the artist sets an API key, the desk can ask an OpenAI-compatible service to draft captions. That request contains the track title, artist name, genre, streaming links, and lyric text only when the artist has put a lyrics file in the release folder. It does not contain Google, Meta, or Buffer tokens. With no key, captions stay on the local template and nothing is sent.

What this does not do

How long it is kept

Local files, the catalogue database, and tokens stay on the artist’s computer until the artist deletes them. Objects in the R2 bucket stay until they are deleted there. A video that has already been published stays on YouTube, Meta, or TikTok until the artist deletes it in that product.

Revoke access and delete data

The artist is the only user. To disconnect a platform:

There is no separate account database on this website to erase. A request to delete data can be sent to [email protected].

Contact

Questions about this page or the Tasunke Music desk: [email protected].