The short version: the plugin sends files you select directly to Google Drive. Account credentials stay in your local keyring. The project does not operate an upload server or add advertising or analytics trackers.
01Who this policy covers
omadocs is an independent open-source project maintained by pablousx. This policy describes the official omadocs desktop plugin and this project website. It does not cover independently modified versions, Google’s services, or GitHub’s own processing.
You do not create an omadocs website account. Google sign-in happens in your browser through Google’s authorization flow.
02Data the plugin uses
The plugin processes the following information on your computer to carry out your requests:
| Information | Purpose and location |
|---|---|
| Selected file contents | A private local snapshot allows a reliable upload. The selected content and filename are sent directly to Google Drive. |
| Account identity | Google account email and permission identifier identify the upload owner and verify reconnection. These and any account nickname are stored locally. |
| Authorization material | Access tokens, refresh tokens, imported client configuration, and resumable upload session URLs are stored in your system’s Secret Service keyring. Temporary authorization codes and PKCE verifiers are held in memory. |
| Upload activity | Filenames, account associations, file IDs, Google links, size, checksum, progress, timestamps, and error states are stored locally for recovery and recent activity. |
| Preferences | Account choices, history settings, and backups of file associations are kept locally to apply your preferences and restore previous handlers. |
The plugin does not collect your Google password. There is no plaintext fallback for storing tokens if the keyring is unavailable. The release includes the public Desktop application's client ID and client secret for Google sign-in. These shared application fields are separate from your private account tokens, which are never bundled or published.
03Google access and use
omadocs requests
https://www.googleapis.com/auth/drive.file,
Google’s per-file Drive permission. The permission can cover
files created by or explicitly shared with an application. The
current plugin uses it to create new uploads, check its own
upload file IDs, and obtain the account identity needed to
verify ownership. It does not enumerate your Drive.
Selected files are sent to Google only to provide the upload functionality you request. The project does not use Google user data for advertising, sell it, or use it to develop or train generalized AI or machine-learning models. There is no automatic transfer of your Google user data to the maintainer.
omadocs’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google processes uploaded files and sign-in information under Google’s Privacy Policy.
04Storage and retention
Your original file remains on your computer. Upload snapshots and recent activity are kept in private omadocs directories under your system’s XDG cache and state locations. Your keyring holds persistent authorization material.
By default, completed activity is limited to the most recent 100 entries and a 30-day retention window. Pending snapshots expire after 7 days by default. These settings are adjustable. Cleanup runs while the helper is active or when it starts again, so data can remain on disk while the application is not running.
Snapshots for finished operations are removed during cleanup. Failed or uncertain operations can retain recovery records until resolved or the app’s local data is cleared. Cleanup can also be delayed if the keyring is locked. Connected-account credentials remain until you remove the account or complete the app’s uninstall flow.
Files already uploaded remain in Google Drive until you manage or delete them there. Removing omadocs does not delete those copies.
05Your controls
- Choose what to send. Upload only files you select, to the connected account you choose.
- Disconnect an account. Removing an account clears its locally stored authorization tokens and cancels pending work. It does not erase all past activity or delete Drive files.
- Revoke Google access. Visit your Google Account’s third-party connections to revoke the authorization grant. Removing a local account alone does not necessarily revoke that grant.
- Clear local app data. Follow the uninstall instructions to clear omadocs account/activity data, snapshots, and app-tagged keyring items. Resolve any reported cleanup errors before removing the plugin source.
- Manage your originals. Original documents and any OAuth JSON you imported remain under your control; the plugin does not delete them.
06This website
This is a static website designed for GitHub Pages. It has no upload form, sign-in system, advertising, analytics scripts, or third-party font requests. It does not access the accounts or files connected to your desktop plugin.
If you change the color theme, the site stores one preference,
omadocs-theme, in your browser’s local storage. It
is not sent to the maintainer and remains until you clear site
data. The site works without that storage. No application
cookies are set by this site.
GitHub, as the website host, may process connection and request information, including your IP address, for hosting and security. Its processing is described in the GitHub Privacy Statement. Following an external link takes you to a service with its own privacy practices.
07Support and contact
You can contact the maintainer through the project’s GitHub Issues page. If you choose to post an issue, the maintainer and other visitors can read what you share, and GitHub stores it under its own policies.
Issues are public. Do not post documents, credentials, tokens, private file paths, or account details. Start a privacy inquiry without personal data and request a private contact method if needed. The plugin’s diagnostic export is designed to omit document names, emails, paths, tokens, and file IDs; review any information before sharing it.
For data held only on your device, the maintainer cannot retrieve or erase it remotely. Use the local controls described above. Contact Google or GitHub for requests relating to data they hold independently.
08Policy changes
This policy may change as the project evolves. Revisions will be published on this page with an updated effective date, and material changes to data handling will be described in project release notes. The repository records the history of policy changes.