Multifamily
Apartment & HOA Building Cameras
Camera count, placement, pixel density, storage and the privacy limits that apply to shared property.
Open page
A California homeowners association with private roads may install and operate automated license plate recognition cameras; there is no expectation of privacy on a roadway, no municipal permit for cameras on private property. But the moment the cameras turn plate images into searchable text, the association becomes an “ALPR operator” under Civil Code § 1798.90.5 and owes three things: reasonable security for the data, an access log, and a written usage and privacy policy posted publicly. Skip the policy and the exposure is $2,500 in liquidated damages per violation, plus attorney’s fees — and after Bartholomew v. Parking Concepts (2026) a plaintiff does not have to show the data was ever misused. Separately, most systems sold to HOAs fail on physics rather than law: a plate needs roughly 100–150 pixels across its width and a camera angle under 30°, and a general-purpose dome at the gate delivers neither.
Free on-site assessment across Los Angeles, Orange and Ventura counties. C-10 CSLB #1043428 · BSIS ACO 7755.
Text (805) 517-4668 Call (805) 517-4668 Email usIt is legal, and the boards that get into trouble are almost never the ones that asked whether it was. Adams Stirling, the firm behind the Davis-Stirling reference California managers use, puts it plainly: because there is no expectation of privacy on a roadway, associations with private roads may install and operate automated license plate readers, municipalities do not regulate them, and cameras on private property do not require a permit.
What California does regulate is the database. Civil Code § 1798.90.5(d) defines an ALPR system as “a searchable computerized database resulting from the operation of one or more mobile or fixed cameras combined with computer algorithms to read and convert images of registration plates and the characters they contain into computer-readable data.” An “ALPR operator” is anyone who operates one, and “person” is defined to include an association or corporation. Your HOA qualifies.
That distinction matters more than most vendors explain. A camera that simply records video of the entrance is a security camera, governed by the ordinary California recording rules. The instant the system converts plates into searchable text — which is the entire point of buying one — three duties attach under Title 1.81.23:
The enforcement clause is the part boards should read twice. Civil Code § 1798.90.54 lets an individual harmed by a violation sue for actual damages “but not less than liquidated damages in the amount of two thousand five hundred dollars ($2,500),” plus punitive damages on proof of willful or reckless disregard, plus reasonable attorney’s fees and costs.
In 2026 the Court of Appeal decided Bartholomew v. Parking Concepts, Inc., in which a customer alleged a parking operator had failed to implement and publish an ALPR policy. The trial court dismissed for want of harm. The Court of Appeal reversed, holding that the missing policy was itself the harm: no data breach, no misuse, no measurable monetary loss required, and no exception for small deployments or for people who could have avoided the scan. The court did keep a limit — a plaintiff still needs “harm beyond a mere statutory violation” — and expressly left open whether an incomplete policy, or one published but not implemented, is actionable. Commentators reading the decision have flagged HOAs, retailers and parking operators as the exposed categories.
Two practical consequences. First, the policy is drafted and published before the cameras are energized, not after the first incident. Second, buying the system as a service does not move the duty: read the vendor agreement and see who it says is responsible for ALPR compliance, because the statute follows the operator, not the software company.
These are the minimum contents in § 1798.90.51(b)(2). Your association’s counsel writes the document; what an installer owes you is the technical half — the retention days the storage is actually sized for, who holds the credentials, and where the recorder physically lives — so the policy describes the system you really have.
| What the statute requires | What it means for an HOA board |
|---|---|
| (A) Authorized purposes for using the system and collecting the data | Write the narrow version: investigating crimes and incidents on association property, and gate access for vehicles on the resident list. “General community safety” authorizes casual browsing, which is exactly the misuse pattern that produces plaintiffs. |
| (B) Who may use it job titles or designations, plus training requirements | Usually the community manager and named board officers — not “the board” as a body, and not the gate guard by default. The statute also makes you state the training those people must have, which means your management contract has to say who provides it. |
| (C) Monitoring for security and compliance | Who reviews the § 1798.90.52 access log, how often, and what happens when a search has no case behind it. Davis-Stirling’s guidance is blunt about the point of this: restrict searches to specific cases and record who searched and when. |
| (D) Sale, sharing or transfer purposes, process and restrictions | Sharing with law enforcement is optional for a private association. Whatever you decide — on request with a report number, on subpoena only, or never — the policy has to state the process, and the answer belongs to the members, not to a vendor default. |
| (E) The official custodian or owner of the system | A named title responsible for implementing the section. Leaving this blank is the easiest of the seven failures to prove. |
| (F) Accuracy and error correction | Plate reads are probabilistic: dirty plates, paper dealer plates, motorcycles and trailer-obscured plates all misread. State how a wrong read gets corrected before it becomes a violation letter or a towing decision. |
| (G) Retention and destruction how long, and the process for deciding when to destroy | Pick a number, then size the storage for it. This is where the technical and legal halves meet: a policy that promises 30 days on a recorder that overwrites in nine is a written misstatement of your own practice. |
Boards are usually shown one of two things: a subscription service that puts a solar camera on a pole for an annual fee per camera, or a community-owned system wired back to a recorder the association controls. Both trigger the same statutory duties. They differ on retention, on control, and on what happens in year six.
The retention gap widened sharply this year. On August 13, 2026, Flock Safety announced it was cutting its default plate-data retention from 30 days to one week, with an “Evidence Mode” for preserving specific records in an active investigation. For an HOA that is not a footnote: a garage burglary noticed on the twentieth of the month is, under a seven-day default, already gone. An owned recorder is sized for whatever retention you write into your policy.
| Question a board should ask | Community-owned system | Subscription ALPR service |
|---|---|---|
| Who holds the database? | The association, on its own recorder and network. You remain the ALPR operator and owe the policy. | The vendor’s platform. You are still the operator for your own use of it, and you still owe the policy. |
| How long is footage kept? | Whatever the storage is specified for — write the number in the policy and size the drives to it. | The vendor’s default, which can change. Flock’s moved from 30 days to 7 in August 2026. |
| Can it be searched by anyone outside the community? | Only if you build a path for it. Nothing is contributed to a regional database by default. | Depends entirely on the platform’s sharing settings and its agreements — the question that drove several California cities to leave in 2026. |
| What does year six look like? | A capital asset the association owns, with service and eventual replacement. | The same annual fee per camera, subject to renewal pricing. Read the term, renewal and termination clauses before signing a multi-year deal. |
That last row is not hypothetical. The City of Santa Barbara notified Flock it would not renew when its contract ended on August 23, 2026, and staff recommended replacing the twelve cameras with city-owned units on a closed system whose data “would not be contributed to, or searchable through, a public, regional, or multi-agency license plate database.” A private association is not a police department, but the governance question is identical: who can see the plates of the people who live here, and can the board still answer that question in three years?
Most disappointing plate systems are not badly bought, they are badly aimed. Axis Communications’ license plate capture white paper gives the numbers that decide it, and they are worth quoting to any bidder:
| Design target | The number | Why it decides the job |
|---|---|---|
| Pixels across the plate | 74 px minimum to resolve the characters; most recognition software wants 100–150 px across the full plate width | This, not the camera’s megapixel count, is the specification. It is a function of resolution and how tightly the lens is zoomed on the lane. |
| Angle to the direction of travel | Total angle under 30° | Above it the plate is foreshortened and the software fails. The angle is set by mounting height and how far off the lane centre the camera sits — a decision made on installation day, not in the quote. |
| Sensor resolution | 1 MP for a single lane under ~13 ft wide; 2 MP for two lanes under ~25 ft. Keep it at 2 MP or less when the recognition runs on the camera | More megapixels is actively worse here: bigger frames take longer to analyse and plates get missed in a queue. Cover more lanes with more cameras, not more pixels. |
| Capture distance vs speed | ~13 ft at 6 mph, ~23 ft at 19 mph, ~36 ft at 31 mph | Based on roughly 0.2 s of detection time. A gated entrance where cars slow or stop is the easiest LPR scenario there is — and an open community entrance at 25 mph is a genuinely different design. |
| Shutter time | At ~19 mph: 19.3 ms at a 5° angle, but only 3.4 ms at 30° | Geometry buys you light. Halving the angle roughly doubles the usable infrared range, which is why a well-placed camera outperforms a brighter one. |
| Infrared placement | Plates are retroreflective — they send light straight back to its source | Any separate illuminator must sit right next to the camera or the plate goes dark. A general-purpose camera forced to a 1/500 s shutter also loses roughly half its rated IR reach. |
Three settings follow from the same white paper and are worth writing into the scope: wide dynamic range switched off (it introduces motion artefacts on moving vehicles), maximum gain capped so the retroreflective plate does not blow out to white, and tone mapping reduced so headlight glare is not amplified. A dedicated plate camera ships configured this way. A general dome does not, and the default settings that make a nice picture of the entrance are precisely the settings that lose the plate.
The consequence for a community entrance is that plate cameras are installed in pairs. The recognition camera is zoomed tight, exposed dark and shows little except a legible plate. A second overview camera on the same pole gives the vehicle, the colour, the direction and, at the right height, the driver. Ask any bidder which camera in the schedule is which; if the answer is that one camera does both, the plate is what you will lose.
Reading plates for evidence and opening a gate with a plate are two different projects. The second one is access control: the association is now maintaining a list of vehicles entitled to enter, which means a resident who sells a car, a tenant who moves out and a landscaper whose truck changed all become administrative events. A plate is also a credential you cannot revoke from the vehicle’s side, so most communities that do this keep the plate list for residents and leave visitors on a code, a call box or a one-time credential.
The gate hardware itself carries its own standards, and they are the ones an association is most often found short on after an injury. UL 325 governs the operator, ASTM F2200 the gate, and they are written to work together: where a risk of entrapment exists the operator needs a minimum of two independent means of entrapment protection; the gate must have guard posts, screen mesh, covers over exposed rollers and no opening in the frame larger than 2¼ inches; and warning signs must be posted. If the plate reader is being added to an existing gate, that is the moment to have the gate assessed rather than the moment to skip it.
An ALPR deployment is an operating rule as well as a purchase, and Civil Code § 4360 sets the sequence. The board must give members general notice of the proposed rule change at least 28 days before making it, including the text of the rule and a description of its purpose and effect; decide at a board meeting after considering member comments; and deliver general notice of the adopted change within 15 days. There is an emergency exception for an imminent threat to health or safety or an imminent risk of substantial economic loss, but a camera project planned over a budget cycle is not that.
The order that keeps a board out of Bartholomew territory is therefore:
Two things to tell members while you are at it. Owners may review the association’s written ALPR policy and the vendor contracts; they do not have a right to the captured images. And the state has not settled this area: SB 274, which would have imposed 60-day deletion and Department of Justice audits, was vetoed on October 1, 2025, with the Governor writing that it did not “strike the delicate balance between protecting individual privacy and ensuring public safety.” The private-operator duties above have been in force since January 1, 2016 regardless, and a policy written to them now does not need rewriting if the public-agency rules change.
| Item | Planning range | Notes |
|---|---|---|
| Community-owned camera system: entrance plate cameras plus overview cameras, recorder, UPS | $1,500–$30,000+ | Driven by lane count, in and out, conduit and power at the gate island, retention days, and how much of the rest of the community goes on the same recorder. |
| Plate-triggered gate access: controller, resident list, call box or intercom tie-in | $3,000–$40,000+ | A separate scope from evidence cameras. Gate operator and gate panel work to UL 325 and ASTM F2200 is the gate contractor’s responsibility and should be priced as its own line. |
| Subscription ALPR service | Roughly $2,500–$3,000 per camera per year in published California city contracts, plus an installation fee | The City of Indio’s staff report records $2,500 per camera per year with the vendor noticing an increase to $3,000. Retention is the vendor’s default unless negotiated. |
| The written usage and privacy policy | Association counsel | Not an installer deliverable, and any contractor who offers to write it for you is selling you the wrong document. We supply the retention, access and physical-security facts it has to describe. |
Every Innov8av proposal is a written line-item quote with model numbers, the recorder’s storage and retention days and the UPS runtime spelled out, priced after a free on-site assessment. We do not quote a camera count over the phone, and we will not quote a plate camera without standing at the gate.
Innov8av holds a California C-10 Electrical contractor licence, CSLB #1043428 — the classification has no voltage ceiling and encompasses the low-voltage work the C-7 defines — and a BSIS Alarm Company Operator licence, ACO 7755, the separate licence California requires for alarm work. Both are verifiable in the state’s public lookups. The work is done by our own technicians, carries a one-year parts-and-labor warranty, and existing clients get same-day response.
Working across Los Angeles since 2016, insured and bonded, bilingual in English and Spanish, rated 5.0/5 across 22 verified Reviews.io reviews with a BBB A+ rating. We install wired security camera systems that record locally with no mandatory monthly fee, with NDAA-compliant camera options on request. On a gate scope we write the lane, the capture distance and the camera angle into the proposal alongside the model numbers, so the board can hold the installed system to the same numbers it was sold on — and so the retention figure in your policy matches the drives that are actually in the recorder.
Los Angeles County recorded 57,987 vehicle thefts in 2024, more than any other county in California, on the CHP’s figures — down 7.4% from 2023, but still the largest share of a statewide total of 176,230 vehicles worth an estimated $1.56 billion. About 84.6% of stolen vehicles were recovered statewide; of those recovered, 28.7% came back burned or wrecked. That gap between recovered and recovered intact is the argument for a legible plate at the entrance rather than a wide shot of the driveway.
We will look at the gate island, the lane widths, where power and conduit already run, and give the board a written scope it can put out to bid on equal terms. Free on-site assessment across Los Angeles, Orange and Ventura counties.
Sources: California Civil Code § 1798.90.5, § 1798.90.51, § 1798.90.52 and § 1798.90.54; Adams Stirling, HOA License Plate Readers; Shook, Hardy & Bacon on Bartholomew v. Parking Concepts, Inc. (March 2026); Civil Code § 4360; Axis Communications, “License plate capture” white paper; The Hill on Flock’s retention change (August 2026); Santa Barbara Independent (August 21, 2026); City of Indio Flock agreement staff report; DASMA TDS-353 on UL 325; SB 274 veto message (October 1, 2025); CHP 2024 California Vehicle Theft Facts. Nothing here is legal advice; your association’s counsel drafts the policy.
Yes. Because there is no expectation of privacy on a roadway, an association with private roads may install and operate automated license plate readers; municipalities do not regulate them and cameras on private property do not require a permit. What the law attaches is not a ban but a set of duties: Civil Code § 1798.90.51 requires reasonable security procedures and a written usage and privacy policy that is publicly available and posted conspicuously on the association’s website, and § 1798.90.52 requires an access log recording the date and time, the plate queried, the username and organization, and the purpose of every search.
Civil Code § 1798.90.54 lets an individual harmed by a violation recover actual damages but not less than $2,500 in liquidated damages, plus punitive damages on proof of willful or reckless disregard and reasonable attorney’s fees. In 2026 the Court of Appeal held in Bartholomew v. Parking Concepts, Inc. that failing to implement and publish the policy can itself be the harm — no data breach, no misuse and no monetary loss required, and no exception for small deployments. Draft and publish the policy before the cameras are switched on, not after an incident.
No. Sharing is optional for a private association, and the choice is yours to make in advance rather than in the moment. Civil Code § 1798.90.51(b)(2)(D) requires your policy to state the purposes of, process for, and restrictions on any sale, sharing or transfer, so the board should decide the rule — on request with a report number, on legal process only, or not at all — and write it down. If you subscribe to a hosted service rather than owning the system, the sharing settings and the vendor’s own agreements are part of that answer and should be read before signing.
Plan on two per lane, in each direction you care about. A recognition camera is zoomed tight, exposed dark and angled under 30° to the direction of travel so the plate fills 100–150 pixels across its width; it shows almost nothing else. A second overview camera on the same pole captures the vehicle, its colour, the direction of travel and, at the right height, the driver. A single dome asked to do both jobs will give you a pleasant picture of the entrance and an unreadable plate. Beyond the entrance, the mail kiosk, pool gate and garage are separate design problems.
It is a smaller first cheque and a permanent annual one. Published California city contracts put subscription ALPR at roughly $2,500–$3,000 per camera per year plus an installation fee; a community-owned entrance system falls in the $1,500–$30,000+ range as a capital cost with no per-camera annual fee. Two non-price differences matter more for an HOA: retention, since Flock cut its default from 30 days to seven in August 2026 while an owned recorder keeps whatever you size it for, and control over whether your residents’ plates are searchable outside the community.
Owners may review the association’s written ALPR usage and privacy policy and the vendor contracts relating to the system; they do not have a right to the images the cameras captured. That split is one more reason the policy has to be genuinely public and genuinely accurate — it is the document members are entitled to, and the one a plaintiff will point at if it does not exist. Requests for footage of a specific incident are handled under the authorized-purpose and access-log rules the policy sets out.
Related: California Security Camera Laws · Apartment Building Cameras · Parking Garage Cameras · Access Control in Los Angeles · CCTV Installation Cost