A brokerage website privacy policy is required in California once your site has a contact form: you need a privacy policy, and the law says where it goes, on a page a visitor can reach from your homepage. A form that asks a home buyer, seller or renter for a name or an email address is enough to trigger it. A site that collects nothing is in a different position, and so, possibly, is a site whose only visitors are businesses (see below).
We opened the homepages of 43 Sacramento-area brokerage sites on 2026-11-14 and looked for the link. 19 link a policy of their own. 21 do not, and 6 of those have a form that asks for a name or an email. Three sites would not load for us. A few of the sites also do other work, such as loans and property management.
We build websites for brokerages, so weigh this accordingly. This is not legal advice. It is what the statute says in plain words, and what we found.
The rule, in one paragraph
California's online privacy law is Business and Professions Code 22575. It says the operator of a commercial website that collects personally identifiable information from California residents "shall conspicuously post its privacy policy on its Web site." Section 22577 defines the information: "A first and last name," "An e-mail address," "A telephone number," and a home address are all on the list. So a contact form with a name and an email box collects it. So does a "get my home value" form.
There is a grace period. The statute says you are in violation "only if the operator fails to post its policy within 30 days after being notified of noncompliance." The Attorney General's office used that in 2012, when it sent letters to about 100 app companies and "gave 30 days to post a conspicuous privacy policy". A grace period is not a reason to wait. It means a missing policy is cheap to fix and a bad idea to ignore.
One limit to know about. The law protects a "consumer," which 22577 defines as someone who seeks goods, services, money or credit "for personal, family, or household purposes." A residential brokerage is plainly inside that. A commercial brokerage whose forms only ever hear from business owners and investors may be outside it, and that is a question for a lawyer. A policy costs little, and commercial sites also hear from individuals, so we would post one either way.
What a brokerage website privacy policy has to say
Section 22575(b) lists what the policy "shall do." In plain words:
- Say what you collect and who gets it. The categories of information (name, email, phone, the property you asked about) and the categories of outside companies it may be shared with (your form tool, your email service, your CRM).
- Say how to change it, if you let people review or correct what you hold.
- Say how you will tell people the policy changed.
- Show the effective date. The statute says to "Identify its effective date."
- Say how you respond to "do not track" signals from a browser, if you track people across sites.
- Say whether other parties may collect information about a visitor's activity "over time and across different Web sites" while they use yours. A site with an advertising pixel or a map or video embed usually has that.
One more rule catches the copy-and-paste policy. Section 22576 makes it a violation to fail to follow your own posted policy, "knowingly and willfully" or "negligently and materially." A policy that promises something your site does not do is worse than a short honest one.
The Attorney General published a guide in May 2014, Making Your Privacy Practices Public. It is older and it is advice, not law. Its useful points: describe how you respond to "do not track" "within your privacy policy instead of providing a link to another website," say what you collect, how you use it and how long you keep it, and write in plain language.
What 40 sites show
Homepage links a privacy policy of the site's own business
Links something that is not that (see below)
No privacy link anywhere on the homepage
Could not be read (a bot check, and two that came up blank)
| What we found on 2026-11-14 (43 sites) | Sites |
|---|---|
| Homepage links a privacy policy of the site's own business | 19 |
| Links something that is not that (see below) | 3 |
| No privacy link anywhere on the homepage | 18 |
| Could not be read (a bot check, and two that came up blank) | 3 |
So 21 of the 40 we could read have no policy of their own. Of those 21, six have a form that asks for a name, an email address or both, and they are where the rule above most plainly applies. Some are commercial sites, and whether their visitors count as "consumers" is the question raised above. The others have a search box, a phone number or a plain page with nothing to type into, which is a different position.
The three that link something else:
- One policy page opens "Welcome to Estatify!", the name of another company, in terms-and-conditions wording.
- One page titled "Privacy Policy" calls itself "A legal disclaimer."
- One has a "Privacy Policy" link only inside the line "This site is protected by reCAPTCHA and the Google Privacy Policy," and it opens Google's policy, not theirs.
The 19 that have one
A link is the start. We then read the 19 policies:
- 12 name California and 7 do not.
- 12 carry a real calendar date and 7 do not. Without one you cannot satisfy item 4. The oldest dated policy says "last updated on April 15, 2015." Two of the undated ones promise an "updated" or "revised" effective date without ever showing one.
- Length runs from about 200 words to over 4,000. Short is fine when the site collects little. A 216-word page that does not name California or any date is not doing the job the statute lists.
We counted what a policy says, not whether it is true. Whether a site's words match what its tools do is exactly the 22576 question, and it takes a look under the hood to answer.
Do I also need the CCPA?
Probably not, and you should know why. The California Consumer Privacy Act, in Civil Code 1798.140, covers a for-profit business that does business in California only if it meets one of three tests: gross revenue above $25,000,000 "as adjusted," buying, selling or sharing the personal information of 100,000 or more consumers or households a year, or getting 50 percent or more of revenue from selling or sharing it. The California Privacy Protection Agency adjusted the revenue figure to $26,625,000 on 2025-01-01, and the next adjustment is due 2027-01-01.
A small brokerage that does not sell its leads and does not run a large advertising audience meets none of the three. The online privacy law above applies anyway, because it has no size test. If you are close to a line, ask a lawyer.
What to put on your site
- Write the policy from your own site. List every box on every form, every tool that gets the answers (the form service, your email, your CRM, a scheduling tool), and every analytics or advertising script.
- Cover the six items above, in short sections with plain headings. Name California.
- Put the date at the top, and change it when the policy changes.
- Say how you respond to "do not track." One honest sentence is enough, such as "We do not respond to these signals" if that is true, or what you really do.
- Link it from the footer of every page, with the word "privacy" in the link text, and again next to the contact form.
- Check it twice a year, or whenever you add a tool. A new pixel makes an old policy wrong. We covered the tracking side in who is actually being sued over website tracking.
A brokerage contact page has other jobs too. We looked at those in what a brokerage contact page needs, and the wider checklist is in what a brokerage website needs.
Our own site
flarebuilt.com links its privacy policy from the footer of every page. It names California residents' rights, lists the kinds of vendors we use by role, and shows an effective date of June 20, 2026. Our analytics does not use tracking cookies.
The gap: the policy has no sentence on how we respond to browser "do not track" signals (we checked the policy text in our code for the phrase and for the word "signal"). Item 5 applies only to a site that collects information across sites over time, and ours says it does not use cross-site tracking, so this is not a legal gap. It is a missing plain sentence that the Attorney General's guide recommends, and one we should add.
What we would build for a brokerage
A site where the privacy policy is written from the real form and tools, linked from every footer and beside the form, with a date at the top. It is a small part of a real estate website and it is the part most often left as a template.
How we did this, so you can check it
- The sites. 43 Sacramento-area California brokerage company websites, the same list as our earlier audits. A few do other work (loans, property management, a charity), which we noted. We named a site only when we had to to describe a fault, and then only as "one site."
- The look. On 2026-11-14 we loaded every homepage in a desktop Chrome browser and listed every link with "privacy" in its address or text, then repeated it by script on the raw page and scrolled to the footer of every site with no link. We opened each policy that loaded and searched it for "California" and a calendar date, and read the short and odd ones by eye. We read form boxes on the sites with no link.
- The law. Business and Professions Code 22575, 22576 and 22577 and Civil Code 1798.140 on the Legislature's own site, the California Privacy Protection Agency's threshold page, and the Attorney General's 2014 press release, all opened on 2026-11-14. We did not research penalties.
- Limits. 43 sites, one region, one day. A policy reachable only after a click on a banner, or from a page other than the homepage, would not be counted as a link. Three sites would not load, so we count none of them. Two sites have expired security certificates, and we read them in a way that skipped the warning. We did not check whether any policy's words match what its site really does.
