Use information and services you are authorized to access
Use your own account and only provide content, credentials, or data that you have permission to use. Respect the access restrictions of the platform, other users’ projects, and the external services connected to your app.
Review generated code and content
AI output can be incomplete or incorrect. Review the source, verify factual content, and test the app’s behavior before sharing it with customers. Check dependencies, licenses, accessibility, and security requirements that apply to your project.
A generated claim, testimonial, or sample record is not evidence. Replace placeholders with information you can verify and label demonstration data clearly.
Configure and test the services your app needs
A working frontend preview does not establish that a backend, database, email sender, or payment integration is ready. Those services need their own configuration, testing, and operational support.
External providers may impose their own costs, limits, and conditions. Usage availability depends on the platform configuration and the chosen model. Source export lets you continue the project in your own environment.
Check access before publishing
Decide who should be able to open a project and check its contents before enabling public access. Keep private data and credentials out of the published frontend. Publish deploys supported apps with their frontend, Workers backend and production database after verification. Existing Node backends require conversion first. Taking the app offline disables its public routes while keeping its database and saved releases. Older public preview links have a separate privacy control.
Read the privacy overview for the implemented account, prompt, and project-storage flows.