Last updated: August 11, 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.
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.
When you connect a Google account through "Add Google Account," AllieMinate requests the drive.file scope. This scope limits access to only the files and folders you explicitly open, create, or select through AllieMinate's own interface — it does not grant blanket access to your entire Drive.
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.
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.
If this policy changes, the updated version will be posted at this same URL with a revised date above.
Questions about this policy or your data: vansh080605@gmail.com