Swift Clone Phone Transfer File Privacy Policy
Updated Date: August 27, 2026
Effective Date: August 27, 2026
This Privacy Policy applies to the “Swift Clone Phone Transfer File” app. This app is a phone-to-phone data migration tool that helps users transfer contacts, calendars, photos, videos, audio, files, app installation packages, and other selected data between their own devices.
1. App Functionality
The app mainly uses local networks, local hotspots, QR code connection, connection codes, and similar device-to-device methods to establish connections and transfer data between user devices.
The app does not upload migrated user data to company servers and does not use company servers to relay contacts, calendars, photos, videos, audio, or files.
2. Information We Process
To provide phone migration features, the app may process the following information after the user grants permission or actively selects data:
1. Contacts: used to migrate contact data.
2. Calendars: used to migrate calendar data.
3. Photos, videos, audio, and files: used to display, select, and transfer user-selected data.
4. App installation package information: used to transfer supported app installation packages.
5. Camera access: used to scan QR codes and establish device connections.
6. Network and Wi-Fi information: used for device discovery, hotspot connection, local network connection, and data transfer.
7. Local IP address, connection status, and transfer progress: used to establish connections, synchronize transfer status, and display migration progress.
8. Local installation identifier, local migration history, and local status information: used to keep migration records on the device, identify local device status, and maintain the migration process.
3. Purpose of Use
The information above is used only for the following purposes:
1. Displaying transferable data types and content;
2. Establishing connections between user devices;
3. Performing local or local-network data transfer;
4. Displaying transfer progress and results;
5. Keeping local migration records;
6. Maintaining basic app functionality and stability;
7. Displaying ads and measuring ad performance.
4. Data Transfer and Storage
Migration data is mainly transferred directly between user devices through local networks, local hotspots, QR code connection, connection codes, and similar methods.
The app does not upload migrated user data to company servers and does not use migrated data for cloud storage, user profiling, behavior analytics, or purposes unrelated to migration.
Local migration history, connection status, and related information are stored only on the user’s device.
5. Accounts, Login, Payments, and Membership
The app does not provide registration, login, user accounts, VIP membership, payments, orders, or auto-renewing subscriptions.
The app does not require users to log in before using migration features and does not use server authorization to limit migration frequency or migration capabilities.
6. Analytics
The app no longer connects to the company’s own analytics backend. It does not upload user behavior data, device identifiers, or user profiling data to a company analytics backend.
7. Advertising Services
The app integrates Google AdMob to display app open ads, banner ads, and interstitial ads.
Google AdMob may process advertising identifiers, IP address, device information, network information, ad interaction information, diagnostics, and similar information under Google’s applicable policies for ad display, ad performance measurement, fraud prevention, and service security.
Users can manage ad personalization options through their device system settings. Google’s Privacy Policy is available at:
https://policies.google.com/privacy
8. Permissions
The app may request the following permissions:
1. Camera permission: used for QR code scanning and device connection.
2. Contacts permission: used to read and write contact migration data.
3. Calendar permission: used to read and write calendar migration data.
4. Photos, videos, and audio access: used to display, select, and transfer media files.
5. File read and write access: used to transfer user-selected files.
6. Network and Wi-Fi permissions: used for device discovery, local network connection, hotspot connection, and data transfer.
7. Nearby devices or location-related permissions: used on some Android systems to discover nearby devices or obtain Wi-Fi connection information.
If users deny certain permissions, the corresponding migration features may not work, but other features that do not depend on those permissions may still be available.
9. Third-Party SDKs and System Capabilities
The app may use the following third-party SDKs or system capabilities:
1. Google AdMob: used for ad display and ad performance measurement.
2. Google ML Kit / scanning-related capabilities: used for QR code recognition and device connection.
3. Android WebView: used to display local legal pages or in-app pages.
4. File, media, contacts, calendar, permission, local storage, and network connection system capabilities: used to provide phone migration features.
10. Children’s Privacy
If the user is a minor, the app should be used under the guidance of a parent or guardian. Parents or guardians should help minors understand this Privacy Policy and manage permissions when necessary.
11. User Rights
Users can manage the app’s access to camera, contacts, calendars, media, files, network, and other permissions through system settings.
Users may also delete locally stored migration records and local status information by uninstalling the app or clearing app data.
12. Updates to This Policy
We may update this Privacy Policy based on app functionality, legal requirements, or Google Play requirements. The updated Privacy Policy will be displayed in the app or on a public page and will become effective from the date of publication.
13. Contact Us
If you have any questions about this Privacy Policy or how personal information is processed, you may contact us through the contact method provided in the app.