This Policy describes the current implementation of the FileGuard app. Mandatory laws in your country or region may take precedence.
FileGuard is a security utility that lets you keep selected files, captured media, notes, and clipboard text in encrypted vaults on your device and create encrypted backup files.
The app does not require registration or sign-in. The developer does not operate a server that receives your vault files, file contents, passwords, vault names, or activity history. On Android, however, the app may use Google AdMob and Google User Messaging Platform (UMP) for advertising and privacy choices.
The app may process the following information on your device:
This information is processed on your device to provide the app’s features. The developer does not upload it to a developer-operated server.
The app may process the following information in secure storage on your device:
Your plaintext password is not sent to the developer. Biometric authentication is performed by the operating system. The app does not collect fingerprint or face images or biometric templates; it receives only the authentication result.
The app may locally store:
Sensitive settings, including backup state and the automatic-backup password, are stored in a device-key-encrypted local store. You are responsible for keeping your backup password secure.
On the supported advertising platform, currently Android, the app may use Google AdMob and UMP. Google and advertising technology providers may process:
This information may be used for ad delivery, non-personalized ads, frequency capping, measurement, fraud prevention, consent management, security, and legal compliance. The app is implemented to initialize the Google Mobile Ads SDK only after UMP indicates that ads may be requested.
See the Google Privacy Policy and Google advertising technologies information.
FileGuard processes information to:
| Category | Storage and retention | How to delete |
|---|---|---|
| Encrypted vault files and metadata | Stored in app-private local storage until you delete them | Delete the item or vault in the app, clear app data, or uninstall |
| Credentials and security settings | Stored in operating-system secure storage and device-key-encrypted storage until changed or app data is removed | Disable the relevant feature, clear app data, or uninstall |
| Activity history | Up to 500 entries in encrypted local storage | Clear app data or uninstall |
| Temporary decrypted files | Temporarily written to app cache and cleared on startup, backgrounding, or feature completion on a best-effort basis | Close the app or clear its cache/data |
| Clipboard content | Processed through the operating-system clipboard when copy or automatic protection is used | Automatic best-effort clearing, copy other content, or restart the device |
| Encrypted backup files | Stored in a device folder, document provider, or cloud-synced location selected by you until you delete them | Delete through the relevant file manager or storage service |
| Google advertising data | Retained under Google and processor policies and legal obligations | Change app/device ad settings or use Google privacy controls |
The operating system, device manufacturer, document provider, or cloud backup provider may keep separate copies of app data or backup files you create. Those copies are governed by the relevant provider’s policies.
The developer does not sell vault content, passwords, or in-app activity history and does not provide them to third parties through a developer-operated server.
When Android advertising or consent features operate, Google LLC, Google affiliates, advertising technology providers, and related processors may process the information described in Section 2.4. See the separate International Data Transfer Notice.
If you directly select an external app or cloud service through a file picker, sharing function, or backup destination, that provider may process files at your direction. Its privacy policy and security settings apply, and the developer does not control the provider’s practices.
Vault content is not transferred to a developer-operated server. Advertising and consent information may be processed by Google and related processors in the United States and other countries where they operate infrastructure.
If you choose an overseas cloud service as the location for an encrypted backup, the file may be synchronized to servers outside your country at your direction. See the International Data Transfer Notice for details.
The app may use the following permissions or system capabilities when you use the relevant feature:
Denying a permission may disable only the related feature. When the system file picker is used, access is generally limited to items you select.
The current implementation uses measures that include:
No security method eliminates every risk. Device theft, malware, operating-system vulnerabilities, weak passwords, files shared by you, or security issues at an external storage provider may expose information.
Opening or exporting decrypted content to another app may create a separate copy. Original-file deletion and temporary-file or clipboard cleanup may be restricted by the operating system, so you should verify the removal of sensitive content.
Most information remains only on your device, so the developer cannot remotely access, correct, or delete it. You can:
You may contact us regarding information you directly provided to the developer, such as an inquiry email. Where applicable, local law may give you rights of access, correction, deletion, restriction, withdrawal of consent, and complaint to a supervisory authority.
FileGuard is not designed primarily for children and does not require children to provide personal information. Guardians may use parental controls provided by the device or app store. The under-age consent configuration for Android advertising should be separately reviewed against the intended audience and applicable law before distribution.
For questions about this Policy:
For advertising data processed by Google, use the privacy controls and contact procedures described in the Google Privacy Policy.
We may update this Policy when laws, app features, permissions, or third-party SDK practices change. Material changes may be communicated on this page, in the app, or through the distribution page.
Last updated: June 23, 2026