CRE Trust, Privacy & Terms

CRE should be used with anonymized incident information only. Users must not enter passwords, secrets, API keys, personal data, customer data, regulated data, confidential production logs, or commercially sensitive information.

CRE may process user-submitted information to generate AI-assisted incident reasoning outputs, including likely RCA hypotheses, recommended actions, stakeholder updates, and human-reviewable runbooks.

CRE may store account information, plan details, usage history, submitted incident scenarios, and analysis results based on the active plan. Analysis history may be retained for a limited period to support user access and product improvement.

CRE may use third-party infrastructure, hosting, payment, authentication, analytics, and AI model services to operate the platform. Data may be processed by these services only to provide the CRE service.

Users are responsible for ensuring that information submitted into CRE is anonymized and suitable for AI-assisted processing.

Where applicable, users may contact CRE to request access, correction, or deletion of their account or stored analysis information.

Contact:support@creaiops.com

CRE provides advisory AI-generated analysis only.

CRE outputs may be incomplete, incorrect, delayed, or not suitable for a specific production environment. All outputs must be reviewed and validated by qualified human operators before any operational decision is taken.

CRE does not replace ITSM platforms, observability tools, security tools, compliance processes, change management, incident governance, or professional operational judgement.

CRE does not execute remediation actions automatically. Human approval and validation are mandatory before taking any action.

Users remain responsible for decisions, actions, changes, communications, and operational outcomes based on CRE outputs.

CRE may evolve as the platform improves and new capabilities are introduced.

CRE currently works with anonymized user-provided incident scenarios.

Users must not enter secrets, credentials, API keys, tokens, passwords, customer records, confidential logs, regulated data, or sensitive production data.

CRE does not directly connect to or change production systems unless explicitly enabled through approved future integrations.

CRE does not automatically execute scripts, commands, remediation steps, or infrastructure changes.

Human-in-the-loop approval is required for any recommended action.

Security concerns can be reported to:support@creaiops.com

CRE aims to provide a usable and accessible experience across modern browsers and devices.

If users face accessibility issues or need support accessing any part of the platform, they can contact CRE.

Contact:support@creaiops.com

For feedback, support, investor queries, product questions, accessibility issues, or security concerns, contact:

Contact:support@creaiops.com