Probara

Plan & write

  • Test case managementSuites, shared steps, custom fields and review

Automate & connect

  • Test automationReporters, CLI and CI runs
  • MCPWork in Probara from your AI agent

Track & report

  • Dashboards & PQLQA dashboards, metrics and saved queries
  • Requirements traceabilityCoverage of Jira and GitHub requirements
See every feature
IntegrationsPricing
  • Docs homeStart here and search every page
  • GuidesHow to use Probara, screen by screen
  • DevelopersREST API, CLI, reporters, MCP and webhooks
  • ComparisonsProbara next to other test tools
  • BlogNews, product updates and articles on testing

Language

  • EnglishEN
  • EspañolES
Log inContact usStart free

Product

Test case managementTest automationMCPDashboards & PQLRequirements traceabilitySee every featureIntegrationsPricing

Resources

Docs homeGuidesDevelopersComparisonsBlog
Log inContact usStart free

Draft

Acceptable Use Policy

Last updated: November 3, 2026

About this policy

This Acceptable Use Policy describes what you may not do with Probara, the service that OrderStorm Ecommerce, Inc. ("OrderStorm", "we" or "us") operates (the "Service"). It is part of our Terms of Service, and the terms it uses have the meaning given there.

The policy applies to everything done with your account or within your organization: by you, by the members you invite, and by the scripts, integrations, test reporters and AI agents that use your credentials. You are responsible for all of it, including actions you did not intend. Helping or allowing someone else to break this policy also breaks it.

The examples below are not exhaustive. We may act on other uses that harm the Service, our customers or anyone else.

Unlawful or harmful content and activity

You may not use the Service to store, share or take part in:

  • anything unlawful, or that promotes or helps others carry out unlawful activity;
  • fraud or deception, such as phishing, scams or impersonating another person or organization;
  • content that infringes someone else's intellectual property or privacy rights;
  • content that threatens, harasses, defames or promotes hatred or violence against others;
  • child sexual abuse material, or any content that exploits or harms minors;
  • viruses, malware or other malicious code, including through attachments or public run links.

Security testing of Probara

You may not probe, scan, penetrate or test the vulnerability of the Service or of the infrastructure behind it, or run load, stress or performance tests against it, without OrderStorm's prior written consent. This applies whether the testing is manual or automated, and whether it is done by a person, a security scanner or an AI agent.

This rule is about testing Probara itself. Testing your own applications and recording the results in Probara is exactly what the Service is for.

If you find a vulnerability, report it to us through the contact form on probara.net. Do not access, change or delete data that is not yours, do not degrade the Service, and give us reasonable time to fix the problem before you disclose it to anyone else. We will not treat a report made in good faith under these conditions as a violation of this policy.

Unauthorized access and network abuse

You may not:

  • access, or try to access, accounts, organizations, data or systems that you are not authorized to use, including other customers' data;
  • use credentials, tokens or secrets that were not issued to you, or try to obtain them from the Service, its infrastructure or other users;
  • bypass or weaken authentication, permissions, rate limits, plan limits, confirmations or other security or usage controls;
  • interfere with or disrupt the Service, for example by flooding it with requests or attempting a denial of service attack;
  • scrape or crawl the Service other than through the published API, or in a way that impairs its performance;
  • hide or falsify the origin of your requests, or your identity;
  • use the Service to attack, scan or send unwanted traffic to other systems, for example by pointing webhooks or other outgoing features at systems you are not authorized to use.

AI agents and automation

API tokens, test reporters and AI clients connected to the MCP server act on your behalf, with your permissions. Everything they do counts as activity under your account, including when an agent goes beyond what you asked it to do.

  • Give agents and scripts only the access their task needs, and supervise the ones that can change or delete data.
  • Do not instruct or allow an agent to test the security of the Service, to reach data outside your organization, or to work around limits or confirmations.
  • Revoke a token or disconnect a client as soon as it behaves in a way you did not intend, and tell us if it may have affected the Service or other customers.

We may revoke tokens, disconnect clients or limit requests that break this policy, without notice when that is needed to protect the Service.

Messages and spam

You may not use invitations, notifications, comments, public run links, issues created in connected tools or any other feature that reaches other people to send spam, unsolicited bulk messages or deceptive content. Invite only people who expect to work with you.

Fair use of shared resources

The Service runs on shared infrastructure. Where a plan offers unlimited seats, projects or viewers, that means no fixed limit for the ordinary work of a team managing its testing, not unlimited use for any purpose. In particular:

  • each account belongs to one person, and accounts may not be shared;
  • viewer accounts are for people who need to follow your testing, not a way to publish content to the general public;
  • requests through the API, the MCP server and test reporters are subject to rate limits, and storage and history follow the limits of your plan;
  • you may not use the Service mainly as general file storage, or in a way that consumes a disproportionate share of resources.

If your use goes far beyond what is typical for your plan, we will contact you first to reduce it or move you to a plan that fits, such as Enterprise. We may limit it without waiting when it harms the Service or other customers.

Monitoring and enforcement

We have no obligation to monitor how the Service is used, but we may investigate suspected violations. We may report suspected unlawful activity to the authorities and share related information with them as the law permits.

If we find a violation, we may remove or disable content, revoke tokens or integrations, limit requests, or suspend or terminate the account or organization involved, as described in the Terms of Service. We may do so even if the violation was unintentional or was committed by someone else using your account or your agents.

Reporting violations

To report a suspected violation of this policy, contact us through the contact form on probara.net with as much detail as you can, or write to:

  • OrderStorm Ecommerce, Inc., 11757 W. Ken Caryl Ave. F-272, Littleton, CO 80127, USA

We may ask for your help to stop or remedy a violation.

Changes to this policy

We may update this policy from time to time. We will publish the new version on this page with a new "Last updated" date, and when a change is material we will notify the owners of affected organizations as described in the Terms of Service.

Questions about this document? Contact us

Probara

Test case management for QA teams.

Product

  • Test case management
  • Test automation
  • Dashboards & PQL
  • Requirements traceability
  • MCP server
  • Pricing

Integrations

  • Jira
  • GitHub
  • Playwright
  • Jest
  • Cypress
  • Vitest
  • Cucumber
  • All integrations →

Compare

  • vs TestRail
  • vs Qase
  • vs Xray
  • vs Zephyr
  • vs Testmo
  • vs PractiTest
  • All comparisons →

Resources

  • Documentation
  • Guides
  • Blog
  • API reference
  • MCP docs
  • SDK & CLI on GitHub
  • Security
  • FAQ

Get started

  • Start free
  • Log in
  • About Probara
  • Contact us
© 2026 Probara
Get an AI summary of Probara
Terms of ServicePrivacy PolicyAcceptable Use