The California Consumer Privacy Act (“CCPA”) was enacted in early
2018 as a political compromise to stave off a poorly drafted, and
plaintiff’s friendly ballot initiative. Although the CCPA is scheduled
to go into force in early 2020, there is a great deal of confusion
regarding the requirements of the CCPA, including the degree to which it
aligns with other privacy regulations such as the European General Data
Protection Regulation (“GDPR”).
Q. Is an IP address considered “personal information” under the CCPA?
Personal information is defined by the CCPA as “information that identifies, relates to, describes, is capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular consumer or household.” While the Act provides a list of examples of personal information – which explicitly includes “Internet Protocol Address” – it qualifies the examples by stating that they only fall within the definition of personal information if they identify, relate to, describe, are “capable of being associated with,” or “could be reasonably be linked” with a particular person.
In order to determine whether an IP address is linked to a person, it
is important to understand what an IP address represents. Computers
that access the internet are assigned either a static or a dynamic
Internet Protocol (“IP”) address. A static IP address does not change
over time (i.e., it is dedicated to a particular computer to
that network or user). A dynamic IP address is assigned by a network
when a computer connects and, thus, changes over time (e.g., each time that the user reconnects to the network).
When examining whether a static or a dynamic IP address constitutes personal information, California courts may look to how European regulators viewed IP addresses in the context of the European GDPR’s definition of “personal data” which is substantially similar to the CCPA’s definition of “personal information.” The Article 29 Working Party took the position that because static IP addresses do not change, and IP addresses can be used to identify the computer (or user), “[t]he possibility exists in many cases . . . of linking the user’s IP address to other personal data . . . that identify him/her, especially if use is made of invisible processing means to collect additional data on the user (for instance, using cookies containing a unique identifier)….” The Working Party further recognized that because of the nature of dynamic IP addresses in some cases “a third party can get to know the dynamic IP address of a user but not be able to link it to other data concerning this person that would make his/her identification possible.”
Often we need to check for reference or to clear doubt what we know about Adobe Analytics. So I manage to maintain reference list in Excel for my personal use, today I thought to share this list on my blog that others can take benefit out of it too. Some of them are now outdated due to new advances in Adobe Analytics. I tried my best to give credit to actual author of the blog/article, even I tried to keep this list in order as much as possible and will keep on updating it as I come across other good reference links. Feel free to share your feedback or share the link which you want me to add in this list or do let me know if you have any questions.
For the purposes of this conversation, I’ll use the following definitions:
Native apps are built for a specific platform with the platform SDK, tools and languages, typically provided by the platform vendor (e.g. xCode/Objective-C for iOS, Eclipse/Java for Android, Visual Studio/C# for Windows Phone).
Mobile Web apps are server-side apps, built with any server-side technology (PHP, Node.js, ASP.NET) that render HTML that has been styled so that it renders well on a device form factor.
Hybrid apps are a great option for you if you:
Want to target multiple mobile platforms
Want to take advantage of device capabilities like geolocation, accelerometer or the camera
Want the app to be useable when the device is offline
Don’t need the advanced graphics performance that you can only get from a native app.
Hybrid apps are built with web technologies which means there are millions of web developers who already have the base skill set to build mobile apps.
Adobe Analytics tracking can be enabled for Hybrid app by creating 2 web property in Adobe Launch
Drastically reduced the seven-day expiry cap to one day. Released April 24, 2019.
the impact of ITP 2.1, ITP 2.2, and future ITP releases, complete the following
the Experience Cloud ID (ECID) library to your pages.
The ECID library
enables the people identification framework for Experience Cloud Core
solutions. The ECID library allows you to identify same site visitors and their
data in different Experience Cloud solutions by assigning persistent and unique
identifiers. The ECID library will be updated frequently to help you mitigate
any ITP-related changes that impact your implementation.
2. Use Adobe’s CNAME and Enroll in Adobe Analytics’ Managed Certificate Program.
the ECID library 4.3.0+, you can leverage Adobe Analytics’ CNAME and Managed
Certificate Program. This program lets you implement a first-party certificate
for first-party cookies at no charge. Leveraging CNAME will help customers
mitigate the impact of ITP 2.1 and ITP 2.2.
We will use XAMPP in this example.
XAMPP is a very easy to install Apache Distribution of Linux, Solaris, Windows,
and Mac OS X. The package includes the Apache web server, MySQL, PHP, Perl, an
FTP server and phpMyAdmin. With that, you can have fun with your own
website/scripting experiments in future with XAMPP on your machine.
you can choose to install any popular package such as LAMP, WAMP, MAMP etc.)
Install with default settings. Just notice the directory where it’s getting installed (e.g. C:\XAMPP)
After install, open the “XAMPP Control” app in your computer. Then start “Apache”:
Apache server should start with default ports: 80/443:
That’s your local web-server switched On!
Troubleshooting:If Apache could not start on default ports,
probably something (e.g. IIS, Skype etc.) was blocking/using the default ports.
Consider changing the ports configured for Apache (try using some other ports e.g. 88 and 488). You can do that by clicking on “Config” and then editing and saving the files: httpd.conf and httpd-ssl.conf:
In those configuration files, find the line that mentions Listening on the ports (80 in httpd.conf and 443 in httpd-ssl.conf) and change those numbers (you can try 88 and 444 respectively).
save those two configuration files. Re-start with Step#3 (Starting Apache)
After a successful start of Apache, in your browser,
type “localhost” as the URL and proceed.
If you had used a port other than the default, you will need to add the port
number to the URL separated by colon e.g. “localhost:88“
You should be redirected to XAMPP Dashboard and see a welcome page like this:
(with default settings)
(with HTTP port changed to 88)
Locate your XAMPP install directory in your computer. You should see a sub-directory “htdocs“:
Your websites and web pages usually reside in that
sub-directory. We will come back to this during the Lab.