Privacy policy

Google access and its purpose

MirageSSD requests https://www.googleapis.com/auth/drive.file. It accesses file contents and metadata for files created with, opened with, or otherwise authorized for the app. It uses that access to list, read, upload, update, and delete files as needed for the mounted drive and operations you initiate. It also reads account identifiers and storage quota information to identify the connected account and report capacity. It does not request your Google password.

What stays on your device

OAuth access and refresh tokens are stored locally so the app can connect and refresh authorization. The application’s token store uses Windows protection mechanisms; authorized provider processes receive credentials while running. Local cache data includes staged uploads and downloaded file contents. Local metadata includes file attributes and operational state. Diagnostic logs can include paths, filenames, transfer details, and error messages.

Ordinary writable-drive files and cached contents are not client-side encrypted by MirageSSD. Protect your Windows account and local disk. Do not share credentials or unredacted logs.

Where data goes and who can access it

File contents and Google authorization requests are transmitted to Google’s services over HTTPS. The writable mount uses rclone and WinFsp locally. This website is not a file-transfer proxy and does not receive your Drive tokens or mounted file contents. MirageSSD maintainers do not receive your files through normal mount operation. Information you voluntarily submit in a support request is received through that support channel; public GitHub issues are visible to others.

Google processes information under its own policies. Hosting and network providers, including Vercel and Cloudflare where used, may process website request information such as IP address, requested URL, timestamp, and browser details to deliver and secure this website.

No advertising use or AI training

MirageSSD does not sell Google user data, use it for advertising, or use it to train generalized AI or machine-learning models. MirageSSD’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Retention, disconnection, and deletion

Cloud files remain in your Google account until deleted by you or by an operation you authorize. Cache cleanup depends on local space and upload state; pending writes may remain indefinitely until resolved. Uninstalling the preview intentionally retains credentials, cache, metadata, and cloud files to avoid unintended data loss.

To stop access, stop the mount and remove MirageSSD’s authorization in your Google Account connections. Revocation prevents future authorized access but does not delete files already stored locally or in Drive. Delete cloud files through Google Drive when you no longer need them. Remove retained local data only after uploads and a restore are verified, and after stopping MirageSSD. Contact the maintainer for help identifying these files.

Website cookies and support

This website has no application login, forms, advertising trackers, or analytics scripts. Infrastructure providers may retain operational logs according to their policies. If you contact support, avoid posting personal files, tokens, or private paths. Request a private channel before sharing sensitive information.

Policy changes

This page will be updated when the described practices change. The date above identifies the current revision. Review the policy before installing a new preview build.