Fair Use Policy
1. Purpose and scope
This Fair Use Policy (Policy) sets out requirements for acceptable use of Savira's services, including the Consent API, associated integrations and related platform functionality (Services). It is intended to protect the security, availability, performance and integrity of the Services while supporting legitimate customer activity.
This Policy applies to customers and to persons and integrations using the Services on their behalf, including authorised users, developers, employees and contractors. Customers must take reasonable steps to ensure those within their control comply with this Policy.
This Policy forms part of Savira's Terms of Service only where incorporated into the applicable agreement. If there is any inconsistency, the order of precedence in that agreement applies.
2. Permitted use
Customers may use the Services for legitimate business purposes in accordance with their subscription, agreed usage allowances, applicable documentation and Terms of Service. This includes displaying consent banners and published policies; recording visitor choices, changes and withdrawals; connecting authorised websites and plugins; and retrieving published configurations and tracking-script classifications.
High website traffic, increased customer activity and frequent genuine consent submissions do not, by themselves, breach this Policy.
3. Prohibited activities
Customers must not knowingly or recklessly use the Services, or permit their authorised users or integrations to:
- Access or attempt to access another customer's account, data or resources without authorisation.
- Circumvent authentication, access controls, technical restrictions or rate limits.
- Introduce malicious code, interfere with operations or conduct denial-of-service attacks.
- Conduct vulnerability scanning, penetration testing or other security testing against Savira production systems without prior written authorisation. This does not prevent testing expressly authorised by Savira.
- Generate artificial traffic, fraudulent consent submissions or misleading usage records.
- Deliberately falsify, manipulate or corrupt consent records, audit information or compliance evidence.
- Operate automated processes that unnecessarily overload the Services or materially impair their availability to others.
- Use the Services in breach of applicable law or the rights of others.
These restrictions do not prohibit legitimate testing in an authorised environment or normal compliant integration activity. Customers are not automatically responsible for fraudulent requests made independently by unrelated third parties, without their authorisation or knowing or reckless involvement. This does not remove their obligation to take reasonable steps to secure systems and credentials within their control.
4. API credentials and integrations
The Consent API uses public script tokens and confidential API keys. Public script tokens are intended for browser-side use. API keys must be used only in secure server-side integrations and transmitted in the Authorization header.
Customers must take reasonable steps to protect API keys against unauthorised access, use or disclosure. They must not expose keys in browser-side code, URLs, source code repositories or to unauthorised parties.
Customers are responsible for managing access within their systems and by their authorised users and integrations, subject to the governing agreement and applicable law. If a key is known or reasonably suspected to be compromised, customers must promptly rotate it and notify Savira where the incident may affect the security or integrity of the Services.
Savira remains responsible for its own obligations under applicable law and the governing agreement.
5. Consent records and data integrity
Customers must use the Consent API to record genuine visitor choices or other appropriately authorised consent-related events. They must not deliberately fabricate preferences, impersonate visitors or generate misleading consent evidence.
Consent records are maintained as historical events. Subsequent changes, including withdrawals, are recorded as new events rather than edits to previous submissions.
Customers must not put names, email addresses, customer IDs, health information or other sensitive personal information into consent tokens or metadata. Other personal information must not be included in fields not designed to receive it unless Savira expressly authorises the particular use under agreed safeguards.
Customers are responsible for configuring and implementing the Services within their own websites, applications and systems in accordance with applicable legal requirements and Savira's published documentation. Customers and their authorised integrations must take reasonable steps to ensure submitted information, including integration identifiers and source information, is accurate and not deliberately misleading. Savira remains responsible for the functionality, security and guidance it provides in accordance with the governing agreement and applicable law.
Savira will handle personal information and related requests in accordance with its Privacy Policy, applicable law and contractual obligations.
6. Rate limits and reasonable usage
Savira applies reasonable technical rate limits to protect security, performance and availability. Limits may vary by endpoint, usage patterns, technical requirements and service arrangements.
Requests exceeding a limit may be temporarily restricted or receive an HTTP 429 response. Integrations should follow any Retry-After header and use appropriate caching, retry and backoff practices.
Customers must not deliberately evade technical limits by artificially distributing automated requests across IP addresses, accounts or systems. This restriction does not apply to ordinary requests made by different visitors' browsers through an authorised website or hosted banner script.
Savira may adjust, increase or disable technical rate limits for particular customers or integrations, including to support legitimate high-volume usage. Where reasonably necessary for reliability, security or performance, Savira may also change applicable limits. Where practicable, it will give advance notice of material changes that may adversely affect legitimate customer integrations. Technical rate limiting does not, by itself, establish a breach of this Policy. Removal of a rate limit does not alter any separately agreed service levels or other contractual commitments.
7. Usage charges and unusual activity
Usage allowances, subscription fees, plan changes and additional charges are governed by the customer's agreed subscription, Service Order and Terms of Service. Increased capacity or the adjustment or removal of throttling may be subject to additional charges, but only where those charges and their basis have been disclosed and agreed under the applicable contract before they apply. This Policy does not independently authorise undisclosed fees, penalties or charges.
Where Savira identifies usage that may be fraudulent or abusive and may affect billing or plan allocation, Savira will, where reasonably practicable, investigate before treating that activity as chargeable usage or using it to trigger a plan change. Savira may ask the customer to assist and may apply immediate proportionate technical protections where necessary.
Where Savira confirms that usage resulted from unauthorised third-party abuse, rather than the customer's own activity or implementation, Savira will exclude that usage from chargeable usage calculations and any resulting subscription or plan adjustments. Where charges have already been applied, Savira will make an appropriate billing adjustment.
8. Monitoring and enforcement
Savira may monitor service usage to the extent reasonably necessary and permitted by law and the governing agreement to identify threats, investigate misuse, enforce technical limits and maintain availability.
Where Savira reasonably believes this Policy has been breached, it may take proportionate action, including notifying the customer and requesting corrective action, applying technical limits, temporarily restricting affected credentials or integrations to address immediate risk, or suspending or terminating access where permitted by the Terms of Service.
Savira will follow applicable notice and remediation requirements, except where immediate action is reasonably necessary and contractually permitted. Where practicable, restrictions will be confined to affected credentials, integrations or functionality.
9. Changes to this Policy
Savira may update this Policy to reflect changes in technology, security, law or operations. Material changes affecting customers' rights or obligations will be notified and take effect in accordance with the governing agreement. Changes will not retrospectively impose additional charges or remove accrued contractual rights.
10. Contact
Questions about this Policy, suspected credential compromise or legitimate high-volume usage should be directed to the Savira support team:
- Email: hello@savira.com
- Website: savira.com
- Post: PO Box 2045, Hornsby Westfield NSW 1635
- ABN: 53 273 071 022