Skip to content
  1. SerwisOS
  2. Blog
  3. Rules and taxes

Device passcodes and customer privacy: what repair shops should do

A phone on your bench holds a customer’s photos, messages and bank apps. Ask for the passcode only when you need it, never write it on a sticker, and delete it at pickup.

7 min read

Table of contents
  1. Loaner phones with someone else’s data
  2. Manufacturer repair modes solve half the problem
  3. Recording a passcode: three practices, one bad
  4. Ask about backups
  5. Which rules apply
  6. Put it in your terms
  7. Who does what
  8. A checklist for tomorrow’s intake
  9. Sources

A phone repair shop handles personal data all day, even without a marketing database. Photos, messages, email, banking apps: all of it sits on the device a customer hands you across the counter, usually with the passcode. From that moment you are responsible for it as if it were your own.

This article covers the practical side: when you need a passcode, how manufacturer repair modes shrink the problem, how to record a passcode without creating a risk, and which rules to keep in mind. It is not legal advice. US privacy law is a patchwork of state laws, and what applies to you depends on where you operate and how big you are.

Loaner phones with someone else’s data

The most embarrassing privacy failure in a repair shop is not a database leak. It is the drawer of loaner phones. If a loaner goes out with the previous customer’s photos or accounts still on it, you have an incident. One missed reset is enough.

The rule is simple: a loaner goes back into circulation only after a full reset, done from a written checklist.

Manufacturer repair modes solve half the problem

You no longer need a passcode for everything:

  • Samsung Maintenance mode (Galaxy devices on One UI 5 or later) restarts the phone into a separate profile where only pre-installed apps are available and photos, videos, contacts and messages are inaccessible. The customer turns it on in Device care in Settings (Samsung).
  • Apple Repair State (iPhone, iOS 17.5 and later) keeps Find My on during the repair, so the customer does not have to switch it off first (AppleInsider).

Both work only on supported devices and software, and some repairs still end in a reset, so ask for a backup first. For other brands you are back to a PIN, pattern or password, and that is where good documentation starts.

Recording a passcode: three practices, one bad

The intake form for a phone should ask one question every time: how will you get access to the device? Options like “customer provided passcode,” “repair mode” and “no access needed” make you decide before the first screw comes out.

The bad practice is a passcode on a sticky note stuck to the phone or on a pad by the register. Everyone who walks by can read it, and it often outlives the repair.

The minimum practice is a sealed envelope in a locked drawer, a line on the intake record (“passcode provided in sealed envelope”), and destroying the note at pickup. It takes two minutes.

The better practice is to not keep the passcode at all. Ask the customer to unlock the phone at the counter, and to change the passcode after pickup. Where you must record it, limit who can see it and delete it at pickup. In SerwisOS, the phone intake preset already includes the access question and a backup question, and the device intake module keeps the passcode in a vault: it is stored encrypted, only staff with permission can see it (a technician only on their own work order), every view is logged, and the code is deleted automatically after pickup. It never appears on printouts or in messages to the customer. The front desk can save the code but cannot read it.

Ask about backups

The other half is who is responsible for the data. The phone preset asks the customer directly whether they have a backup. Answers such as “yes,” “no, I accept the risk” and “the shop will back up” go on the intake record. A written answer settles the most common dispute in phone repair: who deleted the photos. Record the device’s condition too, including any warning messages the phone already shows, such as an unknown-part notice.

Which rules apply

There is no single US privacy law for repair shops. Three points, each with limits:

  • State privacy laws. California’s CCPA applies to for-profit businesses that meet a threshold: over $25 million in annual gross revenue, or buying, selling or sharing the personal information of 100,000 or more California residents or households, or earning half their revenue from selling or sharing it (California Attorney General, accessed 2026-11-03). Most single-location shops fall below those lines, and the dollar figure is adjusted over time. Other states have their own statutes with different thresholds; we have not verified each one, so check the states where you operate.
  • Reasonable security. Even where no privacy statute applies, the FTC expects businesses to protect the personal information they hold. Its small-business guide says to keep only what you need, lock it up, and dispose of it properly (FTC, accessed 2026-11-03). That is the envelope-and-shred routine above.
  • Breach notification. Every US state has a breach notification law, and the details differ (Justia 50-state survey, accessed 2026-11-03; seen in search results, not read in full). A sticky note is not a database breach, but a stolen notebook of customer logins could be.

Shops in Canada, the UK, Ireland, Australia and New Zealand have their own privacy regimes, which we do not cover here. The lesson is the same everywhere: collect only what the repair needs, keep it safe, delete it when the job is done.

Put it in your terms

Two short statements are worth having in writing:

  1. The shop uses data on the device only as needed to diagnose, repair and test it.
  2. The customer confirms backup status at intake, and the shop is not responsible for data that was not backed up after a clear warning.

Have a local attorney review the wording for your state. Our privacy policy and terms describe how the platform handles data; your terms with your own customers are a separate document.

Who does what

Name three roles, because “everyone did everything” in practice means nobody:

  1. Intake records how access is provided, the backup status and the condition.
  2. The technician has the passcode only while working on that job.
  3. Pickup confirms the test with the customer at the counter and destroys any passcode note.

A checklist for tomorrow’s intake

  1. Add an access question (customer passcode, repair mode, none needed) to every phone intake.
  2. Record whether the customer has a backup.
  3. Remove passcode sticky notes. Use a locked drawer.
  4. Put a reset checklist on the loaner phones.
  5. Offer Maintenance mode or Repair State whenever the customer is willing.

You can start a free account with phone-repair intake fields in the sign-up wizard. See also the phone repair page, the features and pricing.

Sources

  • #privacy
  • #device passcode
  • #phone repair
  • #intake
  • #customer data

Keep reading

More on running a repair shop

All posts