FieldLedger
Field Compliance & Inspection Tools
Open demo →
LEGAL & DATA PROTECTION

Privacy Policy

Last updated: August 2026

1. Information We Collect

FieldLedger collects information required to deliver field service recording, asset barcode indexing, photo capture, and customer report compilation:

  • Account Credentials: Email address, business name, operator name, and authenticated user IDs.
  • Field Service Records: Equipment serial numbers, barcode data, inspection dates, technician observations, deficiency flags, and customer location identifiers.
  • Visual Evidence: Photographic records of fire extinguishers, kitchen hoods, and grease trap manifests uploaded by technicians.
  • Payment & Billing Data: Payment card details are entered directly into Stripe Checkout when billing is configured. FieldLedger does not store raw credit card numbers.

2. How We Use and Protect Your Data

Your data is used solely to provide, maintain, and secure the FieldLedger service. Organization membership and role checks are implemented in database rules and server operations. Local tests cover cross-workspace denial; production enforcement still requires deployed acceptance.

We never sell, rent, or monetize your customer lists, equipment records, or service inspection histories.

3. Third-Party Subprocessors

The candidate uses the following providers. The responsible owner must verify production configuration, data locations and applicable provider agreements before customer onboarding:

  • Google Cloud Platform & Firebase: Hosting, database storage, photo storage, and authentication. Production data locations have not yet been verified.
  • Stripe Inc.: Payment processing, customer portal, and recurring billing.

4. GDPR, CCPA / CPRA, and Consumer Rights

Subject to applicable privacy legislation, you have the right to request access to, correction of, export of, or deletion of your personal and business records. Data export is available in standardized formats directly within your account console. A monitored privacy contact must be published by the responsible owner before customer onboarding.

5. Data Retention & Offline Storage

The fictional demonstration stores its sample workspace as readable browser data on the device and does not synchronize it to a production account. Do not enter real customer or inspection information in demo mode. Production-mode records use the configured Firebase services. An owner can request workspace deletion after billing ends. The application disables the workspace and schedules deletion after seven days. Backup retention, provider retention and a monitored request channel must be confirmed before customer onboarding. Device drafts and pending photos remain local until uploaded; signing out clears them.