Educational overview only. This article is not legal advice. Consult qualified counsel for compliance decisions specific to your business.
If you build a SaaS product that touches TikTok data and any of your users live in California, the California Consumer Privacy Act (CCPA) and its 2023 amendment, the California Privacy Rights Act (CPRA), almost certainly apply to you. This guide walks through the practical pieces a US product team should think about when shipping a TikTok analytics or scraping tool to a US audience, with a focus on California first and the rapidly growing multi-state landscape second.
The CCPA went into effect in 2020. The CPRA, which took effect in January 2023, did not replace it but layered new obligations on top. For most product teams, the differences that matter day-to-day include:
If you only built for CCPA in 2020 and never revisited the policy, your privacy notice is almost certainly behind. The CPRA expects specific disclosure of retention periods for each category of personal information collected, not a vague "as long as necessary" line.
Not every California-facing site is in scope. A business is generally covered if it does business in California, determines the purposes and means of processing personal information, and meets one of three thresholds:
The 100,000 threshold catches many small-to-mid SaaS tools more often than founders expect, especially anything with an analytics integration, a logged-in user base, or marketing pixels firing on a high-traffic landing page. A TikTok data product with a popular free tier can hit this faster than its revenue figures suggest.
The California definition is sweeping: "information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular consumer or household." That includes IP addresses, device identifiers, inferences drawn from any of the above, and, importantly for our space, persistent identifiers tied to a public TikTok account when that identifier is reasonably linkable to a real person.
A public TikTok handle is not automatically personal information in the abstract. The moment you store it next to an account, an inference, or any other signal that lets you link back to a real human, it becomes personal information under California law. Teams building TikTok dashboards should assume that scraped public data, once stored alongside customer accounts and queries, sits inside the CCPA / CPRA perimeter.
This pair trips up a lot of founders. "Sale" under CCPA is intentionally broad and covers exchanging personal information for "monetary or other valuable consideration." Sharing a list of leads with an ad network in return for better targeting can qualify as a sale even though no money changes hands. CPRA's "share" is narrower and aimed specifically at cross-context behavioral advertising.
For a TikTok SaaS, two patterns matter:
If any sale or share occurs, California requires a conspicuous "Do Not Sell or Share My Personal Information" link or button on your homepage and a working Global Privacy Control (GPC) signal handler.
California is an opt-out state for adults: you can sell or share personal information until the consumer says stop. There are two key opt-in exceptions:
Contrast this with the EU's GDPR, which is opt-in by default. If you serve both audiences, the simplest path is to default to GDPR-style consent globally and treat the California opt-out as a fallback. That approach also tends to satisfy newer state laws that lean toward opt-in for sensitive data.
A Consent Management Platform handles the cookie banner, the consent record, the GPC handshake, and the "Do Not Sell or Share" toggle. Common picks for US-focused SaaS include Cookiebot, OneTrust, Osano, and Termly. The key features to look for when evaluating any of them:
If your TikTok dashboard already runs a lightweight cookie banner, swapping in a CMP is the highest-leverage compliance step you can take in an afternoon. Pricing on your pricing page should not change; this is purely an infrastructure addition.
California consumers have the right to request access, deletion, correction, and to know what categories of personal information you hold. You have 45 days to respond, extendable once by another 45 days. Before you act on any of these, you must verify the requester is who they claim to be. For an account-based SaaS, that usually means matching the email on file plus a re-authentication step. For non-account holders, the verification standard scales with the sensitivity of the data.
Practical implementation for a TikTok data tool:
This is the area where TikTok-focused SaaS products diverge the most from generic dashboards. Three rules of thumb:
Be conservative in your privacy and terms language. Acknowledging a potential sale or share is far less costly than getting an enforcement letter that says you concealed one.
If you only process personal information on behalf of another business under a written contract that meets CCPA's contractual requirements (purpose limitation, no combining with other data, deletion at end of relationship), you can qualify as a "service provider" and avoid being treated as a separate "business" with respect to that data. The contract requirements are specific. The template Data Processing Addendum your customer sends is often a good starting point, but you should still have counsel review whether each clause matches the statute.
For a B2B TikTok analytics tool, the service-provider model is usually the right structure for enterprise customers, with consumer-facing self-serve users treated under your direct relationship.
CCPA / CPRA penalties are tiered: up to $2,500 per unintentional violation and up to $7,500 per intentional violation or violation involving a minor. "Per violation" historically meant per affected consumer, which means the multiplier on a data set of any meaningful size becomes existential quickly.
Public enforcement actions have so far focused on:
The 30-day cure period that existed under the original CCPA was sunset by the CPRA for most violations. Treat enforcement risk as live the moment your site goes up.
California is no longer alone. Quick orientation for the other states most likely to apply to a US SaaS:
Texas, Oregon, Montana, Tennessee, Iowa, Delaware, New Jersey, and others have since followed. The good news for builders: most of these laws share a common shape (notice, opt-out for sale and targeted ads, opt-in for sensitive data, DSAR rights). A single well-built compliance program can usually serve all of them, with California as the strictest baseline.
A concise checklist to run quarterly:
You can find more context on how the product is structured on our about page, the live API surface in our documentation, and the no-watermark and credit-based model on the pricing page. Hands-on testing is available in the playground, and account-level controls live in your profile. More walkthroughs are published regularly on the blog.
Most likely yes, if you do business with California residents and meet one of the three thresholds. Physical location of the business is not the test.
Generally no, when the data is processed on behalf of a paying customer for that customer's own stated purposes under an appropriate contract. Reselling enriched profile datasets to third parties is a different story.
If you serve California users and have any advertising pixel, analytics, or third-party tag on the site, a CMP is the practical way to handle the opt-out, the GPC signal, and consent logs.
You expose yourself to per-consumer penalties under CPRA and increasingly to private actions in states that allow them for data breach scenarios. Always log, verify, and respond inside the 45-day window.
California's thresholds already exclude many small businesses, but once you cross the 100,000-consumer mark, size no longer matters. Some newer state laws (Utah, for example) carry higher revenue thresholds.
Inferences drawn from personal information are themselves personal information. If you build profiles or scores from public TikTok signals, those derived attributes fall inside CPRA scope and must appear in your notice.
The California Attorney General and the California Privacy Protection Agency share enforcement. Both have brought public actions in the last two years.
Reminder: this article is for educational purposes and is not legal advice. Privacy law evolves quickly. Engage qualified counsel before making compliance decisions for your business.
Questions about how TikLiveAPI processes data on your behalf? Reach us through the contact page or review the privacy policy and terms for the current contractual baseline.
Ready to put what you read into code? Try our endpoints live or grab the full reference.