Use only what the service needs. Keep agency work inside authorized workflows.

FieldScout processes account, billing, source, and customer-work information to operate the product, support your agency, and protect the service. FieldScout does not sell user data.

Ask a privacy question Read Terms

Effective and last updated: September 1, 2026

What FieldScout uses

Only the information needed to operate the service.

The exact information depends on the workflows your agency chooses. Each category supports a specific product, administrative, billing, support, or security purpose.

Account and agency: Names, work email addresses, usernames, roles, agency membership, agency contact and service-address details, jurisdiction assignment, timezone, and account status support access and administration.
Billing: Billing contact, subscription, invoice, cadence, purchased-user quantity, Stripe customer and subscription references, payment status, and consent records support purchasing and account management.
Customer work and field data: Jobs, Standalone Work, Job Work Packets, notes, observations, measurements, photographs, supported tool inputs and results, and review history preserve work continuity. Authorized workflows may include the client last name and the complete service or property address needed to identify the job.
Source data: Approved source documents, source metadata, extracted page content, verification state, and processing records support jurisdiction-scoped Field Documents and source-backed workflows.
Support and communications: Support requests, business correspondence, safe screenshots, and the operational context an agency chooses to provide support troubleshooting, purchasing, and rollout.
Security and technical: Authentication, session, request, audit, payment-confirmation, email-delivery, readiness, error, browser, device, and limited product-use diagnostics help operate, protect, and improve the service.

Why information is processed

Three clear reasons—and no hidden business model.

FieldScout uses information to deliver the product, protect the service, and improve supported workflows. FieldScout does not sell user data.

Provide and administer FieldScout

Create accounts and agency access, deliver requested workflows, preserve authorized work, process subscriptions, provide support, and communicate about the service.

Protect the service

Authenticate users, enforce agency, role, and jurisdiction boundaries, prevent misuse, investigate operational or security issues, and preserve necessary audit history.

Maintain and improve

Diagnose failures, understand bounded product use, maintain source processing, and improve supported workflows without using protected customer identifiers in broad analytics.

Payment boundary

Your 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

Public product information stays public. Agency work does not.

Protected customer-work identifiers remain inside authorized workflows. FieldScout excludes client last name and complete service or property address from public surfaces, broad analytics, generic logs, unrelated telemetry, owner aggregate dashboards, cross-tenant exports, unrelated feedback, and production-derived fixtures.

How information is handled

Clear rules across access, records, and change.

These practices explain how FieldScout handles information after collection without turning the policy into a wall of legal text.

Access and service

Who may use protected information and which systems support the service.

Agency access and isolation

Authorized agency administrators manage workforce access. Agency, role, object, and jurisdiction checks limit who can open or change protected records. One agency does not receive another agency's customer work.

Service providers

FieldScout may use hosting, storage, monitoring, email-delivery, and other operational providers to process information only for providing and protecting the service. Google Workspace is intended for FieldScout business communications when configured.

Cookies and sessions

FieldScout uses essential cookies and session technology for sign-in, security, request integrity, and continuity. Public marketing pages do not require an advertising-cookie program.

Records and lifecycle

How information is retained, exported, corrected, deleted, or handled after termination.

Retention

FieldScout retains information for the period needed to provide the service, preserve required account, billing, audit, security, provenance, and customer-work history, resolve disputes, and meet applicable obligations. Retention depends on the record and agency workflow; this policy does not state a fixed period.

Export, correction, and deletion

Agency administrators are responsible for appropriate access and record-management requests for their workforce and agency work. Authorized requests may be sent to the privacy contact. Export or deletion may be limited by identity verification, agency authority, immutable history, security, billing, legal, or technical requirements.

Termination

After termination, agencies remain responsible for timely export of needed records. FieldScout may retain or delete information under the applicable service, storage, audit, security, and legal requirements; termination does not guarantee immediate deletion of every record.

Communications and policy

How FieldScout handles incidents, professional use, children’s privacy, and policy changes.

Incident communications

FieldScout uses available agency and account contact information for security or service communications when notice is appropriate. This policy does not promise a particular incident-notice deadline.

Professional use and children’s privacy

FieldScout is offered to agencies and their authorized workforce for professional Weatherization work. It is not directed to children and is not intended for personal consumer accounts.

Policy changes

FieldScout may update this policy as the service and its processing change. The public policy will show the effective and last-updated date, and material operational changes may also be communicated through available business contact channels.

Privacy rights and agency administration

Start with your agency administrator.

Depending on applicable law and the agency relationship, a person may ask to access, correct, export, or delete information. FieldScout does not promise rights that do not apply. Agency administrators validate authority and manage workforce and agency-record requests.