Qualified Solicitor. Writer at TermsFeed.
On this page
- 1. What is CalOPPA
- 2. How to Comply with CalOPPA
- 2.1.1. What Personal Information You Collect and How/Why
- 2.1.2. How/If You Share Personal Information
- 2.1.3. How Users Can Review and Update Their Information
- 2.1.4. How You Respond to "Do Not track" Requests
- 5. All US Privacy Laws
The state of privacy legislation in the United States is pretty shocking: there's no overarching federal data privacy law at all.
The United States lags far behind Europe and the UK, and even behind many up-and-coming economies in Southeast Asia.
The primary data privacy law in the US that applies generally, rather than to a specific privacy field such as health or children's privacy, is a state law rather than a federal law known as the California Online Privacy Protection Act 2003 (CalOPPA).
This guide will cover what CalOPPA is, what the law covers, who it applies to, and how to comply.
At Step 1, select the Website option or App option or both.
Answer some questions about your website or app.
Answer some questions about your business.
What is CalOPPA
- What types of personal information is collected and the third parties this collected personal information may be shared with
- How users can request changes to any of the personally identifiable information that was collected
- How the operator responds to the "Do Not Track" requests of users
- Whether other third parties may collect personally identifiable information about users through the operator's service
How to Comply with CalOPPA
First, ask if CalOPPA applies to your business. CalOPPA applies to operators of commercial websites or online services that collect "personally identifiable information through the Internet about individual consumers residing in California."
In 2012, the California Attorney General issued an agreement with mobile app providers that stated that CalOPPA also applies to mobile apps.
"Personally Identifiable Information" for the purposes of CalOPPA includes but is not at all limited to:
- First and last names
- Home or physical street addresses
- An email address
- A telephone number
- A Social Security number
- Or any other information that permits a specific individual to be contacted physically or online
- Height, weight, hair color
What Personal Information You Collect and How/Why
Take a look back at the list of "personally identifiable information" above and check whether your website/mobile app collects any of those or any other information that could possibly be used to identify an individual. If you have users signing up for accounts, making purchases on your e-commerce store or if you use third-party services such as (Google Analytics, you collect personally identifiable information.
For example, you might want to say "If you create a user account, we will collect your contact details. If you purchase an item through our store, we will ask you to provide your physical address and credit card details so that we can process your payment."
Here's an example of a clause that discloses this information in an easy-to-understand way:
How/If You Share Personal Information
This clause addresses everything from working with third parties and conducting marketing campaigns to complying with laws and being involved in a transfer or sale of the business.
How Users Can Review and Update Their Information
This can be a simple instruction such as "You can login to your user profile and correct, amend, or delete information about yourself."
Or, if you don't have that type of user account/interface, be sure to include your contact details where users can reach out and request to have their information changed.
For example: "Contact us at [X] phone number or [X] email address to find out what information we have collected about you, and to request any changes."
Here's a clause that includes a link to account settings where users can access and adjust their personal information, as well as an email address where users can reach out to request that the company make the adjustments on behalf of the user:
How You Respond to "Do Not track" Requests
In this clause you need to outline whether or not you honor Do Not Track requests. You aren't required to honor them, but you are required to disclose whether or not you do. This clause can be a simple, basic statement acknowledging what you plan to do, such as this one:
Also include a clause that lets users know you may update your Policy from time to time and how you'll alert them of any material changes.
[...] being written in capital letters equal to or greater in size than the surrounding text or by being displayed in a type, font or color that contrasts with the surrounding text of the same size or must be otherwise distinguishable from surrounding text on the homepage.
In mobile apps, you can add a link within a menu, such as an About, Settings or Legal menu:
As long as your Policy can be accessed at any time, isn't hidden or in an unintuitive location, and actually includes the word "Privacy," you can add it to your website or mobile app in the way that best works with the layout and design.
In the example above, this leaves no doubt about whether the link has been clear and conspicuous enough for the user. It's clearly distinguished from other text.
In the case of mobile apps, a clickwrap method can be implemented by way of an "I agree" button or checkbox whenever users first open the app or whenever they sign-up for an account through the app.
Here's a great example from Samsung of how to implement a good clickwrap method in mobile apps:
If you collect personal information from residents of the state of California, you'll need to:
- Include CalOPPA-specific requirements like a DNT clause and effective date
- Use clickwrap methods to get users to agree to your Policy
All US Privacy Laws
Want to read more about privacy laws in the USA? Start here:
|COPPA: Children's Online Privacy Protection Act||Federal law that protects the privacy of children under 13 years of age when online or using a mobile app.|
|HIPAA: Health Insurance Portability and Accountability Act||Federal law that protects the privacy of health information of individuals.|
|California CCPA: California's Consumer Privacy Act||California law that gives consumers many privacy rights while putting transparency obligations on businesses.|
|California CPRA: California's Privacy Rights Act||California law that expands the CCPA and gives consumers additional rights.|
|Virginia VCDPA: Virginia's Consumer Data Protection Act||Virginia law that allows users to opt out of the sale of their personal data.|
|Maryland PIPA: Maryland's Personal Information Protection Act||Maryland law that requires businesses to keep personal information private and secured.|
|Utah UCPA: Utah's Consumer Privacy Act||Utah law that provides a range of consumer privacy rights, including the right to data portability.|
|Connecticut CTDPA: Connecticut's Personal Data Privacy and Online Monitoring||Connecticut law that places transparency requirements on businesses while granting consumers rights over their personal data.|
|Colorado CPA: Colorado's Privacy Act||Colorado law that grants privacy rights to consumers while dictating how businesses can collect and process personal data.|
|Florida FPPA: Florida's Privacy Protection Act||Florida law that lets consumers control how their personal data is used, while requiring businesses to be more transparent.|