Effective Date: August 21, 2026
This Privacy Policy applies to CloudVault, an Android mobile application developed and provided by HyperNest Innovations.
CloudVault is designed to allow users to create an account, upload and organize files and media in cloud storage, manage folders, view photos and videos, play audio files, mark supported cloud files as favorites, access recently uploaded content, use a protected Vault area, download or share files, and manage account and security settings.
This Privacy Policy explains what information CloudVault may access, collect, process, store, transmit, or share when you use the Application.
Depending on the features you use, CloudVault may collect or process information including:
account information such as your name, email address, Firebase user identifier, and authentication information;
files, photos, videos, audio, and documents that you explicitly select, scan, upload, or otherwise add to CloudVault;
file metadata such as file name, file type, MIME type, file size, folder association, upload date, favorite status where supported, and storage path;
media metadata such as generated thumbnails, video or audio duration, and audio waveform information where generated by the Application;
folder information such as folder names, item counts, storage totals, and creation dates;
account plan and storage-usage information;
Vault configuration and Vault-related file metadata;
application security preferences, including app-lock and Vault configuration;
application preferences such as selected language, onboarding state, and login preferences;
application usage and technical information processed by Firebase or other enabled Google services;
crash and diagnostic information where Firebase Crashlytics is enabled;
Firebase Cloud Messaging information needed to provide supported notifications.
CloudVault does not intentionally access user files that the user has not selected, uploaded, scanned, or otherwise provided through supported Application functionality.
CloudVault uses Firebase Authentication to provide account functionality.
Depending on the sign-in method selected by the user, CloudVault may process:
email address;
password authentication credentials through Firebase Authentication;
Google account authentication credentials through Google's supported authentication services;
Firebase user identifier;
basic account profile information provided through the authentication method.
Passwords used with Firebase Authentication are handled through Firebase Authentication infrastructure. HyperNest Innovations does not intentionally store plain-text account passwords in the CloudVault Realtime Database.
CloudVault may use Android Credential Manager and Google's identity services to support Google authentication.
Authentication information handled by Google or Firebase is subject to Google's applicable terms and privacy practices.
CloudVault may allow users to sign in using a Google account.
When Google authentication is selected, Google may provide CloudVault and Firebase Authentication with information necessary to identify and authenticate the user, such as:
Google account identifier;
email address;
display name or other basic profile information made available by the authentication flow;
authentication tokens required to complete sign-in.
CloudVault uses this information for account authentication and account-related Application functionality.
CloudVault does not obtain the user's Google account password.
CloudVault uses Firebase Storage to store user-uploaded cloud content.
Depending on the content selected by the user, stored files may include:
photos;
videos;
audio files;
PDF files;
documents;
scanned documents;
other supported files.
CloudVault stores files under account-specific Firebase Storage locations associated with the authenticated user's unique Firebase identifier.
Uploaded content is used to provide the cloud-storage functionality requested by the user.
HyperNest Innovations does not intentionally inspect user-uploaded files for advertising profiling.
Users should avoid uploading information they do not have permission to store or share.
CloudVault uses Firebase Realtime Database to store information required to organize and provide cloud functionality.
This may include metadata such as:
file identifier;
file name;
MIME type;
media category;
folder identifier;
file size;
Firebase Storage path;
thumbnail path or thumbnail URL;
media duration;
waveform data for supported audio files;
favorite status for supported non-Vault files;
creation or upload timestamp.
This metadata allows the Application to display files, organize folders, show media thumbnails, provide playback information, calculate storage usage, and support other CloudVault functionality.
Users may explicitly choose photos to upload to CloudVault.
CloudVault may:
upload selected images to Firebase Storage;
generate or store thumbnail information;
display image previews;
display images through the built-in image viewer;
allow supported images to be shared;
allow images to be downloaded to the user's device;
allow normal cloud images to be marked as favorites;
allow users to delete uploaded images.
CloudVault does not intentionally upload the user's entire photo library merely because the Application is installed.
Only content selected or otherwise explicitly added by the user is intended to be processed for upload.
Users may explicitly choose videos to upload to CloudVault.
CloudVault may process:
the selected video file;
file name and file size;
MIME type;
thumbnail;
video duration;
upload and folder metadata.
CloudVault includes video playback functionality using Android media technologies.
Video content may be downloaded, shared, or deleted where supported.
CloudVault supports audio-file storage and playback.
For audio selected by the user, the Application may process:
the audio file;
file name;
MIME type;
size;
duration;
waveform information used for the audio-player interface;
folder and upload metadata.
Audio playback occurs through supported Android media functionality.
CloudVault may allow audio files to be shared or downloaded to the user's device.
CloudVault may allow users to upload and manage documents and other supported file types.
When a user chooses to open a file type that CloudVault does not display internally, the Application may prepare a temporary local copy and use Android's standard file-opening mechanism to allow the user to choose a compatible external application.
The selected external application is independent from HyperNest Innovations and may process the file according to its own privacy practices.
CloudVault includes Google's ML Kit Document Scanner dependency and may provide document-scanning functionality.
When the user explicitly starts document scanning, Google's document-scanning technology may process camera or document information needed to provide the scanning experience.
Documents produced through the scanner are processed only as required for the user-selected feature and may subsequently be stored in CloudVault if the user chooses to add them.
Information processed by Google components is subject to Google's applicable privacy practices.
CloudVault allows users to organize files into folders.
The Application may store folder information including:
folder identifier;
folder name;
item count;
total size;
creation date;
association between files and folders.
Folder information is associated with the authenticated user's account.
CloudVault may display recently uploaded files.
The Application may use stored upload timestamps and file metadata to determine which files should appear in the Recent section.
This information is part of the user's CloudVault account data.
For supported normal cloud files, users may mark files as favorites.
CloudVault stores favorite status in the user's account data so that supported files can be shown in the Favorites category.
Vault files are not currently assigned favorite status.
CloudVault provides a protected Vault area intended to give users an additional level of privacy within the Application.
Vault functionality may process and store:
Vault security configuration;
Vault PIN-related security information in protected form;
security question and related recovery configuration where used;
Vault folder information;
Vault file metadata;
Vault photos, videos, audio, and documents added by the user;
thumbnail or media metadata necessary to provide supported Vault interfaces.
Vault data is associated with the authenticated user's account.
CloudVault may require the user to enter the configured Vault PIN before accessing protected Vault content.
The Application also locks the Vault in security-sensitive situations, such as when the Application leaves the foreground or when the user leaves the protected Vault flow according to the implemented security behavior.
CloudVault may provide Application-level security features including:
PIN-based app lock;
supported device-authentication or biometric options where available;
security configuration settings;
Vault PIN protection;
security-question recovery functionality where implemented.
Security settings may be stored locally and/or in the user's account configuration as required by the implemented feature.
Biometric authentication, when used, is handled through Android's security mechanisms. CloudVault does not receive or store the user's fingerprint or facial biometric template.
When the user explicitly selects Download, CloudVault may retrieve the selected file from cloud storage and save it to publicly accessible media storage on the device.
Depending on the media type, downloaded content may be stored under directories such as:
Pictures/CloudVault for images;
Movies/CloudVault for videos;
Music/CloudVault for audio;
a supported Downloads location for other file types where applicable.
On modern Android versions, CloudVault uses Android's supported MediaStore mechanisms for public media storage.
On older supported Android versions, legacy external-storage access may be used where required by Android.
Downloaded media may therefore become visible to other compatible applications on the user's device, such as Gallery, Photos, video-player, music-player, or file-manager applications.
Once downloaded outside CloudVault's private application storage, the file may be accessible according to Android's storage rules and the permissions of other applications.
CloudVault allows users to share supported files using Android's system sharing interface.
When the user chooses Share:
CloudVault may temporarily retrieve or prepare a local copy of the selected file;
the Application may expose the file through Android FileProvider;
Android's share chooser allows the user to select another application to receive the file.
The receiving application is chosen by the user and is not controlled by HyperNest Innovations.
Once a file is shared with another application or person, its subsequent use is governed by the recipient or receiving service.
Temporary sharing copies may be stored in the Application's cache and may later be removed through normal cache cleanup, sign-out cleanup, Android system behavior, or Application data removal.
For Android versions where direct writing to shared public storage requires legacy permission, CloudVault may request:
WRITE_EXTERNAL_STORAGE
The Application declares this permission only for Android versions where it is applicable.
CloudVault uses this access when required to save user-requested downloads into publicly accessible storage.
On newer Android versions, supported MediaStore APIs are used instead and this legacy permission is not required.
CloudVault requires Internet access for core cloud functionality.
Internet access may be used for:
account registration and authentication;
Google authentication;
uploading files;
downloading files;
synchronizing file and folder metadata;
Firebase Realtime Database;
Firebase Storage;
Firebase Analytics;
Firebase Crashlytics;
Firebase Remote Config;
Firebase Cloud Messaging;
application updates;
billing-related functionality;
other online functionality expressly provided by the Application.
Uploading and downloading files consumes network bandwidth and may count toward the user's Internet or mobile-data allowance.
CloudVault may use Android network-state information to determine whether Internet connectivity is available.
The Application declares:
ACCESS_NETWORK_STATE
This information is used to support connectivity-dependent features and does not provide CloudVault with the contents of the user's network communications.
On supported Android versions, CloudVault declares:
POST_NOTIFICATIONS
CloudVault may use notifications for supported Application functionality, account-related information, updates, cloud activity, or Firebase Cloud Messaging where implemented.
Notification permission is optional unless Android requires a notification for a specific supported operation.
Users may decline or disable notifications through Android Settings.
CloudVault uses Firebase Realtime Database to store and synchronize account-related metadata.
Information stored may include:
user profile information;
plan information;
storage usage;
folders;
cloud-file metadata;
favorite status;
Application security configuration;
Vault configuration;
Vault-file metadata;
account creation information;
other data necessary to provide CloudVault functionality.
Database records are associated with the user's authenticated Firebase identifier.
CloudVault uses Firebase Storage for user-uploaded files and generated media resources.
Storage content may include:
uploaded files;
photos;
videos;
audio;
documents;
thumbnails;
Vault content;
other media generated or uploaded through supported Application functionality.
Storage objects are organized within user-specific account paths.
CloudVault includes Firebase Analytics.
When enabled, Firebase Analytics may process information such as:
Application interactions;
screen and feature usage;
session information;
Application version;
device and operating-system information;
Firebase installation identifiers;
general usage and engagement events.
Analytics information may be used to understand how the Application is used, improve features, evaluate reliability, and improve the overall user experience.
HyperNest Innovations does not intentionally include users' uploaded file contents, Vault PINs, passwords, or raw private media contents in custom Firebase Analytics events.
Information processed by Firebase Analytics is governed by Google's applicable terms and privacy practices.
CloudVault includes Firebase Crashlytics.
Crashlytics may process technical information such as:
crash stack traces;
Application version;
device model;
operating-system version;
diagnostic logs;
technical identifiers;
crash-related Application state.
Crash information is used to identify technical problems and improve Application reliability.
HyperNest Innovations does not intentionally submit users' file contents, passwords, or Vault PINs as Crashlytics data.
CloudVault may use Firebase Remote Config to remotely provide Application configuration values.
Remote Config may process technical identifiers and device/Application information necessary to provide its service.
Remote Config is not intended to retrieve the contents of users' cloud files or Vault files.
CloudVault includes Firebase Cloud Messaging.
Firebase Cloud Messaging may process:
device or Application-instance identifiers;
messaging registration tokens;
technical device/Application information needed to deliver notifications.
These technologies may be used to deliver supported CloudVault notifications.
Information processed by Firebase Cloud Messaging is governed by Google's applicable privacy practices.
CloudVault may use Google Play technologies including:
Google Play Services;
Google Play In-App Updates;
Google Play In-App Review;
Google Play Billing;
Google authentication services;
Google ML Kit Document Scanner.
These services may process technical or account-related information necessary to provide their respective functionality.
Information processed by Google is subject to Google's applicable privacy policy and terms.
CloudVault includes Google Play Billing support.
If paid plans, subscriptions, or other in-app purchases are offered in the published version, payment processing is handled by Google Play.
HyperNest Innovations does not directly receive or store full payment-card information through CloudVault.
Google may process purchase information, payment status, order information, and related account details according to Google Play's own privacy practices.
CloudVault may process subscription or entitlement status required to provide purchased functionality.
CloudVault's Android configuration may declare Google's advertising identifier permission:
com.google.android.gms.permission.AD_ID
Declaring this permission does not by itself mean that CloudVault directly reads or uses the Advertising ID.
If advertising or another integrated SDK in the published version accesses the Advertising ID, that processing is subject to the relevant SDK configuration, Google Play requirements, consent requirements, and this Privacy Policy.
HyperNest Innovations will keep the published Application and Google Play Data safety disclosures aligned with the SDKs actually enabled in the released version.
CloudVault includes Google's User Messaging Platform (UMP) library.
Where required by applicable law or Google policy, UMP may be used to present consent or privacy choices associated with supported Google services.
Information processed through UMP is governed by Google's applicable terms and privacy practices.
CloudVault stores certain preferences locally on the device.
These may include:
onboarding completion;
selected language;
remembered-login preference;
basic Application state;
permission or disclosure state;
other configuration values necessary for the Application.
These preferences are intended to improve user experience and preserve Application settings.
Certain features may temporarily store files in CloudVault's private cache.
Examples include:
media prepared for sharing;
files prepared for opening through another application;
temporary processing data.
Temporary files are not intended to serve as permanent user downloads.
CloudVault may clear account-specific temporary files when the user signs out or deletes an account.
Android may also remove cached files according to normal operating-system behavior.
For file types that CloudVault does not display internally, the Application may use Android's external application chooser.
A temporary local file may be created and shared with the selected application using a protected content URI.
CloudVault grants the receiving application temporary read access where necessary.
HyperNest Innovations is not responsible for the privacy practices of third-party applications chosen by the user.
CloudVault allows authenticated users to sign out.
When the user signs out:
the Firebase Authentication session is terminated;
remembered-login state is removed;
account-specific Application state is cleared from the active session;
Vault and Application unlock state is reset;
selected media and folder state is cleared;
temporary account-specific cache used by supported features may be deleted.
Signing out does not delete the user's cloud account, uploaded files, Firebase Storage content, or Realtime Database account data.
The user may sign back into the same account to access supported cloud data again.
CloudVault provides an in-Application Delete Account option.
When account deletion is successfully completed, CloudVault is designed to remove data associated with the authenticated account, including applicable:
uploaded files in Firebase Storage;
generated thumbnails;
Vault content;
file and folder metadata;
user profile information;
storage usage information;
security and Vault configuration;
Firebase Realtime Database account data;
Firebase Authentication account.
Local account-specific Application state and temporary cache are also cleared after successful deletion.
Account deletion is intended to be permanent and cannot normally be undone.
Firebase may require the user to authenticate again before allowing sensitive account operations such as permanent account deletion.
If reauthentication is required, the user may need to sign in again before deletion can be completed.
CloudVault does not intentionally delete remote cloud files merely because the user signs out. Permanent remote deletion occurs only through supported deletion actions.
Users may delete supported cloud files through CloudVault.
When deletion succeeds, the Application may remove:
the file from Firebase Storage;
associated thumbnail data;
corresponding Realtime Database metadata;
references required to display the file within CloudVault.
Vault-file deletion similarly removes the applicable Vault storage object and metadata.
Folder deletion behavior depends on the functionality offered by the current Application version.
Users should understand that deleted cloud content may not be recoverable unless CloudVault explicitly provides a recovery feature.
Account information, cloud metadata, and uploaded files may remain in Firebase services while the user's CloudVault account remains active and until:
the user deletes individual content;
the user permanently deletes the account;
the data is removed in accordance with service configuration;
retention is otherwise required or permitted by applicable law.
Local preferences may remain until:
the relevant setting is changed;
Application data is cleared;
the Application is uninstalled;
Android removes the data;
CloudVault explicitly clears account-specific session information.
Temporary cache may be removed automatically and is not intended as long-term storage.
Information processed by Google and Firebase services may be retained according to their configurations, terms, and retention practices.
Based on the current Application design, HyperNest Innovations does not intentionally collect through CloudVault:
contact lists;
SMS messages;
call history;
precise GPS-location histories;
Wi-Fi passwords;
microphone recordings obtained in the background;
government identification documents unless the user intentionally uploads such a document as a file;
full payment-card numbers;
biometric fingerprint or facial templates;
files from the device that the user has not selected or otherwise explicitly added;
passwords in plain text;
continuous Clipboard contents.
Users may choose to upload files containing personal or sensitive information. Such content is treated as user-provided cloud content and processed as necessary to provide CloudVault's storage functionality.
Information processed through CloudVault may be used to:
create and authenticate user accounts;
maintain user sessions;
store uploaded files;
display and organize cloud content;
create and manage folders;
show image and video thumbnails;
play video and audio;
generate and display supported media metadata;
provide Recently Added and Favorites functionality;
provide protected Vault functionality;
provide PIN and app-security functionality;
calculate cloud-storage usage;
synchronize cloud metadata;
allow files to be downloaded;
allow files to be shared;
open supported files through compatible external applications;
process account deletion;
deliver notifications;
process subscriptions or purchases where offered;
diagnose crashes and technical problems;
understand general Application usage;
improve Application functionality and reliability;
provide remotely configured settings;
provide Application updates and review functionality;
comply with applicable legal obligations.
HyperNest Innovations does not intentionally use uploaded private files for undisclosed advertising or surveillance purposes.
HyperNest Innovations does not intentionally sell users' personal information or private uploaded files.
Information may be transmitted or processed in the following circumstances.
CloudVault uses third-party infrastructure and services, particularly Google and Firebase, to provide Application functionality.
Depending on enabled services, these providers may process account, technical, diagnostic, cloud-storage, messaging, purchase, or usage information.
When the user chooses to share a file, the selected content may be provided to another application, service, or recipient chosen by the user.
When the user chooses to open a file externally, that file may be made available to the external application selected by the user.
Information may be disclosed where reasonably necessary to comply with applicable law, legal process, regulation, court order, or lawful governmental request.
Information may be processed or disclosed where reasonably necessary to protect users, investigate misuse, prevent fraud, respond to security incidents, or protect the Application and its services.
CloudVault may use third-party technologies or services including:
Google Firebase Authentication;
Firebase Realtime Database;
Firebase Storage;
Firebase Analytics;
Firebase Crashlytics;
Firebase Remote Config;
Firebase Cloud Messaging;
Google Play Services;
Google Credential Manager integration;
Google Identity services;
Google Play Billing;
Google Play In-App Updates;
Google Play In-App Review;
Google User Messaging Platform;
Google ML Kit Document Scanner;
Coil for media loading;
Android Media3 for supported media playback and processing;
OkHttp.
These providers and technologies may process information according to their applicable configurations, terms, and privacy policies.
HyperNest Innovations is responsible for configuring the SDKs in the published Application consistently with this Privacy Policy and applicable Google Play requirements.
HyperNest Innovations uses reasonable technical and platform measures intended to protect CloudVault information.
These measures may include:
Firebase Authentication for account access;
account-specific Firebase data paths;
Application-level PIN and Vault controls;
Android's secure file-sharing mechanisms;
HTTPS/TLS protections provided by Firebase and supported services;
temporary private Application cache for file sharing/opening;
Android platform permission controls.
Users are responsible for maintaining the confidentiality of their account credentials and PINs.
No electronic storage or network-transmission system can be guaranteed to be completely secure.
Depending on Android version and enabled functionality, CloudVault may declare or request the following permissions.
Used for:
Firebase Authentication;
Firebase Storage;
Firebase Realtime Database;
file upload and download;
analytics and diagnostics;
Firebase messaging;
Google services;
updates and online functionality.
Used to determine whether network connectivity is available.
Used on supported Android versions for Application notifications where enabled.
Users may decline notification permission.
Declared only for Android versions up to Android 9 where legacy public-storage access may be required for user-requested file downloads.
CloudVault uses modern Android storage APIs on newer Android versions where this legacy permission is not required.
CloudVault's manifest may declare Google's Advertising ID permission.
Its presence does not by itself mean the Application directly accesses the Advertising ID. Any actual processing by enabled SDKs must remain consistent with this Privacy Policy and Google Play disclosures.
Based on the current Android Manifest you provided, CloudVault does not currently declare broad permissions for:
precise location;
contacts;
SMS;
call logs;
microphone;
broad media-library reading.
Where Android system pickers or specialized Google components can provide scoped access to user-selected content, CloudVault uses those mechanisms rather than requesting unnecessary broad access.
CloudVault is not specifically directed to children under the age of 13.
HyperNest Innovations does not knowingly use CloudVault to collect personal information directly from children under 13 in violation of applicable law.
Because users can create accounts and upload files, parents or guardians who believe a child has provided personal information to HyperNest Innovations may contact:
hypernestinnovations@gmail.com
HyperNest Innovations will review the request and take appropriate action where required.
CloudVault may be made available to users in multiple countries.
Depending on the user's location, applicable privacy laws may provide rights regarding access, correction, deletion, restriction, portability, or other treatment of personal information.
Users may contact HyperNest Innovations regarding privacy questions or applicable rights.
Users may control their data and Application experience in several ways, including:
choosing which files to upload;
deleting supported individual files;
creating or deleting supported folders;
marking supported cloud content as favorite or removing that status;
controlling notifications through Android Settings;
downloading their media;
sharing files only when they choose;
signing out of the account;
permanently deleting the account through the provided account-deletion feature;
clearing CloudVault's Application data through Android Settings;
uninstalling the Application.
Some CloudVault functionality requires an authenticated account and Internet connection.
HyperNest Innovations intends to keep CloudVault's Google Play Data safety declaration consistent with:
the actual behavior of the published Application;
Firebase Authentication;
Firebase Realtime Database;
Firebase Storage;
SDKs included in the published build;
analytics and diagnostic services;
account information;
user-uploaded files;
notifications;
purchase functionality;
this Privacy Policy.
Google Play Data safety declarations account for data collected or shared by both Application code and incorporated SDKs.
Therefore, certain data may need to be declared as collected or shared because it is processed by Google or Firebase even where HyperNest Innovations does not manually inspect that information.
HyperNest Innovations may update this Privacy Policy when:
CloudVault functionality changes;
storage or authentication behavior changes;
new permissions are introduced;
SDKs or service providers change;
security features change;
data-handling practices change;
Google Play requirements change;
applicable law changes.
The revised Privacy Policy will be published on the publicly accessible CloudVault Privacy Policy page.
The Effective Date at the top of this Privacy Policy will be updated when material changes are made.
If you have questions, concerns, privacy requests, or account/data-deletion questions regarding CloudVault, contact:
HyperNest Innovations
Email: hypernestinnovations@gmail.com