12 clear answers about access, confidentiality, ownership, diligence and platform transfer restrictions.
Roblox states that there is no official system for buying or selling experiences and warns users not to exchange Robux, items, or account credentials for one. A proposed deal therefore needs careful off-platform legal structuring plus confirmation of any platform-permitted control change. Do not treat a private contract as a guarantee that Roblox will recognise or support the transfer.
No. Source files, copyright, a live experience, community ownership, payout eligibility and account permissions are separate. The agreement must define the seller-owned assets, while the parties independently verify what Roblox permits them to change. Never rely on password sharing as the transfer mechanism.
Epic documents project and team ownership transfers through the Creator Portal for eligible users and teams. That platform step does not automatically assign seller-owned code, art, trade marks, contracts or other IP, so the legal transfer and Creator Portal transfer should be planned together.
Epic's Developer Program FAQ says the day's allocation follows the island owner with the most active audience minutes that day. The contract should still define the economic cutoff, reporting, taxes, adjustments and cooperation if portal data or payment timing crosses completion.
Do not assume so. Epic and partner-brand rules can restrict use, modification, redistribution and promotion. Review the applicable Developer Rules, IP Partner Licensing Agreement and brand rules, then identify which content is seller-owned, platform-provided, licensed, replaceable or excluded from the deal.
Request founder, employee and contractor assignments; publisher and collaboration agreements; music, voice, art and asset licences; open-source notices; registered-right searches; repository history; and any prior sale, security or financing documents. Exceptions should become consents, replacements, licences, price adjustments or closing conditions.
Valve says wishlists and followers remain with the transferred application. Historic financial access does not transfer by default, and publisher API keys must be replaced. Verify the current Steamworks rules and build these exclusions into the data-room and transition plan.
The platforms preserve important listing and user continuity, but some reports, test groups, certificates, cloud links, payment settings, analytics, multiplayer configuration or signing tasks require separate work. Use the current Apple and Google transfer checklists and assign an owner to every dependency.
Only if the relevant licence or provider allows it. Some licences are personal, account-bound, seat-limited, non-assignable or triggered by a change of control. Inventory the actual build, review each licence, and obtain consent, a buyer licence or a replacement where necessary.
Value often depends on customer contracts, integrations, package and marketplace listings, signing systems, documentation, support obligations and specialist staff. Buyers should test a reproducible build and deployment, examine open-source and commercial dependencies, and confirm customer assignment or change-of-control terms.
Review the technical file, declarations, test reports, radio/electrical/battery requirements, labels, traceability, complaints, returns, recalls, inventory and supplier controls in every target market. Also schedule patents, designs, trade marks, firmware, CAD, tooling and manufacturing know-how separately.
No. IP ownership and product compliance are different. A buyer may need new economic-operator arrangements, updated declarations, relabelling or re-testing, especially if components, manufacturer details, target territories or the tested configuration change.