FileWave Location Tracking (Version 10.1+)
The location reporting feature in FileWave is disabled by default. It is recommended that you; verify that this feature is in accordance with your organization’s policies and AUP (Acceptable Use Policy). Notify your end users before activating location reporting, as enabling the feature will prompt for permission to location information.
Global Location Reporting Disable
If there are any reasons, legal or otherwise, that you do not wish to enable tracking on a global level within your organization, your FileWave license can be adjusted to enable personal mode. This will disable devices from sending application usage as well as location information.
To have verify the current status of personal data collection. From FileWave Admin : Server Menu → "Activation Code..." → There you will see "Allow collection of personal data:" with Yes or No after it.
To have personal enabled or disabled on your license, please submit a support ticket with "Personal data License" in the subject.
Only tickets from authorized support agents whose names are on the support contract will be accepted to adjust license personal data settings.
Selective Location Reporting Disable/Enable
If you wish to control location gathering, you have two options.
Option 1 - Device State (New in v10.1)
Use the standard upgrade procedure for the server, Admin application and boosters; You will note that all devices that are not archived now have a status of "Not tracked" For these steps to work you will need to have the 10.1 or newer FileWave .ipa download on to the device. This is located at the bottom of the latest FileWave Management download page.
- Select several devices (don't select a group or filter by everything all at once)
- Right-click → Client State
- Select "Normal" or "Missing"
- Update the Model
Changing the state back to "Not tracked" will disable tracking.
Option 2 - Superprefs
Use the standard upgrade procedure for the server, Admin application and boosters. Note that state will supersede client prefs 
- Open your newly upgraded 10.1 Superprefs editor and hit cancel to create a new Superprefs file
- Go to the "Privacy" tab and change the "Location refresh interval" to "Never" (checking "Disable personal data collection" will disable location tracking, but it will also disable application usage and some other inventory fields)
- Deploy this Superprefs file as you would any Superprefs fileset
Associate this fileset to your OSX, Win, and Android devices that you do not want to track – The client will save these settings but not understand them – When you continue with your upgrade and send out the new 10.1 client, the upgraded client will read the already saved config when it starts, and will not start a location scanner.
Either option will allow you to change location tracking at a later date in controlled groups, if desired, after proper notification has been given to users.
It is important to consider that tracking should be enabled before a device goes missing. An informed and willing end-user is far more likely to agree to location services – knowing it will benefit them later – than a missing device in the hands of a malicious person getting a prompt for "FileWave would like to know your location." So think ahead and be considerate of your end-users privacy.
Warning: In order to avoid legal issues concerning user location tracking, it is highly recommended that you enable location tracking only on devices when a unique user may authorize the service.
Addition OS Specific Considerations
Any user can agree to tracking, admin or not. Only an administrator can disable location services and/or FileWave's rights to location, as per Apple Inc. policy
Any user can agree to tracking, can disable location services, and revoke FileWave's right to location, as per Apple Inc. policy
The Windows operating system does not prompt the local user for access to location.
Upon installing or upgrading the Android FileWave Client to version 10.1 or greater, the user is requested to approve all rights an application needs. This includes location services, running in the background and several other rights.
Normal - tracking enabled, personal data collection enabled
Not Tracked - Personal date collection enabled
Missing - tracking enabled, personal data collection enabled
The client sends location immediately, does not wait for other scans to finish)
The recommended approach would be to make a smart group based on client status is missing. To this smartgroup associate a Superprefs file that enables tracking, and changes to refresh interval to something more frequent. This will help resolve order of operation issues.
 Order of operation
It is important to note the way a client verifies it is able to ask the system for location information.
For example setting the state to "Missing" but it has a Superprefs file telling it the refresh interval is 0 See the flowchart for reference: