Use the data needed to provide the product—and no more than the work requires.

FieldScout uses information for public pages, agency access, billing, supported records, documents, product operation, and support. FieldScout does not sell user data.

Ask a privacy question Read Terms

Data categories

What supports the product, in plain language.

The exact information depends on the workflows an agency chooses to use.

Account: Names, work email addresses, usernames, roles, agency membership, and jurisdiction assignment support access and administration.
Billing: Agency, billing contact, subscription, invoice, billing cadence, quantity, and payment-status references support purchasing and account management.
Agency work: Projects, Saved Work, Building Files, work packets, field documentation, and supported tool records preserve work continuity.
Source documents: Approved documents, metadata, extracted page content, and processing state support source work for your agency's assigned jurisdiction.
Product use: Requested pages, product actions, and limited diagnostics help operate, secure, and improve FieldScout.
Operations: Security, payment-confirmation, delivery, readiness, error, and audit records support controlled operation.

Payment processor

Card details stay with Stripe.

Stripe processes checkout and billing-portal activity. FieldScout receives the payment and subscription references needed to confirm and operate the subscription, not raw card numbers.

Public and agency areas

Product information is public. Agency work is not.

Public pages explain FieldScout. Signed-in areas contain agency tools, records, documents, and billing management, with access checks intended to limit visibility to the appropriate agency and people.