1 Status and purpose
1.1 This Fair-Use Policy (OVR-POL-006) is an ORamaVR Standard-Form Document, published at oramavr.com/legal/fair-use. It sets out the current fair-usage limits referenced by, and read together with, the ORamaVR Acceptable Use Policy (OVR-POL-004) §6. Capitalised terms not defined here have the meanings given in the Acceptable Use Policy and the ORamaVR Master Glossary (OVR-GLO-001).
1.2 These limits exist to protect platform stability and fair access for all Users. They are not entitlement caps: contractual entitlement (for example, licensed CCU count) is set in the applicable Order Form, Schedule, or Principal Agreement and prevails over this Policy where the two address the same quantity.
1.3 ORamaVR may update these limits from time to time, by publishing a revised version at the URL above. A change that materially reduces a limit takes effect on not less than thirty (30) days’ notice; any other change takes effect on not less than ten (10) days’ notice, in each case in accordance with the Standard-Form Document Amendments mechanism in the applicable Principal Agreement.
2 VTC Platform
| Dimension | Current limit |
|---|---|
| Concurrent Users (CCU) | As set out in the applicable Order Form or Schedule. Overage is handled by add-on concurrent-pack purchase or an increase in the contracted entitlement, not by this Policy. |
| Registered Authorised Users | Unlimited per Client Tenant. Only concurrent active sessions (CCU) are constrained, in line with the licensed CCU count. |
| Storage per Client Tenant | No per-tier cap. VTC operates on a CCU floating-licence model; simulations are hosted and sized by ORamaVR. Customer-generated data (analytics, session records, learner rosters, IFU PDFs ingested into JARIA) is governed by the general anti-abuse threshold in §6 and by ORamaVR infrastructure capacity. |
| API rate limits | Not applicable. The platform API is not publicly exposed in the Creator or VTC tiers. Where API access is later made available under a Developer or OEM tier, rate limits will be published at that time. |
3 SIM Library
| Dimension | Current limit |
|---|---|
| Subscribed titles | No volume cap on the number of SIM Library titles an organisation may subscribe to. Licensing is per SIM, per organisation, per year, as published in Schedule LIB (OVR-SCH-007). |
| Concurrent sessions per SIM | Aligned to the End Customer’s licensed CCU count. No additional per-SIM session limit is imposed beyond the CCU entitlement; the CCU ceiling applies on an aggregated basis across all SIMs in use. |
4 Creator Pro
| Dimension | Current limit |
|---|---|
| Authorised Users per seat | One (1) named Authorised User per seat; non-transferable except as permitted under the Creator Pro EULA (OVR-CRE-001) §6. |
| OMEN text prompts | Unlimited per seat per month. |
| OMEN image generation | 30 generated images per seat per month (hard cap; throttle on overage; no automatic charge). This is the contractually-bound figure and prevails over any higher figure in product collateral. |
| Medical 3D Asset Library downloads | Unlimited per Creator Pro seat per month. |
| Derivative Work compiles / builds | Unlimited per Creator Pro seat per month. |
5 General anti-abuse threshold
5.1 ORamaVR reserves the right to investigate and remediate usage patterns that are materially inconsistent with the size, stated purpose, or permitted use of a User’s subscription — including automated scraping, credential sharing beyond the licensed seat or CCU count, denial-of-service-like load, and circumvention of the CCU model — in accordance with the tiered enforcement mechanism in Acceptable Use Policy §8.
5.2 Nothing in this Policy limits ORamaVR’s rights or a User’s obligations under the Acceptable Use Policy, the applicable Principal Agreement, or applicable law.