Free Template for Dealers

BYOD Policy Template for Dealerships

A fill-in policy for the personal phones, laptops and tablets your staff use for work. What they may reach, the controls they need, and what comes off them when someone leaves.

Or download the template as an editable Word file or a printable PDF.

Dealership sales manager signing a printed BYOD policy at his desk, his phone lying face down beside the page

A BYOD policy template for dealerships is a fill-in document that says which personal phones and computers may reach dealership email, the CRM or the DMS, the controls they need, and what comes off them when someone leaves.

Last updated: November 17, 2026

Personal phones
Home computers
Customer data
One policy

The Phone Is Theirs. The Customer Data on It Is Yours.

Picture a salesperson photographing a finance customer’s driver’s license on a personal phone to save a walk to the desk. The phone belongs to the salesperson. The license doesn’t. The FTC staff’s Safeguards Rule FAQ for dealers says customer information “generally will include any nonpublic personal information you collect from customers for whom you have arranged the financing or leasing of an automobile,” and nothing in the rule turns on who owns the phone it lands on.

Erik Nachbahr, Helion’s founder and president, puts the other half of it as a question for dealers: “why are you allowing your employees to become the personal point of contact of your customers?” A BYOD policy answers both halves in writing, and our cybersecurity for dealerships page covers the controls behind it.

One rule before you start. This template is not legal advice. Notice of monitoring and paying staff back for work use of their own phones can be set by state law, so have your attorney review it before anyone signs.

Section 2

Which Personal Devices May Reach Which Systems?

Decide it system by system, before anyone signs. The store-issued column is the baseline. The two personal columns are starting points in brackets, so change them to match what your store really allows. Give the DMS and deal paperwork the strictest rows.

The systemPersonal phonePersonal computerStore-issued device
Email and calendarOnly inside [the work profile or approved email app], with multi-factor sign-in and a screen lock.[Web browser only, nothing downloaded / Not allowed].Allowed.
The CRM[The CRM’s own app], with multi-factor sign-in. No exports and no screenshots of customer lists.[Not allowed / Web browser only].Allowed.
The DMS[Not allowed / The approved DMS app only], with multi-factor sign-in.Not allowed.Allowed, at the store or through [approved remote access].
Calls and texts with customersFrom a company number in [the store’s phone app], never the personal number.[The store’s phone app], same rule.Through the store’s phone system.
Driver’s licenses and deal paperworkNever photographed, saved or texted. Scan it at the desk into [the DMS or deal system].Never saved or opened.Into [the DMS or deal system] only.
Shared filesOpened in [approved app]. Nothing saved to the phone itself.[Not allowed].Allowed.
Remote access to store systemsNot allowed.[Not allowed / Through approved remote access, with multi-factor sign-in].Through [approved remote access], with multi-factor sign-in.

Whatever you allow, the controls in section 3 come with it. The program around all of it belongs in your written information security program.

What Do the FTC and NIST Say About Personal Phones?

Neither one bans them. The Safeguards Rule never mentions personal devices by name. It protects customer information, and its definition of an information system includes resources “connected to a system containing customer information.” The definition doesn’t depend on who owns the device.

State law adds its own layer. Notice of monitoring, and whether you pay staff back for work use of their phones, can depend on the state each store sits in, so a group with stores in several states may need more than one answer. Our guide to dealership privacy laws by state maps the privacy side.

The phone is theirs. The rules follow the data.

FTC Safeguards Rule

16 CFR 314.4(c)(5) calls for multi-factor authentication “for any individual accessing any information system,” unless your Qualified Individual approves an equivalent or stronger control in writing.

Any individual includes a salesperson on a personal phone.

FTC FAQs for dealers

The FTC staff’s Safeguards Rule FAQ for auto dealers says the rule applies to financial institutions under the FTC’s authority, and “That includes most automobile dealers who finance or lease automobiles.” Approved financing and lease applications are always customer information, it adds.

Approved financing and lease applications are on its “always” list.

NIST SP 800-124

NIST SP 800-124 Revision 2 (May 2023) says many mobile devices, “particularly those that are personally owned,” “are not inherently trustworthy,” and tells organizations to treat every mobile device as untrusted until they’ve secured it and keep monitoring it.

