Storing Gate Codes Safely for Pool Service
How to store customer gate codes with consent, limit who can see them, and handle a lost phone or a tech who leaves your company.
A gate code is a key
A gate code lets you onto someone's property when they are not home. Treat it like a house key that a customer lent you, because that is what it is.
Most pool techs know a bad habit when they see it: codes in a group text, codes scribbled on the back of a service sheet, codes in the notes app next to the grocery list. Each of those works until a phone is lost, a tech quits, or a customer asks who has their code.
The goals are simple. Get consent, store only what you need, limit who can see it, and be able to remove access fast.
Get consent and say what the code is for
Ask the customer before you store the code, and keep a record of the yes.
- Add a line to your service agreement that says you will store gate and access information for service visits only. The pool service contract guide covers what else belongs there.
- If a customer texts you a code, reply that you have saved it for service access and ask them to tell you when it changes.
- Store only what you need to do the job. The gate code, the gate location and a dog note are enough. You usually do not need an alarm code or a house door code.
Privacy and notification rules differ by state. For anything legal, ask a licensed professional or check your state's guidance. This page covers practical habits.
Limit access
Most of the risk comes from how many people and places can see the code. Shrink both.
| Place | Risk | Better option |
|---|---|---|
| Group text with helpers | Everyone in the thread keeps it, forever | A record that only the assigned tech can open |
| Notes app with other notes | No separation, shows in search and previews | A dedicated field in your route tool |
| Paper in the truck | Anyone who opens the cab sees it | Avoid, or carry only today's codes and shred them |
| Photos of the gate keypad | Code shows in the camera roll and backups | Never photograph a code |
| Spreadsheet on a shared drive | Anyone with the link can read it | Restrict access and turn off link sharing |
| Memory | Fine, until you have 60 accounts | Use a protected record |
Beyond where the code lives, apply these rules:
- Assign by route. A tech who services Tuesdays does not need Thursday's codes.
- Use separate logins. If everyone shares one login, you cannot take away one person's access.
- Lock the phone. Use a passcode, and set the screen to lock quickly.
- Hide lock screen previews. A text that includes a code should not appear on a locked screen.
- Keep codes out of reports. Customer-facing reports and messages should not contain access details.
The phone setup guide covers the lock and preview settings.
What to ask any app
If you store codes in route software, ask these questions during a trial:
- Is there a separate field for access info, or does it live inside general notes?
- Can each tech see only their own stops?
- Does each person have a separate login that I can disable?
- How is data protected on the phone and on the server? Ask the vendor to explain it in plain words and in writing.
- Can I delete a code, and is it removed from backups and exports?
- Does a data export include the codes? If so, the export file now holds sensitive data and needs the same care.
- Is there a way to see who changed a code and when?
A vendor who cannot answer these questions plainly has told you something.
When a tech leaves
Decide this before you hire. The hiring first pool tech guide covers the broader process. For codes, the checklist is short:
- Disable the person's login the same day.
- Collect or wipe any company phone. If they used a personal phone, ask them to sign out and delete the app and any exported files.
- For high-value or sensitive accounts, ask customers whether they want to change their code.
- Rotate your own passwords if the person had owner-level access.
A separate work phone makes steps 1 and 2 much easier. It is worth considering once you have a helper.
When a customer changes the code
Customers change codes without telling you. Build a way to catch it:
- When a gate code fails, mark the record as "needs update" the same day so the next visit does not repeat the problem.
- Text the customer once for the new code, and record it.
- Track the skipped stop. The locked gates and skipped stops guide covers what to bill and how to document it.
Mistakes to avoid
- Storing everything. More data means more to lose. Skip what you do not use.
- Pasting codes into photos or reports. They persist in places you forget.
- Keeping codes for former customers. Delete the code when you drop an account.
- Leaving exports lying around. A spreadsheet export on a laptop desktop is a copy of every code you hold.
- Assuming the app handles it. Features help, but habits protect.
Common questions
Do I need customer permission to store a gate code?
Ask first, and write down that the customer agreed. Putting it in your service agreement is a clean way to do it. Rules differ by state, so check with a licensed professional for your situation.
Where is the safest place to keep gate codes?
In a locked app or record that is separate from general notes, on a phone with a passcode, with per-person logins so you can remove access later. Avoid text threads, photos and paper in the truck.
What should I do if a phone with gate codes is lost?
Lock or wipe it remotely right away, change your own passwords, and tell affected customers so they can change codes. Notification duties vary by state, so check with a licensed professional.