Privacy

Privacy notice

This notice explains what account and operational data we collect, why we collect it, and how to contact us about retention, access, or deletion. The service is designed around public-data workflows, but account and usage metadata still deserves clear handling.

Service data

Account, billing, and API usage metadata

Primary uses

Security, support, quota enforcement, and product operations

Contact

kaneliu10@gmail.com

What we collect

We collect the minimum account, billing, API usage, and operational log data needed to provide the service and keep it stable.

  • Account profile details such as workspace name and login email
  • Billing events, plan changes, and payment provider references
  • API usage metadata such as product, request timing, quota consumption, and technical status

Why we collect it

We use this information to operate the service, support the service, prevent abuse, and improve product reliability.

  • Authenticate users and keep account sessions secure
  • Enforce plan limits, detect fraud, and investigate incidents
  • Understand which products and endpoints need operational improvement

How request content is handled

Query strings and request payload fragments may be retained for debugging, quota enforcement, and product improvement, especially when an endpoint fails or returns unexpected data.

  • We do not sell personal data derived from your account activity
  • Retention windows are limited to what operations and support workflows require
  • Access is restricted to team members or processors with a legitimate operational need

Your controls

You can contact us for privacy requests, retention questions, or account-level access and deletion requests.

  • Ask what account information we currently store
  • Request deletion of an account that is no longer needed
  • Raise questions about specific exports, logs, or support interactions

Privacy requests

For privacy requests or questions about data retention, contact kaneliu10@gmail.com. Include the email address tied to your account and enough context for us to identify the request quickly.