Privacy & security

RIB Creative is designed to help you build quickly while keeping control over access, review, and publishing decisions.

What you should protect

Treat the following as sensitive:

• API keys and tokens.
• Passwords and private credentials.
• Customer data.
• Internal company strategy.
• Client documents.
• Payment, health, legal, or regulated information.
• Security architecture details.

Do not paste secrets into prompts. If your app needs a credential, use the appropriate environment or deployment setting when that workflow is available.

How to reduce risk

Use these habits:

• Keep workspaces separated by client or company.
• Invite only the people who need access.
• Ask for plans before large changes.
• Review generated code and copy before publishing.
• Test forms, links, and auth-related flows.
• Remove placeholder legal, pricing, or security claims.
• Keep sensitive apps behind careful review.

AI safety expectations

AI can make mistakes. It may misunderstand intent, over-edit, or produce incomplete logic. RIB Creative helps you move faster, but it does not replace review.

For important projects:

• Ask for a summary of changes.
• Test the user flow yourself.
• Review pages that collect data.
• Verify generated assumptions.
• Use a technical reviewer when the project handles sensitive information.

Security checklist before publishing

• No secrets are visible in code, prompts, or UI.
• Forms collect only the data you need.
• Placeholder privacy, terms, or compliance claims are removed or reviewed.
• Access to the workspace is limited to the right people.
• The app has been tested on desktop and mobile.
• Any payment, login, or database behavior has been reviewed carefully.

FAQ

Can I build production apps with RIB Creative?

You can use RIB Creative to create and evolve production-bound projects, but production use should include careful review, testing, and security checks.

Does AI review replace security review?

No. AI-assisted checks can reduce risk, but they do not replace responsible review for sensitive apps.

Should I put customer data into prompts?

Avoid it unless you have a clear policy and a safe reason. Use sample or anonymized data whenever possible.

Next steps

• Manage people: People
• Learn prompting safety: Prompting best practices
• Understand support: Support policy