DataGen Pro Privacy Policy

This page explains the data we collect, why we use it, our retention timelines, security safeguards, and how to exercise your rights. Generated dummy data is discarded after we return the response. During beta we may log minimal extra signals to prevent abuse.

1. Information we collect

Information collected automatically

Server access logs (IP address, user agent, request count, timestamp)
Authentication metadata for API key usage (key ID, call count, status code)
Minimal telemetry required for rate limiting and abuse detection

Information you provide

Profile details shared via contact forms (name, email, company—optional)
Content submitted through public channels such as GitHub Issues

Generated dummy datasets are not persisted. We delete them immediately after the response is sent.

2. How we use the information

Understand usage patterns and improve the service
Prevent abuse (rate limiting and blocking suspicious activity)
Respond to support and inquiry requests
Investigate critical outages or security incidents

3. Sharing with third parties

We do not share personal data with third parties unless required by law. When using external services we anonymize data or put contractual safeguards in place and transmit only what is necessary.

4. Retention

Access logs: Deleted or anonymized within 90 days wherever possible.
API usage metadata: Retained only for the period needed to enforce rate limits.
Support inquiries: Removed about one year after the request is resolved.

5. Your rights

Contact us if you need to access, correct, or delete information about you. We will also help revoke API keys or remove logs whenever feasible.

6. Safeguards

HTTPS encryption for data in transit
Hashed storage and access control for API keys
Automated monitoring and blocking of abnormal traffic

7. Beta-specific notes

Features and data collection points may change quickly while we are in beta.
We may collect extra request metadata (such as frequency or user agent) during beta to prevent misuse.

8. Updates

If we change this policy we will note the revision date and publish a summary. Significant updates will be announced through reasonable channels.

9. Contact

Reach out via GitHub Issues or the documented support channel for privacy questions. We recommend consulting your legal/privacy team before production rollout.