Privacy Policy

Last updated: September 24, 2026

AllieMinate is a cloud storage aggregation and device-sync application. This policy explains what data AllieMinate accesses, how it's used, and — most importantly — what AllieMinate does not do with it.

The short version

AllieMinate has no server of its own that stores, sees, or relays your files, credentials, or account data. It runs entirely on your own devices. When you connect a cloud account (e.g. Google Drive) or pair a device (e.g. your phone), all communication happens either directly between your device and the cloud provider's own servers, or directly between your own paired devices over your local network. Nothing passes through any server operated by AllieMinate or its developer, because none exists.

Google User Data

AllieMinate accesses Google user data only after you explicitly connect a Google account and authorize the requested permissions. Depending on the Google service you connect, AllieMinate may access the following data:

Google Drive files, folders, and metadata

AllieMinate requests the https://www.googleapis.com/auth/drive scope, which provides read and write access to your Google Drive. This includes file and folder contents and related metadata, such as names, IDs, folder structure, file types, sizes, timestamps, and storage usage where Google provides it.

AllieMinate uses this data to provide its core unified file-management features. You can browse, search, preview, upload, download, rename, move, organize, delete, transfer, and synchronize the Drive files you authorize AllieMinate to manage.

Why full Google Drive access is required

AllieMinate must display and manage your existing Drive folders and files, including files that were not created by AllieMinate. The narrower drive.file scope cannot list and manage your complete existing Drive structure, so it does not support AllieMinate's core purpose as a unified file manager.

Google account email address

AllieMinate accesses your Google account email address where needed to identify, label, and prevent duplicate entries for connected Google accounts. It does not use your email address for advertising or marketing.

Google Photos media selected by you

AllieMinate uses Google's Photos Picker API and the photospicker.mediaitems.readonly scope. You choose the photos or videos in a Google-hosted picker. AllieMinate accesses only the selected media and metadata needed to display or download your selection; this flow does not provide blanket access to your entire Google Photos library.

How AllieMinate Uses Google User Data

AllieMinate uses Google user data only to provide or improve visible features that you request in the app. These features include browsing and managing Drive files, showing connected-account information, previewing and downloading files, transferring files to a destination you select, and running synchronization that you configure.

AllieMinate does not use Google user data for targeted advertising, profiling, or training generalized artificial-intelligence or machine-learning models.

Data Protection Mechanisms for Sensitive Google User Data

AllieMinate protects Google user data and OAuth credentials through the following concrete technical and organizational mechanisms:

• Every request from AllieMinate to Google's OAuth endpoints and Google APIs uses HTTPS/TLS encryption while the data is in transit.
• Google OAuth refresh tokens are stored only in AllieMinate's application-support data on your device. Short-lived access tokens are obtained as needed and held by the local app process.
• AllieMinate stores local application data inside your operating-system user profile. Access is controlled by your operating-system account and filesystem permissions. AllieMinate does not upload local credential files to an AllieMinate-operated service.
• AllieMinate does not operate a central server that receives, stores, or processes your Google Drive files or Google Photos data.
• AllieMinate accesses Google user data only after you explicitly authorize the requested Google permissions.
• AllieMinate never asks for or stores your Google password. Authentication takes place on Google's OAuth page.
• AllieMinate's developer, employees, and contractors have no remote server through which they can view your Google files or OAuth credentials.
• You can revoke OAuth authorization at any time through your Google Account.
• AllieMinate does not sell Google user data or use it for advertising.

Google User Data Retention and Deletion

AllieMinate does not retain your Google Drive files, Google Photos data, account email, or OAuth credentials on an AllieMinate-operated server because AllieMinate does not operate such a server. The following retention rules apply only to data stored locally on your device:

• OAuth refresh tokens: retained in local application data while the Google account remains configured. A token remains until you remove that linked account where the app provides a Remove action, delete AllieMinate's local application data, or Google invalidates the token after you revoke access.
• OAuth access tokens: retained by the running local app only as needed for authorized API requests. Google sets their expiration, after which AllieMinate refreshes or discards them.
• Account email and labels: retained locally while needed to identify the connected account and prevent duplicate account entries.
• Opened or previewed files: may remain in AllieMinate's local cache until you clear the cache in Settings or AllieMinate evicts cached files under its configured cache limit.
• Downloaded, synchronized, or transferred files: remain in the destination you selected until you delete them through AllieMinate where deletion is available, or through your operating system.
• Files still stored in Google: remain in your Google account under Google's retention controls until you manage or delete them from AllieMinate or Google.

Disconnecting, removing, revoking, and deleting

• Disconnect: stops AllieMinate from using that provider in the app. Disconnecting may retain the local credential and configuration so the account can be reconnected.
• Remove: deletes the selected additional Google Drive or Google Photos account record and its OAuth refresh token from AllieMinate's local application data. It does not delete files stored in Google.
• Revoke: use your Google Account's third-party connections settings to invalidate Google's authorization. Revocation prevents further Google API access.
• Delete all local application data: removes remaining local account records, credentials, settings, and cached Google data. It does not delete files stored in Google.

How to delete Google user data from AllieMinate

1. Remove each additional Google Drive and Google Photos account in AllieMinate Settings.
2. Use Clear Cache in AllieMinate Settings to delete locally cached previews and opened remote files.
3. Revoke AllieMinate from your Google Account's third-party connections settings to invalidate authorization.
4. For the primary Google Drive account, or to remove all remaining local Google data, quit AllieMinate and delete its local application data as described on the Google Data Deletion page.
5. Delete downloaded or synchronized copies from their destination folders if you also want those local copies removed.

Deletion from AllieMinate takes effect on the local device when you complete the applicable step. Google controls token revocation and data that remains in your Google account. AllieMinate does not keep a server copy that requires a separate deletion request.

Sharing and Transfer of Google User Data

AllieMinate does not sell, rent, or provide Google user data to advertisers or data brokers. It does not disclose Google user data to unrelated third parties.

When you explicitly request a transfer or configure synchronization, AllieMinate may send the selected file data directly to your selected destination, such as your own device, a paired device, or another cloud provider account you connected. This transfer occurs to provide the user-facing feature you requested and does not pass through an AllieMinate-operated server.

Google API Limited Use

AllieMinate's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Revoking Google Access

You can disconnect your Google account at any time through AllieMinate's Settings. You can also revoke AllieMinate's authorization from your Google Account's third-party connections settings. After revocation, AllieMinate can no longer access your Google Account unless you authorize it again.

Other cloud providers

The same principle applies to every other provider AllieMinate supports (OneDrive, Backblaze B2, IDrive e2, MEGA, pCloud): credentials are stored locally on your device, and all file operations happen directly between your device and that provider's API.

Device pairing and local network features

Pairing a phone, Mac, or Windows PC with AllieMinate (for file transfer, Sync Pairs, Universal Clipboard, Nearby Share, or remote unlock) works entirely over your own local network via direct, token-authenticated connections between your devices. No pairing data, transferred file, or clipboard content is ever routed through an external server.

Data AllieMinate does not collect

• No analytics or telemetry is sent off your device.
• No account registration is required to use AllieMinate.
• No file contents, filenames, or metadata are transmitted anywhere other than the cloud provider you explicitly connected, or a device you explicitly paired.

Changes to this policy

If this policy changes, the updated version will be posted at this same URL with a revised date above.

Contact

Questions about this policy or your data: vansh080605@gmail.com