Last updated 4 September 2026
ContentSense is a private tool with a single operator. It holds almost no personal data, and what it does hold exists to do one job: upload a finished video to the operator's own TikTok account as a draft. This page says what is stored, where it goes, and how to get rid of it.
There are no public users. Accounts are created by the operator and there is no sign-up. The only personal data in the system belongs to the operator: an account to sign in with, and — if TikTok is connected — the details TikTok returns for that connection.
Connecting an account through TikTok Login Kit stores exactly this:
The only scope requested is video.upload. It permits placing a
video in the account's inbox as an unposted draft. It does not permit posting
publicly, and it does not grant access to followers, messages, analytics or
any other account data — none of which is requested or stored.
Series, episodes, scripts, generated images, narration audio, rendered videos, uploaded or downloaded source recordings, their transcripts, and a record of what each generation cost. These are the operator's own working files. Source recordings are supplied by the operator, who is responsible for holding the rights to them.
ContentSense runs on a single server controlled by the operator. Content is sent to these third parties only as needed to produce it, and each is governed by its own privacy policy:
TikTok tokens are never sent to any of the others, and nothing is sold, rented or shared for advertising. Some generation runs on the operator's own self-hosted models, in which case nothing leaves their infrastructure at all.
Disconnecting TikTok in the panel deletes the stored tokens; you can also revoke the connection from TikTok's own settings, which invalidates them immediately. Videos already uploaded as drafts live in the TikTok account and are managed there, not here. Generated media and records are deleted by the operator at their discretion and are kept no longer than they are useful.
Tokens are encrypted at rest. Generated media is stored privately and served only through authenticated routes — nothing is on a public URL. Logs are written with credentials, tokens and pre-signed upload URLs redacted, because an upload URL is itself a capability. The panel requires a verified account to reach anything at all.
A session cookie for signing in, and a CSRF cookie. There is no analytics, no tracking and no third-party script on this site.
This policy may change. The date at the top is the version in force.
Questions, or a request to delete data, can be sent to the operator of this deployment.