Effective date: September 20, 2026
Last updated: September 20, 2026
App: IFTP: FTP Client & WiFi Server
Android package: com.iftp.app
Publisher name used in this policy: IFTP
Privacy contact: Use the developer contact email shown on IFTP's Google Play Store listing.
This policy describes the IFTP Android app. It explains what information the app handles,
where it goes, who may receive it, and how it is retained or removed. The app name is used
to identify the publisher because no separate legal publisher name or privacy email is
provided in the project materials.
1. WHAT IFTP DOES
IFTP is an FTP and FTPS client, a file manager for remote servers, a media player for
supported server files, and an optional FTP server that runs on your phone. You provide
the server details and choose what files to browse, upload, download, play, or share.
IFTP does not require an account, and the app does not use an IFTP-operated server to
relay your files or store your saved server passwords.
2. INFORMATION THE APP HANDLES
Saved server connections. If you save a connection, IFTP stores its name, server address,
port, username, connection type and settings, and password on your device. Saved
passwords are encrypted in private app storage using Android's secure key storage. The
app uses these details to test or connect to the server you selected. They are not sent
to the IFTP publisher or included in advertising requests.
Files and folders. When you browse, upload, download, ZIP, or play content, IFTP handles
the file and folder names, file sizes, and file contents needed for that action. You grant
access using Android's file picker, or you can enable All phone folders and grant Android's
All files access on supported versions. On older Android versions the app requests the
applicable shared-storage permissions. Android restricts access to other apps' private
data and protected system files. You can revoke permissions in Android Settings. Access
to a folder selected through Android's picker can be revoked there as well.
Transfer history. Transfer entries, including their names, progress, state and result,
are kept in the app's process memory while it runs. They are not sent to the publisher and
are cleared when the app process ends. You can remove finished entries in Transfers.
Temporary files. ZIP archives created for upload are held in the app cache and deleted
after the upload attempt. Playback may temporarily buffer media or use a cached fallback
file in the app cache. A newer fallback replaces the previous one. Android may clear app
cache files. If the app or device stops unexpectedly, a temporary file can remain until
Android clears the cache or the app next replaces it. A cancelled or failed download to a
location you selected may leave a partial file there; check that location and remove it
if you do not want to keep it.
Phone server. If you start PC access, IFTP runs an FTP server on your phone and shares the
folder or accessible storage scope you selected. Connected computers can browse or
download those files. If you turn off read-only protection, they can also upload, replace,
rename, or delete files within the shared scope. If you turn off password protection,
devices that can reach the server on the network can connect without a password. The
server shows a foreground notification with a stop control and ends after its session
limit or when stopped. Phone-server FTP is not encrypted; use a trusted private network.
The Copy connection details control puts the server address and login details in Android's
clipboard so you can paste them on your computer. On supported Android versions IFTP marks
this content as sensitive. Keep it private and clear it when you no longer need it.
Network and device information. A server you connect to receives the network connection,
login credentials, commands, and file data needed to carry out your request. The server
operator may keep its own connection logs. In phone-server mode, the connecting computer
can receive your phone's shared files and the connection details shown by the app. IFTP
does not collect your precise location, contacts, or call history.
3. FILE TRANSFERS AND OTHER RECIPIENTS
Transfers and remote playback connect directly between your phone and the FTP/FTPS server
you select. Uploads go to that server; downloads are written to the destination you select
in Android's save dialog. If you select a cloud-backed document provider, that provider
may process the selected files under its own privacy policy. If you open a downloaded file
with another app, that app receives access to the file you chose to open and handles it
under its own policy.
When you deliberately run the phone FTP server, computers you authorize or allow onto
your local network can access the shared scope according to your password and read-only
settings. The IFTP publisher does not receive these files through the phone-server feature.
4. ADVERTISING AND GOOGLE PRIVACY SERVICES
IFTP includes Google Mobile Ads (AdMob) and Google's User Messaging Platform (UMP). The
Google Mobile Ads SDK can automatically collect and share your IP address (which may be
used to estimate general location), interactions with the app and ads (such as app opens,
ad taps and video views), diagnostic information, and device or account identifiers. These
may include the Android advertising ID and app set ID, where applicable. Google describes
these uses as advertising, analytics, and fraud prevention. Google says SDK data is
encrypted in transit using TLS. Google's SDK and privacy practices may change; see its
current disclosures and privacy policy:
Google Mobile Ads SDK data disclosure:
https://developers.google.com/admob/android/privacy/play-data-disclosure
Google Privacy Policy:
https://policies.google.com/privacy
Google advertising information:
https://policies.google.com/technologies/ads
UMP requests consent and regional privacy configuration from Google and presents privacy
messages when they apply. You can reopen available choices inside IFTP at More > Ad
privacy choices. Your region and choices affect ad requests. Choosing non-personalized
advertising or using a rewarded-ad period without ads does not necessarily stop all data
processing by the ad service. Android provides controls for resetting or limiting the
advertising ID.
Rewarded ads are optional. If you choose to watch an available rewarded ad, IFTP offers
15 minutes without ads. Saving connections and transferring files do not require you to
watch an ad.
5. PERMISSIONS
Internet and network-state access let IFTP connect to your chosen FTP/FTPS server, run
the phone FTP server when you start it, and communicate with Google advertising and
privacy services.
All files access on Android 11 and later, or shared-storage permissions on older Android,
lets you use the optional All phone folders mode. You can instead choose one folder with
Android's system picker. Android protects private app data and system areas.
Foreground-service and notification permissions support transfers or phone-server
sharing that continue while you use another app, show status and provide a stop or cancel
control. Wake-lock access helps active transfers continue while the screen is off. IFTP
does not use these permissions to track your location.
6. RETENTION AND DELETION
Saved connections are kept in encrypted private app storage until you delete them in IFTP,
clear IFTP's app data, or uninstall the app. Clearing app data or uninstalling removes
those private app records. It does not remove downloaded files saved in a folder you
selected or files already uploaded to a remote server.
Transfer history exists only in app process memory. Remove individual finished entries or
clear finished history from the Transfers screen. The transfer-list controls do not delete
downloaded or uploaded files. Partial files from cancelled or failed transfers may remain
at their selected destination.
Temporary ZIP and playback data are kept in the app cache as described above. Android may
remove cache data. Files saved to a user-selected location remain there until you delete
them. Remote files and server logs are managed by the operator of that server, not by IFTP.
Google retains and processes advertising and privacy-service data under Google's policies
and controls. Removing IFTP data does not itself delete records Google or your server
operator already holds. Contact those providers for their data requests and controls.
7. SECURITY
Saved connection passwords are encrypted at rest in app-private storage. FTPS protects
the connection with TLS when supported and correctly configured by the server. Plain FTP,
including the phone FTP server, does not encrypt the username, password, commands, or file
contents in transit. Use FTPS where available and use phone-server mode only on a trusted
network. No software or network method can guarantee absolute security.
8. CHILDREN
IFTP is a general file-transfer utility and does not ask for a user's age, create child
profiles, or offer child-directed features. The Google advertising SDK may process the
technical and advertising information described in section 4. The publisher should keep
the app's Google Play target-audience declaration and AdMob child-directed settings
consistent with its actual audience and applicable requirements.
9. YOUR PRIVACY REQUESTS AND REGIONAL RIGHTS
Depending on where you live, you may have rights to request access to, correction of, or
deletion of personal information, or to object to or restrict certain processing. IFTP
does not operate a user account or central file-transfer database. You can manage saved
connections and transfer history in the app, revoke Android permissions in system
settings, and use Google's and your server operator's privacy controls for information
they process. For a privacy question or a request relating to the IFTP publisher, use the
developer contact email on IFTP's Google Play Store listing. Do not send passwords or
private files with a privacy request.
10. CHANGES
This policy will be updated if IFTP's data practices change. The effective date at the top
will be revised when a new version is published. The publisher should keep this policy,
the Google Play Data safety form, the app's actual behavior, and its privacy contact
consistent.
RELATED GOOGLE PLAY DISCLOSURES
Google Play requires a privacy policy and accurate disclosure of data handled by the app
and its third-party SDKs. The Google Mobile Ads SDK's automatically collected data is
described above. The publisher remains responsible for reviewing and completing the
IFTP-specific Google Play Data safety form.
Google Play User Data policy:
https://support.google.com/googleplay/android-developer/answer/10144311