Last Updated: August 6, 2026
Operator: Pocket Robot Inc.
This Privacy Policy (the “Policy”) explains how Pocket Robot Inc. (“Pocket Robot,” “we,” “us,” or “our”) collects, uses, discloses, retains, and protects personal information in connection with the FieldOps website, web application, mobile applications, application programming interfaces, support channels, trial and pilot programs, Managed Services, and related offerings collectively referred to as the “Services.”
This Policy should be read together with the FieldOps Terms of Service, any applicable Order Form, Data Processing Addendum, and notices shown when information is collected. Where a Customer uses FieldOps for its employees, contractors, project contacts, or other individuals, the Customer may have its own privacy obligations and policies that also apply.
Privacy at a glance
- We do not sell personal information.
- FieldOps normally operates on shared multi-tenant infrastructure with logical tenant separation unless a dedicated environment is expressly agreed.
- Precise location is collected only when device permission is granted and a location-enabled feature is used or otherwise clearly disclosed.
- The mobile application is not used for third-party advertising or cross-app tracking.
- Customers control the project and workforce information they submit, and Pocket Robot generally processes that information to provide the Services.
The summary above is provided for convenience. The complete Policy below governs our privacy practices.
1. Scope and Application
1.1 This Policy applies to personal information collected through the Services, including through our public website, free-trial and subscription forms, FieldOps web and mobile applications, APIs, support channels, sales and onboarding communications, Managed Services requests, pilot projects, and Enterprise engagements.
1.2 “Personal information” means information about an identifiable individual, as defined by applicable law. It does not include business contact information where applicable law excludes that information, or information that has been aggregated or de-identified so that it can no longer reasonably identify an individual.
1.3 This Policy applies to Pocket Robot’s handling of personal information. It does not govern the independent privacy practices of a Customer, third-party website, app store, identity provider, payment processor, mapping provider, or other third party.
1.4 The Services are intended for business use and are not directed to children. See Section 21.
2. Our Role and the Customer’s Role
2.1 Pocket Robot is accountable for personal information that we collect and control directly, such as website inquiries, trial registrations, account administration information, billing records, support communications, security logs, and marketing preferences.
2.2 For project, workforce, property, assignment, location, photograph, document, and other information submitted to FieldOps by or for a Customer (“Customer Data”), the Customer generally decides why the information is collected and how it is used. Pocket Robot generally processes that information to provide the Services, perform requested Managed Services, maintain security, and follow the Customer’s lawful instructions.
2.3 Customers are responsible for providing required notices and obtaining any consent or other lawful authority needed to submit and use personal information in FieldOps, including information relating to employees, contractors, property owners, residents, project contacts, utility representatives, and other individuals.
2.4 A Customer Administrator may be able to view or manage Authorized Users, project activity, assignments, audit events, uploaded files, and other Customer Data according to the Customer’s configuration and permissions. Individuals should direct questions about their organization’s use of FieldOps to that organization.
2.5 Where an Enterprise Order Form or Data Processing Addendum assigns different privacy roles or obligations, that document applies to the extent of the inconsistency.
3. Personal Information We Collect
3.1 Account, Trial, and Contact Information
We may collect:
- Name, work email address, company name, job title or business role, telephone number, mailing address, and communication preferences;
- Information submitted through trial, demo, contact, sales, onboarding, support, survey, and feedback forms; and
- Records of service-related and marketing communications.
3.2 Account and Tenant Information
We may collect:
- Internal user, company, tenant, project, assignment, and request identifiers;
- Username, authentication status, role, permissions, invitation and activation records, and account status;
- Subscription plan, entitlements, limits, trial dates, billing status, and Enterprise agreement information; and
- Administrative actions, access history, audit events, and impersonation or support-access records.
3.3 Billing and Transaction Information
We may collect:
- Billing contact name, company name, email address, billing address, tax information, exemption information, invoice and transaction records, payment status, and payment-processor customer or subscription identifiers;
- Limited payment-method information returned by the payment processor, such as card brand, expiry month and year, and last four digits; and
- Pocket Robot does not store full payment-card numbers or card security codes on its own systems.
3.4 Mobile Application and Device Information
When the FieldOps mobile application is used, we may collect:
- Device model, operating-system version, application version, language, time zone, network status, and device or installation identifiers;
- Push-notification tokens and notification preferences;
- IP address, session information, authentication tokens, request identifiers, and technical logs;
- Photos, videos, documents, drawings, spreadsheets, and other files selected for upload, including metadata contained in those files; and
- Project records, map features, notes, assignments, measurements, task statuses, forms, reports, and other data created or changed in the application.
3.5 Location and Map Information
We may collect:
- Precise or approximate device location when permission is granted and a location-enabled feature is active or when collection is otherwise clearly disclosed;
- Coordinates chosen, entered, imported, or generated for map features and project records;
- Map viewport, project area, and geospatial interaction information needed to provide map functionality; and
- Location permission status and related device settings.
3.6 Project, Managed Services, and Customer Content
We may process:
- Project names, addresses, property information, coordinates, drawings, locates, photographs, notes, reports, quantities, due dates, contact details, and operational records submitted by a Customer;
- Information included in Managed Services drafts, requests, supporting documents, communications, quotations, and completed deliverables;
- Information Pocket Robot creates or enters on a Customer’s behalf while providing Managed Services; and
- Activity in fictional demo projects, which may be used to record onboarding progress but must not be used for real field operations.
3.7 Support and Administrative Access Information
We may collect:
- Support requests, emails, chat messages, troubleshooting details, screenshots, screen recordings, and attachments supplied to us;-
- Records showing when authorized Pocket Robot personnel accessed or impersonated a Customer environment for support, security, onboarding, billing, or Managed Services; and
- Diagnostic context reasonably needed to investigate an issue, which may include user, company, project, feature, attachment, route, or request identifiers.
3.8 Diagnostic, Performance, and Security Information
We may collect:
- Crash reports, application errors, stack traces, API latency, screen or route performance, failed requests, and service-availability metrics;
- Browser type, operating system, IP address, user agent, timestamps, session events, and authentication events;
- Security events, rate-limit events, suspected abuse, cross-tenant access attempts, malware indicators, and audit logs; andLimited contextual information needed to reproduce, diagnose, secure, or resolve a problem.
3.9 Website, Cookie, and Marketing Information
We may collect:
- Pages viewed, referral source, links or buttons selected, form interactions, campaign identifiers, browser and device information, IP address, and cookie or similar identifiers;
- Cookie consent and advertising preferences; and
- Events shared through approved website analytics or advertising tools, including Meta Pixel where enabled and permitted.
3.10 Integration and API Information
We may collect or process:
- Information received from or sent to identity providers, mapping providers, cloud-storage providers, payment processors, app stores, Customer-authorized integrations, and other service providers;
- API keys, integration identifiers, scopes, webhook records, and synchronization logs; and
- Contact and directory information received from a Customer-authorized identity or business system.
4. How We Collect Personal Information
4.1 We collect personal information directly from individuals when they register, subscribe, sign in, use the Services, permit device access, upload content, submit a form, communicate with us, or participate in a trial, pilot, survey, or Managed Services engagement.
4.2 We collect information from Customers and Customer Administrators when they invite users, assign roles, import data, provide project documents, create assignments, or request that Pocket Robot configure or maintain their environment.
4.3 We collect information automatically from browsers, devices, applications, APIs, cookies, logs, and diagnostic tools when the Services are accessed or used.
4.4 We may receive information from service providers and integrations, including identity providers, payment processors, app stores, mapping services, analytics providers, and Customer-authorized systems.
4.5 We may generate information from existing records, such as calculated workflow status, usage summaries, risk or fraud indicators, project metrics, and aggregated service telemetry.
5. How We Use Personal Information
5.1 We use personal information only for purposes that are identified, reasonably expected in the circumstances, permitted by law, or authorized by the individual or Customer.
These purposes include:
- Creating, verifying, administering, and securing accounts and Customer environments;
- Providing web, mobile, API, mapping, assignment, file, spreadsheet, reporting, notification, and other FieldOps functionality;
- Processing Customer Data and performing requested Managed Services;
- Authenticating users, applying roles and permissions, and maintaining tenant separation;
- Processing subscriptions, payments, invoices, taxes, exemptions, refunds, and plan entitlements;
- Providing support, troubleshooting issues, responding to requests, and communicating service information;
- Sending security, billing, account, operational, maintenance, and legal notices;
- Operating free trials, demo projects, onboarding checklists, and product tours;
- Monitoring availability, performance, security, fraud, abuse, and compliance;
- Debugging, testing, backing up, restoring, and improving the reliability, usability, and scalability of the Services;
- Creating aggregated or de-identified analytics, capacity forecasts, and product insights;
- Evaluating sales, trial, onboarding, and marketing effectiveness where permitted;
- Enforcing agreements, protecting rights and safety, resolving disputes, and complying with legal obligations; and
- Carrying out another purpose disclosed at collection or authorized by law.
5.2 We do not sell personal information. We do not use precise mobile location or Customer project data for cross-app advertising.
6. Consent, Choices, and Other Permitted Authority
6.1 Where consent is required, we seek consent that is appropriate to the sensitivity of the information and the proposed use. Consent may be express or implied where permitted by law.
6.2 Certain information is necessary to create an account, authenticate users, provide requested functionality, maintain security, process payment, or comply with law. If that information is not provided, some or all Services may be unavailable.
6.3 Optional collection or use, such as marketing communications, testimonials, non-essential advertising cookies, device permissions, or certain feedback activities, is subject to a separate choice where required.
6.4 An individual may withdraw consent to an optional use at any time, subject to legal or contractual restrictions and reasonable notice. Withdrawal does not affect processing already lawfully completed and may limit available functionality.
6.5 We may collect, use, or disclose information without consent where permitted or required by applicable law, including for security, fraud prevention, debt collection, investigations, emergencies, legal proceedings, or compliance with lawful demands.
7. Multi-Tenant and Dedicated Environments
7.1 Unless an applicable Order Form states otherwise, FieldOps is delivered through a multi-tenant architecture. Application, database, storage, computing, network, monitoring, and other resources may be shared among multiple Customers.
7.2 Pocket Robot uses logical tenant identifiers, access controls, role and project permissions, tenant-scoped queries, private storage paths, and related safeguards designed to separate Customer Data from data belonging to other Customers.
7.3 Authorized Pocket Robot personnel may temporarily enter or impersonate a Customer environment where reasonably necessary for support, security, onboarding, billing administration, data migration, or requested Managed Services. Access is limited to authorized purposes and may be logged.
7.4 A dedicated application, database, storage account, region, mobile application variant, private network, encryption arrangement, or release schedule applies only where expressly stated in an Enterprise Order Form or other written agreement.
7.5 Information from one Customer is not used to provide another Customer with identifiable project, user, or operational data. Aggregated or de-identified service insights may be used as described in Section 13.
8. When We Disclose Personal Information
8.1 Service Providers and Subprocessors
We disclose personal information to service providers that help operate the Services, including providers of:
- Cloud hosting;Databases and storage;
- Content delivery;
- Identity and authentication;
- Email and push notifications;
- Mapping and geocoding;
- Payment processing;
- Customer support;
- Diagnostics and monitoring;
- Security;Backup;
- Communications; and
- Analytics.
These providers are permitted to process information only for authorized services and are subject to contractual, technical, or organizational safeguards appropriate to their role.
A current subprocessor list may be made available through our website, security documentation, or on reasonable request.
8.2 Customers and Authorized Users
Information may be visible to the Customer and Authorized Users according to their roles, project access, assignment, and administrative permissions.
Customer Administrators may receive account, usage, audit, security, billing, and support information concerning their Customer environment.
8.3 Customer-Authorized Integrations
We disclose information when a Customer enables an integration, requests an export, uses an API, connects an identity provider, or otherwise instructs us to transmit information to another service.The receiving third party’s own terms and privacy practices apply after the information is transmitted.
8.4 Legal, Safety, and Enforcement Disclosures
We may disclose information:
- Where required by law, court order, subpoena, warrant, regulatory demand, or other lawful process;
- To investigate or prevent fraud, abuse, unlawful conduct, security incidents, or threats to rights, property, health, or safety;
- To enforce our agreements, collect amounts owed, establish or defend legal claims, or obtain professional advice; or
- To notify appropriate organizations or individuals of a security incident where permitted or required.
8.5 Business Transactions
Personal information may be reviewed or transferred as part of a proposed or completed financing, merger, acquisition, reorganization, sale of assets, insolvency process, or similar transaction, subject to appropriate confidentiality and legal protections.
8.6 With Consent
We may disclose personal information for another purpose with valid consent or at the individual’s direction.
9. Payment Processing
9.1 Subscription payments are processed by Stripe or another payment processor identified at checkout. Payment-card details are submitted directly to the payment processor and are governed by that provider’s privacy terms.
9.2 Pocket Robot may receive billing contact information, payment status, invoice details, tax information, fraud or risk signals, and limited payment-method details, but does not store full payment-card numbers or card security codes on its own systems.
9.3 We use billing and transaction information for payment processing, subscription management, invoicing, refunds, tax compliance, fraud prevention, accounting, audits, and legal recordkeeping.
10. Cookies, Website Analytics, and Advertising
10.1 Essential Technologies
We use essential cookies and similar technologies for authentication, session continuity, security, load balancing, preference storage, form protection, and core website functionality.
Disabling essential technologies may prevent the website or Services from functioning.
10.2 Analytics and Performance
We may use analytics and performance technologies to understand website traffic, page use, form completion, errors, and campaign effectiveness.
Where required, non-essential analytics technologies are activated only after appropriate notice or consent.
10.3 Meta Pixel and Advertising
Our public marketing website may use Meta Pixel or similar advertising technologies to measure conversions, understand campaign performance, and deliver or assess advertising on third-party platforms.
These technologies may collect or receive:
- Page visits;
- Actions taken on the website;
- Browser and device information;
- IP address;
- Campaign information; and
- Cookie or similar identifiers.
The third-party provider may process that information under its own privacy terms.
Where required, we seek consent before activating non-essential advertising technologies.
Users can change available cookie choices, use browser controls, and use advertising-preference tools provided by the relevant platform.
10.4 Mobile Application
At the date of this Policy, the FieldOps mobile application does not use third-party advertising cookies, advertising SDKs, or cross-app tracking technologies. We do not use precise mobile location for advertising.
10.5 Cookie Choices
Cookie and tracking choices may be managed through our cookie banner or preference centre where available, browser settings, device settings, and third-party advertising controls.
Blocking cookies may affect functionality.
11. Marketing and Service Communications
11.1 We send service-related messages needed to administer the Services, including activation, invitation, authentication, security, billing, trial, maintenance, support, project, assignment, and legal notices. These messages are not optional where they are necessary to provide the Services.
11.2 We send promotional email, text, or similar commercial electronic messages only where we have consent or another lawful basis. Marketing messages include required sender identification and an unsubscribe mechanism where applicable.
11.3 Unsubscribing from marketing does not stop service-related communications. Marketing preferences may take a reasonable time to process, and records of consent and unsubscribe requests may be retained for compliance.
11.4 Testimonials, public case studies, and public use of a Customer’s name or logo require consent or an applicable written agreement.
12. Location, Workforce, and Field Information
12.1 FieldOps may use device location to show the user’s position, centre the map, place or update a map feature, assist with field navigation, or support another location-enabled function. The app requests device permission before accessing location.
12.2 Location collection depends on the feature used, device permissions, application state, and settings. We do not represent that device location is continuous unless the relevant feature and permission notice expressly state that it is.
12.3 Location, timestamps, assignments, audit events, uploaded photographs, and project activity may be visible to a Customer or Customer Administrator according to permissions. A Customer is responsible for deciding whether and how these functions are used with its workers and for providing required workplace notices or obtaining required consent.
12.4 Customers must not use FieldOps for covert, unlawful, discriminatory, or disproportionate monitoring. FieldOps is not intended to be an employee-surveillance or emergency-tracking system.
12.5 GPS, device sensors, maps, imagery, geocoding, and user-entered coordinates may be inaccurate or unavailable. Location data must be independently verified before excavation, drilling, plowing, construction, safety, emergency, surveying, utility, or other operational reliance.
13. Aggregated, De-Identified, and Statistical Information
13.1 We may create and use aggregated or de-identified information that does not reasonably identify an individual, Authorized User, or Customer.
13.2 We may use that information for security analysis, service analytics, capacity planning, reliability improvement, benchmarking, product development, research, and business operations.
13.3 We take reasonable steps not to re-identify de-identified information except where necessary to test de-identification, protect security, or as permitted by law.
14. Artificial Intelligence and Automated Tools
14.1 Pocket Robot may use automated tools to assist with software development, security, diagnostics, support, data import, document processing, or other service functions. Any use involving personal information remains subject to this Policy, applicable agreements, and appropriate access controls.
14.2 We do not sell Customer Data or use Customer Data to train a general-purpose artificial-intelligence model for unrelated third-party purposes without the Customer’s express written agreement.
14.3 If FieldOps introduces an optional AI-enabled product feature that materially changes how personal information is collected, used, or disclosed, we will provide additional notice and obtain consent where required.
15. Cross-Border Processing
15.1 Pocket Robot and its service providers may process or store personal information in Canada, the United States, or other jurisdictions used to deliver the Services.
15.2 When information is transferred to a service provider in another jurisdiction, Pocket Robot remains accountable for personal information under its control and uses contractual, technical, and organizational measures designed to provide appropriate protection.
15.3 Information processed in another jurisdiction may be accessible to courts, law-enforcement agencies, regulators, or national-security authorities under the laws of that jurisdiction.
15.4 A Canadian-only region, dedicated infrastructure, customer-managed key, or other location-specific commitment applies only if expressly stated in an Order Form or Data Processing Addendum.
16. Security Safeguards
16.1 We maintain administrative, technical, and physical safeguards designed to protect personal information against loss, theft, unauthorized access, disclosure, copying, use, alteration, or destruction.
16.2 Depending on the information and system, safeguards may include:
- Authentication controls;
- Role and project permissions;
- Tenant-scoped authorization;
- Encryption in transit;
- Private storage;
- Logging and monitoring;
- Backups;
- Vulnerability management;
- Secure development practices;
- Incident response; and
- Personnel confidentiality obligations.
16.3 Access by Pocket Robot personnel and service providers is limited to authorized purposes and is based on role, operational need, and applicable contractual obligations.
16.4 No electronic system, method of transmission, or storage technology is completely secure. Customers and users are responsible for protecting credentials and devices, using supported software, assigning appropriate permissions, and promptly reporting suspected unauthorized access.
17. Security Incidents
17.1 We maintain processes to identify, investigate, contain, document, and respond to suspected or confirmed security incidents involving personal information.
17.2 Where required by applicable law, we will notify affected individuals, Customers, regulators, or other organizations of a breach of security safeguards. Notifications may include information about the incident, affected information, mitigation steps, and measures individuals can take to reduce risk.
17.3 Where Customer Data is involved, we will reasonably cooperate with the Customer regarding investigation, mitigation, and legally required notifications, subject to the parties’ roles and applicable agreements.
17.4 We maintain records of breaches of security safeguards for the period required by applicable law, including at least 24 months where the federal Breach of Security Safeguards Regulations apply.
18. Retention and Deletion
18.1 We retain personal information only for as long as reasonably necessary for the purposes described in this Policy, to provide the Services, follow Customer instructions, maintain security and continuity, resolve disputes, enforce agreements, and comply with legal, tax, accounting, and regulatory obligations.
18.2 Retention depends on the type of information and context.
In general:
- Account and Customer Data are retained while the Customer Account is active and during any post-termination export or retention period described in the Terms of Service or Order Form;
- Trial and demo information may be removed after the trial, after inactivity, or when the demo is reset;
- Billing, tax, contract, and transaction records are retained for legally required accounting and recordkeeping periods;
- Security, audit, diagnostic, and support records are retained for periods appropriate to security, troubleshooting, compliance, and dispute resolution;
- Marketing consent and unsubscribe records may be retained to demonstrate compliance;
-Security incident records are retained for legally required periods; and
-Backups may retain residual copies until overwritten or deleted through normal backup-rotation processes.
18.3 When information is no longer required, we delete, anonymize, or securely dispose of it, subject to backup limitations, legal holds, security requirements, and technical constraints.
18.4 Customer Administrators may delete or modify Customer Data according to their permissions. Pocket Robot is not responsible for authorized deletion or modification by a Customer or Authorized User.
19. Access, Correction, Withdrawal, and Other Privacy Rights
19.1 Subject to applicable law, an individual may request:
- Access to personal information Pocket Robot controls about them;
- Information about how it has been used and disclosed; and
- Correction of inaccurate or incomplete information.
19.2 Depending on the applicable law, an individual may also request deletion, restriction, withdrawal of consent, a copy in an available format, or another privacy right.
19.3 We may require identity verification and enough information to locate the relevant records. We may deny or limit a request where permitted or required by law, including where disclosure would reveal:
- Another person’s personal information;
- Confidential commercial information;
- Privileged information;
- Security-sensitive information; or
- Information subject to a legal restriction.
19.4 Withdrawing consent may prevent us from providing a feature or the Services where the information is necessary for that purpose.
19.5 Requests may be submitted to the Privacy Officer using the contact information in Section 24. We aim to respond within the period required by applicable law.
20. Requests Concerning Customer-Controlled Data
20.1 If personal information was submitted to FieldOps by an employer, contractor, municipality, utility, or other Customer, that Customer may control the information and be responsible for responding to access, correction, deletion, or workplace-privacy requests.
20.2 We may direct the individual to the relevant Customer and will assist the Customer as required by applicable law and the applicable agreement.
20.3 A user who leaves a Customer organization may lose access to the Customer Account. The Customer, not the departing user, generally controls project records and business data created for the Customer.
21. Children and Minors
21.1 The Services are intended for business users who are at least 18 years old and are not directed to children.
21.2 We do not knowingly collect personal information directly from children through public trial or account registration. If we learn that a child has submitted personal information without appropriate authority, we will take reasonable steps to delete or restrict it.
21.3 Customers must not create accounts for minors or submit information about minors unless legally permitted, necessary for a legitimate business purpose, and expressly supported by the Services and applicable agreement.
22. Third-Party Sites, App Stores, and Services
22.1 The Services may contain links to or depend on third-party websites, app stores, operating systems, identity providers, mapping services, payment processors, or integrations.
22.2 Those third parties may independently collect and process information under their own privacy policies. Pocket Robot is not responsible for their independent privacy practices.
22.3 Users should review the privacy settings and policies of third-party services they choose to use with FieldOps.
23. Changes to This Policy
23.1 We may update this Policy to reflect changes to the Services, technology, law, providers, or privacy practices. The revised Policy will display a new “Last Updated” date.
23.2 We will provide reasonable notice of material changes through email, an in-product notice, our website, or another appropriate method before the changes take effect, except where immediate changes are required for law, security, or prevention of harm.
23.3 Where a material change requires new consent, we will seek that consent before applying the change to affected information.
24. Contact, Privacy Officer, and Complaints
24.1 Pocket Robot has designated a Privacy Officer responsible for overseeing our privacy program and responding to privacy questions and requests.
24.2 Questions, requests, and complaints may be directed to:
Organization: Pocket Robot Inc.
Mailing Address: 319 Dumaine Road, Ile Des Chenes, MB, Canada
Support Email: [info@pocketrobot.ca]
Privacy Officer: Dylan Eggleston
24.3 Please include enough information for us to understand the request, but do not send passwords, full payment-card numbers, or unnecessary sensitive information by email.
24.4 We will investigate privacy complaints and respond in accordance with applicable law. If an individual is not satisfied with our response, they may have the right to contact the Office of the Privacy Commissioner of Canada or the applicable provincial, territorial, or international privacy regulator.