Effective August 28, 2026
This policy applies to the EPMOS public website at epmos.tech and to the Companion Factory Delivery OAuth client used for controlled Google Drive delivery qualification and governed delivery operations.
PRIVACY & DATA USE
Privacy Policy
This policy explains how the EPMOS public portal and the Companion Factory Delivery authorization path handle information and Google user data.
PUBLIC-SAFE · PRIVACY NOTICE
EFFECTIVE DATE
Governed use
EPMOS systems are designed around bounded authority, traceability, and human oversight. Access to Google services does not itself grant broader operational authority beyond the specific approved delivery purpose.
INFORMATION WE MAY HANDLE
Public website information
The public portal may receive information that a visitor voluntarily provides through an authorized contact or inquiry channel, such as a name, email address, organization, topic, or message. The site may also be served by infrastructure providers that process ordinary technical information needed to deliver web pages, such as IP address, browser information, request metadata, and security logs.
Google account information
When an authorized user grants Google OAuth access to Companion Factory Delivery, the application may receive basic authorization metadata and access tokens needed to use the approved Google API scope. Authentication credentials and tokens are used only to perform the authorized delivery function and are not intended for public display.
Google Drive data
The Companion Factory Delivery path is intended to create, read back, and verify governed delivery artifacts in the Google Drive location authorized for that purpose. Depending on the Google scope approved during qualification or production authorization, the application may technically be able to access more Drive content than it needs. EPMOS policy limits use to the approved delivery workflow and destination and does not authorize unrelated browsing, deletion, disclosure, or reuse of Drive content.
HOW INFORMATION IS USED
Authorized purposes only
Information is used to operate the public portal, respond to authorized inquiries, authenticate an approved user, deliver validated Companion Factory artifacts, verify delivery, preserve provenance and audit evidence, maintain security, and troubleshoot failures.
No sale of Google user data
EPMOS does not sell Google user data. Google user data is not used for advertising or unrelated profiling.
No unauthorized disclosure
Google user data is not intentionally disclosed to third parties except service providers acting as necessary infrastructure for the authorized function, when required by law, or when the user expressly authorizes the disclosure. Service providers may process data subject to their own contractual and security obligations.
STORAGE, SECURITY & RETENTION
Credentials and tokens
Long-lived credentials should not be placed in public source code or exposed in public logs. OAuth tokens and other secrets are to be stored only in approved secret-storage mechanisms and used only for their authorized purpose.
Retention
Delivery artifacts, receipts, audit records, and failure evidence may be retained when required for provenance, rollback, compliance, or governance. Authentication tokens are retained only as needed for the authorized workflow and according to the authorization method in use. Public inquiry information may be retained as reasonably necessary to respond, maintain records, or meet legal obligations.
Security limitations
No system can guarantee absolute security. EPMOS uses bounded-access and audit-oriented controls and preserves detected failures for repair and retesting rather than representing unverified security as complete.
USER CHOICES
Revoking Google access
An authorized user can revoke an application's Google Account access through Google's account security and third-party access controls. Revoking access may prevent further automated delivery until authorization is restored.
Questions and requests
Questions about this policy, access, correction, or deletion requests should be submitted through the published EPMOS contact channel on the Contact & Engagement page. Requests may be subject to identity verification, legal requirements, and preservation obligations for governed audit records.
GOOGLE API SERVICES DISCLOSURE
Google user data
The use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, to the extent those requirements apply to this application and its approved Google API scopes.
Scope discipline
The production authorization path should request only the Google API permissions necessary for the governed delivery function. Any expansion of scope requires separate review and authorization.
This policy describes public-safe privacy and data-use practices. It does not disclose protected formulas, private prompts, controlled source code, credentials, security topology, or Founder-Locked implementation mechanisms.