Current scope: Journal AI Companion is an early-stage private prototype. This policy focuses on Journal Sync Writer’s current Google OAuth and Google Drive access. It will be updated before any materially different data handling or broader release.
What Google information is accessed
Journal Sync Writer uses Google OAuth to access the minimum information needed for its current validation and synchronization-safety work:
- basic Google account identity information, used to confirm that the authorized account is the intended account; and
- read-only Google Drive file content and metadata.
The current Google OAuth scope provides read-only access to the authorized Google Drive and can technically permit the utility to view and download Drive files. Journal Sync Writer is designed to restrict its own operations to the explicitly configured Journal files and validation objects required for the workflow.
The utility does not request Google Drive API permission to create, edit, delete, organize, or manage Drive files.
Why Google Drive information is accessed
The utility accesses Google Drive information to validate journal source files, confirm expected file identity and state, and support synchronization-safety checks. Google OAuth account identity helps prevent operations against an unintended account.
Local storage and credential protection
The utility is designed as a local macOS component. Its local working information may include configuration, file identifiers, validation results, synchronization state, and local copies or representations of Journal Markdown needed for the workflow.
OAuth credentials and tokens are intended to remain on the user’s Mac and to be protected using macOS Keychain and operating-system access controls. Credentials should not be placed in journal content, source control, or public files.
Data retention and deletion
Journal Sync Writer does not maintain an InfoGlade-operated server-side copy of Google Drive journal content.
Local working information may include configuration, file identifiers, validation results, synchronization state, and local copies or representations of Journal Markdown needed for the workflow. That information may remain on the user’s Mac until removed or replaced through the local workflow.
OAuth credentials are stored locally using macOS secure credential storage.
Revoking Google authorization prevents future access through that authorization, but it does not automatically remove local Journal files or local utility data. Those must be removed locally by the user if desired.
Transmission and sharing
Journal Sync Writer communicates with Google’s services as required for OAuth authorization and the requested read-only Google Drive operations. The current design does not rely on an InfoGlade-operated cloud service to store or process Google Drive journal content.
Google user data is not sold, used for advertising, or shared with advertisers. No third-party analytics or advertising system is part of the current utility.
Google API Limited Use
Use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, where applicable.
The project does not request Google Drive API write or manage scopes for the current utility.
Revoking authorization
A user can revoke Journal Sync Writer’s Google authorization at any time from the security settings of their Google Account, under third-party apps and services or connected applications. Revocation prevents future access through the revoked authorization. Local journal files and local utility data must be removed separately by the user if desired.
Security and project status
Careful permission scope, account verification, local credential protection, validation, and recoverability are core design concerns. No software can promise absolute security, and this utility remains a private prototype under development rather than a generally available service.
Questions and updates
For privacy or data-related questions about Journal AI Companion or Journal Sync Writer, contact privacy@