Acceptable Use Policy

What you may and may not do with Vultax. Most of it reduces to two ideas: do not use a manipulation detector to manipulate, and do not turn our data into someone else's data product. The rest is detail, and the enforcement ladder is published so you can see what a breach actually costs.

In force from: 5 September 2026
Version: 1.1
Issued by: OmniOS OÜ

Version 1.1 adds prediction-market and paper-desk conduct to §§ 2 and 3.

1Scope

This policy forms part of the Terms of Service and applies to everyone who uses Vultax — free terminal visitors, subscribers and API consumers alike. Where it conflicts with the Terms, the Terms govern.

2Unlawful and market-abusive use

The Service exists to make manipulation visible. Using it to commit manipulation inverts the point of it, and we treat that as the most serious breach on this page.

Do not use the Service to plan, coordinate or carry out market manipulation, including wash trading, spoofing, layering, ramping, or pump-and-dump schemes — conduct prohibited by Articles 91 to 92 of Regulation (EU) 2023/1114 and by equivalent law elsewhere.
Do not use the Service to front-run, or to trade ahead of, an order flow you have inferred from someone else's confidential information.
Do not use it to commit fraud, launder money, finance terrorism, or evade sanctions.
Do not use it to harass, threaten, stalk or dox any person, including through wallet attribution or a prediction-market participant ranking.
Do not use the Service to place, automate or route a wager on any venue, or to trade on a prediction market where doing so is unlawful for you. The Service cannot do this for you, and building something that makes it do so is a breach.
Do not use it where doing so breaks the law that applies to you.

3Extraction, redistribution and derived products

The compiled datasets and computed Outputs are the substance of what we sell. You may use them; you may not turn them into a competing product.

Allowed	Not allowed
Reading and analysing Outputs for your own trading or research.	Systematic scraping or crawling of the terminal, or automating a browser to extract data outside the API.
Calling the API within your plan's rate limits, and caching responses as long as your application reasonably needs.	Bulk-extracting a substantial part of the datasets, whether in one pass or by repeated small requests.
Showing Outputs inside your own application to your own users, attributed to Vultax.	Reselling, sublicensing or republishing Outputs as a data feed, dataset or signal product.
Quoting a figure in research, journalism or a report, with attribution and a link.	Using Outputs as training data, features or labels for a machine-learning model without our written consent.
Screenshotting a surface for a post or a deck, with attribution.	Presenting our analysis as your own, or stripping attribution from it.
Using the paper desk to practise, and sharing your simulated results as what they are.	Presenting paper-desk results as real trading performance, or republishing participant rankings as a copy-trading or signal product.

We assert the sui generis database right in our compiled datasets under Directive 96/9/EC. If you want to do something in the right-hand column, ask at [email protected] — we license data, and asking is cheaper for both of us than being blocked.

4Technical conduct

Do not circumvent authentication, entitlement checks, rate limits, paywalls or any other technical restriction.
Do not share, resell or publish credentials or API keys, and do not use one subscription to serve multiple end users unless your plan says you may.
Do not run load, stress or penetration tests against our infrastructure without written permission. The security policy says how to get it, and how to report a vulnerability you find without testing.
Do not deliberately degrade the Service for others, whether by volume, by malformed requests, or by exploiting a bug you have found.
Do not reverse-engineer, decompile or disassemble the Service, except to the extent Article 6 of Directive 2009/24/EC gives you a right that cannot be excluded by contract.
Do not upload malware, or use the Service as a vector to reach a third party's systems.

Rate limits are published per plan. Hitting one is not a breach — it is the limit doing its job. Engineering around one is a breach.

5Vi AI

Do not use Vi AI to generate unlawful content, or content that harasses or defames a person or company.
Do not attempt to extract system prompts, model weights or other users' conversations.
Do not use it as a general-purpose model proxy for work unrelated to market analysis. It is metered per plan because the compute is not free.
Do not enter credentials, private keys, seed phrases, or other people's personal data. Prompts leave our infrastructure for our model provider — see the sub-processors page.

6How we enforce this

We match the response to what actually happened. Most breaches are accidental, and most are fixed with an email.

Step	When we use it
Rate limit or throttle	Automated, for excess volume. Nothing is held against you.
Email asking you to stop	First-time or apparently accidental breaches. The default.
Suspension of the API key or account	Breach continues after notice, or the breach is serious enough that letting it continue causes harm.
Immediate termination without notice	Unlawful use under § 2, a security attack, or systematic extraction under § 3. No refund, per § 15 of the Terms.
Referral to an authority	Where we are legally required to report, or where the conduct is a serious crime.

If we act against your account and you think we got it wrong, reply to the notice or write to [email protected]. A person who was not involved in the original decision reviews it, and we answer within 14 days. If we were wrong, we restore access and extend your subscription by the time you lost.

7Reporting abuse

Tell us at [email protected] if you see the Service being abused, and at [email protected] if you believe content on it infringes your rights. Include what you saw and where, and we will come back to you within 14 days.