Who is responsible
Easy Cloud Sync is published by Alexandr Ponomarenko, Ukraine (the “publisher,” “we,” or “us”). This policy describes the Windows desktop app and this website. Microsoft, Google, GitHub, and Cloudflare process information under their own policies when you use their services.
Our contact channel is GitHub Issues. It is public and requires a GitHub account to post. Do not include personal account details, file contents, credentials, or other sensitive information. No private support channel is provided.
File access and permissions
The app reads the names, paths, identifiers, sizes, timestamps, permissions, hashes, and other metadata needed to list and compare items in your selected folders. It reads file content to transfer files or calculate hashes and can create, overwrite, or delete items according to the plan you approve.
You choose the root folders for each sync job. Cloud authorization is broader than those selected folders. OneDrive requests delegated User.Read and Files.ReadWrite.All permissions. Google Drive requests https://www.googleapis.com/auth/drive, which permits access to all Drive files available to your account. A selected job folder does not narrow the OAuth permission granted to the app.
Access remains subject to your cloud account’s permissions and organization policies. Sign-in happens in your system browser. The app does not ask you to enter your Microsoft or Google password into its own interface.
Transfers and temporary files
Transfers pass through the app running on your Windows PC to or from your selected storage providers. A transfer between cloud providers also passes through the PC. There is no publisher-operated server that receives or relays your synced file contents.
Some transfers buffer content in temporary local files, including Google Drive uploads and certain OneDrive uploads. The app attempts to remove these temporary files when the operation finishes or is disposed. A crash or interrupted cleanup may leave temporary data behind. Files saved into a selected destination remain there until you remove them or a later sync changes them.
Cloud connections use HTTPS. Your cloud provider processes files and requests under its own terms, security practices, storage locations, and retention policies.
Accounts and subscriptions
The app uses provider account identifiers, usernames or display names, connection settings, and authorization information to identify the account connected to each saved connection and restore its session. Providers may return other profile information, such as an email address.
Microsoft Store processes purchases, payment details, billing, and subscription management. The app queries Store products and license information to display subscription status and determine Pro access. The publisher does not receive your payment-card details through the app. This website has no sign-in, checkout, or separate Easy Cloud Sync account.
Local data and token storage
The app saves connection settings, account identifiers, job paths and options, comparison metadata, cached inventories, checkpoints, and run history under %LocalAppData%\EasyCloudSync. This includes sync-state.json and supporting session files. The ordinary JSON state is not all encrypted and may reveal filenames, folder paths, account details, or activity. Run history is normally limited to the latest 200 entries overall.
Google access tokens, refresh tokens, and the OAuth client secret are stored in a separate file protected with Windows data protection for the current Windows user. OneDrive uses an encrypted Azure.Identity SDK token cache and a separate authentication-record file. Unencrypted SDK token caching is disabled. The authentication record and general app settings are not equivalent to encrypted token storage.
Saved authorization allows silent session restoration and token refresh. New interactive sign-in only starts from an explicit sign-in command. Windows account protection does not protect you from every program running as that user or from a compromised device; keep your Windows account and device secure.
Disconnecting and deleting data
Removing a connection, revoking cloud access, deleting local app data, deleting synced files, and cancelling a subscription are separate actions.
- Delete a job: removes its saved configuration and associated job history and comparison state. It does not remove the files you synchronized.
- Delete a connection: first remove jobs that use it. Deleting a Google Drive connection removes its reusable protected local session. Deleting a OneDrive connection does not currently guarantee removal of its authentication record or encrypted SDK token cache. Other cached account or item metadata may remain in local app data.
- Revoke provider access: use your Google account connections or the app-permission controls for your Microsoft account or organization. Deleting a connection in the app does not revoke the cloud grant. Revocation can take effect according to the provider’s token and session rules.
- Remove local app data: stop running jobs and close the app before deleting
%LocalAppData%\EasyCloudSync. This removes saved jobs, history, and app-managed session records. The OneDrive SDK token cache is managed separately and may remain. Revoke provider access as well if you want to withdraw authorization. Do not assume uninstalling erases all app data, cached tokens, or temporary files. - Delete synchronized files: manage copies in each local folder or cloud service separately. Removing the app, a job, or a connection does not delete those copies.
- Cancel Pro: manage recurring billing in Microsoft Services & subscriptions. Deleting local data or disconnecting a provider does not cancel it.
Use, sharing, and retention
Provider data is used to deliver the synchronization features you request: connection management, browsing, comparison, transfers, and local run history. We do not sell your cloud data, use it for advertising, or use it to develop or train generalized artificial-intelligence or machine-learning models. The app has no built-in publisher analytics or telemetry.
Easy Cloud Sync’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace API User Data and Developer Policy.
Local settings and caches remain until removed, replaced, or limited by the app’s retention rules. The publisher cannot remotely erase files, cloud grants, or local data held on your device. Information you voluntarily post in a support issue is available to the publisher and other GitHub visitors and may remain under GitHub’s retention policies. Microsoft Store, Windows, and your cloud providers may collect their own diagnostics independently of this app.
Website and third parties
This website uses no analytics scripts, advertising trackers, contact forms, third-party embeds, or nonessential cookies set by the website. Fonts, styles, and images are served with the site. Visiting a linked external service is subject to that service’s policies.
Cloudflare hosts and delivers the website. It processes network and request information such as IP addresses, requested URLs, browser information, and timestamps to deliver and protect the site. Cloudflare may process data internationally under its own retention and security practices; “no analytics” does not mean there is no hosting or network processing.
See Cloudflare’s privacy policy, GitHub’s privacy statement, Microsoft’s privacy statement, and Google’s privacy policy.
Requests and policy changes
Depending on the laws that apply to you, you may have rights to access, correct, delete, restrict, or object to processing of personal information, or to complain to a relevant data-protection authority. For data stored only on your device, use the local removal steps above. For data held by Microsoft, Google, GitHub, or Cloudflare, use that service’s privacy controls or request process.
For a publisher-related privacy question or request, open a minimal, non-sensitive GitHub issue. State the type of request without posting the personal information itself. This public channel is not suitable for transmitting sensitive evidence; we do not offer a private contact channel.
We will publish policy changes on this page and update the effective date. Material changes in app behavior should be reviewed before you use the updated version.