Privacy policy
This policy describes the personal AntEye Obsidian Sync configuration and its accompanying information website.
Purpose and Google data
The configuration uses GSync inside Obsidian to exchange note files with Google Drive. This requires access to file contents and metadata such as names, folder locations and modification details, and authorization credentials needed to communicate with Google.
The permission granted on Google’s consent screen may cover more of Drive than the folder selected in GSync. Selecting a folder is not a Google-enforced restriction on that permission.
Use and storage
The intended use of Google data is synchronizing the owner’s notes. Copies of notes reside in the Obsidian vault and Google Drive. Separately configured preservation work can create reading mirrors, previous-version copies and source registers; these have their own retained files.
This website has no note upload form, AI feature or Google sign-in integration. It does not receive vault contents through its page code. Its hosting provider may process connection and access information to serve and protect the website.
Third parties and authorization
The setup involves Google Drive, Obsidian and the third-party GSync plugin. The configured sign-in redirect currently uses https://dg0988.github.io/ObsidianGSync/callback.html. This is hosted outside the owner’s domain.
In the reviewed 1.0.4 source, the client ID, client secret and refresh token are saved through Obsidian’s plugin data storage (normally .obsidian/plugins/gsync/data.json). The plugin does not add encryption to these saved settings. Temporary pending sign-in state, including the PKCE verifier, is also saved locally during authorization. Access tokens are held in plugin memory. Do not share or publish the plugin settings file.
The callback’s reviewed page code receives a one-time authorization code, state and an encoded vault name, then hands them to Obsidian. It removes the query string from browser history and has no analytics scripts or explicit storage calls. Google and the callback host may process the initial request, including URL parameters, under their own practices. The plugin uses a device-generated PKCE verifier and checks state before exchanging the code directly with Google.
Reviewed sync and authorization code sends data to Google’s authentication and Drive endpoints. The source has no telemetry or advertising integration. This source review does not establish the exact bytes of the installed phone plugin, current hosted callback, or every third-party component.
Use limits
This personal configuration uses Google user data to provide note synchronization and the owner’s separately requested preservation work. It does not sell Google user data, use it for advertising, or use it to train generalized AI models. Any additional disclosure or service integration requires the owner’s authorization and a matching policy update.
AI and other services
GSync synchronization does not require an AI API key. A separately configured AI plugin or assistant is outside this website’s sync function; sending notes to such a service requires considering that service’s terms and permissions separately.
Retention and control
The owner controls the retained vault, Drive files and archives. Stopping sync or revoking authorization does not automatically erase existing copies or preserved history. Review and remove copies separately if desired.
You can review or revoke Google access in Google Account connections. Revocation can stop sync until you authorize it again.
Source and scope of review
Checked on 18 October 2026: GSync release tag 1.0.4, including authorization, plugin settings, Drive operations, sync and callback page source. This is a limited source review, not a security certification.
Contact and changes
Contact anteyeofficial@gmail.com for questions about this configuration or its retained copies. Publish an updated policy before adopting materially different data uses.