RiskWise Fair Use Policy
1. Purpose
This Fair Use Policy ("Policy") is designed to ensure that all users of the RiskWise website and/or software ("Service") enjoy reliable, secure, and high-quality access. It outlines acceptable usage of the Service, usage limits on the Service, and practices to prevent abuse or excessive resource consumption that may impact other users. This Policy is in addition to, and supplements, other policies and guidelines of RiskWise as in force from time to time, including the Acceptable Use Policy.
You must comply with the standards set out in this Policy in spirit as well as to the letter.
S2 Software Ltd will determine, in its sole and absolute discretion, whether your use of the Service breaches these acceptable use standards.
2. Scope
This Policy applies to all users of the Service, and covers all features, APIs, integrations, and data usage.
3. Acceptable Use
Users must use the Service in a manner that is consistent with its intended purpose. Acceptable use includes:
- Accessing and using the Service to access and record relevant data.
- Integrating with approved third-party systems via established system integrations and documented APIs.
- Storing and processing data within the Usage Limits, set out below.
4. Unacceptable Use
The following activities are considered violations of this Policy:
- Use that exceeds the Usage Limits, set out below.
- Automated or scripted access that exceeds normal usage patterns.
- Use that causes degradation to the Service and/or performance.
- Placing disproportionate demand on shared infrastructure within the Service.
- Hosting or distributing malware, spam, or illegal content, or content which is in breach of any our terms, policies or guidelines.
- Attempting to bypass security controls or access unauthorised data.
- Automated scraping, stress-testing or bulk extraction of data without prior written consent.
- Manipulating data with the intent to affect change on licensing costs.
- Use that is otherwise inconsistent with the normal commercial use of the Service.
5. Usage Limits
To maintain service quality, the following limits apply:
- API Requests: specific limits apply to each API, however, for indicative purposes only, our standard limit is 1,000 requests per 24 hours. Any requirements that differ to the standard volume should be discussed and agreed at the time of requesting the API key and are subject to approval by the RiskWise team.
- File Storage: As standard, we would expect and allow an increase, to the total stored files, of 0.5 GB per property per Year, averaged across all active properties. Monitored accordingly.
- Concurrent Sessions: Users can only access the system via a single active session, either through the Web portal or mobile application.
- Max Unique Sessions: 20,000 per month per system
- Data Export: Exports will default to a specific number of records. Typically, 1000 records. Deviating from the recommended defaults may result in the request failing to complete within the allowed request timeframe.
- RiskWise Insight Credits/Tokens: specific limits apply to RiskWise Insight features, as per your licence agreement.
These limits are subject to our sole and absolute discretion, and may change based on system capacity and user feedback.
6. Monitoring and Enforcement
We monitor usage patterns to ensure compliance. If a system or user exceeds fair usage thresholds or violates this Policy:
- We may contact the user, and or the system’s key contact to discuss usage.
- We may throttle or temporarily suspend access.
- We may disable functionality or integrations temporarily, until the RiskWise team are satisfied usage will return to within the acceptable range.
- We may terminate the user’s licence with the Service if continue breach of this Policy occurs.
7. Changes to This Policy
We reserve the right to update this Policy at any time. The Client Representative for a system will be notified of significant changes via email.
8. Contact
For questions or concerns about this Policy, please contact us at riskwise@s2partnership.co.uk.
Comments
0 comments
Article is closed for comments.