Privacy policy

1. Files and device information

Files lets you browse, open, organize, copy, share, archive and review files. Viewing, metadata indexing, storage reviews, duplicate detection, installed-app review and file tools run on your device. Device/shared-storage files remain in their chosen locations; app-managed copies, settings and caches use local app storage. Your documents, file names, paths, contents, installed-app inventory and file-lock passwords are not included in our analytics or advertising payloads.

Storage, media, notification, usage-access and APK-install permissions are requested for the relevant functions. Broad storage access is optional. Declining permissions leaves supported picker/scoped paths available. Android continues to protect other apps' private data. Installed-app inventory and usage-access results are processed locally for app management and unused-app reviews, not sold or sent to advertisers.

You can explicitly share files through Android, transfer selected files to a paired device, or connect to a server/cloud provider. Those actions send the files and connection information needed to the destination you choose. They are different from uploading files to our advertising or analytics systems. Destination services apply their own privacy practices. Connection credentials saved by Files are encrypted locally using Android-protected keys. A paired transfer uses a temporary session and device approval.

Google Drive connections

Connecting Google Drive is optional. Google presents its account and permission screens before access is granted. Files requests Drive file-management access so you can browse your Drive root and folders, open files, copy selected files to or from Drive, create folders, rename supported files and move supported files to Drive’s Trash. Files does not permanently delete Drive files or change their sharing permissions.

Your Google account email, display name and Drive account identifier identify your connection on this phone. The access token and connection record are encrypted with Android-protected keys. Saved folder labels and open-view state use app-private local preferences. Google Play services manages the authorization grant and can renew access. Drive authorization is separate from the anonymous credential used for purchase verification. Drive credentials and file data are not sent to our purchase-verification backend.

Drive requests go directly from your device to Google over HTTPS. Opened files may be downloaded into a private temporary cache for viewing. Use Connect cloud → Clear downloaded cache to remove cached downloads, or Disconnect to remove the account credentials and its cached downloads from Files. Files also attempts to revoke its Google authorization; if offline, remove the grant through your Google Account connections. Files you explicitly copied into Saved files or other destinations remain until you remove them. Direct Drive accounts are not crawled by scheduled storage scans or reminder discovery.

Files’ use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google Drive data is used only to provide the file-management features you choose. It is not sold, used for advertising or ad targeting, sent to analytics, used to train generalized artificial-intelligence models, or made available for human review by us.

2. Optional usage analytics

Share usage analytics is off by default and can be changed during setup or in Settings. When enabled, Firebase Analytics processes installation/first-launch events, app interactions, coarse feature/task counts and timing, campaign context, app/device technical information and advertising/purchase revenue events. It uses pseudonymous installation identifiers; these records should not be described as irreversibly anonymous. Firebase may derive approximate region information from network data. Files does not request precise device location.

Turning analytics off stops future consented analytics collection through our controls and discards pending local measurement uploads. It does not erase data already received by a service or delete Google Play purchase records. Existing backend/export functionality is not enabled in this build; Firebase receives the consented Analytics events directly.

3. Advertising and consent

The free app uses Google Ad Manager and Google's User Messaging Platform. Depending on consent, availability and Google settings, Google may process IP addresses (which can indicate approximate location), app/ad interactions, diagnostics, device/app identifiers and consent signals to deliver and measure ads and prevent fraud. This Android build removes the Advertising ID permission and disables Firebase Advertising ID collection; other app or installation identifiers may still be used.

Use the app's advertising/privacy choices and applicable device settings to manage available consent options. Analytics consent and advertising consent are separate. Ads may be contextual or limited where consent/settings require it. Optional rewarded actions describe their benefit before the ad; basic file access and manual cleanup remain available. An active ad-free membership or earned ad-free period suppresses ads according to the app's displayed terms.

4. Purchases, restoration and verification

Google Play handles checkout and payment details. We do not receive your complete payment card details. To verify or restore an owned ad-free purchase, Files sends the product identifier and Google Play purchase token over HTTPS to our Google Cloud/Firebase purchase-verification function. Firebase Authentication supplies an anonymous app-install credential; App Check/Play Integrity supplies an application/device integrity credential. The verifier checks the purchase with Google Play and returns entitlement status, plan and expiry as applicable.

Purchase fulfillment is independent of optional analytics consent. We do not put purchase tokens, receipt contents or authentication credentials in our Analytics events. Google Play and linked Firebase Analytics may process purchase amount/currency and product/revenue information for consented measurement. Google retains its own transaction records under its policies. The function does not operate a file-storage service or a customer-content database.

5. Diagnostics and security

Google's ad and platform SDKs can process technical performance, security and fraud-prevention information. Optional Firebase crash-reporting support exists in the application, but the dedicated Crashlytics dependency is not enabled in this release. Our diagnostic adapters do not intentionally attach document names, paths or content. Network services receive ordinary request metadata, such as source IP and timing, and may retain security/operational logs.

Publisher analytics, purchase verification and Google SDK traffic use encrypted network connections. User-selected transfers use the protocol you choose. HTTPS/WebDAV, SFTP, encrypted SMB and FTPS provide encrypted transport as supported by the destination. Plain FTP is unencrypted and requires an explicit warning/approval in the app; file contents and connection credentials can be exposed in transit when you choose it. Consequently, not every possible transfer in this app is encrypted. Local file locking creates an encrypted copy; the original file and other readable copies are not automatically removed or encrypted. Access controls and encryption do not replace backups or guarantee protection against every device compromise.

6. Service providers and data sharing

We use the Google Drive API for optional Drive connections, Google Play Billing, Firebase Analytics, Firebase Authentication, Firebase App Check/Play Integrity, Google Cloud Functions, Google Ad Manager and Google UMP as applicable. Google may process data in other countries under its applicable policies and contractual arrangements. User-selected storage/connection providers and Android sharing destinations receive only what is necessary for the action you request. We do not sell your file contents or installed-app inventory.

Google privacy: https://policies.google.com/privacy
Firebase privacy: https://firebase.google.com/support/privacy
Google partner services: https://policies.google.com/technologies/partner-sites

7. Retention and deletion choices

Local caches can be cleared in Settings; individual app-managed items and saved connections can be removed in the app. Android app-data clearing/uninstallation removes app-private local data, but does not automatically delete shared-storage originals, external copies, Google Play orders or information already processed by Google services. Back up important app-managed content before clearing app data.

Analytics and platform records follow their configured service retention and deletion controls. Purchase and security information may be retained where needed to provide entitlements, prevent fraud, resolve disputes or meet legal requirements. There is no promise that all third-party records are immediately erased when a local switch is changed.

For a privacy/deletion request, email developer@lookfinity.com and identify Files (com.ideaclan.files), the request and any information needed to locate the relevant records. We will assess the request and any applicable retention requirements. Google Drive authorization does not create a separate Files user account. Because purchase verification uses an anonymous app credential and some measurement data is pseudonymous, we may need additional verification or may be unable to identify a record from an email alone. Do not email file-lock passwords, full payment card details or unnecessary private documents. Google account and Play transaction controls remain available through Google.

8. Children and contact

Files is a general file-management utility, not directed at children under 13. If you believe a child has provided data contrary to this policy, contact developer@lookfinity.com. For privacy questions or changes to this policy, contact the same address. We may update this policy when our practices change. The effective date above identifies this version.