App information · Privacy · Terms
Foreman V2 Privacy Policy
Version dated October 27, 2026
Scope and operator
FLX Business Services LLC operates Foreman V2, identified in Google’s authorization settings as FLX Foreman Operating. This policy covers the application and its Google connection, not all activities of FLX’s general website or unrelated services. Steve Clapp is the responsible contact for privacy and deletion requests at flxbizserv@gmail.com.
Information and purpose
The pilot reads a minimized operational-status packet, work instructions and controls from three approved Drive files. The packet uses coded references and excludes client names, identity mappings, transaction details, full source documents and email bodies; it remains client-derived information. The app also handles file and account information needed for its connection, authorization credentials, generated drafts and technical records such as run identifiers, timestamps, hashes, file references, usage counters and outcomes. It uses this information for approved internal workflows, draft generation, saving and verifying outputs, preventing duplicate work and diagnosing failures. Its drive.file permission applies to eligible individual files, not general access to all Drive files.
Service providers and access
Google provides authorization and Drive storage. DigitalOcean runs the workflow and processes its inputs, prompts and outputs, with runtime credentials and technical logs. The OpenAI API receives the minimized packet and instructions to generate drafts. GitHub stores code and technical journals in a private repository; journals are designed to contain verification records, not source documents or draft bodies. Healthchecks.io and Pushover support operational monitoring and alerts for FLX. Monitoring uses technical status information rather than business documents. FLX and people with authorized access to the relevant service accounts may handle these records for operation, review and support.
Limits on use
FLX does not sell Google-derived data, use it for advertising or use it to train general-purpose AI models. FLX’s use of information received from Google APIs will adhere to the Google API Services User Data Policy and applicable Google Workspace policies, including Limited Use requirements. At the October 27, 2026 settings review, OpenAI organization sharing for API inputs and outputs, feedback, and evaluation or fine-tuning data was disabled. This is a current configuration statement, not a guarantee about historical settings or zero provider retention.
Retention
The pilot does not automatically delete Drive outputs, technical journals or locally retained evidence. FLX reviews retention manually: working records are kept while needed for the approved workflow, and qualification evidence while needed for reconciliation and review. Records no longer needed are reviewed for deletion, subject to applicable obligations and technical limitations. OpenAI requests use store=false, but the project uses standard retention, not zero-data-retention controls. Provider logs, backups and retained copies may remain subject to the relevant provider’s retention rules. Stopping the app does not erase existing records.
Stopping access and requesting deletion
You can revoke the Google connection through your Google Account’s third-party connections settings to stop future access. Revocation does not delete files or records already created. To identify app-created records or request deletion, email flxbizserv@gmail.com with enough non-secret detail to identify the relevant records. Steve Clapp will review the request, confirm authority before acting, identify the affected stores and explain any retention or provider limitations. Deletion is handled manually; FLX does not promise immediate removal from all provider logs, backups or historical copies. Do not email passwords or tokens.
Protection and changes
The workflow uses selected-file controls and stops when required checks fail. Credentials must not be included in support messages. No service is risk-free, and this policy is not a security certification. FLX will update these disclosures when data practices change and obtain any required additional consent before a new use begins.
Policy references: Google API Services User Data Policy; Google Workspace policies; OpenAI API data controls.
FLX Business Services LLC · flxbizserv@gmail.com