PixelVault Privacy Policy

1. Scope

This Privacy Policy explains how PixelVault for Android accesses, processes, stores, and transfers information when you use the app.

It covers the Android application. It does not automatically cover browser-based tools, other applications, or unrelated website services. PixelVault performs media processing on your device and does not operate a developer-controlled server for storing your backups. However, information you voluntarily send to our support email may be received and retained by us and our email provider.

2. Photos, Videos, and Selected Files

PixelVault accesses files and folders you select or authorize for compression, backup, restoration, enhancement, transfer, or storage management.

This information may include file contents, filenames, folder paths, file sizes, media types, modification dates, dimensions, and associated metadata. Device access is provided through Android’s file and folder selection mechanisms or permissions applicable to older Android versions. Google Photos imports use Google’s Photos Picker. Folder access may remain available after your initial selection so that enabled backups can run later.

3. Photo Metadata and Location Information

Selected photos may contain capture dates, camera details, and GPS coordinates embedded in their metadata.

PixelVault can preserve this information in supported compressed backups. You can change the “Keep date, camera & location” setting in backup options. Original-file backups and file transfers may retain the source file’s metadata even when metadata preservation for compressed photos is disabled. If a file containing GPS metadata is uploaded, that metadata may leave your device with the file. PixelVault does not request your current device location or use photo location information for advertising.

4. Google Account Information and Authorization

When you connect a Google account, PixelVault receives account information needed to identify the account and perform the authorized operations.

The app may keep your account email address, an optional label you assign, the account’s selected role, cached storage-quota information, and authorization-status indicators. PixelVault uses Google authorization provided through Google Play services. You do not give PixelVault your Google password. Access tokens are requested when needed. PixelVault does not intentionally store them as permanent credentials in its backup settings or exported recovery files.

5. Google Drive Access

Google Drive features may request permission to:

• Read Drive files and folders to browse destinations, access selected sources, verify backups, and restore files.
• Create or manage files created by or specifically authorized for PixelVault.
• Read storage-quota information.
• Download selected files and upload backup copies.

The read-only Drive authorization can cover the account’s broader Drive contents. PixelVault uses this access for its visible backup, browsing, verification, restoration, and transfer features. Connecting an account does not authorize us to access it independently through a developer-operated backend.

6. Google Photos Access

Google Photos features may request permission to upload supported media, manage supported app-created content, check items PixelVault uploaded, and import items selected through Google’s Photos Picker.

The app does not use its Photos integration to browse or modify your entire existing Photos library. Google’s own interfaces, terms, privacy practices, processing rules, and storage limits apply when you use Google Photos.

7. Processing on Your Device

Photo compression, supported video processing, AI enhancement, and backup encryption run on your phone.

The app may read battery level, charging status, network type, and available storage to apply your processing and backup rules. PixelVault does not operate a remote AI enhancement service, upload images to a developer-operated AI server, or use your media to train its included AI model.

8. Transfers to Google

When you enable Google backup or transfer features, selected content and necessary metadata travel directly between your device and Google over HTTPS. Drive-to-Drive transfers also pass through your phone. Temporary local copies may be created before the files are uploaded to the destination account. These transfers use your own Google account storage and authorization. Google may process account, connection, request, device, and service information under its own policies.

9. Google API Limited Use

PixelVault follows the Google API Services User Data Policy, including its Limited Use requirements, when using or transferring information received from Google APIs.

Google user data is used to provide the app’s visible features. We do not sell that data, use it for advertising, or use it to train general-purpose AI models. We do not routinely inspect your Google content. If you voluntarily share specific information with support, we use it to address your request. Other access or disclosure would require an applicable legal or security basis.

10. Local App Storage

PixelVault stores working information in its private app storage, including settings, connected-account references, folder selections, backup history, file indexes, transfer progress, upload checkpoints, and temporary processing files.

It also keeps information needed to manage local Pro access, such as subscription verification state and a local installation identifier. Private app working data is excluded from the app’s configured Android cloud-backup and device-transfer mechanisms. Files saved to shared device folders, exported reports, settings exports, and recovery kits are separate from private app storage.

11. Backup Status and Setup Files

Supported Drive backups may include small status and setup files containing filenames, folder paths, file sizes, checksums, backup dates, destination file identifiers, account email addresses, routing preferences, schedules, backup totals, and the phone’s display name.

These files help PixelVault recognize backups and restore supported configuration on another device. They do not intentionally include your Google password, access tokens, encryption passphrase, or payment-card details.

12. Encryption and Recovery Keys

Optional Google Drive backup encryption protects supported file payloads before upload. Your saved passphrase is protected using Android Keystore-backed encryption. A recovery kit contains secret information needed to decrypt your backups. Keep it private and separate from the encrypted backups. Do not send it to support. We cannot recover a lost passphrase or recovery key.

13. Google Play Purchases

Google Play processes PixelVault Pro purchases and subscription payments. PixelVault receives information necessary to verify and restore access, which can include subscription status, purchase tokens, and purchase or order references. We do not receive your complete payment-card, bank-account, or UPI payment credentials through the app’s purchase flow.

14. Advertising, Analytics, and Tracking

PixelVault does not include advertising, behavioral advertising, or developer-operated analytics and crash-reporting integrations. We do not sell your personal information or build advertising profiles from your files.

15. Support Messages and Reports

When you contact us, we may receive your email address, message, attachments, and any information you choose to provide. Support information is retained only for as long as reasonably needed to respond, investigate the issue, maintain necessary records, or satisfy applicable obligations.

16. Features that Change or Delete Files

Some features act on files at your request: backup conflict settings, "Free up space" verified deletions, mirrored deletions, or cache clearing. Compression and AI enhancement create separate processed outputs. Deletion and backup-replacement features require user confirmation and safety checks.

17. Retention and Deletion

Private app information remains on your device until the app updates, clears, or removes it, or you clear app storage or uninstall the app. Uninstalling PixelVault does not automatically delete exported files or cloud backups from your Google storage.

18. Disconnecting Accounts and Withdrawing Access

You can remove a connected account from PixelVault’s account manager at any time. To revoke Google authorization, remove PixelVault’s access through your Google Account connections settings. Disconnecting does not automatically delete previously uploaded content.

19. Your Choices and Rights

Depending on applicable law, you may have rights to access, correct, erase, or restrict personal information. For locally stored information and your own Google content, Android and Google account controls provide direct ways to manage the data. Contact pixelvault.apps@gmail.com for inquiries.

20. Children

PixelVault is not designed or marketed for children under 13. Where local law requires a higher age or parental permission, that requirement applies.

21. Security and Third-Party Services

PixelVault uses HTTPS for network transfers, private app storage for working information, Android Keystore protection for saved encryption credentials, and supported backup-verification checks.

22. Policy Updates and Contact

We may update this policy when features, data handling, or applicable requirements change. The date at the top identifies the current version.