EHM Operating System
EHM Operating System: Privacy and Google Data Use
Updated October 23, 2026

Purpose
EHM Operating System is a private internal operations application for Echo Hull Management. It organizes employee-role instructions, department work references, owner-assigned tasks, and execution records. The cockpit and business records require owner authentication.

Google spreadsheet access
The owner can authorize the Google Sheets read-only permission. Although Google's permission covers spreadsheets available to the connected account, this application's reader uses an owner-configured list of consolidated department workbooks. It reads the TASKS tab, including work-item identifiers, company scope, assignment descriptions, assignees, status, priority, source links, approval gates, and next steps. It does not edit Google spreadsheets, access Gmail, or access bank accounts through this connection.

RainSoft operational references
When the owner configures the RainSoft customer workbook, the spreadsheet reader also refreshes active customer and job references, including contact details, service addresses, source job status, and quote references. Synthetic test customers and closed jobs are excluded. These references are encrypted in the private database and shown only in the authenticated cockpit. Reading a reference does not create customer work, apply an approval, send a message, or change the original workbook. The owner may review a source job and explicitly create an internal assignment; only the assignment text and selected role instructions are then sent for an AI draft.

Optional RainSoft mailbox comparison
A separate owner authorization can enable Gmail read-only access for the configured RainSoft business mailbox. The comparison reader begins with the mailbox history at authorization time; it does not scan older mail. It checks headers of new messages to identify Smith call summaries, website contact notifications, and Housecall Pro estimate responses. It reads message bodies only for those recognized notification types. Recognized messages are parsed into encrypted reference records in the private database. Unrelated message bodies are not retrieved. Attachment APIs are not used, and attachment content is excluded from parsing and saved previews. Only opaque message identifiers and timestamps are retained for progress tracking for unrelated messages. This comparison does not send mail, modify labels, mark messages read, apply estimate approvals, create customer work items, or call AI. It uses a separate saved token from the department spreadsheet connection.

Use and storage
Spreadsheet references and capture timestamps are stored in the application's private PostgreSQL database on Railway and displayed in the authenticated cockpit. Scheduled refreshes update these references. Importing a reference does not create an assignment or perform the referenced action. Google authorization tokens are encrypted in the database, with the encryption key kept in the application's runtime configuration. The application uses a session cookie for owner authentication and records operational audit events.

AI drafting
When the owner assigns an AI planning task, the application sends the assignment text and the selected role's saved instructions to OpenAI to produce an internal draft. Role instructions may have been imported separately from owner-authorized documents. The automatic Google Sheets reader does not invoke AI or automatically send spreadsheet snapshots to OpenAI. Draft results remain in the authenticated work queue. Existing external business systems remain separate unless an integration is explicitly enabled.

Service providers and disclosures
Google supplies authorized spreadsheet data and separately authorized mailbox data; Railway hosts the application and database; OpenAI processes explicitly assigned AI drafts. These services process data under their own applicable terms. The application does not publish business records, sell Google user data, use it for advertising, or use it to develop or train generalized AI models. This application's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Retention and access removal
The application retains the latest saved snapshot for each configured workspace, role instructions, task results, mailbox comparison references, and audit records until the owner removes them. Refreshing a snapshot replaces the previous snapshot; it does not delete the original Google spreadsheet. The owner may disconnect each Google connection in the cockpit to remove its saved token and cancel pending authorization states. Disconnecting stops future authorized refreshes but does not erase previously saved references. Google permissions may also be revoked through the Google Account connections settings. Requests to remove retained application records can be sent to the owner at ibuildleaders@gmail.com. Deleted records may remain in any separately retained backups until those backups are removed.

Changes and contact
Any future change that expands Google data access or changes its purpose must be disclosed before that use is enabled. Questions about this private application or its retained records may be sent to ibuildleaders@gmail.com.