Privacy and preparation
Gate codes, alarm codes and lockbox numbers in service notes
By SourceX Editorial · Updated
Short answer
Gate codes, alarm codes and lockbox numbers in service notes must always be removed before records leave your company, with no exceptions. Paired with an address or a customer, a code is a working key to a home. Technicians write codes in many formats, so find them with pattern searches plus a human review of every note that mentions access.
Key takeaways
- Access codes are a physical security risk, not only a privacy one, so the rule is always remove.
- Removing the address does not make a code safe, because records can be relinked and people reuse codes.
- Codes hide in location notes, dispatch notes, technician notes, photos, texts and call recordings.
- Pattern searches catch most codes; human review catches the ones written as words or descriptions.
- Keep the fact that access was needed, and drop the code itself.
Why are access codes different from other personal details?#
Access codes are different because a leaked code does not just reveal something about a person; it lets someone into their home. A gate code, an alarm disarm code or a lockbox combination is a credential for a physical door, and it is not changed every time a contractor visits.
People also reuse codes. The digits that open a garage keypad may also be the alarm code, the phone PIN or a card PIN. A code that looks harmless without an address can still be harmful to the person who chose it.
That is why access codes get an always-remove rule rather than the case-by-case treatment used for names and addresses. Even if the address is generalized and the customer is coded, the code itself has no analytical value worth that risk.
Where do access codes end up in field service systems?#
Access codes end up wherever a dispatcher or technician needed to remember how to get in, which in a busy shop means almost everywhere. Field service platforms such as ServiceTitan, Housecall Pro and Jobber have dedicated location or property notes, but codes spill well beyond them.
Legacy imports deserve extra attention. When a shop moves from one platform to another, years of access notes are often pasted into a single catch-all field on the customer record, mixed with billing remarks and equipment history. That field tends to hold the oldest and least reviewed codes in the account.
- Location and property notes attached to the customer or service address.
- Dispatch notes and job summaries written by CSRs at booking.
- Technician notes typed on mobile devices at the end of a visit.
- Photos of keypads, lockboxes, key safes and gate panels.
- Text messages and app chat between the office, technicians and homeowners.
- Call recordings and transcripts of booking calls.
- Maintenance agreement notes that repeat the same access details every visit.
- Imported notes from an earlier system, often pasted into a single legacy field.
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Detection patterns that catch most access codes#
Most access codes can be found with patterns that pair an access keyword with a short run of digits or symbols nearby. The table lists the patterns that matter and what each one tends to miss.
Open-source detectors such as Presidio combine regular expressions, rule-based logic and context words, which suits this problem well: a short number next to gate or alarm is a code, while the same number next to tons or SEER is equipment data. Tune the context words to how your technicians actually write.
| Pattern | Typical form | What it misses |
|---|---|---|
| Access keyword near digits | gate, code, alarm, disarm, keypad, garage, pin, combo followed by digits | Codes written in words or split across lines |
| Keypad symbols | Digits followed by a pound or star key | Codes stored without symbols |
| Lockbox and key safe | lockbox, key box, key safe, combo with digits or letters | Box location described without the word lockbox |
| Hidden key locations | key under, key in, spare key, behind the planter | Phrasing unique to one technician |
| Callbox and buzzer | callbox, buzz, unit number with access code | Commercial door and badge codes |
| Network and device logins | wifi, password, thermostat login, app account | Passwords without a label |
What replaces the code in the record?#
A neutral placeholder replaces the code, so the record still shows that access was needed. Whether a technician needed a gate code, waited for a homeowner or found the key in a lockbox explains real differences in arrival time and job duration, and that pattern is worth keeping.
Use a small set of placeholders such as access code removed, key location removed and network credential removed. Keep notes like gated community or dog on property in general form, since they describe the job conditions rather than how to break in.
Remove the whole location notes field when it is used mostly for access instructions. In many shops that field holds little else, and dropping it is safer and faster than cleaning it line by line.
A review workflow for access notes#
A review workflow combines automated search with human reading, because no pattern list covers every way a technician writes a code. The aim is zero codes in the release, so the workflow ends with a second check rather than a single pass.
- Run the pattern searches across every note field in scope and flag all hits.
- Read every flagged note and a random sample of unflagged notes from the same fields.
- Replace codes with placeholders and add any new phrasing to the pattern list.
- Exclude photos of keypads, lockboxes and gate panels, and review other photos for visible codes.
- Run the updated patterns again on the cleaned output.
- Have a second person check a fresh sample before approval.
Illustrative: an electrical contractor clears codes from its notes#
Illustrative: a fictional electrical and low-voltage contractor uses Jobber and installs panels, generators and security wiring for residential customers. It wants to license its job notes and repair history.
The first search finds codes in location notes, in technician notes for generator maintenance visits, and in photos of lockboxes taken so the next technician could find the key. The low-voltage jobs also contain alarm panel model notes next to installer codes.
The team drops the location notes field entirely, replaces codes in job notes with placeholders, excludes every photo of a keypad, panel or lockbox, and adds installer and master code to the pattern list. A second reviewer finds no codes in a fresh sample, and the owner approves the release with the access rule written into the privacy record.
What other secrets travel with access codes?#
Payment card details are the other secret that turns up in the same notes. A CSR who took a card over the phone may have typed the number or security code into a job note. PCI DSS v4.0 Requirement 3.3.1 says sensitive authentication data, including card verification codes and PINs, is not retained after authorization at all, so finding one is a finding for your own security team as well as a removal for the dataset.
Wi-Fi passwords, smart thermostat logins and camera app accounts belong in the same always-remove category. Treat any credential the same way as a gate code.
How SourceX handles access codes#
SourceX treats access codes and credentials as an always-remove category in the Preparation step of the SourceX five-step transaction. The rule, the patterns used and the reviewer checks are recorded in the privacy record of the SourceX Evidence Packet, and the supplier approves the cleaned release before Delivery.
Frequently asked questions
Isn't removing the address enough to make a code harmless?
No. Coded records can sometimes be relinked to an address through other details, and people reuse the same digits across their garage, alarm, phone and cards. The code has no analytical value, so there is no reason to accept any risk by keeping it.
Should we tell customers to change codes found in our records?
Finding codes in your own system is not a leak, but it is a sign that access details are stored widely. Many companies use the cleanup to move access details into a restricted field and to remind customers to change codes after staff turnover. Counsel can advise if a code was exposed outside the company.
Can automated tools find every code?
No tool finds every code, because technicians write them as words, split them across lines or describe them only in context. Automated detection narrows the search; human reading of flagged notes and a sample of unflagged ones closes the gap.
What about door and badge codes at commercial sites?
Treat them exactly like residential codes. Commercial notes often carry door codes, alarm instructions and after-hours contacts for facilities, and a leak exposes a business and its employees. Add commercial terms such as badge, after-hours and night entry to the pattern list.
Do call recordings need the same review?
Call recordings and transcripts are usually excluded from a license entirely, partly because homeowners read out codes and card details on booking calls. If transcripts are in scope for a specific buyer, run the same patterns on them and review every hit by hand.
Sources
- Presidio is an open-source, MIT-licensed SDK for PII identification and anonymization that combines named-entity recognition, regular expressions, rule-based logic and checksums with context. Source
- PCI DSS v4.0 Requirement 3.3.1 states that sensitive authentication data is not retained after authorization, even if encrypted, covering full track data, card verification codes and PINs or PIN blocks. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.