ozdy

Privacy Policy

Last updated: October 30, 2026

This Privacy Policy explains how ozdy (“ozdy”, “we”, “us”) handles information. ozdy is the name for the personal, non-commercial apps and tools built and maintained by Özgür Duyar. This policy applies to this website (app.ozdy.net) and to every ozdy app, including ozdy Drive Sync.

In short: ozdy apps run on your own device. Google user data accessed by ozdy Drive Sync goes only between your device and Google; it is never sent to or stored on ozdy servers, never sold or shared, never used for advertising, and never used to train AI or machine-learning models.

1. Who we are

ozdy is a personal project of Özgür Duyar. It is not a company and does not sell products or services. ozdy apps are built for personal use and are offered free of charge.

2. This website

  • This website does not use cookies, local storage, analytics, advertising, tracking pixels, fingerprinting or any third-party scripts. It contains no forms and asks for no personal information.
  • The web server that serves this site is configured not to keep access logs. The hosting infrastructure in front of it may keep short-lived technical logs (such as IP address and requested URL) only for operation and security; they are not used for analytics or tracking.
  • Requests to this site pass through Cloudflare, a content delivery network, which processes technical request data (such as IP address and browser user agent) as needed to deliver and protect the site, under Cloudflare’s privacy policy.

3. Google user data (ozdy Drive Sync)

ozdy Drive Sync is a Google OAuth application (client) registered by ozdy. It is used by rclone, an open-source file sync program that you install and run on your own computer, to access your Google Drive through the Google Drive API. ozdy does not operate any server for this app: when you use it, your computer talks directly to Google.

3.1 What data is accessed

With your permission, and only for the Google account you authorize, ozdy Drive Sync can access:

  • Google Drive files and their content that you choose to list, download, upload, copy, sync, move or delete with rclone.
  • Google Drive file metadata, such as file and folder names, folder structure, sizes, MIME types, modification times, checksums and sharing-related attributes needed to perform those operations.

The exact access depends on the Google Drive scope you select when you set up rclone. rclone may request one of these scopes:

  • https://www.googleapis.com/auth/drive — full access to the files in your Google Drive (rclone’s default).
  • https://www.googleapis.com/auth/drive.readonly — read-only access to your files and metadata.
  • https://www.googleapis.com/auth/drive.file — access only to files created or opened by rclone.
  • https://www.googleapis.com/auth/drive.appdata (selected in rclone as drive.appfolder) — access only to rclone’s hidden application data folder.
  • https://www.googleapis.com/auth/drive.metadata.readonly — read-only access to file metadata, without file content.

ozdy Drive Sync does not request access to your Google profile, email address, contacts, Gmail, Calendar or any other Google service.

3.2 How the data is used

Google user data is used only to provide the file operations that you start yourself in rclone on your own device, such as listing folders, copying, syncing, backing up or restoring files. It is not used for any other purpose.

3.3 Where the data is stored

  • File content and metadata are transferred directly between your device and Google’s servers over encrypted HTTPS connections. They are not sent to, processed by or stored on ozdy servers, and ozdy has no way to see them.
  • The OAuth access and refresh tokens that Google issues are stored only on your device, in your local rclone configuration file (rclone.conf). You can encrypt this file with rclone’s configuration password feature.
  • Files you download with rclone are saved where you choose on your own storage and are under your control.

3.4 Sharing, transfer and disclosure

  • ozdy does not sell Google user data.
  • ozdy does not share, transfer or disclose Google user data to third parties. The only parties involved are you, your device and Google.
  • ozdy does not use Google user data for advertising, including personalized, re-targeted or interest-based advertising.
  • ozdy does not use Google user data to develop, improve or train generalized artificial intelligence or machine-learning models.
  • ozdy does not use Google user data to determine credit-worthiness or for lending purposes.

3.5 Human access

Because ozdy never receives your Google user data, no person at ozdy can read it. Even so, ozdy commits that no human will read Google user data unless (a) you give your affirmative agreement for specific data (for example, a file you choose to send us when asking for help), (b) it is necessary for security purposes, such as investigating abuse, (c) it is required to comply with applicable law, or (d) the data has been aggregated and anonymized and is used for internal operations, in each case as permitted by the Google API Services User Data Policy.

3.6 Limited Use disclosure

ozdy’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

3.7 Retention and deletion

  • ozdy retains no Google user data, because none is ever sent to ozdy.
  • Your OAuth tokens remain in your local rclone configuration until you remove them. To delete them, run rclone config delete <remote-name> (or remove the remote in rclone config), or delete the rclone configuration file.
  • Files you copied to your own device stay there until you delete them yourself.

3.8 Revoking access

You can revoke ozdy Drive Sync’s access to your Google account at any time at https://myaccount.google.com/permissions. Revoking access immediately invalidates the tokens stored by rclone, so the app can no longer reach your Google Drive. You can also remove the remote from rclone as described above.

3.9 Security

All communication with Google APIs uses HTTPS (TLS) encryption. Because tokens and data live only on your device, keep your device secure, protect your rclone configuration file, and consider enabling rclone’s configuration encryption.

4. Other ozdy apps

Every ozdy app is covered by this policy. If a future ozdy app processes personal data or Google user data in a different way, this policy will describe that app’s data practices before the app is made available.

5. Information you send us

If you contact ozdy, we receive your email address and the content of your message. We use them only to reply to you and do not add you to any mailing list.

6. Children

ozdy apps are not directed to children under 13 (or the minimum age required in your country), and ozdy does not knowingly collect personal information from children.

7. Changes to this policy

We may update this policy from time to time. The “Last updated” date at the top shows when it was last changed. If we ever change how an app uses Google user data, we will update this policy before the change takes effect and, where required, ask for your consent again.

8. Contact

Questions about this policy or your data can be sent to Özgür Duyar (ozdy).

Contact: [CONTACT EMAIL — to be added]