Untrusted until secured.

The template

The Dealership BYOD Policy Template

Download it as an editable Word file or a printable PDF. Same nine sections, same numbers, and the access table comes with it. Fill in the brackets with whoever runs IT. Then hand it to your attorney.

Dealership operations manager pointing to a printed policy page while a salesperson reads along, his phone face down on the counter

Where Helion fits

The final policy is the dealer’s to set. A complimentary IT and cybersecurity assessment looks at where the store stands against the FTC Safeguards Rule’s requirements and puts the findings in writing.

BYOD policy: section by section Each numbered line is a rule the store follows. Anything in [brackets] is yours to fill in or change.

1 Who and what this covers

  • 1.1 This policy covers anyone who uses a personal phone, tablet or computer for [Dealership Name] work, including part-time staff, temps and contractors.
  • 1.2 Using a personal device for work is [optional / allowed only with approval]. Anyone who would rather not can ask for [a store device / another option].
  • 1.3 The policy owner is [name, title]. Questions go to [name, phone] before you act, not after.

2 Approval and setup

  • 2.1 A personal device reaches dealership email, the CRM or the DMS only after [IT contact] approves it and writes down whose it is, what it is and which systems it may reach.
  • 2.2 What each device may reach follows the access table in this policy. Anything not on the table needs [policy owner]’s approval first.
  • 2.3 Dealership apps and data live only in [the managed work profile or approved apps] that [IT contact] sets up.

For line 2.3, both phone platforms have a setup made for staff-owned phones. Apple calls User Enrollment “Designed specifically for BYOD programs,” and on an Android phone with a work profile, personal apps and data “aren’t visible or accessible to your organization.” Our post on mobile device management for dealerships covers the tools behind both.

3 Required controls

  • 3.1 A screen lock with [a six-digit PIN, fingerprint or face unlock], set to lock after [number] minutes.
  • 3.2 Multi-factor sign-in on every dealership account used on the device.
  • 3.3 Operating system updates installed within [number] days. A device that no longer gets security updates from its maker comes off the list.
  • 3.4 No jailbroken or rooted devices, and apps only from the official app store.

Line 3.2 follows the FTC Safeguards Rule, which calls for multi-factor authentication for anyone accessing an information system. The rule also names “devices” among the things a dealer has to identify and manage, which is what line 2.1’s record is for.

4 What never goes on a personal device

  • 4.1 Photos of driver’s licenses, insurance cards, credit applications or any other deal paperwork.
  • 4.2 Customer lists, exports or reports from the CRM or the DMS.
  • 4.3 Customer or employee information in personal email, personal cloud storage, personal messaging apps or personal AI accounts.
  • 4.4 Passwords for dealership systems, unless they’re kept in [approved password manager].

Section 4 spells out line 2.4 of our acceptable use policy template, the rules every employee signs at hire.

5 Calling and texting customers

  • 5.1 Staff call and text customers from a company number in [the store’s phone app], not from their personal number.
  • 5.2 Texts to customers follow the store’s consent and opt-out rules.
  • 5.3 If a customer reaches you on your personal number, move the conversation to the company number.

Rex Marchant, our Vice President of Service, explains how a company number in an app on the employee’s own phone works, and which texting questions to ask your phone provider first.

6 Lost, stolen or replaced devices

  • 6.1 Report a lost or stolen device to [name, phone] within [number] hours.
  • 6.2 The store can then remove dealership apps and data from the device remotely, and only those.
  • 6.3 Before you sell, trade in or give away a device, tell [IT contact] so dealership data comes off it first.

A lost phone with dealership email on it is a possible incident until someone checks. Our incident response plan template has the steps.

7 Privacy on a personal device

  • 7.1 The store can see [device model, operating system version, whether the screen lock is on, the work apps installed]. [IT contact] keeps this list current.
  • 7.2 The store’s setup is chosen so it doesn’t see [personal apps, photos, texts, email, browsing, or location outside the work apps]. If that changes, staff are told in writing first.
  • 7.3 Any notice of monitoring uses the wording counsel approves for [state].

