PEG privacy
Effective November 12, 2026. PEG (Project Execution Graph) is an invited-access project workspace for equipment, schedules, connections and field work. Contact James Holmes at 00jholmes@gmail.com with privacy or account questions.
Information used
PEG uses account names, email addresses, account identifiers and project permissions to sign users in and control access. It processes authorized equipment and schedule records, work status, notes, evidence-reference text, assignments and edit history. Changes are associated with the account that submits them. Do not enter sensitive information that is unnecessary for the project.
Purpose and access
Information is used to operate the project workspace, share authorized updates, maintain an audit history, support users and protect the service. Other authorized project participants and administrators may see submitted records. Google Cloud hosts the service and Cloudflare handles web requests. These services process requests and technical metadata such as network addresses, request times and error information to deliver and secure the service.
Device storage and synchronization
The iOS app stores downloaded project records, drafts and pending updates in its local database for field use. Its embedded browser manages sign-in sessions; the native equipment database does not store your password. Saved field updates remain local until synchronized and accepted. Planned-date changes require an online connection and become shared records when accepted. Transfers use HTTPS; local files use iOS sandboxing and file protection.
Signing out locks the account in the app and clears its browser session, but intentionally retains downloaded records and pending work for that account. It is not a data-erasure command. Removing the app can destroy unsynchronized work. Keep the app installed while updates are pending.
Retention and requests
Accepted changes remain in project revision and audit history. Project administrators manage access and recordkeeping. Contact the address above to request access, correction, account deactivation or deletion. Some project and audit records may need to be retained for operational, contractual or legal recordkeeping; a correction may be recorded as a new revision rather than erasing the original event. Do not send passwords or confidential documents in a support email.
Native permissions and beta feedback
The current iOS version does not request location, contacts, camera, microphone or photo-library access and contains no third-party advertising or analytics SDK. Apple operates TestFlight under its own terms and can provide beta feedback, screenshots and crash reports. Review feedback before sending it because screenshots or notes may contain project information.
Sample project
The sample sign-in uses a separate account limited to fictional equipment and schedules. It provides no company-directory or live-project access. Sample edits are stored on the service and visible to other authorized sample participants; enter fictional information only.