Privacy Policy

Information covered

This policy is intended to cover (1) information submitted through the public website (demo and support requests), (2) account and operational data processed through the customer application, and (3) technical information needed to operate and protect the service (logs, device, and security events).

Customer data ownership

Company workspaces are multi-tenant and isolated. Operational records — including people, equipment, projects, safety files, inspections, and uploaded photos — belong to the customer company that created them. River Parish Operations does not use customer operational data to train public models or to market to other customers.

Customers control who in their company can access records. Administrators may offboard users, which deactivates login and revokes unused invitations.

Export and deletion

Company administrators and platform operators can export company records (JSON packages and verified backups). A restore dry-run can be run against a backup without writing live data. After a company is archived or the agreement ends, remaining copies follow the backup retention schedule, then deletion, except where law requires a longer hold.

How information may be used

Information may be used to respond to demo or support requests, provide and improve the service, administer accounts and billing, send transactional email or SMS (invites, password resets, safety alerts), protect the platform, and meet legal obligations.

Electronic records and signatures

Some workflows store electronic acknowledgements or signatures. Those records are customer operational data. See the Terms of Service ESIGN / Louisiana section for the counsel review placeholder covering legal effect.

Service providers

Hosting, authentication, email, SMS, backups, and (when configured) payment processing may be provided by vetted vendors. Stripe, if enabled, processes subscription billing data; card numbers are not stored in the River Parish Operations database.

Retention and security

Retention periods for website requests, customer records, backups, and logs should be finalized with counsel. Administrative, technical, and organizational safeguards are used to protect information. No system is completely secure.

Choices and contact

Authorized company administrators can update profile data, export records, and request deletion of a workspace through support. Individual end-user rights depend on the customer’s role as the data controller for their employees and contractors.