Niapoa Privacy Policy
This Privacy Policy explains how Niapoa, an Android file-transfer application, handles information when users transfer user-selected files to Google Drive.
1. Information Niapoa may process
- Basic Google account identity, such as the email used to show which account is connected.
- Google Drive files and metadata that Niapoa creates, uploads, or is otherwise authorized to work with.
- Local files and folders that the user explicitly selects.
- Transfer metadata such as file name, size, content URI, resumable-session state, confirmed byte position, integrity hashes, retry state, speed measurements, and queue status.
- Operational signals such as connection type, available storage, battery/charging state, and thermal state when used for transfer stability.
2. How information is used
Niapoa uses this information to authorize the Google account chosen by the user, upload selected files, resume supported uploads, verify transfer completion, prevent duplicate queue work, adapt transfer behavior, and perform user-enabled local cleanup after safety checks.
3. Google Drive permission
Niapoa is designed to use the file-specific scope https://www.googleapis.com/auth/drive.file. It does not require unrestricted access to the user's entire Google Drive for its normal transfer feature.
4. Processing and storage
Niapoa is designed to transfer selected file contents directly from the Android device to Google Drive using Google's APIs. The current app does not operate a separate Niapoa developer-hosted server for storing users' transferred file contents.
Small operational records may remain locally on the device, including queue state, resumable-session details, preferences, route-learning measurements, and AGP transfer telemetry. Google OAuth token state may be stored or managed on the device by the app and Google authorization components as needed for an authorized session.
5. Sharing and sale
Niapoa does not sell Google user data or user-selected file contents. File contents are transmitted to Google Drive when the user requests a transfer. Information may be disclosed where required by applicable law or necessary for security or abuse prevention.
6. Retention and deletion
Files uploaded to Google Drive remain under the user's Google Drive controls. Local Niapoa queue and preference data may remain until removed through application controls, Android app-data controls, or uninstallation. User-enabled Safe Move behavior is designed to delete a local source only after applicable transfer verification and source-reference safety checks.
7. User controls
- Choose which files to transfer.
- Disconnect or switch the Google account used by Niapoa.
- Revoke Niapoa from Google Account permissions.
- Clear Niapoa app data or uninstall the app.
- Manage or delete transferred files directly in Google Drive.
8. Security
Niapoa is designed to use HTTPS for Google API transfers and to minimize local temporary file duplication. No security method guarantees absolute protection.
9. Google API Services User Data Policy
Niapoa's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including applicable Limited Use requirements.
10. Changes
This policy may be updated as Niapoa evolves. The effective date will be revised when material changes are published.
11. Contact
For privacy or support questions, use the developer/support contact shown on Niapoa's Google OAuth consent screen. Official website: https://niapoa.com/.