Skip to content

Commit b4fc1ba

Browse files
jaredmoscowjaredmoscow
authored
Merge pull request #107 from jaredmoscow/jaredmoscow-statesections-1
GPP Extensions: FL, MT, OR, TX State Sections for Public Comment
2 parents 31e01c1 + 1ee7970 commit b4fc1ba

9 files changed

Lines changed: 934 additions & 0 deletions

‎Sections/Section Information.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,33 @@ Each section represents a unique privacy signal, usually a unique jurisdiction.
8787
</td>
8888
</td>
8989
</tr>
90+
<tr>
91+
<td><code>13</code></td>
92+
<td>usfl</td>
93+
<td>US - Florida section </td>
94+
</td>
95+
</td>
96+
<tr>
97+
<td><code>14</code></td>
98+
<td>usmt</td>
99+
<td>US - Montana section </td>
100+
</td>
101+
</td>
102+
</tr>
103+
<tr>
104+
<td><code>15</code></td>
105+
<td>usor</td>
106+
<td>US - Oregon section </td>
107+
</td>
108+
</td>
109+
</tr>
110+
<tr>
111+
<td><code>16</code></td>
112+
<td>ustx</td>
113+
<td>US - Texas section </td>
114+
</td>
115+
</td>
116+
</tr>
90117
</table>
91118

92119
>**Note:** In order to make it simple to distinguish a GPP string from the existing IAB Europe TCF v2 TC String the first space in the header should be the version. This would allow current implementations to more easily understand and adapt to a GPP string. If the reader of a string finds “C” as the first character this indicates the string is IAB Europe’s TCF v2.0 ("2" in bits corresponds to letter "C" in base64). If the reader of a string finds a “D” as the first character this indicates the string is GPP ("3" in bits corresponds to letter "D" in base64).

‎Sections/US-States/FL/GPP Extension: IAB Privacy’s Florida Privacy Technical Specification.md‎

