Acceptable Use Policy

1. Overview

This Acceptable Use Policy ("AUP") governs your use of Veridian Data Systems LLC's synthetic data generation services, APIs, and related products (collectively, the "Services"). This AUP is incorporated into and forms part of our Terms of Service.

By using our Services, you agree to comply with this AUP. We may update this policy at any time, and continued use of the Services constitutes acceptance of any changes.

2. Quick Reference

3. API Usage Rules

3.1 Authentication and Access

• API keys are personal and non-transferable; do not share your credentials
• Store API keys securely; never expose them in client-side code or public repositories
• Rotate API keys periodically and immediately if you suspect compromise
• Use separate API keys for development, staging, and production environments
• Implement proper authentication in all API calls

3.2 Rate Limits and Quotas

API usage is subject to rate limits based on your subscription tier:

Exceeding rate limits will result in HTTP 429 responses. Implement exponential backoff in your integration. Persistent abuse may result in temporary or permanent suspension.

3.3 API Best Practices

• Implement proper error handling for all API responses
• Cache results when appropriate to reduce unnecessary API calls
• Use webhooks instead of polling for long-running generation jobs
• Include meaningful User-Agent headers for debugging purposes
• Log API usage for your own monitoring and troubleshooting
• Test integrations thoroughly in staging before production deployment

4. Synthetic Data Handling

4.1 Data Classification

All synthetic data generated by Veridian must be clearly identified and handled appropriately:

• Labeling: Always label synthetic datasets as "SYNTHETIC" or "TEST DATA" in filenames, metadata, and documentation
• Segregation: Store synthetic data separately from production/real data to prevent accidental mixing
• Access Control: Implement appropriate access controls consistent with your data governance policies
• Retention: Define and follow retention policies for synthetic datasets

4.2 Permitted Data Uses

Synthetic data from Veridian may be used for:

• Development and Testing: Software development, QA testing, integration testing, and performance benchmarking
• Machine Learning: Training ML models, validating algorithms, and testing AI systems
• Regulatory Preparation: Testing compliance systems, preparing for examinations, and training staff on regulatory scenarios
• Analytics Development: Building dashboards, reports, and analytical tools
• Demonstrations: Product demos, sales presentations, and educational materials
• Research: Academic research, industry studies, and internal analysis

4.3 Prohibited Data Uses

4.4 Data Quality Disclaimer

While Veridian strives to generate statistically accurate synthetic data, users must understand:

• Synthetic data is generated using statistical models and may not capture all real-world edge cases
• Users are responsible for validating that synthetic data meets their specific requirements
• Synthetic data should not be used as the sole basis for critical business decisions
• Quality metrics provided are estimates and should be independently verified for high-stakes applications

5. Security Requirements

5.1 Infrastructure Security

• Use HTTPS/TLS for all API communications
• Implement network security controls appropriate to your environment
• Keep all systems and dependencies updated with security patches
• Use secure coding practices when integrating with our APIs

5.2 Incident Reporting

You must promptly notify Veridian if you discover:

• Unauthorized access to your API credentials
• Security vulnerabilities in our Services
• Suspected misuse of synthetic data
• Any breach that may affect Veridian or other customers

Report security incidents to [email protected] with "SECURITY" in the subject line.

6. Compliance Obligations

6.1 Regulatory Compliance

Users are responsible for ensuring their use of synthetic data complies with all applicable laws and regulations, including but not limited to:

• State insurance regulations and NAIC guidelines
• Data protection laws (GDPR, CCPA, etc.)
• Industry-specific compliance requirements
• Internal corporate policies and governance frameworks

6.2 Audit and Monitoring

Veridian reserves the right to:

• Monitor API usage for compliance with this AUP
• Investigate suspected violations
• Request documentation of your data handling practices
• Audit usage patterns to ensure compliance

7. Enforcement

7.1 Violation Consequences

Violations of this AUP may result in:

• Warning: Written notice for minor or first-time violations
• Temporary Suspension: Suspension of API access pending investigation
• Permanent Termination: Termination of services for serious or repeated violations
• Legal Action: Civil or criminal proceedings for fraudulent or illegal use

7.2 Reporting Violations

If you become aware of any violation of this AUP, please report it to [email protected].

8. Contact Information

For questions about this Acceptable Use Policy, please contact us: