US Privacy (CCPA) String Decoder
Ek 4-character US Privacy (CCPA) string apne browser mein decode karein aur notice, opt-out-of-sale, aur LSPA flags plain language mein padhein.
US Privacy (CCPA) String Decoder poori tarah aapke browser mein chalta hai. Jo us_privacy value aap paste ya build karte hain woh aapke device par process hoti hai, kabhi ArrayKit ko upload nahi hoti, aur koi ad endpoint ya USPAPI callback contact nahi kiya jaata.
GPP String Decoder kholein
US Privacy String Decoder ke baare mein
US Privacy (CCPA) String Decoder us 4-character us_privacy signal ko khol deta hai jise ad-ops teams OpenRTB requests, USPAPI callbacks, aur usprivacy cookie mein dekhti hain. Ek value jaise 1YNN paste karein aur yeh har character aapke liye padhta hai: spec version, kya explicit notice aur opt out karne ka mauka diya gaya, kya user ne apne data ki sale se opt out kiya, aur kya publisher IAB Limited Service Provider Agreement ka signatory hai. Har flag — Y, N, ya not-applicable ke liye ek dash — ko ek plain-language matlab mein expand kiya jaata hai taaki aap ek compliance signal seconds mein confirm kar sakein. Ek Build mode aapko dropdowns se ek test bid ya ek QA fixture ke liye ek correct string assemble karne deta hai. Sab kuch aapke device par parse hota hai, isliye real user signals kabhi browser se bahar nahi jaate.
Features
- 4-character IAB US Privacy (CCPA) string ko version, notice, opt-out, aur LSPA fields mein decode karta hai
- Har Y / N / - flag ko raw characters ke bajaye plain language mein explain karta hai
- Ek opted-out-of-sale signal ko ek nazar mein flag karta hai taaki aap use downstream honor kar sakein
- Length, ek numeric version character, aur har flag position validate karta hai
- Clear, position-specific errors jab ek character Y, N, ya ek dash na ho
- Build mode simple dropdowns se ek correct us_privacy string assemble karta hai
- Ek click ek built string ko wapas Decode mein bhejta hai taaki aap verify karein ki yeh round-trip karta hai
- Poori tarah aapke browser mein chalta hai — koi us_privacy value kabhi upload nahi hoti
US Privacy String Decoder kaise use karein
- us_privacy value ko ek OpenRTB regs.ext.us_privacy field, ek __uspapi callback, ya usprivacy cookie se copy karein
- Use Decode mein paste karein, ya 1YNN load karne ke liye Sample click karein
- version aur notice, opt-out-of-sale, aur LSPA flags ka plain-language matlab padhein
- Dropdowns se ek test string assemble karne aur use copy karne ke liye Build par switch karein
Example
Input
1YNN
Output
version: 1
Notice/opt-out opportunity: Y (provided)
Opt-Out of Sale: N (has not opted out)
LSPA: N (not under the agreement)
1YNN: notice diya gaya, user ne opt out nahi kiya, aur publisher LSPA ke under nahi hai.
Common errors aur troubleshooting
- Decoder kehta hai string 4 characters ki nahi hai. — Ek us_privacy value hamesha bilkul chaar characters ki hoti hai: version + Notice + Opt-Out of Sale + LSPA. Sirf raw value paste karein bina quotes, URL-encoding, ya surrounding JSON ke.
- Aapne lowercase y ya n enter kiya aur yeh reject ho gaya. — Flags uppercase Y ya N hain, ya not applicable ke liye ek dash (-). Character ko uppercase mein re-enter karein; specification lowercase flags use nahi karta.
- Aap unsure hain ki ek position mein ek dash ka kya matlab hai. — Ek dash ka matlab hai signal not applicable hai — jaise user California ke bahar hai ya CCPA apply nahi hota — isliye us field ke liye koi notice ya opt-out value set nahi hui.
- Aapne expect kiya ki 1--- ka matlab hai user ne opt out kiya. — 1--- ka matlab hai har flag not-applicable hai, isliye koi opt-out nahi hai. Ek explicit opt-out of sale teesri position mein value Y hai, jaise 1YYN.
Aksar pooche jaane wale sawaal
- Ek US Privacy string jaise 1YNN ka kya matlab hai?
- Har character ek field hai. 1 spec version hai, Y ka matlab explicit notice aur opt out karne ka mauka diya gaya, pehla N ka matlab user ne apne data ki sale se opt out nahi kiya, aur doosra N ka matlab publisher IAB Limited Service Provider Agreement ke under operate nahi kar raha.
- String mein N aur ek dash mein kya farak hai?
- N ek explicit 'no' hai — jaise user ne opt out nahi kiya. Ek dash (-) ka matlab field not applicable hai aur koi signal set nahi hua, jaise jab request CCPA ke scope ke bahar hai. Isliye 1--- koi notice ya opt-out determination bilkul carry nahi karta.
- Main paste karne ke liye us_privacy value kahan dhoondhoon?
- Yeh ek OpenRTB bid request mein regs.ext.us_privacy ke roop mein aati hai, USPAPI __uspapi('getUSPData', ...) call se return hoti hai, aur usprivacy cookie mein store hoti hai. In mein se koi bhi 4-character value copy karke decoder mein paste karein.
- Chauthi position mein LSPA flag kya hai?
- Yeh record karta hai ki publisher ne IAB Limited Service Provider Agreement sign kiya, jo govern karta hai ki downstream partners data kaise process kar sakte hain. Y ka matlab woh signatory hain, N ka matlab nahi hain, aur ek dash ka matlab signal set nahi hua.
- Kya yeh tool ek us_privacy string decode ke saath build bhi kar sakta hai?
- Haan. Build mode aapko notice, opt-out-of-sale, aur LSPA fields ke liye Yes, No, ya Not-applicable pick karne deta hai aur ek version-1 string assemble karta hai jise aap ek test bid request ya QA fixture mein copy kar sakein, phir dobara decode karke confirm karein.
- Kya US Privacy string newer GPP string ke same hai?
- Nahi. US Privacy string purana CCPA-era signal hai; IAB Global Privacy Platform (GPP) successor hai jo US state sections aur TCF data ko ek string mein carry karta hai. Agar aapke paas ek GPP string hai, toh iske bajaye GPP decoder use karein.
Related tools
Saare ArrayKit tools