Privacy policy
Last updated: 21 October 2026
Who runs ClipEngine
ReplayRaven (ClipEngine) is run by Justin H in the Netherlands (the operator), who is the controller for the data described here. Contact: privacy@replayraven.com.
ClipEngine is the operator's private publishing software. It makes short clips from campaign videos and from the operator's own brand, and the operator approves every clip before it is posted to the operator's own accounts on YouTube, Instagram, X (@replayraven) and TikTok. It has no other users and no sign-up.
Posts on X and Instagram that nobody pays for are published automatically, through the operator's self-hosted copy of the scheduler Postiz. Posts on TikTok go out through PostPeer, a posting service that the operator connected to the TikTok account through TikTok's own sign-in (see Who else receives data). If TikTok does not accept a public post sent that way, ClipEngine sends the clip to the account's TikTok inbox as a draft instead, and the operator publishes it in the TikTok app. ClipEngine uploads YouTube posts itself as private videos, and the operator makes each one public in YouTube Studio (see YouTube API Services below). The operator publishes the rest by hand in the platform's own app: sponsored (paid) posts on X and Instagram and every post for a Vyro campaign. For posts published by hand, ClipEngine only stores the link the operator pastes.
Data from the connected accounts
The operator connects each account through the platform's own sign-in and consent screen. ClipEngine never receives the password. After the connection, it holds:
- the access and refresh tokens the platform issues;
- basic profile information of the account: account ID, name, username and profile picture, for X also whether the account is verified; for YouTube only the channel ID; for TikTok the account's open ID and display name;
- the IDs and links of the operator's posts, and their statistics: views, likes and the number of comments, and for YouTube also the number of views per country.
It uses this data to publish the clips the operator approved, to show the operator how those posts perform and to estimate what a campaign owes for them. The legal basis is the operator's legitimate interest in running his own accounts, and for the bookkeeping records the legal obligation to keep them. For YouTube and TikTok, ClipEngine reads the counts right after a post goes out, every 6 hours during the first 3 days, and once more after 48 hours and after 7 days; it stops after 8 days. For X and Instagram it reads them up to four times a day during the first 30 days, and not at all for posts published there by hand. The permissions requested per platform are:
- Instagram: read the basic profile, publish content and read insights. The standard permission set also covers comments; ClipEngine does not read or write comments;
- X: read the profile and post on behalf of the account. ClipEngine does not request access to direct messages;
- YouTube: upload videos, view the YouTube account, manage the account's videos (used only to change the title and description of the operator's own videos) and view YouTube Analytics reports (used only for the views per country of the operator's own videos); see YouTube API Services;
- TikTok (through PostPeer): the permissions PostPeer's TikTok app asks for, which cover the basic profile and uploading and publishing videos. The token for that connection is held by PostPeer, not by ClipEngine;
- TikTok (ClipEngine's own TikTok app): read the basic profile (user.info.basic) and the account's public videos with their counts (video.list). ClipEngine holds this token; see TikTok API.
Data about other people
ClipEngine does not collect data about anyone else on these platforms. It does not read comments, messages, followers or other people's posts. The only numbers it reads are totals for the operator's own posts, for YouTube also split by country. These totals say nothing about individual viewers.
The campaign videos it works from are supplied by the campaign owners for clipping. ClipEngine transcribes them on the operator's server and detects where faces are in the frame so it can crop the picture. It does not identify anyone.
Where the data is kept
The tokens and profile information for X and Instagram are stored only in the operator's self-hosted Postiz, on the operator's own server in the Netherlands. The YouTube token and the token of ClipEngine's own TikTok app are kept in ClipEngine's own configuration file on the same server. TikTok can hand out a new refresh token when ClipEngine renews access, and ClipEngine keeps the newest one in its database on that server (see YouTube API Services and TikTok API). That server is not reachable from the internet. ClipEngine's own records of posts, statistics and earnings are kept in a database on the same server. Backups stay on the operator's own equipment in the Netherlands, and the database dumps on the server are normally deleted after 14 days.
Before Postiz publishes a clip, it stores the video in Cloudflare R2 under media.replayraven.com, at a random address that is not linked from anywhere. Instagram fetches the video from that address; for X, Postiz reads the file and sends it to X itself. Postiz also keeps a copy of the X account's profile picture there. ClipEngine uploads the clips the operator posts by hand to the same place in the same way, so the operator can open the file on a phone. Anyone who has the exact address can open a file, and every file is deleted 7 days after upload.
How long the rest is kept:
- campaign videos on the server: 7 days; finished clips: 30 days;
- the readings of each post's statistics over time: 12 months; the last reading stays with the post record;
- records of posts (link, caption, dates) and of earnings: 7 years, for the bookkeeping;
- tokens and profile information: until access is revoked, see below.
Who else receives data
- The platforms receive the published clips and captions, under their own terms and privacy policies.
- The campaign platform or client that commissioned a clip (Whop Content Rewards, Vyro or a direct client) receives the public link to the post, which the operator submits by hand on the campaign's site. The platform measures the views itself; ClipEngine sends it no statistics.
- Cloudflare provides DNS for replayraven.com, serves this website and stores the video files for 7 days.
- PostPeer (postpeer.dev) holds the connection to the TikTok account. For each TikTok post it receives the video and the caption and passes them to TikTok. ClipEngine deletes the video from PostPeer's storage once the post is public, or once a draft has reached the TikTok inbox. ClipEngine does not ask PostPeer for statistics; it reads them through its own TikTok app (see TikTok API). PostPeer handles this data under its own terms and privacy policy.
- Anthropic (Claude) receives transcripts of the campaign videos and the campaign briefs, so it can pick moments, draft captions and check a draft against the brief. To suggest better moments it also receives up to five of the operator's best-performing hook lines from the last 14 days, each with its total view count. Only posts outside TikTok count here: TikTok's numbers never go to Anthropic. In the operator's Anthropic account, the setting that allows Anthropic to train its models on these chats is turned off. Anthropic keeps the requests under its own terms and privacy policy. It receives no tokens, no links to the operator's posts, no statistics other than the hook totals above, and no data read from the platforms about other people. The transcripts and briefs can contain the names and handles of the people in the campaign videos.
Anthropic and Cloudflare are based in the United States, as are the platforms. Data sent to Anthropic and Cloudflare is covered by the EU standard contractual clauses in their terms.
Data is not sold, shared for advertising or used to build profiles.
YouTube API Services
ClipEngine uses YouTube API Services. It uploads the clips the operator approved to the operator's own YouTube channel through the YouTube Data API, as private videos, and the operator makes each one public himself in YouTube Studio. Using ClipEngine's YouTube connection means agreeing to the YouTube Terms of Service. Google's handling of data is described in the Google Privacy Policy. ClipEngine's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
The connection asks Google for four permissions: upload videos (youtube.upload), view the YouTube account (youtube.readonly), manage the account's videos (youtube.force-ssl) and view YouTube Analytics reports (yt-analytics.readonly). ClipEngine uses them for this and nothing more:
- it uploads each approved clip as a private video, with its title and description, and for a sponsored clip with the "paid promotion" setting switched on. The video goes straight from the operator's server to YouTube. The operator makes it public himself;
- when the operator asks for it, it changes the title and description of one of the operator's own videos. It never deletes a video and never changes a video's other settings; ClipEngine's software refuses any other kind of request before it is sent;
- it reads which channel the connection belongs to (the channel ID), so that it does not upload to any other channel;
- before each upload it reads the titles and descriptions of the channel's 50 newest videos and compares them with the new clip, so that it does not upload the same clip twice. It does not store them;
- right after an upload it reads the new video's status: whether it is public, whether paid promotion is on and whether YouTube accepted it. If one of these is wrong, the post does not count as published until the operator has fixed it in YouTube Studio;
- for the first 8 days it reads the view, like and comment counts of the operator's videos (YouTube Data API), and after 48 hours and after 7 days the views per country of each of those videos (YouTube Analytics API). ClipEngine uses the views per country only to show the operator which share came from the countries a campaign pays for.
It does not read other channels or other people's videos, comments, subscribers, the account's email address or any YouTube Analytics data other than views per country of the operator's own videos.
The refresh token is kept only in ClipEngine's configuration file on the operator's own server in the Netherlands, and only the operator can read that file. The access tokens Google issues from it stay in the server's memory and expire within an hour. ClipEngine stores the channel ID with the account, and the video ID, link, dates and counts with each post record, for the periods listed above.
The operator can revoke ClipEngine's access at any time, with the "Revoke YouTube access" button in ClipEngine's dashboard or on Google's security settings page (also at myaccount.google.com/permissions). The token stops working at once, and the operator deletes it from the server within 7 days. A request to delete the data ClipEngine received from YouTube can be sent to privacy@replayraven.com. The operator deletes it within 7 days, apart from the records the law requires the operator to keep for the bookkeeping (see Where the data is kept).
TikTok API
Besides posting through PostPeer, ClipEngine has its own TikTok app, "ReplayRaven", which uses TikTok's Login Kit and Display API. The operator connected the TikTok account to it once, through TikTok's own sign-in and consent screen. It asks TikTok for two permissions and uses them for this and nothing more:
- read the basic profile (user.info.basic): the account's open ID and display name, so ClipEngine reads data of this one account only and stops if the connection belongs to any other account;
- read the account's public videos (video.list): for each of the operator's own TikTok posts its ID, creation time and link, and its view, like, comment and share counts. ClipEngine reads them right after a post goes out, every 6 hours during the first 3 days, and after 48 hours and after 7 days, and shows them to the operator so he can see how each clip performs and check what a campaign owes him.
ClipEngine never posts, likes, follows, comments or sends messages through this app, and it reads no data about other users. It uses the data it receives from TikTok only for the purposes above, within ClipEngine. The data is not sold, not used for advertising and not used to build profiles, and TikTok's numbers are not sent to anyone else.
The refresh token is kept in ClipEngine's configuration file on the operator's own server in the Netherlands, and the newest one TikTok hands out when access is renewed in ClipEngine's database on the same server. Only the operator can read them. The access tokens TikTok issues from it stay in the server's memory and expire within 24 hours; the refresh token works for at most a year. The counts are kept with each post record for the periods listed under Where the data is kept.
The operator can revoke the app's access at any time in the TikTok app's settings, under the apps connected to the account (Security & permissions). The token then stops working, and the operator deletes it from the server within 7 days. A request to delete the data ClipEngine received from TikTok can be sent to privacy@replayraven.com; the operator deletes it within 7 days, apart from the records the law requires the operator to keep for the bookkeeping. TikTok's handling of data is described in the TikTok Privacy Policy, and its use is subject to the TikTok Terms of Service.
Revoking access and deleting data
Access can be revoked at any time in the connected-apps or security settings of the platform (for Google, see the link above). A revoked token no longer works. The operator then deletes the stored token and profile information within 30 days.
Anyone who wants to know whether ClipEngine holds data about them, or wants it deleted, can email privacy@replayraven.com. The request is answered within 30 days. Records the bookkeeping needs are kept for the 7 years mentioned above.
For X there is a shorter deadline. If a post is deleted, protected or withheld on X, the operator deletes or updates the stored X data for that post as soon as he learns of it, and within 24 hours of a request from X or the account owner.
Copies in backups disappear when the backups rotate (the database dumps normally after 14 days). Deleted data is never restored from a backup.
Under the GDPR you have the right to access, correct and delete your data and to object to its use. You can also complain to the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).
This website
This site is a set of static pages. It sets no cookies and has no analytics, tracking or embedded content. Cloudflare, which serves it, may keep technical logs such as IP addresses for security, as described in Cloudflare's privacy policy.
Changes
When this policy changes, the date at the top changes with it.