Fill in 7.1 from what your setup really shows. A work profile isn’t invisible. Google’s help page lists details a personally owned Android phone still shares with the organization, such as the model, serial number and phone number, plus location and network activity from apps inside the work profile. Notice rules differ by state, and our acceptable use policy template spells out three of them.

8 When someone leaves

  • 8.1 On the last day, [IT contact] removes the work profile and every dealership account from the person’s personal devices.
  • 8.2 Their company number is rerouted to [manager or team].
  • 8.3 The person confirms in writing that no dealership or customer information is left on any personal device.

Section 8 belongs on the same list as email, DMS access and door codes. Our employee offboarding checklist has a line for the phone.

9 Review and sign-off

  • 9.1 [Policy owner] reviews this policy [every year] and whenever we add a system, an app or a store.
  • 9.2 Signed by [employee name, date] and approved by [name, title, date].

Who’s Behind This BYOD Policy Template

2,000+ Automotive and heavy truck dealerships
35,000+ End users supported daily
98% Client retention rate
1997 Working only with dealerships since

Helion Technologies has worked only with automotive and heavy truck dealerships since 1997. Managed IT, cybersecurity and compliance run as one team here, so the phones, the accounts on them and the controls around both can sit with one owner instead of several.

How to Roll Out a BYOD Policy at a Dealership

Start with what’s already happening. Personal phones may be reading work email long before anyone writes a rule about them, so the first step is finding out which ones. The signatures come last.

  1. 1

    Find out what’s connected

    Ask sales, F&I, service, parts and the office who reads work email, the CRM or customer texts on a personal device.

  2. 2

    Fill in the access table

    Decide what each personal device may reach, starting with the DMS and deal paperwork, then set the controls in section 3.

  3. 3

    Set up devices, then sign

    Put the work profile and multi-factor sign-in on each approved device, then collect signatures on line 9.2.

  4. 4

    Build it into every exit

    Add sections 6 and 8 to the exit process, and review the policy every year and whenever a system changes.

Common Questions

Two dealership managers at a conference table going over printed policy pages, their phones face down on the table

Finished the policy?

A complimentary IT and cybersecurity assessment reviews your current technology and where the store stands against the FTC Safeguards Rule, and puts the findings in a written report.

Is BYOD a good idea for a dealership?
It’s a trade, and the store gives up some control in it. On a store-issued phone, the store can manage the whole device. Under the setups Apple and Google offer for personal phones, it manages the work side only, which is why this policy spends as long on what never goes on the device as on what may.
Can salespeople text customers from their own phones?
From their own phone, yes. From their own number, no. A company number in an app on the same phone stays with the store’s phone system, so the store can reroute it when that salesperson moves on.
Does the FTC Safeguards Rule cover personal devices?
The rule doesn’t name personal devices. It protects customer information, its definition of an information system includes resources connected to a system containing customer information, and it calls for multi-factor authentication for anyone accessing one. Ask counsel how that applies to a personal phone signed into dealership email.
What should a BYOD policy include?
Which personal devices may reach which systems, the controls they need, what never goes on them and what comes off them when someone leaves. Add customer texting, lost devices and what the store can see, and you have the nine sections above.
Do we have to pay employees for using their own phones?
It depends on the state. In California, a 2014 appeals court decision held “that when employees must use their personal cell phones for work-related calls, Labor Code section 2802 requires the employer to reimburse them,” and that what’s owed is “a reasonable percentage of their cell phone bills.” Ask your attorney about each state where you have a store.
Do we need an attorney to review this?
Yes. This template isn’t legal advice, and Helion isn’t a law firm. Whether you owe staff a monitoring notice, or money for their phone bills, comes down to state law. Have counsel read the policy before anyone signs it.
Can the dealership wipe an employee’s personal phone?
It shouldn’t need to. Apple says that under User Enrollment, IT “can’t remotely wipe a device” and can “remove only corporate data and apps.” On a personally owned Android phone with a work profile, Google lists deleting data in the work profile, and lists a factory reset only for company-owned phones. Line 6.2 puts that limit in writing.

Your policy says what a personal phone may reach. A complimentary assessment looks at the systems behind it and puts what it finds in a written report.

Get Your Complimentary IT & Cybersecurity Assessment →