1. Scope and who this policy covers
This Privacy Policy describes data handling by Multi Space, the Android app with package name com.multispace.appcloner, and this Multi Space website. “We,” “us,” and “our” refer to Fidei Trading Limited, the developer of Multi Space.
Multi Space manages separate instances of applications you choose to use. A source application, a cloned instance, Google Play, and other external services may have their own privacy policies. Their collection and processing are covered by those policies as well as any handling by Multi Space described here.
2. Information used on your device
- Installed applications: Multi Space reads application names, package names, icons, versions, and related package information to list compatible source applications and create or launch the instances you select.
- Instance data: The container stores installed application files and each instance’s application data, which may include signed-in sessions, account tokens, settings, and files created by that application. These are handled within the app’s storage on your device; the application itself may communicate with its service provider.
- Organization and preferences: Multi Space stores instance identifiers and numbers, custom names and icon choices, workspaces, display order, theme and language choices, and recent launch or failure records for management and search.
- Device and compatibility information: Device model, Android version, CPU architecture, application version, permission and notification settings, and network availability may be read for operation and local diagnostics. Supported instance settings may provide virtual device identifiers to an application. These do not guarantee anonymity or prevent that application from identifying a device or account.
The management interface does not send your custom instance names, workspace names, installed-app list, or cloned account contents to Firebase Remote Config. Local diagnostics can be previewed and exported by you; reports can include device configuration, application package names, and instance identifiers. The diagnostic export flow does not automatically upload a report to us.
3. Permissions and application content
Applications running inside Multi Space may need permissions for their features. Depending on the Android version, the application you run, and the permissions you grant, this may involve contacts, calendars, location, photos, video, audio, files, camera, microphone, phone or account information, Bluetooth, and notifications.
Multi Space supports access to these capabilities through the container where Android and the engine allow it. For example, a messaging application may use your microphone for a call or a photo you select for an attachment. A permission declaration alone does not mean every feature is used or every item is read.
You can review or revoke available permissions in Android Settings. Revoking a permission may limit the relevant application feature. Review the policies and permission requests of the applications you run: their content and network traffic are not made private merely by running in a separate instance.
4. Firebase configuration and Analytics choices
Multi Space uses Google Firebase Remote Config to retrieve updates and feature configuration, including minimum supported app versions, update notices, component visibility, advertising display settings, and free-use limits.
To provide this service, the Firebase SDK processes an installation identifier and technical information such as the application ID and package name, application or SDK version, platform and Android version, country and language codes, time zone, and service request information. Google may also process IP addresses and operational service logs. An installation identifier identifies an installation; it is not the same as your cloned account or its password.
Configuration values are cached on your device so previously received settings can continue to apply when a network request fails. Changing component visibility does not delete your existing instances or their account data.
Firebase Analytics consent settings follow the app’s recorded privacy choice. This choice is separate from Google’s advertising consent messages described below. Analytics collection is disabled by default in the current configuration; updating a consent setting does not itself establish that Analytics collection is enabled. Automatic Crashlytics reporting is also disabled. Remote Config still makes network requests and processes technical data for its service independently of Analytics consent.
For Google’s processing and retention information, see Privacy and Security in Firebase, Firebase Android data disclosure information, and the Google Privacy Policy.
5. Advertising and ad privacy choices
Multi Space uses Google Mobile Ads (AdMob) to display advertising in the Multi Space interface and Google User Messaging Platform (UMP) to obtain consent information and present privacy messages where required. Ad requests depend on the app’s access checks and UMP’s ad-request eligibility result. Eligible ads may be displayed without personalized advertising; declining personalization does not necessarily remove all ads or all technical processing.
Google’s advertising SDK processes information such as IP addresses (which can indicate approximate location), device, advertising, and applicable account-related identifiers when available, app and device information, app launches, ad views and interactions, and diagnostic and performance information. This is used to deliver and measure ads, operate the advertising service, and detect fraud or abuse. UMP processes consent information and privacy choices. Processing depends on your device settings, consent choices, and the applicable ad-serving mode. If mediation partners are enabled to supply an ad, they may also process advertising data; review the provider information in the applicable consent message or ad information.
Where Google requires an ad privacy options form, an advertising privacy entry is available in Multi Space Settings to review or change your choices. You can also review Android’s advertising privacy controls. Active Premium access removes advertising supplied by the Multi Space interface; it does not remove advertisements within applications you run or change those applications’ data practices.
See Google Mobile Ads data disclosure, How Google uses information from sites or apps that use its services, and the Google Privacy Policy.
6. Subscriptions and other in-app purchases
Multi Space uses RevenueCat with Google Play Billing to offer purchases, check subscription entitlements, and restore eligible purchases. RevenueCat is initialized when the app’s main process starts and can contact its service to check access even if you do not make a purchase. Subscription processing is separate from Analytics and advertising consent.
The integration uses a RevenueCat-generated app user identifier rather than a Multi Space login. RevenueCat processes this identifier, purchase and subscription records (such as product identifiers, purchase tokens, transaction dates, renewal or expiration status, and entitlements), and technical app, device, operating-system, and service-request information to validate purchases and maintain access. This identifier is pseudonymous; it does not mean that no information is processed. The integration does not attach your cloned-app passwords, messages, or workspace names as customer profile attributes.
Google Play handles billing and payment details under its own terms and privacy policy. Multi Space does not ask you to enter payment-card details in the app. Purchase and entitlement status may be cached locally. Restoring a purchase restores eligible access; it does not restore cloned application files, accounts, or messages.
See RevenueCat’s Privacy Policy, RevenueCat’s Google Play data disclosure, and the Google Privacy Policy. Purchase, renewal, and cancellation conditions are described in our Terms of Service.
8. Storage and security
Multi Space uses Android app-private storage and the engine’s per-instance storage separation for container data. Local separation is a management feature, not a guarantee of security against a compromised device, malicious application, or someone who can unlock your phone.
Firebase configuration requests use HTTPS. Network security and storage inside applications you run depend on those applications and their providers; we cannot promise that all guest-application traffic or files are encrypted.
The app’s Android backup rules exclude the virtual application data directory and selected legacy data stores from system cloud backup and device transfer. Other app preferences or management metadata may be included according to Android, device-provider, and user backup settings. Files or reports you export are outside this protection and remain at the destination you choose.
9. Retention and deletion
- Remove an instance: Deleting an instance through Multi Space removes that installation and its container data through the engine. It does not delete the source application or the account held by its service provider. Some management records, including a retired instance identifier, can remain locally to avoid confusing an old instance with a later one.
- Remove a workspace: Deleting a workspace moves its instances to the default group; it does not erase their application data or signed-in sessions.
- Remove all local Multi Space data: Use Android Settings → Apps → Multi Space → Storage → Clear data, or uninstall Multi Space. This removes the local app container and preferences. System backup copies and any files you exported must be managed separately with the relevant device or storage provider.
- Delete a third-party account: Use that application’s account-deletion process or contact its provider. Multi Space does not create a separate cloud Multi Space account in the current version.
- Purchases and subscriptions: Clearing app data or uninstalling Multi Space does not cancel a Google Play subscription or delete purchase records held by RevenueCat or Google. Manage or cancel subscriptions in Google Play. Use Restore purchases with the relevant Google Play account to recover eligible access after reinstalling. Purchase records may be retained to validate access, handle refunds or disputes, prevent fraud, and meet legal obligations.
- Provider data: Google/Firebase, advertising providers, RevenueCat, and GitHub retain identifiers and service records under their applicable policies and service requirements. Clearing local data is not a promise of immediate deletion from their servers. Contact us for a request concerning data processed for Multi Space, and consult the linked provider policies.
Support information is retained while needed to handle the request and meet applicable legal obligations. Avoid sending unnecessary sensitive information. Public support posts remain governed by GitHub’s tools and policies.
10. Your choices and privacy rights
You can choose which applications to add, change or delete local organization information, revoke available Android permissions, delete instances, and clear local app data. You can also choose whether to send an exported diagnostic report or support message.
Review any privacy choice presented by the app, use the advertising privacy options in Settings when available, review Android’s advertising controls, and manage purchases through Google Play. If you need help withdrawing consent or making a privacy request beyond the controls available in the app, contact us below. Advertising choices do not cancel a subscription or erase provider transaction records.
Depending on your location and the law that applies, you may have rights to request access, correction, deletion, portability, restriction, or objection concerning personal data, withdraw consent where processing relies on consent, or complain to a data protection authority. Contact us to make a request. We may need information sufficient to verify and locate the request without asking for your application account password.
Google/Firebase, advertising providers, RevenueCat, and GitHub may process information in countries other than your own. Their linked privacy and data-processing information describes their international handling. These rights do not remove independent processing by an application provider you use.
11. Children
Multi Space is a general-purpose application-management tool and is not designed as a service directed to children. Do not provide a child’s personal information in a support request. If you believe a child has provided personal information to us, contact us so we can review and address the matter under applicable law. Applications used inside Multi Space may have separate age requirements.
12. Changes to this policy
We may update this policy when the app’s data handling or legal requirements change. The last-updated date above identifies this policy version. Where required, material changes will be accompanied by an appropriate notice or consent request. An updated policy does not substitute for permission or consent required by law.
13. Contact
Developer: Fidei Trading Limited
App: Multi Space (com.multispace.appcloner)
Email: addaeisidore@gmail.com
For questions about Multi Space, this policy, or a privacy request, email us at the address above. Describe the request and include only information needed to help us respond. Do not send passwords, account tokens, or unnecessary sensitive documents.
General, non-sensitive issues may also be reported through the Multi Space support issue tracker. That channel is public; use email for a private privacy inquiry.