You may register and analyze only websites, stores, servers and repositories that you manage or have explicit permission to test. Do not use the service to bypass access controls, disrupt systems or test third parties without authorization.

MuriOps combines crawling, browser automation and technical checks to produce scores, findings and evidence. When you configure your own key, AI providers may interpret this data and generate summaries and remediation plans.

Automated results may contain false positives, omissions or recommendations that do not fit your environment. Human review remains necessary before any production change.

Some connections write data to external systems. GitHub may create branches and pull requests; GitLab may create branches and merge requests. When an action-plan item identifies an existing file and the configured AI provider returns a suggestion, the branch may include a proposed code change. These actions depend on the credentials and permissions you provide.

These records do not guarantee that a technical fix was implemented. MuriOps does not automatically merge on GitHub or GitLab; an authorized person must review and approve the change.

You are responsible for providing least-privilege credentials, monitoring their use and revoking them at the source when a connection is no longer needed. Do not share credentials in fields not intended for secrets.

The service is provided “as is” and may experience outages, changes or limitations. Keep backups, use test environments when possible and validate every change before publication. You remain responsible for decisions based on reports and for the effects of integrations you authorize.

You are also responsible for the lawfulness and accuracy of the content and personal data submitted, for obtaining required permissions, and for complying with the terms of each connected platform. Do not treat automated output as legal, security or professional advice.

Questions about these terms can be sent to .privacidade@muriops.com.br