GPS Tracking for Your Sales Team: How to Write a Fair Privacy Policy in Nepal

Many owners ask the same question before they switch on GPS for the sales team: is this fair, and will my people accept it? The honest answer is that GPS tracking of a sales team works when it is clear, limited and written down. When it is secret, constant or vague, it creates resentment and good people leave. This guide shows how to build a short GPS tracking privacy policy for your sales team in Nepal, and how to introduce it.

One note first. This article is practical guidance, not legal advice. Employment and privacy rules can change, so have your lawyer read the final wording.

Why a written policy beats a verbal promise

A salesperson who is tracked without being told will find out sooner or later, usually from a colleague. From that day, every number you show him looks like a trap. A salesperson who read the policy, asked questions and signed a copy knows exactly what the phone does.

A written policy also protects you. If a dispute arises about a visit, a warning or a pay deduction, you can show what the employee agreed to and what the system recorded.

The five questions every policy must answer

1. What is recorded?

List it plainly: location points during the working day, check-ins at shops with a photo, and the time the day started and ended. If you also record phone status such as battery or whether location is switched on, say so.

2. When is it recorded?

Say that tracking runs only between "start my day" and "end my day". Say clearly that nothing is recorded on days off, holidays or after the day ends.

3. Who can see it?

Name the roles, for example the owner, the sales manager and the regional manager. Say that other staff and customers cannot see it.

4. What is it used for?

Good reasons: attendance, proof of visits, route planning, settling disputes with shops, and fair commission. Say what it is not used for, such as checking where someone lives or what they do at lunch.

5. What happens when something looks wrong?

Promise a conversation before any action. A dead battery, a long tunnel on the highway or a hill with no signal are honest causes. Say that alerts start a question, not a punishment.

A one-page policy you can adapt

Copy this outline and change it to fit your company:

1. Purpose: We use location data to confirm visits, calculate attendance and plan routes fairly.
2. Scope: Applies to all field staff who use the company app.
3. When: From start of day to end of day only. Never on off days.
4. What we record: Location points, shop check-ins with photos, day start and end times.
5. Who sees it: Owner, sales manager and the direct supervisor.
6. How long we keep it: State a period you can actually follow, for example the current and previous fiscal year. Check this with your accountant or lawyer.
7. Your rights: You may ask your supervisor to explain any record about you.
8. Process for alerts: The supervisor speaks to you first and notes your explanation.
9. Personal phone use: State whether staff use their own phone or a company phone, and who pays for data.
10. Acknowledgement: Signed copy kept in your file.

Handle the phone question honestly

Many Nepali field staff use their own phone. That makes privacy feel more personal. Three things help:

• Track only through the work app and only during work hours.
• Reimburse a mobile data allowance, or provide a basic company phone for the team.
• Tell staff how to see whether tracking is on, so they never wonder.

A short worked example

Suppose a company with 12 salespeople in the Kathmandu Valley wants to start. The owner prints the policy, holds a 30-minute meeting and answers questions. He also states one commitment: tracking data will not be used to cut pay without a conversation first. The company starts with a pilot of three people for two weeks. The numbers here are illustrative, but the order matters: explain first, pilot second, roll out third.

After the pilot, the owner asks the three pilot staff what felt wrong. One says he did not realise the photo was required at every visit. The company changes the wording and rolls out to all twelve.

Mistakes to avoid

• Tracking outside working hours. It is hard to defend and it ends trust.
• Using alerts as proof of guilt. Treat them as questions. See stopping fake visits ethically.
• Showing the map to everyone. Limit access by role.
• Keeping data forever. Decide a retention period and follow it.
• Surprising the team. Announce before you switch on.

Build trust with the first month

Pair the policy with something staff like. Fair targets, timely commission and quick expense approval make tracking feel like part of a professional system rather than suspicion. Read field sales tracking in Nepal for what to track, and onboarding a 20-person sales team in one week for a rollout plan.

A second example: before and after a clear policy

These figures are illustrative. A company with 40 field staff switched on tracking with a short announcement and no written policy. Within two weeks, six people turned location off during the day, three asked the owner whether the data was used to cut pay, and the sales manager spent hours answering rumours.

The owner then paused, wrote the one-page policy above, held two small meetings and promised that no pay action would follow an alert without a conversation. A month later the staff who had switched location off were back on, because they now knew what was recorded and when it stopped. Nothing about the technology changed. What changed was that people could read the rules, ask questions and see that the owner kept his word.

	Without a policy	With a policy
Staff questions	Many, informal, rumour-driven	Few, answered by the document
Location switched off	Common	Rare, and handled by a conversation
Manager time	Spent calming people	Spent reading the day view
Trust in the numbers	Low	Higher

Questions owners ask

What if an employee refuses to be tracked?

Start by listening. The objection is often about a personal phone, battery or fear of being watched at lunch. Offer a data allowance or a company phone, and restate the limits. If tracking is part of the job, as for most field roles, it should be in the appointment letter. Ask your lawyer how to handle a refusal.

What if someone turns location off?

Do not assume bad intent. Phones switch off location to save battery, and some people reduce the permission by accident. Ask first. If it keeps happening after you have explained the policy, treat it like any other repeated breach of a work rule.

Should we use company phones or personal phones?

Both work. Company phones make the boundary clear, because the phone is a work tool. Personal phones are cheaper but need extra care: only the work app tracks, only during the working day, and you cover the data cost.

How long should we keep location data?

Choose a period you can really follow and write it in the policy. Many companies tie it to the accounting year. Confirm the right period with your accountant or lawyer, since we do not give legal advice.

Can tracking data be used in a disciplinary matter?

It can be evidence, but it should never be the only thing. Combine it with the salesperson's explanation, order records and photos, and give the person a chance to respond before any decision.

A review calendar for the first quarter

1. Week 1: announce, hold the briefing and collect signed copies.
2. Week 2: pilot group only. Ask what felt wrong.
3. Month 1: roll out to all staff. Review the alerts together with the team lead and note any that were honest causes.
4. Month 3: revisit the policy. Remove anything nobody uses and clarify anything people asked about twice.

How GamiTrack handles this

In the GamiTrack field app, tracking starts when the salesperson taps Start my day and stops at End my day or sign-out. The first time, the app shows a disclosure titled "Location tracking during your working day" that explains what is recorded and why, and the person must tap "I understand, continue". Android also shows a notification while the route is being recorded. Managers see alarms and an integrity score as signals to discuss, with a resolution note for each. The help article on tracking and offline work explains it from the staff side, and alarms explains it from the manager side.

If you want to see how this looks for your team, you can start a free trial with a small pilot group.

Key takeaways

• Write the policy before switching tracking on.
• Limit tracking to the working day and name who sees the data.
• Treat every alert as a question first.
• Have your lawyer check the final wording.