VynFi is in early access — some features may be unavailable.

Acceptable Use Policy

Effective date: February 20, 2026

This Acceptable Use Policy (“AUP”) forms part of the Terms of Service and governs acceptable use of the VynFi platform, API, and all related services. By accessing or using VynFi, you agree to comply with this AUP. VynFi reserves the right to update this policy at any time with notice provided through the dashboard or email.

1. Introduction

This Acceptable Use Policy governs use of VynFi's synthetic financial data generation platform and API. VynFi provides a commercial Data-as-a-Service (DaaS) platform that generates realistic but entirely synthetic financial datasets for development, testing, research, and compliance purposes. This AUP is designed to ensure that all users interact with the platform responsibly and in accordance with applicable laws and regulations.

All users, including those on the Free tier, are bound by this AUP. Violations may result in enforcement actions as described in Section 7 below.

2. Permitted Use

VynFi is designed for the following lawful and intended use cases:

  • Software development and testing — Use synthetic financial data to build, test, and validate applications without exposing real customer or market data.
  • Machine learning model training and evaluation — Train, validate, and benchmark ML models with statistically representative synthetic datasets.
  • Academic research and education — Use generated data for coursework, research papers, and educational demonstrations.
  • Quality assurance and demo environments — Populate staging, QA, and demo systems with realistic data for testing and presentation purposes.
  • Compliance testing and audit preparation — Simulate financial scenarios for compliance workflows, audit readiness testing, and regulatory sandbox environments.

3. Prohibited Activities

The following activities are strictly prohibited when using the VynFi platform:

  • Misrepresentation of synthetic data — Representing synthetic data as real financial data to regulators, auditors, or third parties.
  • Use in real financial transactions — Using generated data for actual financial transactions or regulatory filings.
  • Reverse engineering — Attempting to reverse-engineer the generation algorithms or extract proprietary models.
  • Circumventing platform controls — Circumventing rate limits, credit systems, or API authentication mechanisms.
  • Credential sharing — Sharing API keys or allowing unauthorized access to your account.
  • Automated scraping or bulk extraction — Automated scraping or bulk extraction beyond API rate limits.
  • Illegal activities — Using the service for illegal activities or fraud of any kind.
  • Unauthorized resale — Reselling raw generated data without transformation or value-add.

4. Data Handling Requirements

All users must adhere to the following data handling practices when working with synthetic data generated by VynFi:

  1. Labeling — Clearly label all synthetic data as “SYNTHETIC — NOT FOR PRODUCTION USE” or an equivalent designation that unambiguously identifies the data as artificially generated.
  2. Separation — Do not commingle synthetic data with real financial data in production systems. Maintain clear boundaries between synthetic and production datasets.
  3. Access controls — Implement appropriate access controls on generated datasets, consistent with how you would treat sensitive financial data.
  4. Retention — Follow the data retention policies associated with your service tier. Generated datasets are subject to the retention limits outlined in your subscription plan.

5. API Usage Guidelines

When interacting with the VynFi API at https://api.vynfi.com/v1/, you must observe the following guidelines:

5.1 Rate Limits

Respect the rate limits for your tier. Exceeding these limits will result in 429 Too Many Requests responses.

TierRate Limit
Free10 requests/min
Developer60 requests/min
Team200 requests/min
Scale500 requests/min

5.2 Authentication

Use appropriate authentication with API keys bearing the vf_live_ prefix for production environments or vf_test_ prefix for development and testing. Never expose API keys in client-side code, public repositories, or logs.

5.3 Responsible Disclosure

Report security vulnerabilities through responsible disclosure to security@vynfi.com. Do not publicly disclose vulnerabilities before VynFi has had a reasonable opportunity to address them.

5.4 Data Isolation

Do not attempt to access other users' data, jobs, or account resources. Each account's data is logically isolated, and any attempt to circumvent this isolation constitutes a violation of this AUP.

6. Credit System

VynFi operates on a credit-based usage model. The following rules apply:

  1. Consumption — Credits are consumed per API call based on data volume and complexity. The credit cost for each operation is documented in the Terms of Service and the API documentation.
  2. Expiration — Unused credits expire according to the terms of your service tier. Expired credits cannot be recovered or refunded.
  3. Abuse prohibition — Credit abuse is strictly prohibited, including but not limited to: creating throwaway accounts to exploit the Free tier allocation, using automated systems to register multiple accounts, or exploiting pricing errors or system glitches to obtain credits fraudulently.

7. Enforcement

VynFi enforces this AUP through a graduated response model:

SeverityActionExample
First minor violationWritten warning via email with remediation guidanceExceeding rate limits, missing data labels
Repeated violationsTemporary suspension of API access and accountContinued rate limit abuse, credential sharing
Serious violationPermanent termination of account and servicesFraud, misrepresentation to regulators, illegal activity

No refunds for enforcement actions — Credits, prepaid balances, or subscription fees associated with accounts subject to suspension or termination due to AUP violations are non-refundable. VynFi reserves the right to escalate directly to suspension or termination in cases of serious violations without prior warning.

8. Reporting Violations

If you become aware of any violation of this Acceptable Use Policy, please report it immediately to abuse@vynfi.com. Reports should include:

  • A description of the suspected violation
  • Any relevant evidence (screenshots, API request IDs, timestamps)
  • The identity of the violating party, if known

VynFi will investigate all reports promptly and take appropriate action. Reports may be submitted anonymously. VynFi will not retaliate against any user who reports a suspected violation in good faith.

AUP Contact

For questions about this Acceptable Use Policy, contact: abuse@vynfi.com