Privacy Policy

Data accessed

After the owner explicitly authorizes access through Google OAuth, the utility retrieves Google Calendar events and Google Contacts address-book entries, including the information contained in those records. The OAuth permissions may allow broader operations, but the synchronizer is configured to read Google data and store local copies, not to modify Google data.

Purpose and use

The information is used exclusively to maintain personal backups, verify backup completeness, and recover data if it is accidentally edited, deleted, or lost. It is not used for advertising, user profiling, or commercial analytics.

Storage and security

Data is stored on infrastructure managed by the owner. Access to backup data is restricted. Historical backups may be encrypted and stored on separate owner-controlled systems, including an off-site backup location. OAuth credentials and tokens are not published on this website.

Sharing

The operator does not sell Google user data, share it for advertising, or grant public access to it. Authorized communication with Google's services is required to retrieve data. The owner may use private infrastructure and backup storage under their control for recovery and resilience.

Retention and deletion

Current local copies are updated during synchronization. Historical snapshots may preserve older records, including entries subsequently deleted from Google, for the configured backup retention period. The owner can stop synchronization by revoking the OAuth grant and can delete stored copies and associated backups under their control.

Permissions and control

Access can be revoked at any time through Google Account security settings. Revocation stops new access but does not automatically erase local backup copies; the owner must separately delete those copies if desired.

Contact

This is a non-public personal project. Privacy inquiries may be directed to the application owner using the support email shown in the Google OAuth consent screen.