Acceptable use

Vraelis drives a real browser against the web apps and device control panels you point it at, and a plan runs only after a person approves it. That is a real capability, so this policy says plainly what you may and may not use it for. It is part of the Terms, and it applies however you use Vraelis: the website, the console, the API, the CLI, or an AI assistant connected to your account.

Check only what you own or are authorized to test

Point Vraelis only at systems you own, or that their owner has authorized you to test. When you connect a system, Vraelis asks you to confirm this, and confirming it for a system you have no right to test breaks this policy. If you test for a client, keep a record of their permission.

• Fine: your own apps, staging environments, and device control panels.
• Fine: a client's system, when the client has authorized you to test it.
• Not fine: a competitor's site, a public service you only use, or anything you were not invited to test.

Do not attack, overload, or get around protections

• Do not use Vraelis to attack, exploit, or break into any system, or to probe for weaknesses in a system you are not authorized to test. That includes Vraelis itself; security research on Vraelis is welcome through the reporting route below.
• Do not use it to overload a service, flood forms, or run load or stress tests against systems you do not own.
• Do not bypass access controls, CAPTCHAs, paywalls, rate limits, or plan limits, whether on the systems you check or on Vraelis.
• Do not use it to scrape or harvest content or data from third-party sites, or to collect information about other people.
• Do not try to make runs reach internal networks or addresses that Vraelis blocks.

Credentials and test accounts

• Give Vraelis only accounts and credentials you are entitled to use for testing, such as test users you created for it.
• Do not use someone else's account, leaked or stolen credentials, or a real customer's account.
• Use test payment modes and test data wherever you can.

What you write and submit

• Claims, plans, test data, and notes must not contain unlawful content, content that infringes someone else's rights, malware, or material that harasses, threatens, or exploits anyone.
• Do not submit regulated or highly sensitive personal data you are not permitted to share, and do not put other people's personal data in test data unless you have the right to.

Do not use Vraelis to harm others

• No fraud, spam, phishing, or deceptive activity, including creating fake accounts, reviews, or sign-ups on other services.
• Do not present a Vraelis result as a certification, a guarantee, or an endorsement by Vraelis.
• Do not let an AI assistant or any automation connected to your account do anything this policy forbids. What it does with your account is your responsibility.

Approvals are yours

A plan runs only after a person approves it. Approving a plan means you have read what it will do and are authorized to do that to that system. Do not approve plans without reading them, and do not share your account so someone else can approve for you.

Reporting a problem

If you find a security issue in Vraelis, report it as described on the security page: email [email protected] with Security in the subject line. If you believe someone is using Vraelis against a system you run, email the same address with what you saw and when, and we will look into it.

What happens if this policy is broken

We may stop a run, suspend or close the account involved, and revoke its API keys, with or without notice depending on the risk. Serious or repeated breaches can lead to a permanent ban. Where the law requires it, we cooperate with the authorities.

Changes

We may update this policy as the product changes. The date at the top shows when it last changed.

Contact

Questions about this policy? Email [email protected]. See also the Terms.