Lines changed: 190 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,190 @@
1+
<h1 id="gpp-extension-iab-privacy-s-florida-privacy-technical-specification">GPP Extension: IAB Privacy’s Florida Privacy Technical Specification</h1>
2+
<h2 id="about-this-document">About this document</h2>
3+
<p>The global standard <a href="https://github.com/InteractiveAdvertisingBureau/Global-Privacy-Platform">GPP</a> defines a way for local standards to &quot;plug-in&quot; into the existing mechanics defined by GPP and the <a href="https://github.com/InteractiveAdvertisingBureau/Global-Privacy-Platform/blob/main/Core/CMP%20API%20Specification.md">GPP client side API</a>. This document outlines the technical specification for using the Florida section of the GPP specifications in accordance with the IAB Privacy Multi-State Privacy Agreement legal requirements, applicable to both Signatories and non-Signatories of the MSPA.</p>
4+
5+
<h3>Version History&nbsp;</h3>
6+
<div>
7+
<table>
8+
<tbody>
9+
<tr>
10+
<td><strong>Date</strong></td>
11+
<td><strong>Version</strong></td>
12+
<td><strong>Comments</strong></td>
13+
</tr>
14+
15+
<tr>
16+
<td>May 2024</td>
17+
<td>1.0</td>
18+
<td>Version 1.0 released</td>
19+
</tr>
20+
</tbody>
21+
</table>
22+
</div>
23+
24+
<h2>Florida Section</h2>
25+
<p>The Florida Privacy String consists of the following components. Users of the spec should employ the Florida Privacy String if they have determined the Florida Digital Bill of Rights, Fla. Stat. § 501.701 et seq., may apply to their processing or their partners’ processing of a consumer's personal data.</p>
26+
<h3>Summary</h3>
27+
<div>
28+
<table>
29+
<tbody>
30+
<tr>
31+
<td>
32+
<strong>Type</strong>
33+
</td>
34+
<td>
35+
<strong>Value</strong>
36+
</td>
37+
<td>
38+
<strong>Description</strong>
39+
</td>
40+
</tr>
41+
<tr>
42+
<td>GPP Section ID</td>
43+
<td>13</td>
44+
<td>The Florida Section is registered as Section ID 13 under the GPP.</td>
45+
</tr>
46+
<tr>
47+
<td>Client side API prefix</td>
48+
<td>usfl</td>
49+
<td>The Florida Privacy Section is registered with client side API prefix “usfl” in the GPP Client Side API.</td>
50+
</tr>
51+
</tbody>
52+
</table>
53+
</div>
54+
<h3>Section encoding</h3>
55+
<h4>Core Segment</h4>
56+
<p>The core sub-section must always be present. Where terms are capitalized in the ‘description’ field they are defined terms in Fla. Stat. § 501.702. It consists of the following fields:</p>
57+
<div>
58+
<table>
59+
<thead>
60+
<tr>
61+
<th>
62+
<p>Field name</p>
63+
</th>
64+
<th>
65+
<p>GPP Field Type</p>
66+
</th>
67+
<th>
68+
<p>Description</p>
69+
</th>
70+
</tr>
71+
</thead>
72+
<tbody>
73+
<tr>
74+
<td>
75+
<span style="color:rgb(36, 41, 47);">Version</span>
76+
</td>
77+
<td>Int(6)</td>
78+
<td>
79+
<span style="color:rgb(36, 41, 47);">The version of this section specification used to encode the string.</span>
80+
</td>
81+
</tr>
82+
<tr>
83+
<td>
84+
<span style="color:rgb(36, 41, 47);">ProcessingNotice</span>
85+
</td>
86+
<td>Int(2)</td>
87+
<td>
88+
<span style="color:rgb(36, 41, 47);">Notice of the Processing of Personal Data.</span><p></p><code>0</code> = Not Applicable,
89+
<span style="color:rgb(36, 41, 47);">The Controller does not Process Personal Data</span><p></p><code>1</code> = Yes, notice was provided<p></p><code>2</code> = No, notice was not provided</td>
90+
</tr>
91+
<tr>
92+
<td>
93+
<span style="color:rgb(36, 41, 47);">SaleOptOutNotice</span>
94+
</td>
95+
<td>Int(2)</td>
96+
<td>
97+
<span style="color:rgb(36, 41, 47);">Notice of the Opportunity to Opt Out of the Sale of the Consumer’s Personal Data&nbsp;</span><p></p><code>0</code> = Not Applicable<span style="color:rgb(36, 41, 47);">,
98+
</span>The
99+
<span style="color:rgb(36, 41, 47);">Controller does not Sell Personal Data</span>
100+
<span style="color:rgb(36, 41, 47);"><p></p><code>1</code> = Yes, notice was provided</span>
101+
<span style="color:rgb(36, 41, 47);"><p></p><code>2</code> = No, notice was not provided</span>
102+
</td>
103+
</tr>
104+
<tr>
105+
<td>
106+
<span style="color:rgb(36, 41, 47);">TargetedAdvertisingOptOutNotice</span>
107+
</td>
108+
<td>Int(2)</td>
109+
<td>
110+
<span style="color:rgb(36, 41, 47);">Notice of the Opportunity to Opt Out of Processing of the Consumer’s Personal Data for Targeted Advertising</span><p></p><code>0</code> = Not Applicable<span style="color:rgb(36, 41, 47);">, the Controller does not Process Personal Data for Targeted Advertising</span>
111+
<span style="color:rgb(36, 41, 47);"><p></p><code>1</code> = Yes, notice was provided</span>
112+
<span style="color:rgb(36, 41, 47);"><p></p><code>2</code> = No, notice was not provided</span>
113+
</td>
114+
</tr>
115+
<tr>
116+
<td>
117+
<span style="color:rgb(36, 41, 47);">SaleOptOut</span>
118+
</td>
119+
<td>Int(2)</td>
120+
<td>
121+
<span style="color:rgb(36, 41, 47);">Opt-Out of the Sale of the Consumer’s Personal Data</span><p></p><code>0</code> = Not Applicable, SaleOptOutNotice value was not applicable or no notice was provided<p></p><code>1</code> = Opted Out<p></p><code>2</code> = Did Not Opt Out</td>
122+
</tr>
123+
<tr>
124+
<td>
125+
<span style="color:rgb(36, 41, 47);">TargetedAdvertisingOptOut</span>
126+
</td>
127+
<td>Int(2)</td>
128+
<td>
129+
<span style="color:rgb(36, 41, 47);">Opt-Out of Processing the Consumer’s Personal Data for Targeted Advertising</span><p></p><code>0</code> = Not Applicable, TargetedAdvertisingOptOutNotice value was not applicable or no notice was provided<p></p><code>1</code> = Opted Out<p></p><code>2</code> = Did Not Opt Out</td>
130+
</tr>
131+
<tr>
132+
<td>
133+
<span style="color:rgb(36, 41, 47);">SensitiveDataProcessing</span>
134+
</td>
135+
<td>N-Bitfield(2,8)</td>
136+
<td>Two bits for each Data Activity:<p></p><code>0</code> = Not Applicable, the Controller does not Process the specific category of Sensitive Data<p></p><code>1</code> = No Consent <p></p><code>2</code> = Consent&nbsp;<span style="color:rgb(36, 41, 47);"><p></p>(1). Consent to Process the Consumer’s Sensitive Data Consisting of Personal Data Revealing Racial or Ethnic Origin.</span><p></p>
137+
<span style="color:rgb(36, 41, 47);">(2). Consent to Process the Consumer’s Sensitive Data Consisting of Personal Data Revealing Religious Beliefs.</span><p></p>
138+
<span style="color:rgb(36, 41, 47);">(3). Consent to Process the Consumer’s Sensitive Data Consisting of Personal Data Revealing a Mental or Physical Health Diagnosis.</span><p></p>
139+
<span style="color:rgb(36, 41, 47);">(4). Consent to Process the Consumer’s Sensitive Data Consisting of Personal Data Revealing Sexual Orientation.</span><p></p>
140+
<span style="color:rgb(36, 41, 47);">(5). Consent to Process the Consumer’s Sensitive Data Consisting of Personal Data Revealing Citizenship or Immigration Status.</span><p></p>
141+
<span style="color:rgb(36, 41, 47);">(6). Consent to Process the Consumer’s Sensitive Data Consisting of Genetic Data for the Purpose of Uniquely Identifying an Individual.</span><p></p>
142+
<span style="color:rgb(36, 41, 47);">(7). Consent to Process the Consumer’s Sensitive Data Consisting of Biometric Data for the Purpose of Uniquely Identifying an Individual.</span><p></p>
143+
<span style="color:rgb(36, 41, 47);">(8). Consent to Process the Consumer’s Sensitive Data Consisting of Precise Geolocation Data.</span>
144+
</td>
145+
</tr>
146+
<tr>
147+
<td>
148+
<span style="color:rgb(36, 41, 47);">KnownChildSensitiveDataConsents</span>
149+
</td>
150+
<td>N-Bitfield(2,3)</td>
151+
<td>Two bits for each Data Activity:<p></p><code>0</code> = Not Applicable, the Controller does not
152+
<span style="color:rgb(36, 41, 47);">Process Sensitive Data of a known Child</span><p></p><code>1</code> = No Consent <p></p><code>2</code> = Consent&nbsp;<span style="color:rgb(36, 41, 47);"><p></p>(1). Consent to Process Sensitive Data from a Known Child Under the Age of 13.</span><p></p>
153+
<span style="color:rgb(36, 41, 47);">(2). Consent to Process Sensitive Data of Consumers At Least 13 Years of Age but Younger Than 16 Years of Age.</span><p></p>
154+
<span style="color:rgb(36, 41, 47);">(3). Consent to Process the Sensitive Data of Consumers At Least 16 Years of Age but Younger Than 18 Years of Age.</span><p></p>
155+
</td>
156+
</tr>
157+
<tr>
158+
<td>
159+
<span style="color:rgb(36, 41, 47);">AdditionalDataProcessingConsent</span>
160+
</td>
161+
<td>Int(2)</td>
162+
<td>Consent to Processing of the Consumer’s Personal Data that Is Not Reasonably Necessary for nor Compatible with the Disclosed Purpose(s) for which the Consumer’s Personal Data Was Processed<p></p><code>0</code> = Not Applicable, the Controller does not Process Personal Data that is Not Reasonably Necessary for nor Compatible with the Disclosed Purpose(s)<p></p><code>1</code> = Consent <p></p><code>2</code> = No Consent&nbsp;</td>
163+
</tr>
164+
<tr>
165+
<td>
166+
<span style="color:rgb(36, 41, 47);">MspaCoveredTransaction</span>
167+
</td>
168+
<td>Int(2)</td>
169+
<td>
170+
<span style="color:rgb(36, 41, 47);">Publisher or Advertiser, as applicable, is a signatory to the IAB Multi-State Privacy Agreement (MSPA), as may be amended from time to time, and declares that the transaction is a “Covered Transaction” as defined in the MSPA.&nbsp;</span><p></p><code>1</code> = Yes<p></p><code>2</code> = No</td>
171+
</tr>
172+
<tr>
173+
<td>
174+
<span style="color:rgb(36, 41, 47);">MspaOptOutOptionMode</span>
175+
</td>
176+
<td>Int(2)</td>
177+
<td>
178+
<span style="color:rgb(36, 41, 47);">Publisher or Advertiser, as applicable, has enabled “Opt-Out Option Mode” for the “Covered Transaction,” as such terms are defined in the MSPA.</span><p></p><code>0</code> = Not Applicable<p></p><code>1</code> = Yes<p></p><code>2</code> = No</td>
179+
</tr>
180+
<tr>
181+
<td>
182+
<span style="color:rgb(36, 41, 47);">MspaServiceProviderMode</span>
183+
</td>
184+
<td>Int(2)</td>
185+
<td>
186+
<span style="color:rgb(36, 41, 47);">Publisher or Advertiser, as applicable, has enabled “Service Provider Mode” for the “Covered Transaction,” as such terms are defined in the MSPA.</span><p></p><code>0</code> = Not Applicable<p></p><code>1</code> = Yes<p></p><code>2</code> = No</td>
187+
</tr>
188+
</tbody>
189+
</table>
190+
</div>

‎Sections/US-States/FL/README.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
# IAB Privacy’s Florida Privacy Technical Specification
2+
3+
4+
5+
Contained in this directory are technical specifications for Florida privacy strings to support Florida Digital Bill of Rights compliance.

0 commit comments

Comments
 (0)