Skip to content
FieldScout

Security

How we protect your work.

We build and support FieldScout with a responsibility to keep protected work with the people authorized to use it. These safeguards cover account access, Individual and Agency Jobs, field devices, and payment handling. You can also contact us directly about a security concern.

Core safeguards

How we protect access and customer work.

FieldScout applies controls at the point where people sign in, open agency work, send requests, use source-backed features, or change paid access.

Access and identity

Who may access FieldScout and which actions they may perform.

Account and Agency isolation

In full FieldScouts, Individual accounts see only their own Jobs. Lite has no saved Jobs or results. Agency membership checks prevent one agency from opening another agency’s account, records, or billing information.

Roles and jurisdiction

Role checks limit sensitive actions, while jurisdiction checks keep program sources and workflows within the account’s assigned jurisdiction. Full or Lite access determines the tools and saving available to the account.

Authentication and recovery

Passwords are stored as one-way password hashes. Setup and recovery links are time-limited and single-use. A successful password reset invalidates outstanding password-recovery links.

Data and workflow boundaries

How requests, customer work, and source-backed features stay within their intended scope.

Browser and request safeguards

FieldScout checks requests before they change account data and verifies payment notifications before acting on them.

State-changing browser requests use cross-site request forgery (CSRF) protection. Signed webhooks verify incoming payment notifications. Rate limits, bounded sessions, secure production cookies, restrictive browser policies, and safe error pages reduce common request and browser risks.

Protected customer work

The complete service or property address remains inside authorized customer workflows and is excluded from public and unrelated operational surfaces. Prepared Field Visits temporarily retain protected information on the device for use through coverage loss. Job access is checked again before synchronization; conflicting edits are kept for review rather than silently overwriting the Job.

Reviewed guidance for your jurisdiction

In full U.S. FieldScouts, WAP Chat answers from reviewed guidance enabled for your account's jurisdiction. Document and page citations keep the original sources close to the answer.

Operations and trust

Checks before access, payment, and release.

We verify payment events, limit sensitive information in operational logs, and check the service before releasing changes.

01

Payment integrity

FieldScout sends a confirmed order to Stripe, verifies signed payment events, and prevents repeated events from granting duplicate access before changing paid access. FieldScout checkout does not collect raw card numbers.

02

Secrets and operational logs

Credentials, setup links, sessions, raw payment details, and protected customer identifiers are restricted from public pages, routine logs, unrelated telemetry, and review packages.

03

Production safeguards

Required service checks must pass before FieldScout releases an update. Operational monitoring helps us identify service failures affecting account access, billing, email delivery, and saved work.

Shared responsibility

Protect your account and your field devices.

  1. 01

    Use a separate login for each person

    Give each authorized person their own login and remove access when it is no longer needed. Protect field devices with a screen lock. An offline device cannot immediately learn that access has been revoked. Sync needed entries in every open field-work tab before signing out. Confirmed sign-out locks device access and removes local copies. If you confirm the discard warning, unsynced entries are removed too. Newer device work detected during sign-out is retained for recovery.

  2. 02

    Keep sensitive data in supported places

    Keep passwords, payment details, secrets, and unnecessary household identity out of email and unsupported fields.

Report a concern

Report a security concern directly.

Describe the affected page or workflow and what you observed. Do not send passwords, secrets, raw card details, or unnecessary household information.