← Back to Home  ·  Blog  ·  Privacy Policy  ·  Contact

Terms of Service

Version not yet assigned · scope: public paid beta

These terms ("Terms") govern your use of Qalizer, an automated quality-assurance service for web applications. They are written for the public paid beta: the service is offered commercially, but it is a beta and its documented limitations apply.

---

1. The parties and eligibility

The service is provided by the operator identified at the top of this page ("we", "us"). You need to be at least 18 years old and able to enter into a binding contract. If you use Qalizer for an organisation you confirm you may bind it.

2. What the service does

Qalizer crawls, generates, records and runs browser scenarios, performs API, liveness, visual, console/network, load and monkey ("gremlins") tests, injects test data, and produces reports and CI artifacts. Every capability is listed with the ways it can be started and where it runs in the published capability summary; anything not listed there is not supported.

3. Your account

• Give accurate registration data and keep it up to date.
• Keep your credentials and 2FA factors safe; you are responsible for activity under your account.
• Tell us immediately if you suspect unauthorised use.
• Workspace access follows approved, active membership only; you are responsible for whom you invite and approve.

4. Authorized testing only

You may test only systems that you own or are expressly authorised to test. Before you start any test you must:

• hold the owner's permission, including for staging, preview or third-party-hosted environments;
• check that automated crawling, load generation and monkey ("gremlins") interaction are allowed by the target's terms and by the law that applies to it;
• make sure the test data you inject is synthetic or lawfully usable, and that you do not write into production systems you are not allowed to change.

5. Load, side effects and chaos ("gremlins") restrictions

These features deliberately put pressure on a target or click through it at random. You must:

• run load tests only against an environment sized to absorb them, and never against a system you do not control;
• stay inside the concurrency, duration and rate limits the product and your plan allow, and stop a run that is harming the target;
• avoid gremlins/monkey testing on systems where a random click could purchase, delete, publish or send something unless you accept that side effect;
• accept that gremlins runs can create, modify or delete data in the target application.

We may refuse, throttle or stop a run that looks abusive or that puts a third party at risk.

6. Acceptable use

Do not use Qalizer to attack, overload or scan systems without permission, to bypass access controls, to send unlawful content, to infringe rights, to resell the service without written agreement, or to interfere with the service or other customers.

7. Runs on your own runner, and what is uploaded

Browser scenarios can execute on the local runner you start on your own machine. In that mode the browser work happens on your hardware, but the selected results and artifacts are uploaded to Qalizer and are retained on Qalizer (reports, step results, screenshots, recordings, console/network captures, exports), so they appear in your Reports page and in CI artifacts. The retention in §13 applies to them exactly as it does to runs on the shared pool. There is no local-only storage mode today.

Every other test family (API, liveness, visual, console/network, load, gremlins, data injection) runs on the shared server pool.

8. Beta limitations

Qalizer is in a paid public beta:

• features, limits and the interface may change, and a feature may be withdrawn;
• runs can be delayed, queued, throttled or suspended for maintenance and capacity;
• third-party providers (cloud, email, AI, payments) can fail and change;
• test results reflect the state of the tested system at that moment and can be affected by the network, timing, geoblocking, CDN, A/B tests or later changes.

These limitations describe the service; they do not remove your statutory rights (see §10).

9. AI-assisted analysis

AI features generate scenarios and analyses and may be inaccurate. Treat them as advisory: the execution result recorded by the runner is authoritative. You are responsible for reviewing generated tests before you rely on them.

10. Consumer rights are never waived

Nothing in these Terms limits mandatory consumer protections, statutory warranty/defect rights, or any right to withdraw that the law grants you. Where any provision conflicts with mandatory law, the law prevails and the rest of the Terms stay in effect. This section overrides every other clause in case of conflict.

11. Credits and prices

• Credits are prepaid usage units. Each action has a credit cost that is shown before you start it, and prices may change.
• A new account receives 100 signup credits. Signup credits are granted when the account is created — creating a monitor is not a condition for receiving them — and they are usage units, not cash.
• Card payments are processed by Stripe. Card data is entered on Stripe's checkout and is never stored by us.

12. Platform failure, credit restoration and refunds

Verified platform failures that incorrectly consume credits are remedied by restoring the affected credits, or by another remedy where the law requires one.

A platform failure means that our own execution did not run as instructed — for example a run that failed because of our infrastructure or a billing defect. A normal test run that correctly finds a bug in your application is a successful result, not a platform failure.

Credit purchases are generally non-refundable, except where a refund is required by law, by the applicable payment-provider terms or by our stated policy. Restoring credits after a support review is not a cash refund: the affected usage credits return to your balance so you can re-run the work.

To request a review, use the "Service failure / credit restoration" option on the contact page with the run, batch or payment reference; evidence files are optional, because our own execution records usually show what happened.

13. Data retention

Completed execution artifacts are removed 180 days after the execution finished; operational logs are kept 250 days. These are the configured policy values; the product reports the retention that applies to each report and the last completed expiry pass, and does not claim that a pass has run when it has not. Reusable configuration (monitors, scenarios, requirements, schedules) survives report expiry, and financial records follow a separate legal/accounting schedule. Details, including what is deliberately not promised, are in the Privacy Policy. Export anything you need before it expires.

14. Your content and the licence we need

You keep ownership of your scenarios, requirements, test data and reports. You grant us a limited licence to process, store and display them only to provide the service, including sending the feature-specific data described in the Privacy Policy to the configured processors.

15. Our intellectual property

The platform, its code, interface, brand and documentation remain ours. Your content stays yours.

16. Third-party services

The service relies on the providers named in the Privacy Policy (cloud hosting, Purelymail/Gmail, Stripe, AI providers, Docker Hub). Those parties have their own terms and policies.

17. Availability and changes

The service is provided as available. We may change, suspend or withdraw features and change prices, with notice where the law requires it. We do not promise uninterrupted availability or that a test run finds every defect.

18. Suspension and termination

We may suspend or terminate an account for a material breach, abusive use or a legal requirement. You may stop using the service and delete your account at any time. Prepaid, unused credits are handled under §12 and your statutory rights.

19. Liability

We are liable without limitation for intent, gross negligence, injury to life, body or health, and for any liability that mandatory law does not allow to be limited. Otherwise our liability for damages is limited to the amount you paid for the twelve months preceding the event, and we are not liable for lost profit, lost data or indirect damage where that limitation is lawful. Nothing here limits liability that cannot be limited by law.

20. Governing law and complaints

Governing law not yet supplied. Until it is, these Terms do not state a jurisdiction — a gap that must be closed before publication, not an implicit choice of law.

21. Changes to the Terms

The version and effective date at the top of this page identify the text in force. A change is published with a new version and an effective date, and signed-in users are told about material changes.

22. Contact

Questions about these Terms: support@qalizer.online or the contact page.

---

© 2026 Qalizer. All rights reserved. See the The operator preview that reports what is still missing before publication is administrator-only.