Consent is one PIPL basis — bundled ‘I agree to everything’ is not consent.
PIPL allows processing on consent and on other statutory bases (contract necessity, statutory duties, HR/labour rules, public health, reasonable news reporting, and other conditions provided by law). Consent must be informed, voluntary and explicit, and people can withdraw it. Separate consent is a stricter sibling for SPI, export, public disclosure and similar gates. A privacy policy tick-box that bundles analytics, marketing and export is a classic failure. Do not copy GDPR ‘legitimate interests’ as a PIPL basis — it is not in the statute.
4 questions before you choose the route.
This page identifies the right question and evidence. It does not determine the legal outcome on a reader’s facts.
Which PIPL basis actually fits?
Consent vs contract vs HR vs legal duty.
BasisWas it informed and unbundled?
Purpose-by-purpose, not a wall of text.
QualityCan they withdraw?
Withdrawal must be as easy as giving consent.
WithdrawIs separate consent required instead?
SPI, export, disclosure — sibling page.
SeparateWorking rule: Map the regulated role before marketing or launch in China.
The signal ledger.
These facts move the question beyond a label and into a product, money-flow and control analysis.
Bring a compact evidence docket—not a pitch deck.
Give a compliance team or counsel the operating facts that reveal the perimeter.
Questions people ask before they build.
Short answers for orientation. The right result can change with the service model and current rules.
Is consent always required?
No. Contract, HR and legal-duty bases exist. Misusing consent can be worse than using the right basis.
Does withdrawal mean delete everything?
Withdrawal stops processing based on consent. Other bases and legal holds can remain.
Primary authorities
Reviewed sources support orientation, not a fact-specific assessment.
