Draft pending attorney review
This policy describes how Blink Studio actually works, based on a review of the app's source code. It hasn't been reviewed by a lawyer and isn't in effect yet. Section 14 (Your choices and rights) in particular is awaiting legal review.
Summary
Blink Studio runs on your Mac. It doesn't send your data to servers we operate, and it contains no analytics, advertising or telemetry. It talks to Twitch and TikTok directly, using accounts and developer apps you connect. Records, clips and logs are stored on your Mac. Passwords are never seen by Blink. Access tokens and app secrets are stored in the macOS Keychain.
1. Who we are
"Blink Studio", "Blink", "we" and "us" refer to Andrew Rutherford, the publisher of Blink Studio, based in Texas, United States. Contact details are in section 17.
2. What this policy covers
This policy covers (a) this website and (b) the Blink Studio Mac app ("the app"). It doesn't cover Twitch, TikTok or other services you connect to the app. Their own privacy policies apply to them.
The app is operated by its user, the person running it on their Mac ("you"). Because the app stores everything on your Mac and sends data only to the services you connect, you control the data it processes, including information about creators whose streams you monitor.
3. This website
- This site is a set of static pages. It uses no cookies, no analytics, no advertising, no contact forms and no third-party fonts or scripts.
- The site is hosted on Cloudflare Pages. Like any web host, Cloudflare processes technical request data, such as your IP address, browser user agent and requested URL, to deliver and protect the site. See Cloudflare's Privacy Policy.
- If you email us at blinkcliper@gmail.com, we receive your email address and whatever you write. We use it only to reply. Our email is hosted by Google (Gmail), so messages are also processed under Google's Privacy Policy. We keep support emails for up to 12 months after your request is resolved, unless longer retention is legally required or necessary for an ongoing dispute. Old emails are deleted by hand; there is no automatic deletion.
4. Data Blink stores on your Mac
The app keeps a local SQLite database (by default data/agency.db in the app's folder) and local media folders. Nothing in them is uploaded to us. They hold:
| Category | What's stored | Where it comes from |
|---|---|---|
| Twitch channels and creators | Twitch login, display name and user ID. The streamer list you build. Priority settings, content categories and content shares. Optional affiliation details you enter for a creator (organization, role, verification status, a public source link and a note). | You, and Twitch's public API |
| Creator permissions | Permission type (Twitch clipping or TikTok repost), status (pending, granted or revoked), the evidence note you enter (for example, a link to written consent) and dates | You |
| Stream status | Periodic samples of whether a channel is live, its title, game, viewer count and stream ID | Twitch's public API |
| Detected moments | Time, score, kind of moment, chat rate statistics, the most common words or emotes, and up to five short chat message excerpts (80 characters max, without usernames) as context | Twitch public chat, analyzed by the app |
| Clips and review | Twitch clip ID, URLs, title, thumbnail URL, duration, view count, position in the stream, game, outcome, and your approve, reject or hold decision | Twitch's API, and you |
| TikTok drafts | Draft stage, upload progress, TikTok publish ID, error messages, file paths, a SHA-256 fingerprint of each footage file (to catch duplicates), render notes, and the suggested caption and hashtags. A suggested caption may quote one short line (up to 90 characters) from the clip's transcript. | The app and TikTok's API |
| Connected TikTok account | Display name and avatar image URL of the connected account, plus the last 6 characters of its TikTok ID shown on the dashboard | TikTok's API |
| Settings | Manual or Automatic mode, switches, Emergency Stop, selected background audio and the result of the last TikTok test draft | You, and the app |
| Live-feed sessions (experimental) | Session and connection status, buffer segment records, resource usage samples, and audio and visual moment scores. Transcript text isn't stored in the database. | Creator-authorized live feeds, analyzed by the app |
Chat messages are processed in memory as they arrive. Apart from the short excerpts above, the app doesn't save chat logs or chatter usernames. See Public Twitch chat in section 7.
Files on your Mac
Blink keeps its data in one folder on your Mac. For the copy of Blink distributed to creators, that's ~/Library/Application Support/Blink; nothing is stored inside the app itself, so installing a newer version doesn't remove your data. The paths below are relative to that folder.
- Authorized footage you add:
data/media/authorized/. - Rendered TikTok drafts:
data/media/drafts/. Once TikTok has confirmed a draft was delivered, its video file here is deleted automatically after 90 days (see section 12). - Experimental live-feed clips:
data/media/live_clips/. When speech was transcribed, a caption file (.srt) containing the transcript is saved next to the clip. - Live-feed buffer: short video segments, kept on a rolling basis (see section 12).
- Temporary work files: caption files made while rendering, and partial files while footage is being added. These are deleted when the step finishes.
- Logs: see section 11.
5. Credentials and the macOS Keychain
- Twitch: you sign in on twitch.tv with Twitch's device sign-in flow, so Blink never sees your Twitch password. The resulting access and refresh tokens are stored in the macOS Keychain under the service name
blink.twitch. - TikTok: you sign in on tiktok.com, so Blink never sees your TikTok password. Your TikTok app's client key and client secret, and the access and refresh tokens, are stored in the macOS Keychain under the service name
blink.tiktok. If you use both Sandbox and Production credentials, each one's values are kept there separately. - Tokens and secrets are never shown in the app's dashboard, never returned by its local web interface and never written to its logs. Error messages are scrubbed of these values before they're shown or logged.
- Optionally, you can put app credentials in a local
.envfile on your Mac instead. That file isn't sent anywhere.
6. Creator footage and permissions
- The app never downloads Twitch video itself. You add a clip file ("authorized footage") and confirm that you have the creator's permission for it. Files are stored in
data/media/authorized/on your Mac. - Rendered vertical drafts are stored in
data/media/drafts/on your Mac. - A clip can only become a TikTok draft if the creator's TikTok repost permission is recorded as granted, with evidence. Once a withdrawal is recorded, Blink won't approve new clips from that creator, and it won't render or upload any pending drafts of their footage. Draft video files already rendered stay on your Mac until you delete them. Drafts already in a TikTok inbox, and posted videos, stay on TikTok until removed there.
- Creators taking part in the Blink Studio creator program must be at least 18 years old and must have the rights and permissions needed for the footage they submit (see the Terms of Service). Permission records and their evidence are entered by the person running Blink. The app doesn't store a creator's age or date of birth. Blink doesn't independently verify a creator's age, identity or ownership of footage.
- For creator-authorized live feeds (experimental), the app keeps a short rolling buffer of video segments (about 90 seconds per stream by default) and deletes older segments as it goes. Leftover segments from an interrupted session are deleted the next time the app starts.
7. Twitch
When you connect Twitch, the app requests the scopes chat:read (to read public chat) and clips:edit (to create clips). It uses Twitch's API for channel and stream information, Twitch's chat service (irc.chat.twitch.tv) to read chat, and Create Clip and Get Clips to make and confirm clips. It never sends chat messages. Clips created through Twitch are Twitch content under your account and are subject to Twitch's Privacy Notice and terms.
What Blink gets from Twitch: channel login, display name and user ID; live status, stream title, game and viewer count; public chat messages (see below); and details of clips you create (ID, URLs, title, thumbnail, duration, view count).
Signing out of Twitch: the command-line tool can sign out (twitch-logout). This asks Twitch to revoke the token and removes it from the Keychain. The control center doesn't currently have a Twitch sign-out button. Signing out doesn't delete channels, moments or clip records.
Public Twitch chat
Blink may read the publicly available chat of the Twitch channels you choose to monitor, as messages arrive, and analyze it on your Mac to detect highlight moments.
- For each detected moment, Blink may keep up to five short chat excerpts (80 characters each at most) as context. Excerpts are saved without usernames.
- Excerpts are stored only in the local database on the user's Mac. They aren't uploaded to Blink servers, because Blink has no backend server.
- Other chat messages are discarded after analysis and aren't saved.
- Blink doesn't identify who wrote a chat message, so it can't tell whether a message came from a minor.
- Excerpts are deleted when the user deletes Blink's local data (see section 12).
8. TikTok authorization and drafts
- The app uses TikTok Login Kit for Desktop (with PKCE) and asks only for
user.info.basic(to show which account is connected) andvideo.upload(to send drafts). It never asks forvideo.publish, so it can't post publicly. - After you approve, TikTok redirects to a local address on your own Mac (
http://127.0.0.1:8780/tiktok/callback/). The sign-in code is exchanged for tokens directly with TikTok. - When a draft is uploaded, the rendered video file is sent to TikTok through its Content Posting API, together with its size and how it's split into chunks. It lands in the connected account's TikTok inbox. Captions, hashtags, creator permissions, chat excerpts and other records aren't sent. You paste the suggested caption yourself.
- Blink also sends TikTok your app's client key and secret, sign-in and refresh tokens, and status checks for uploads, and it asks for the connected account's display name and avatar.
- TikTok draft delivery is experimental: real integration testing and TikTok's approval are pending.
- You review and publish every draft manually in the TikTok app, or delete it. The app only checks the upload status TikTok reports.
- Disconnect TikTok asks TikTok to revoke the app's access when TikTok is reachable, and always removes the stored tokens and account name from your Mac. It doesn't delete clip records, drafts or creator permissions.
- What TikTok does with uploaded videos and account data is governed by TikTok's Privacy Policy. Blink Studio isn't affiliated with or endorsed by TikTok.
9. Processing on your Mac
- Captions: if whisper.cpp is installed, speech in a clip is transcribed on your Mac. Audio isn't sent to a cloud transcription service.
- Video: reframing, captions, branding and quality checks are done on your Mac with ffmpeg.
- Moment scoring: chat (and, for experimental live feeds, audio and video) is analyzed on your Mac.
10. Third-party services
| Service | Used for | What it receives |
|---|---|---|
| Twitch | Sign-in, channel and stream information, reading chat, creating and checking clips | Your Twitch tokens and app client ID, the channels you request and clip requests |
| TikTok | Sign-in, account name, uploading drafts and checking their status | Your TikTok app credentials and tokens, and the rendered video files you send |
| Cloudflare | Hosting this website | Technical request data from website visitors |
| Google (Gmail) | Receiving email you send us | Your email address and message |
| Google Drive | Delivering Blink Studio app files to selected creators through restricted download links | Information Google collects when a recipient opens or downloads a shared file, such as their Google account details, device and network information, and access activity |
The app has no analytics, crash-reporting or advertising SDKs.
During its initial release, Blink Studio is distributed privately to selected creators. It isn't offered through any public app store.
How Blink Studio is delivered
- App files are delivered through restricted Google Drive download links. Google Drive is a third-party service run by Google.
- A restricted link only works for people who have been given access. To share it, we add the recipient's Google account or email address to the file's access list.
- When a recipient opens or downloads a shared file, Google may independently process information about them, such as account, device and access information, according to Google's own privacy practices. See Google's Privacy Policy.
- Google Drive is used only to distribute the app privately. Blink doesn't integrate with Google Drive, and the app receives no information from it.
- We don't collect, track or use Google Drive access or download activity, and the app has no download tracking or analytics of its own.
11. Logging
- Main log (
logs/agency.log): rotates at about 5 MB and keeps up to 5 older files, so roughly 30 MB at most. - App log (
logs/blink-app.log): when Blink is started from the Blink app icon, its console output is written here. It rotates at about 5 MB and keeps up to 3 older files, so roughly 20 MB at most. - Startup log (
logs/blink-app-startup.log): anything printed before Blink has fully started. It's replaced each time Blink is opened. - The control center also keeps the 60 most recent warnings and errors in memory to show on screen. They're cleared when Blink quits.
- Logs can include channel names, clip and draft IDs, timestamps, status changes and error messages. They don't include chat messages, tokens, client secrets or passwords.
- Logs stay on your Mac and aren't sent to us.
12. Retention and deletion
This is how long each kind of information is kept today. Except where the table says so, nothing is deleted automatically.
| Information | How long it's kept | Deleted automatically? |
|---|---|---|
| Database records: channels, creators, permissions, moments and chat excerpts, clips, reviews, drafts, live-feed records, settings | Until you delete them. Removing a creator pauses them and keeps their permission history, so there's a record of consent. Un-approving a clip removes its pending draft record. | No |
Rendered draft video files (in data/media/drafts/) for drafts TikTok has confirmed as delivered | 90 days after the confirmed delivery. Blink checks each time it starts, so a file can stay longer if Blink isn't opened. | Yes |
| Rendered draft video files for drafts not yet delivered (waiting, uploading, processing or failed) | Until you delete them. They're never removed automatically. | No |
| Authorized (source) footage, live-feed clips and their caption files | Until you delete them | No |
| Live-feed buffer segments | About 90 seconds per stream by default. Leftovers from an interrupted session are removed when the app next starts. | Yes |
| Temporary work files | Until the render or file copy finishes | Yes |
| Main log | Up to about 30 MB, with the oldest entries overwritten | Yes, by rotation |
| App log and startup log | Up to about 20 MB for the app log; the startup log is replaced at each launch | Yes, by rotation and replacement |
| Keychain entries (tokens, TikTok app credentials) | Until you disconnect TikTok, sign out of Twitch, replace them, or delete them in Keychain Access | No |
| Support emails sent to us | Up to 12 months after your request is resolved, unless longer retention is legally required or necessary for an ongoing dispute (see section 3) | No. Deleted by hand. |
What the 90-day rule covers: only the locally stored video file of a delivered draft. It doesn't delete the draft's database record (kept as history), creator permission records, creator attribution and credit, authorized source footage, or any other database records. It doesn't affect the draft in your TikTok inbox or a video you posted.
Disconnecting and uninstalling
- Disconnect TikTok revokes access when TikTok is reachable and removes the token and account name. TikTok app credentials stay in the Keychain, and clip, draft and permission records stay in the database.
- Twitch sign-out (command line) revokes and removes the Twitch token. Records stay in the database.
- Deleting the Blink app icon doesn't delete your data. The database, media folders, logs and Keychain entries remain.
- To delete everything, quit Blink, delete its data folder (
~/Library/Application Support/Blink, includingdata/andlogs/) and remove theblink.twitchandblink.tiktokentries in Keychain Access. Drafts in a TikTok inbox, videos posted on TikTok and clips created on Twitch must be deleted on those platforms.
13. Security
The app's control center only listens on your own computer (127.0.0.1). Every action needs a per-session token from the app's own page, and requests from other websites are refused. Connections to Twitch and TikTok use HTTPS or TLS. Tokens and app secrets are kept in the macOS Keychain. Blink doesn't encrypt its own database, media files or logs. They're protected only by your Mac's user account and disk security, such as FileVault if you've turned it on. Even so, no software is perfectly secure, and keeping your Mac and accounts secure remains your responsibility.
14. Your choices and rights
- You can disconnect Twitch or TikTok, delete local data and remove Keychain entries at any time (see section 12).
- Creators can ask the operator who monitors their channel to update or withdraw permission. A revoked TikTok repost permission blocks further drafts of their clips.
- We don't hold app data on our servers, so we usually can't access, correct or delete data stored on someone else's Mac. For requests about this website or email you sent us, write to blinkcliper@gmail.com.
- Depending on where you live, you may have rights over personal information we hold about you, such as access, correction or deletion. To make a request, email blinkcliper@gmail.com.
15. Adults only (18+)
Blink Studio and this website are intended for adults. You must be at least 18 years old to use Blink Studio (see the Terms of Service). We don't knowingly collect personal information from anyone under 18.
Blink Studio doesn't verify users' ages. The app stores its data on the user's own Mac. Blink has no backend server, so the only personal information we receive directly is email sent to us. Creators taking part in the Blink Studio creator program must also be 18 or older (see section 6).
If you believe someone under 18 has sent us personal information, or that a minor's information has otherwise been submitted to us, email blinkcliper@gmail.com. Tell us what was submitted and how, without including the minor's personal information in your message where you can avoid it. We'll review reports sent to that address and, where appropriate and legally permitted, delete information we hold from someone under 18.
We can only delete information we control. We can't delete data stored in Blink on another person's Mac, clips on Twitch, or videos on TikTok or other services. For those, contact the person who runs that copy of Blink, or report the content to the platform directly.
16. Changes
We may update this policy, for example when the app's data practices change through new features or integrations.
When we change this policy, we'll publish the updated version on the official Blink Studio website (this site) and update the effective date at the top of the page. For significant changes, we'll also email existing participating creators when reasonably practicable. Blink Studio doesn't have in-app or automatic notifications, so please check this page from time to time.
17. Contact
Privacy questions and data requests: blinkcliper@gmail.com. See also the Contact page.