Privacy, limits and good practice

Your projects are private

A Studio project belongs to you alone. Nobody else can open it, and Studio does not offer shared editing. If you want others to use your design, publish it as a template. If you want someone to see the result, deploy it and share the address.

What Studio keeps for abuse monitoring

To keep PGB safe from abuse such as phishing, malware and spam, we keep a copy of what you type into AI features in PGB Studio, PGB Agents and PGB Learn (your requests and your agents' instructions and inputs, not your files, mail, calendar or other data the assistant reads to answer you). Passwords, keys and similar secrets are masked before it is saved, and only a short preview of the assistant's reply is kept. We keep this for 30 days, then delete it. Only a small group of PGB operators can see it, every look is recorded, and it is used only to investigate abuse and protect the service, never for advertising or to train models.

For Studio that means the text of your Describe your app request and each message to the Assistant. Your project files are not copied into that log.

Limits you may see

• Per account: number of projects, stored files, AI edits per day, deploys per day and live apps.
• Per project: a cap on file count and total size, and 1 MB for a single text file.
• Form uploads: 2 MB per picture or file.
• If your account is suspended you can still read, but writes, AI edits and deploys are refused.

A message such as "You have reached a limit for your account. Remove something or ask for more room." names what to free up.

Good practice checklist

1. Start with a template when one fits. It gives you structure and protected core files.
2. Name save points before risky changes.
3. Keep requests small when using the assistant, and read the changed-files list each time.
4. Do not paste secrets into the Assistant box or into files you will export or publish as a template. Template settings refuse names that look like secrets.
5. Test the preview on all three device sizes before deploying.
6. Redeploy after changes; the live site does not update by itself.
7. Delete unused projects to keep room.

Common problems and fixes

• The preview looks stuck. Choose Rebuild the preview.
• Save says the file changed somewhere else. Choose Use the newer version or Keep my version.
• The assistant will not change a file. It may be locked by the template. Unlock it or change values in Customise.
• Deploy did not finish. Open Problems, fix errors and Deploy again.
• The AI builder asks for a key. Add your AI provider key on the AI keys page.

Try it yourself

1. Open Your projects and rename one using the pencil icon.
2. Make a named save point in a project and view its changes.
3. Read the AI privacy paragraph above once more, then check that nothing sensitive is in your instructions or assistant history.

Recap

• Projects are private to you.
• Prompts to the AI are kept 30 days for abuse monitoring, with secrets masked.
• Limits apply per account and project, and messages name them.
• Good habits: templates, save points, small requests, full previews and no secrets.