Museorbit — Privacy Policy
In force from: November 9, 2026
Museorbit (package name: com.museorbit.vidcraft, referred to below as "Museorbit" or "the App") is provided by HAPPY CASTLE ANIMATION TECHNOLOGY CO., LIMITED. This page works like the maker's note that comes with a piece of fired ceramic: piece by piece, it explains what the App takes in, what each part does inside the workshop, and how the finished article is protected.
Keeping the App on your device — or coming back to it after this page has been revised — means you accept the text below. If any part of it does not suit you, uninstalling the App ends the matter.
1. What Museorbit Collects
The short version first: almost everything Museorbit handles stays on the phone or tablet in front of you.
What we never ask for:
- No registration: there is no sign-up form. A legal name, a postal address, a phone number — none of these is requested. The first launch creates an anonymous guest seat on the device, and creation can begin immediately.
- No permanent archive of your output: images and footage the engine makes for you are not retained on our side beyond the job, and nothing from them travels further.
- No attempt to identify you personally: nothing that would tie the handset to a particular person — a name, a home address, a mailbox — is sought or written down.
What is recorded while the App runs:
- An opaque device handle: the service needs a stable, impersonal way to tell one handset from another. It is made on the device itself: the ANDROID_ID value is combined with the App's package name and passed through a one-way MD5 digest, producing a handle that reveals nothing about the device's owner. If ANDROID_ID cannot be read, a random UUID kept in local storage takes its place. A Firebase installation label rides along as a further anonymous install mark — and, on installs judged to come from a direct Meta campaign, a marker supplied by the Facebook SDK also joins the set (its single duty is described in Section 7).
- The guest seat: tied to that handle from the first launch onward, the seat carries no password, no login, and no credential of any kind. It holds your working record and similar conveniences without capturing anything that singles you out.
- Ordinary technical details: model, system version, screen size, language, time zone, and facts of that kind — neutral readings that help the App behave consistently across the wide range of Android hardware.
- Usage traces: which parts of the App are opened and how often — the marks that show us where repairs are needed and which features earn their place.
- The advertising identifier (GAID): the Google Advertising ID may be used for advertising attribution. As soon as "Limit Ad Tracking" or "Opt out of Ads Personalization" is enabled, the read stops entirely, and system settings let you reset the ID at any time.
- Audio captured by the recorder: if you open the built-in recorder, whatever the microphone picks up during that take reaches us — collected only while the take is open, with one destination: custom audio (a piece of background music, for example) attached to the video you create. Section 3 has the details.
- Push routing tokens: notification tokens allow service messages (word that a generation has finished, for instance) to reach your device. You may turn them off permanently; nothing the App truly requires depends on them.
2. Material You Send to Us
Several creation paths ask for source material from you — a photograph, a clip, a video with sound. Files are chosen through the system photo picker or the system document picker, and only the item you select is made available to the App. Anything of that kind is handled as follows:
- Why it is sent: your file is the fuel the computation uses — the finished image or footage is built from exactly what you supplied. It travels to our servers over an encrypted connection.
- A brief stay: the upload and the work it produces remain on our servers only while the job is open; once the job closes, both are removed from the bench.
- Nothing kept in the dark: no copy of your material outlives the job, and no identifying details travel with it.
3. The Five-Second Recording
An optional recorder sits within Museorbit's creation flow. It accepts one take per press (five seconds at most), whose only destination is custom audio — background music among the possibilities — for an AI video:
- The permission matches the feature: the microphone request appears at runtime, at the moment the recorder is opened; declining it then, or revoking it afterwards in system settings, is entirely your choice.
- What limits a take: your own press starts it; the App must be in the foreground; and one take is the full extent of any collection. Background listening, in any form, is outside this App's design.
- Where a take may go: one destination only — the sound layer of the video being made.
- How it is sent: the moment you accept a take, the file leaves over an encrypted channel and is consumed by the generation.
- How long it stays on the server: a copy lasts only for the length of processing and is removed when processing ends.
- No voiceprinting: takes never pass through speech recognition, speaker separation, or any similar biometric process.
- While a take is open: the recording rests in a local cache; clearing App data in system settings removes it.
4. Faces in the Media You Provide
When material you upload contains human faces, Museorbit derives a narrow set of facial signals to drive its AI image and video features:
- The signals involved: eye, nose, and mouth structure (facial landmarks), together with measurements such as outline and proportion — taken from nothing beyond media you chose to upload.
- What they are used for: producing personalized, high-quality imagery; keeping visual effects steady on their subject; and improving the fidelity of what is returned to you.
- How long they serve: all processing takes place on encrypted servers and serves no purpose after your result is produced; once the result is delivered, the data is cleared — as a rule within 24 hours.
- Whether they are shared: never. Face data is not passed to any outside party.
5. Why We Use These Signals
The categories described above are used for these purposes:
- Running the service: delivering and maintaining the features you opened the App to use.
- Service messages: news about your generation jobs and about App releases.
- Improvement: usage traces guide the fixes, refinements, and new features we build.
- Security: keeping fraud, abuse, and unauthorized access out.
- Attribution and measurement: determining where each user came from and assessing how campaigns perform.
Your information is never sold, rented out, or handed to third parties for their own marketing purposes.
6. Payments and Their Records
Wherever a payment is made inside the App:
- Transaction marks: purchase tokens, product identifiers, order references, and subscription status are recorded so that what you paid for can be honored and delivered.
- Google keeps the ledger: every charge is processed by Google Play Billing. Cards, payment methods, and the rest of the financial machinery never come into our custody — that territory falls under Google's own privacy policy.
- Membership status: whether a membership is active, has expired, or was cancelled is tracked so that member features activate at the right moments.
- How long records stay: transaction records are kept to the extent required by delivery obligations, statutes, and dispute handling.
7. Outside Providers We Use
Museorbit relies on these outside services to operate, measure, and deliver:
- Google Play Services: distribution, in-app purchases, and subscription administration all run through this route; whatever Google collects is governed by Google's own privacy policy.
- Google Play Billing: purchases and memberships pass through it; purchase tokens and transaction records travel over Google Play's rails.
- Firebase Analytics: anonymous usage statistics and interaction patterns; device details, usage events, and anonymous marks may be collected. See Firebase Privacy Information.
- Firebase Installations: the component that creates the unique, anonymous installation label the service depends on.
- Firebase Cloud Messaging (FCM): the transport beneath the App's self-built push line (generation status, service notices). Device settings silence every alert whenever you wish. See Firebase Privacy Information.
- Google Play Install Referrer: the channel through which the App learns how it reached the device (install attribution); attribution and measurement are its only occupations.
- Google Advertising ID: used for advertising attribution and nothing else — and unread from the moment "Limit Ad Tracking" is enabled.
- Facebook SDK (Meta): carries one assignment: measuring installs that come from our direct Meta (Facebook) ad campaigns. As shipped it is inactive and remains entirely at rest — nothing initializes, nothing reports — unless an install is judged to be direct-campaign traffic. Only then does it deliver to Meta the install/activation event together with an anonymous device mark; our backend receives the same mark and uses it with Meta's server-side Conversions API to measure conversions. Purchases travel by the server route alone. Facebook login, sharing, and deep links have no place in the App. Details: Meta Privacy Policy.
Each service on this list issues its own privacy policy covering what it handles — worth reading.
8. How We Learn Where an Install Came From
To measure our marketing and improve the service, the following may be combined:
- Attribution data: install-referrer payloads, advertising identifiers, and anonymous device fingerprints (model, manufacturer, resolution, language, time zone, carrier, network type) kept for our marketing attribution.
- Direct-campaign measurement (Meta): where an install is judged to be direct Meta campaign traffic, the Facebook SDK may activate and deliver to Meta the install/activation event plus an anonymous device mark for conversion measurement; under any other finding it stays asleep throughout.
- Analytics data: anonymous usage statistics, feature-interaction counts, and performance figures, all carried by Firebase Analytics.
- IP address: for attribution purposes your IP may be observed in passing; tying a person to it formed no part of the task.
- How to opt out: Settings > Google > Ads offers "Opt out of Ads Personalization", and your advertising ID can be reset at any time.
9. We Do Not Sell Your Data
Selling, trading, or otherwise transferring personal data to third parties for their marketing purposes is not a business we conduct. Anonymized, aggregated data may reach the services named in Section 7, for the purposes stated here and no others. Disclosure also occurs where law requires it or where defending our rights makes it necessary.
10. How We Protect Your Data
These measures guard your data:
- Every leg of the journey is encrypted (HTTPS)
- Storage on our servers keeps its contents encrypted
- Access checks and security monitoring guard the entrances
No protection is absolute. Reasonable measures are in place, yet anything crossing a network carries some residual risk.
11. How Long Each Category Stays
Each category is kept only as long as the purposes above require:
- Uploaded media, sound takes, face data: cleared when processing ends — as a rule within 24 hours.
- Device handles and session data: kept for as long as the App remains on your device.
- Transaction records: kept as long as statutes and dispute handling require.
- Analytics data: kept in aggregate, anonymized form.
12. Children Under 13
Museorbit is not directed to anyone under 13, and no such person's information is knowingly collected. If you believe a child's data has reached us, a message to the address below will start its removal without delay.
13. Your Rights and Controls
These controls over your own data remain in your hands:
- Access and correction: ask to see what we hold; request amendments or erasure.
- Erasure: one message to the address below starts removal. Because finished images, footage, and personal information are not kept in our long-term custody, there is usually little to erase — most of your data rests on the device itself.
- Limited tracking: restrict ad tracking in system settings, and reset the advertising ID whenever you choose.
- Notification settings: every alert follows your on/off choice.
- Subscription controls: memberships are managed or cancelled inside your Google Play Store account.
- Uninstall: remove the App whenever you like — collection stops and the local store leaves with it.
14. International Processing
Processing may take place on servers located outside your home country. Wherever your data travels, appropriate safeguards accompany it.
15. Changes to This Policy
As the service, its features, or the law changes, this Privacy Policy changes with them; each revision updates the "In force from" date at the top. A periodic glance keeps you current.
16. Contact Us
Questions or objections about this policy, or about how your data is handled? Send them here:
Registered entity: HAPPY CASTLE ANIMATION TECHNOLOGY CO., LIMITED
Registered office: Rm 1101D, 11/F, Lippo Sun Plaza, 28 Canton Road, Tsim Sha Tsui, Hong Kong
Email: kristinacra54@gmail.com