Your data

Privacy policy

Last updated: October 18, 2026

This policy covers Keyword Office (also called Keyword), its Windows desktop Google integration, and the website at keywordoffice.online. It describes the reviewed version 0.3.156.

Data accessed and why

When you connect Google, Keyword accesses document content and structure, document identifiers, names, modification information and revisions to find, open, edit, save, and synchronize Google documents. It can read file and folder metadata to resolve Google Drive shortcuts and locations, including shared drives. It can read your Google account email address to match a local Google Drive account.

When you use collaboration features, Keyword reads collaborator names, email addresses, and access roles. If you invite someone, their email address and selected role are sent to Google to grant access and send an invitation. Google and authorized collaborators receive document data as needed for the features you use.

Google OAuth permissions

The reviewed application requests https://www.googleapis.com/auth/drive. This permission allows it to see, edit, create, and delete all Google Drive files accessible to your account. It is broader than access to files you select in Keyword. This is the permission's capability, not a claim that Keyword deletes all your files.

The implementation uses this scope for opening existing Google documents and arbitrary Google Drive shortcuts, listing documents, saving and synchronizing changes, and managing collaborators. It does not request a separate Google Docs scope in the reviewed sign-in code. Google Docs API operations use the Drive authorization.

Keyword also requests offline access, allowing a refresh token to keep the connection working without signing in for every session. Offline access is an OAuth option, not an additional API scope. See Google's Drive permission documentation.

Sign-in and transmission

Sign-in opens Google's authorization page in your system browser. Your Google password is entered with Google, rather than in Keyword. A local loopback callback returns an authorization code to the desktop application; the flow uses PKCE and a state check.

The desktop app sends its OAuth client ID and client secret, the authorization code and verifier, and later its refresh token to Google's HTTPS token endpoint. Access tokens accompany HTTPS requests to Google's Drive and Docs APIs. Document content and metadata are downloaded from and uploaded to Google when you use connected features; active synchronization can exchange updates while a document is open.

The reviewed application code contains no publisher-operated server destination for Google credentials, tokens, or document contents. This does not mean data stays entirely on your computer: Google processes the requests, and collaboration shares content with people who have access. Google Drive for desktop or other sync software may also synchronize files under its own settings.

Local storage and protection

• OAuth refresh tokens are stored under %LOCALAPPDATA%\KeyWord\Google in refresh*.bin files protected using Windows data protection for the current Windows user. Access tokens are held in application memory.
• Imported OAuth client configuration is stored as Windows-protected credentials.bin. A publisher-supplied desktop client configuration may instead be read from google-oauth-client.json alongside the application; that file is not protected by this token-storage mechanism.
• Google document shortcuts and cached metadata can include document IDs, URLs, titles, and origin paths. Cached shortcuts are stored under %LOCALAPPDATA%\KeyWord\Google\Shortcuts; shortcuts may also be saved to selected locations.
• Document contents are held in memory and may be written to temporary files during conversion, opening, or synchronization. The relevant code attempts to delete these temporary files after use; an interrupted process can leave files behind.
• Recovery snapshots can contain document text and formatting in %LOCALAPPDATA%\AccessibleWordProcessor\recovery.json. Documents saved to local paths remain at those paths.

Document files, shortcuts, and recovery snapshots do not use the OAuth token protection mechanism. This policy does not promise that all local data is encrypted, that deletion is secure erasure, or that any system is completely secure. Windows access controls, device protection, and your backup and sync settings affect local data protection.

Use, sharing, and Limited Use

Keyword Office's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Google user data, including data derived from it, is used only to provide or improve the visible document and collaboration features described here. It is not sold, used for advertising, credit or lending decisions, or used to train generalized AI models. The publisher does not separately collect this Google data outside the application.

Transfers are limited to those needed for these visible features with your consent, security purposes, compliance with law, or a business transfer with your explicit prior consent. Human access is limited to your affirmative agreement to specific data, necessary security investigation, legal requirements, or aggregated internal operations allowed by Google's policy. Staff and service providers must follow the same restrictions. Contacting support does not authorize unrestricted access to your Google account.

Retention, sign-out, and deletion

Refresh tokens remain locally until removed by sign-out, replacement, or an invalidated session. Signing out clears the application's in-memory access token and deletes local refresh-token files. It does not revoke Google's authorization, delete imported client configuration, remove cached shortcuts or recovery files, or delete documents on Google Drive.

To revoke authorization, remove Keyword from your Google Account's third-party connections. Revocation stops future authorized API access but does not erase existing local copies or cloud documents.

Local saved documents and shortcuts remain until you delete them. Recovery snapshots are updated or cleared by the application's recovery handling; no fixed retention period is enforced for all local artifacts. To remove remaining local data, close Keyword and delete the relevant files listed above after saving anything you need. Backups and synchronized copies may need separate removal. Manage Google-hosted documents and sharing in Google Drive. Email support for help locating local data or making a privacy request; the publisher cannot directly erase files stored only on your device.

Website and support messages

This static website has no sign-in, analytics scripts, embedded third-party assets, forms, or cookies set by its own code. GitHub Pages, the intended host, processes visitor information such as IP addresses to serve and protect the website; see GitHub's privacy statement. Following external links makes a request to the linked service.

If you email support, your email address, message, and any attachments are processed by the support mailbox provider, Gmail, and are available to the publisher to handle your request. Ask support about deletion of correspondence. This policy does not specify a fixed support-email retention period.

Changes to this policy

Updates will be posted here with a revised date. New uses of Google data require updated disclosures and user consent before that new use, as required by Google's policy.