Privacy Policy

Last updated: 12 September 2026

Sakil Apps provides this website and the Unlock app for macOS and iOS. This policy explains how the website handles information and how Unlock accesses, uses, stores and shares data when you connect Google Drive or Google Photos. Google connection is optional; you choose whether to connect an account and which files to transfer.

Google data that Unlock accesses

Google handles sign-in and asks you to authorize access. Unlock receives authorization tokens so it can perform the cloud features you request. Unlock does not receive or store your Google password.

Google Drive: Unlock reads file and folder information, such as names, identifiers, file types and folder structure, to display its native file browser. It reads or downloads the contents of files you choose to transfer, including exporting supported Google documents when needed. Files you choose to upload are created in the app's Unlock/Files folder.
Google Photos: You select photos or videos in Google's hosted Photos Picker. Unlock receives the selected items' identifiers, filenames, media types and temporary download information, together with a selection-session identifier. It reads the selected media to complete your requested transfer. This integration does not enumerate or access your entire Photos library.
Google Photos uploads: When you choose Google Photos as a destination, Unlock sends the photos or videos you selected and the information needed to create those new media items.

Google permissions and why they are needed

The following permission names use the prefix https://www.googleapis.com/auth/:

drive.readonly lets Unlock browse existing Drive folders and read files you choose as transfer sources. This includes files that were not created by Unlock.
drive.file lets Unlock create its upload folder and files you send to Drive. Unlock does not use this permission to edit or delete unrelated Drive files.
photospicker.mediaitems.readonly lets Unlock create and check a Photos Picker session and retrieve only the photos and videos you selected for that session.
photoslibrary.appendonly lets Unlock add new photos and videos to your Google Photos library when you choose that destination. It is not used to read the whole library or change existing Photos items.

Unlock does not request the retired broad Photos permissions photoslibrary, photoslibrary.readonly or photoslibrary.sharing. It also does not request the full drive permission.

Unlock uses Google data to show cloud files, let you select transfer sources, and complete transfers to the device or connected cloud destination you choose. Google requests are made from your device. Cloud-to-cloud transfers stream through the running app to your chosen destination; the Sakil Apps website is not a relay for your Google tokens or transferred file contents.

When you send a file, its contents and filename are shared with the recipient device or destination service you selected. That destination may retain its own copy under its privacy policy and your account settings. Connecting Google alone does not publish your files or share your entire library.

Sakil Apps does not sell Google user data, share it with advertisers or data brokers, use it for advertising, or use it to train artificial intelligence or machine-learning models. We do not routinely access the contents of your Google files. Human access is limited to information you explicitly provide or authorize for support, or access necessary for security or legal obligations.

Unlock'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 Photos API User Data and Developer Policy.

Storage, retention and security

Google access and refresh tokens are stored on your device in Unlock's private application data, with file permissions restricting access. The iOS app also uses operating-system file protection for this storage. Requests to Google use HTTPS. Transfers to other destinations follow the security protections of the device or service you choose.

Unlock keeps the saved connection until you disconnect it or remove its local data. File listings and active Picker sessions are used while you browse and select media. Queued transfer references can retain filenames, cloud item identifiers and the information needed to retrieve the chosen items until you remove those references. Adding a cloud reference does not itself save the file's contents to the device.

Cloud-to-cloud transfers process media in memory rather than saving a local copy as part of that route. Files you explicitly receive or save locally remain in the chosen storage location until you delete them. Copies uploaded to Drive, Photos or another destination remain there until you manage or delete them in that service.

Unlock keeps a limited local diagnostic log of event times and API response or error codes to help diagnose Photos connection problems. This log does not include Google tokens, passwords or media contents. Information you voluntarily email for support is used to handle your request; contact us to request its deletion.

Disconnecting, revoking access and deleting data

Disconnect in Unlock: Open Cloud Connect and choose Disconnect for Google. This removes the saved Google tokens used by the current connection and clears its cloud browser lists.
Revoke Google's authorization: Open your Google Account's third-party connections, select Unlock and remove its access. Reconnecting later requires Google authorization again.
Remove queued references: Use the remove control beside a file in Unlock's send list. This removes the reference and keeps the original file.
Delete saved or transferred files: Delete local copies from the receiving folder or Files app, and delete uploaded copies in Google Drive, Google Photos or the other destination service. Disconnecting or revoking access does not delete these copies.
Request help or deletion: Email hellosakil@outlook.com for help removing local app data or to request deletion of information you supplied to Sakil Apps. Do not send passwords or authorization tokens. We cannot directly delete files that remain solely on your devices or in your own cloud accounts.

Document Editor

The public web Document Editor processes documents in the browser by default. Documents are not uploaded to the Sakil Apps server by the editor unless a feature explicitly says otherwise.

Website hosting and administration

This website uses Cloudflare for hosting and delivery. The private website editor stores published page content and uploaded website assets in the Cloudflare services configured by the site owner.

The website records aggregate page-view counts by date and page in Cloudflare D1 for the site's private analytics. Those counters do not contain Google file contents or Google authorization tokens. Cloudflare may process technical request information, such as IP addresses and browser information, to deliver and protect the website; see Cloudflare's Privacy Policy.

Policy changes and contact

We will update this page and its revision date when these practices change. Material changes to how Google data is used will be disclosed before the new use, and additional consent will be requested when required.

For privacy questions, access or deletion requests, contact Sakil Apps at hellosakil@outlook.com. Please identify the app and the information concerned so we can help with your request.