Scope and Specific Effect
These terms apply when you make a project Public, add it to Discover, publish Project Genome, or allow other users to create Licensed Copies of your project. They supplement the Terms of Service. For the authorization scope of these features, these terms, the settings you confirm for the specific project, and the corresponding authorization records prevail. A general service licence must not be read as an authorization to publish, copy or use data beyond these settings.
You must hold the necessary rights in the project, or have obtained clear and valid authorization from the rights holder. When acting for a team or organization, you must have the corresponding publishing and licensing authority. A project being public, or containing AI-generated content, does not mean it is free of third-party rights.
Public and Other Visibility Settings
Public means the app and the project profile you choose to make public can be accessed by unspecified visitors. Whether the project enters Discover, whether public Genome is shown, and whether Licensed Copies are allowed are each governed by the settings explicitly displayed in the interface and confirmed by you.
A new project's interface may preset Public, Discover listing, Licensed Copies and public Genome as recommendations. These presets are only adjustable suggestions; the platform prominently explains what they mean before actual publication or authorized copying, and obtains your project-level affirmative confirmation. You can change the settings before submitting; later changes follow these terms.
Private projects do not thereby enter a public catalogue. Unlisted means the project is not actively added to the platform's public discovery catalogue, and must not be understood as access authentication or a confidentiality guarantee. The protection of Protected depends on the password, member permissions or other access verification actually enabled. No access protection authorizes the platform to make full Project Memory, databases or other non-public materials public.
Public Display Licence
For the project name, description, preview, categories, public Genome and other public fields that you have expressly chosen to publish and are entitled to authorize, you grant PocketBay a non-exclusive licence to display, transmit, cache, index and create corresponding summaries, to the extent necessary for providing public project pages, Discover, on-platform search, recommendations, comparison and project-relation analysis. Technical processors may assist only within the scope necessary for providing those services.
The licence does not transfer your intellectual-property rights, does not make the project open source, does not authorize the platform to sell your non-public materials at will, and does not by itself allow other users to download source code, copy trademarks or obtain commercial sublicences. When PocketBay cites customer names, logos, internal metrics or success stories externally, it follows separately specified authorization and cannot presume it from project operation rights.
The scope and handling of public Genome are also governed by the Project Memory and Genome Data Policy. Where separate consent for personal information is required by law, it is obtained through the corresponding process and cannot be replaced by these terms.
Creator Authorization for Licensed Copies
When you affirmatively confirm enabling "allow Licensed Copies" for a project, you grant PocketBay, within the scope you are entitled to authorize, a non-exclusive licence to copy and deploy the approved application runtime materials for eligible users and to create and host independent instances; and you agree to provide copy users the licence limited by the Licensed Copy User Terms.
A Public project may have Licensed Copies recommended by default in the deployment interface, but before you complete this project-level authorization, the platform does not offer new copies to others merely because the project is publicly accessible. Disabling Licensed Copies does not automatically make the original project private.
The licence covers only the programs or build artifacts needed to run the designated version and lawfully copyable, the verified non-sensitive configuration templates, database schemas, and demo material you expressly include in the copy delivery scope and are entitled to distribute. Except with your separate express authorization and the applicable compliance steps, it excludes real business records, user-uploaded content and other production data.
What Does Not Transfer with a Copy
Full Project Memory, raw conversations, Secrets, actual environment-variable values, API keys, tokens, database passwords, payment keys, production database records, customer personal information, run logs, privately uploaded files and unpublished business materials are not part of the default copy delivery scope. Public Genome is likewise not a full Memory package or a reconstruction package.
PocketBay executes these exclusions with actual content separation, permission controls and a copy inventory. You should also avoid hard-coding sensitive information into copyable programs or material. Where possibly leaked content is found, the platform may suspend copy creation or operation and take remedial measures; these terms do not shift the platform's own configuration or isolation faults onto you.
Third-Party Dependencies and Authorization Limits
You must accurately disclose the models, APIs, data sources, external accounts, commercial components and possible third-party charges needed for the copy to run; you must not use your own platform authorization to substitute for sublicences that a third-party provider has not permitted. Materials that cannot be lawfully distributed must not be included in a copy.
Where a copy depends on creator-controlled external interfaces, the interface controller, the necessary data flows, the types of data possibly received and the service-discontinuation risks must be clearly disclosed before creation. A copy's independent data space does not mean its external network requests are naturally unrelated to the creator.
Open-source and other third-party materials must be used in compliance with the corresponding licences. Required attributions, licence texts, source-code offers or statutorily permitted acts are not excluded by these platform terms. The platform may request supplementary proof, adjust delivery, or disable the copy feature for the project.
Copy Fees and Creator Revenue
Copy creation fees, app licence fees and runtime resource fees are displayed separately. Charges not expressly stated in advance and confirmed by the relevant user do not arise merely from these terms. Copies enabled by default are not a platform promise to pay creators licence fees, revenue shares, minimum income or continued promotion.
If you join paid app, subscription, revenue-share or other commercialization programs, you separately accept the then-current merchant or transaction terms. The platform does not presume from an earlier free-copy authorization that you agreed to new fee allocations or additional authorization scopes.
Disabling, Going Private, Delisting and Existing Copies
You may disable new copies, disable public Genome, leave Discover or change project visibility. After a change takes effect, the platform stops the corresponding new authorizations or public display, and updates the indexes and caches it controls.
Disabling new copies or making the source project private does not automatically revoke retroactively the copy rights other users lawfully obtained earlier that remain within the original licence term and scope. Existing copies follow the licence, term, version and service conditions recorded at creation; the creator need not therefore continue to provide upgrades, support or external services never promised. The platform may retain necessary runtime materials to perform existing valid licences, but will not thereby keep original Memory, production data or withdrawn public fields public.
Infringement, illegality, information leakage, security risks, valid termination grounds, subscription expiry or requirements of competent authorities may lead existing copies to be suspended or terminated. The platform does not promise indefinite hosting. Where paid entitlements or copy users' own data are involved, notice, refunds, substitute performance and legally required data return are handled according to actual responsibilities, transaction terms and applicable law; liability is not excluded wholesale on the ground that the source project was deleted.
Public Dissemination and Rights Protection
Public content may be viewed, quoted or cached by others and by external search systems. After you turn off publication, the platform stops continued publication within its control and handles lawful requests, but cannot guarantee withdrawal of all records third parties have lawfully saved. This is not an authorization for anyone to use content beyond the licence, invade privacy or infringe intellectual-property rights, and does not exempt the platform from its deletion, complaint-handling and security obligations.
Public Genome reflects project characteristics only; functional similarity does not by itself prove infringement, nor does it give anyone automatic exclusivity over abstract ideas, generic features or industry methods.
Authorization Records and Changes
Authorization is tied to the specific project, release version, authorizer, settings, terms version and confirmation time. Ordinary iterations may rely on valid settings when the authorization scope, data sources and public fields have not materially changed; expanding copy rights, adding public field categories, making non-public content public for the first time, changing the use of private Memory, or re-enabling disabled authorization requires the corresponding new confirmation.
Historical projects do not automatically gain new copy authorization, Memory uploads or publication of previously private data merely from the publication of these terms.