Life Journey Sources

Privacy policy

How connected documents become private, source-based context.

Last updated: 11 September 2026.

Information processed

When the owner connects Google Drive, Life Journey Sources reads account identity, accessible file metadata and supported document contents. File metadata includes titles, identifiers, modification dates, versions, file types and download permissions. Connection credentials are used to maintain the authorized read-only connection.

The owner may separately submit selected PDFs through the private DukeOS Telegram bot. That path processes the submitted file, caption and the identifiers needed to receive and acknowledge it.

Use and storage

The app retains supported originals or exported document snapshots and derives searchable text locally, including bounded optical character recognition where available. Source copies, extracted text and source history are stored in the owner’s private storage and protected by authenticated application access. Backups retain copies for recovery.

When the owner uses Life Journey chat, relevant bounded text excerpts may be sent to OpenAI to generate a response. File bytes and connection credentials are not included in that text projection. Processing by a model provider is also subject to that provider’s terms and the owner’s account settings. The app does not sell document data or use it for advertising.

Custom-domain access

When the owner accesses Life Journey through its custom domain, Cloudflare provides sign-in checks and traffic delivery. Cloudflare processes the login email and the application requests and responses carried through that connection, including chat content. Only the owner’s approved identity is allowed to reach the private application.

Access changes and retention

The owner can revoke Google access through Google Account permissions and disable collection in the private application configuration. Files found to be removed or inaccessible are withdrawn from current document retrieval during synchronization.

Revoking access does not automatically erase previously retained source copies, saved conversations or recovery backups. Retention and deletion of those records are controlled by the owner.

Extraction and retrieval can be partial. Source dates, import status and coverage are included so the owner can distinguish retained evidence from generated conclusions.

Contact

The application operator is the support contact identified on the Google authorization screen. The owner can contact that operator about access, stored information or deletion.