Acceptable use
Preview draftA working outline for safe, authorized use of FVI services. The final rules must align with executed customer terms, deployment and API documentation.
Owner and legal verification required before publication
This draft leaves material facts and commitments unresolved. It is not an operative notice, policy or agreement, and it does not claim regulatory or accessibility compliance.
- Approve permitted purposes and prohibited-use language with product and counsel.
- Publish endpoint-specific API limits only after the owner verifies them.
- Set the contractual position on resale, reverse engineering and account sharing.
Permitted use
Use FVI only for reconciliation and related workflows that your organization is authorized to run, within the service scope and instructions agreed in writing. Keep data inputs, connected accounts and user access within your organization's authority and applicable law.
This preview does not grant a licence or expand a customer's signed permissions. The final agreement and approved deployment documents control the permitted users, environments and use cases.
Proposed prohibited-use rules
- Do not access, inspect, change or attempt to identify another customer’s data or account.
- Do not bypass authentication, authorization, audit, tenant-separation or usage controls.
- Do not upload data you are not authorized to process, or use the service to violate law or another party's rights.
- Do not submit malware, malicious payloads or instructions intended to disrupt or compromise a service or user.
- Do not interfere with availability, probe third-party systems, or use the service to conceal unauthorized activity.
API limits, resale and account controls
| Topic | Current public position | Required owner decision |
|---|---|---|
| API rate limits | No public numeric rate limit is stated by this preview. | Verify per-endpoint limits, burst behavior, error response and plan differences before publishing. |
| Reselling or service bureau use | This page does not grant resale, sublicensing or service-bureau rights. | Set the permitted commercial model in the MSA/order form. |
| Reverse engineering | No additional restriction is created by this preview. | Counsel must define enforceable limits subject to applicable law and security/research exceptions. |
| Account sharing | Use organization-provisioned user accounts and approved authentication methods. | Confirm any shared/service account exception and contractual accountability rule. |
Enforcement and reporting
Suspension, investigation, notice, appeal and termination rights must be set by the executed service terms. This page does not create a unilateral suspension power or a response deadline.
For security concerns, use the Security disclosure page. For an account or product question, use the Contact route.