[nantes]

It appears to just be an HTTP 301 redirect, so you could use something like curl to unroll it:

  curl -I https://www.tiktok.com/t/ZTRmqkW4N

produces:

  HTTP/2 301 
  server: nginx
  content-type: text/html; charset=utf-8
  location: https://www.tiktok.com/@spencer.sebastian.yang/video/7149578560230034734?_t=8W9Y6CPjvbf&_r=1

Trim off the GET params (the bit after the ? in the URL) and you get <https://www.tiktok.com/@spencer.sebastian.yang/video/7149578...>. That appears to load in a browser for me.

I did check to see if that resulting URL after the first redirect is also a redirect. It is not, but also returned an HTTP 403 response ('Forbidden'), when submitted without cookies that had been added.

[rwalle]

When you run that curl command, TikTok already knows your IP, which is a very valuable piece of information. Unless you maintain a server that has its own IP and does nothing except de-personalizing TikTok links, and always visit the tracking-free URL from another computer with a different IP, something like that. While it is possible, I am pretty sure most people, including most people here, don't want to do that.

[dylan604]

Sounds like a new SaaS to remove TikTok tracking. Some way to redirect any TikTok link w/o the tracking. You could then do the most SV thing to offer it for free and store the same tracking info yourself and/or deliver ads from your accounts

[nantes]

That's an excellent point.

On the other hand, I don't think most people consider a public IP address to be private or protected information. If you're interested in finding the "root" content URL, which lives on a TikTok domain, then you've already implicitly signaled that you accept them knowing your public IP address.

[Aachen]

Of course nobody could consider an IP address private information, similar to how a license plate can be read by everyone wherever you go.

But that doesn't mean it's not protected by privacy legislation. Your plate or IP isn't secret, but tracking everywhere it goes still impacts privacy.