Alarm dealer programs: who owns the customer and the account data?

Who owns the customer in an alarm dealer program?#

In an alarm dealer program, the customer usually belongs to the program company once it buys the monitoring contract the dealer originated. The dealer sells and installs the system, the customer signs a contract on the program's paper or one that is assigned to it, and from then on the program company bills, monitors and holds the relationship.

That is the core trade of a dealer program: the dealer is typically paid up front for each account it sells into the program instead of building recurring monthly revenue, and gives up the customer in return. The exact line depends on the dealer agreement, which can leave some records and service work with the dealer and take others.

Wholesale and proprietary monitoring run the other way. In both, the dealer keeps the contract and the customer; the difference is whether a third-party central station or the dealer's own monitors watch the signals.

Who owns what in each monitoring model#

Ownership differs by item, not only by model. The table shows the usual pattern, which your own contracts can change.

Account brokers and buyers look closely at these structures because they change what is being bought. A book of wholesale-monitored accounts transfers contracts and customer relationships, but the buyer must also arrange monitoring and move call lists and other account data from the old central station.

Dealer agreement clauses that decide data rights#

Dealer agreement clauses decide the details, and they rarely use the word data. Look for how the agreement treats the account, the customer and information about both.

Read older versions too. A dealer that has sat in a program for years may have accounts sold under several versions of the agreement, each with different terms.

• 1Purchase or assignment terms: what the program company buys with each account, and from when.
• 2Definitions of account, customer information and confidential information.
• 3Chargeback or replacement terms when a purchased account cancels early.
• 4Non-solicitation of purchased customers, during and after the agreement.
• 5Rights of first refusal or exclusivity over new accounts the dealer creates.
• 6Records clauses: what the dealer must keep, deliver or destroy, plus audit rights.
• 7Panel access terms, including who controls installer codes and remote programming.
• 8Termination terms: what happens to service, records and branding when the program ends.

What the central station holds, and who can get it#

The central station holds the operating record of monitoring: signals received, operator actions, dispatches, call list changes and passcode checks. In wholesale monitoring, the dealer's contract with the central station sets who may access that history, how it can be exported and what happens when the dealer moves accounts elsewhere.

Moving accounts between central stations is routine, but the receiving station needs current call lists, zone lists and passcodes to take over. Event history may or may not come along. If that history matters to you, for service analysis, disputes or later licensing, ask the station in writing what it will export and in what format before you need it.

Why every model treats account data as sensitive#

Every model treats account data as sensitive because it describes how to get into, or around, a protected property. Passcodes, zone lists, arming and disarming times, and open and close reports show when a home or business is empty and which doors are covered.

That shapes any use beyond monitoring. Internal analysis, a sale of the account base and a data license all need these fields removed or tightly restricted, and an export should never carry passcodes or user codes. Commercial accounts can add another layer, since some customer contracts limit what the dealer may do with information about the site.

Questions to answer before you sell accounts or license records#

The questions to answer before you sell accounts or license records all come down to control: which accounts you own, what the contracts allow, and where the data physically sits. Answer them from documents rather than memory, because program purchases often happened long before anyone thought about a sale.

Gaps in the answers are common in dealers that changed models along the way. Treat an unknown as a task for counsel or the central station, not as a yes.

Illustrative: a dealer with two books of business#

Illustrative: a fictional regional alarm dealer sold residential accounts into a national dealer program in its early years, then switched to wholesale monitoring and began keeping new accounts. Install records, service tickets and technician notes for both books sit in one field service system.

When the owner explores selling the company and, separately, licensing service records, counsel maps every account to its model. The program-sold accounts belong to the program company and the agreement limits contact with those customers, so their records are set aside. The wholesale book, with contracts the dealer owns, becomes the scope.

Within that scope the team keeps install dates, equipment types, service tickets and resolution notes, and removes names, addresses, passcodes, call lists and arming history. The central station confirms which event history it can export under the monitoring contract.

How SourceX approaches alarm dealer records#

SourceX approaches alarm dealer records by establishing control first. In the Rights step of the SourceX five-step transaction (Supply, Rights, Preparation, Approval, Delivery), each group of accounts is matched to its contract model, and records the dealer does not control are excluded.

Passcodes, user codes, call lists and occupancy patterns are removed during Preparation, and the work is recorded in the SourceX Evidence Packet, including provenance, licensing rights and the privacy record. The dealer approves the prepared sample before anything is delivered.