FieldOpsX ("FieldOpsX", "we", "us", or "our") provides the FieldOpsX Android application for field-service businesses and owner-operators. This Privacy Policy explains how FieldOpsX accesses, uses, stores, transmits, and protects information when you use the app.
Privacy contact: Use the protected Support page to reveal the support address after verification.
1. Information handled by FieldOpsX
FieldOpsX can store business and service information that you enter, including customer names, phone numbers, email addresses, service addresses, unit or access details, equipment or appliance information, job descriptions, internal notes, appointment information, invoices, invoice amounts, payment status, parts costs, expenses, receipt or job photos, and generated files such as invoice PDFs and backups.
The app can also use approximate or precise device location when you request a location-based feature such as route calculation, address assistance, or live ETA. Location permission is requested on demand; FieldOpsX does not request background location permission in this release.
During the beta/tester-access period, the app can create an installation identifier and can transmit that identifier, tester-key identifier, and app version to the FieldOpsX licensing service to check whether tester access is active or revoked. The licensing service does not need your customer or job records for this check.
2. Local storage
Core FieldOpsX business records are stored locally in the app's private storage on your Android device. Android system backup is disabled for the app. You control the customer, job, invoice, photo, and other records that you enter.
3. Optional integrations and transfers
FieldOpsX includes optional integrations. Information leaves the device only as needed for a feature you enable or invoke.
- Maps and routing (TomTom / navigation apps): service addresses, search queries, route coordinates, and location information can be sent to routing or navigation services to provide address lookup, maps, routes, distance, and ETA.
- Google Drive backup: if you choose a Google Drive folder for backup, FieldOpsX can write and restore FieldOpsX backup files in the location you select. Google processes that data under your Google account and Google's terms and privacy practices.
- Wave accounting: if you connect Wave, FieldOpsX can send and retrieve customer, invoice, payment, accounting-category, and related business information needed for the accounting features you use. Your Wave access token is stored using Android security controls and is sent only when communicating with Wave.
- QuickBooks Online Integration: QuickBooks Online is optional. When you enable it, FieldOpsX may exchange business and accounting data needed for the features you request, including customers, invoices, invoice line items, payments, expenses, vendors or accounting references, taxes, and related identifiers, with Intuit QuickBooks Online. To support the connection, FieldOpsX may securely store QuickBooks connection information such as the company or realm ID and authorization or refresh tokens on the FieldOpsX backend. The QuickBooks Client Secret is kept server-side and is never stored in the Android app. Accounting data is transmitted only as needed to provide the integration. You can disconnect QuickBooks from FieldOpsX. After you disconnect, FieldOpsX stops using the QuickBooks connection credentials and removes or revokes stored connection tokens as appropriate. QuickBooks and Intuit process information under Intuit's own privacy terms and practices.
- Business server sync: if you configure your own compatible server, FieldOpsX can synchronize the business records covered by that feature to the HTTPS server address you provide. Google Play builds require HTTPS for this connection.
- Email, SMS, sharing, and navigation handoff: when you choose to send an invoice, message a customer, share a file, or navigate, FieldOpsX can hand the information you selected to another app or service that you choose. The receiving service's privacy practices then apply.
Third-party services may process information as independent providers or service providers under their own terms. FieldOpsX does not control data after you intentionally send it to a third-party account or service.
4. How information is used
Information is used to provide FieldOpsX functionality, including scheduling and managing field-service work, customer communication, routing and ETA, creating invoices and PDFs, tracking payments and business performance, storing photos and notes, backing up or synchronizing data when requested, supporting optional accounting integrations, providing tester-access licensing, security, troubleshooting, and customer support.
5. Data sharing and sale
FieldOpsX does not sell personal information. FieldOpsX does not contain third-party advertising or analytics tracking SDKs in version 1.0.35.
Information can be transmitted to third-party services only when required for an enabled or user-requested feature, as described above. We may also disclose information when required by law or to protect the security and integrity of the service.
6. Security
The Google Play build blocks cleartext HTTP traffic and requires HTTPS for FieldOpsX's configurable server-sync feature. FieldOpsX uses Android app-private storage and Android security mechanisms for supported secrets such as the Wave token. QuickBooks connection tokens and related connection information are handled by the FieldOpsX backend; the QuickBooks Client Secret is not stored in the Android app. No method of storage or transmission can be guaranteed to be completely secure, so users should also protect their device, Google account, Wave account, QuickBooks account, server credentials, and exported files.
7. Retention and deletion
Local records remain on your device until you delete them, clear FieldOpsX app storage, or uninstall the app. FieldOpsX provides controls to delete business records such as jobs, customers, invoices, photos, and related data where applicable.
Copies that you intentionally place in Google Drive, Wave, your own server, email, messaging, or another third-party service are retained according to your choices and that service's policies; deleting a local FieldOpsX record does not automatically delete every copy held by another service.
When you disconnect QuickBooks Online, FieldOpsX stops using the QuickBooks connection credentials and removes or revokes stored authorization and refresh tokens as appropriate. Information already transmitted to QuickBooks, including accounting records, remains subject to Intuit's retention and deletion practices and the controls available in your QuickBooks account.
Tester-license records are retained only as reasonably needed to administer access, prevent abuse, support the beta program, and resolve licensing issues. To request access to, correction of, or deletion of information held directly by FieldOpsX, use the protected Support page after verification. We may need enough information to verify and locate the applicable record before acting on a request.
8. Children
FieldOpsX is a professional business application intended for users age 18 and over. It is not directed to children and is not designed for use by children.
9. Your choices
You can choose whether to enable optional integrations, whether to grant location and notification permissions, and whether to send or back up records to third-party services. Android settings can be used to revoke device permissions. You can disconnect optional integrations from FieldOpsX and/or the relevant service.
10. Changes to this policy
We may update this Privacy Policy when FieldOpsX features, integrations, legal requirements, or data practices change. The current version will be published at https://fieldopsxpro.com/privacy with its effective date.
11. Contact
FieldOpsX
Support contact: Protected Support page
Website: https://fieldopsxpro.com
